How to check an assignment against its requirements
Work through the brief, not your draft. Pull every requirement out of the prose into its own line, mark each one as either a rule with a right answer or a judgement someone has to make, then point at the place in your draft where each is satisfied. Anything you cannot point at is not done — and the rules can be checked mechanically, which means most of the list can be finished quickly and the rest given the attention it needs.
Why briefs are hard to check
An assignment brief is written as prose, and prose hides obligations. A single sentence can carry a word limit, an exclusion from that limit, a source count, a recency rule and a referencing style — five things that fail independently. Read as a paragraph it feels like one instruction. Read as five rows it is a list you can finish.
The second difficulty is that the requirements are not all the same kind of thing. Some have a definite answer that does not depend on who is marking. Others are about what your writing does, and no amount of counting settles them. Checking is much easier once those two groups are separated, because you stop applying the wrong kind of attention to each.
One sentence, seven requirements
Take a brief that says: “2,000 words excluding the reference list, drawing on at least six peer-reviewed sources published in the last ten years, Harvard referencing throughout. Critically evaluate rather than describe, and engage with the module’s core reading.” Pulled apart, that is:
| Requirement | Kind | Settled by |
|---|---|---|
| 2,000 words | Formatting | Rule |
| Excluding the reference list | Formatting | Rule |
| At least six peer-reviewed sources | Sources | Rule |
| Published in the last ten years | Sources | Rule |
| Harvard referencing throughout | Formatting | Rule |
| Critically evaluate, do not describe | Content | Judgement |
| Draw on the module's core reading | Sources | Judgement |
Five rules and two judgements. The five can be verified without an opinion; the two are where your reading and your argument are actually being assessed. Notice that the two judgement rows are the ones a read-through tends to skip, because they have no obvious stopping point.
The method, step by step
1. Read the brief once without your draft open
Reading them side by side makes you check what you happened to write rather than what was asked. Read the brief, the rubric and any announcement or forum post that changed it — a later clarification usually overrides the original document, and it is the one people miss.
2. Pull every requirement into its own row
One sentence often carries several. "2,000 words excluding references, using at least six peer-reviewed sources from the last ten years" is four separate obligations that fail in four different ways. Write each as its own line, in the brief's words, not your summary of them.
3. Split content requirements from formatting requirements
Formatting requirements have a right answer: a word limit, a citation style, a section that must exist. Content requirements are about what your argument does — evaluate, compare, apply a framework to a case. Mixing them is why a draft can satisfy every visible rule and still miss the point of the assessment.
4. Settle exactly what the word count includes
This varies by institution, by module and sometimes by assignment, and there is no convention safe enough to assume. Find where the brief states it. If it says nothing about in-text citations, tables, headings, footnotes or appendices, ask — and until you have an answer, know both totals so you are not guessing at 2am.
5. List the sections that must be present
Abstract, introduction, methodology, conclusion, appendices, reflective statement, declaration. A missing required section is one of the cheapest marks to lose and one of the easiest things to verify, because it is a yes or no rather than a matter of quality.
6. Write down the source rules as numbers
How many sources, of what kind, how recent, and whether particular ones are required or forbidden. "Academic sources" and "peer-reviewed journal articles" are not the same instruction, and a brief that names one usually means it.
7. Check the submission mechanics
File format, file name, cover sheet, anonymous marking, word count declaration, submission portal and deadline time zone. None of it improves your argument and all of it can cost you the submission.
8. Map each row to a place in your draft
Go requirement by requirement and write down where it is satisfied — a page, a section, a paragraph. A requirement you cannot point at is not met, however strongly you feel it is covered. This is also the step that finds requirements you answered twice and ones you answered nowhere.
9. Mark the rows that need a human
"Critically evaluate" cannot be settled by counting anything. Flag those rows and give them a separate read, ideally away from the screen you wrote them on. The mechanical rows are done; these are the ones that decide the grade.
Where this usually goes wrong
- Assuming what the word count excludes
- Different institutions and modules count in-text citations, tables, headings and appendices differently. Guessing puts you over or leaves you a thousand words short of the depth expected.
- Checking the rubric instead of the brief
- The rubric says how marks are distributed. The brief says what you must produce. They usually agree, and when they do not, the requirements you can fail on are in the brief.
- Treating the source count as a target
- Six sources cited once each in an introduction is not the same as six sources doing work in the argument. The number is a floor for effort, not evidence of it.
- Verifying format and stopping
- Formatting is satisfying to check because it finishes. It is also where the fewest marks live. A perfectly formatted description of a topic that was supposed to be evaluated still misses the assessment.
- Leaving the check until after the final read-through
- By then you have read your own sentences so many times that you see the argument you meant rather than the one on the page. Do the requirement mapping cold, before the last polish.
Three different kinds of checking
It helps to know which kind of check you are doing, because they need different tools and give different kinds of certainty.
Rule checking
Counting and matching against a stated rule: the word total, whether a required section exists, whether every in-text citation has an entry in the reference list, how many sources there are and how old they are. Both your brief and your document are in front of you, so these have definite answers and nothing needs to be looked up.
Interpretation
Deciding whether a source is the kind the brief asked for, or whether a section does the job its heading claims. This needs information from outside your files — what a journal is, what a publisher is — and it involves judgement about fit rather than a count.
Evidence checking
Deciding whether the source you cited actually supports the sentence citing it. This needs the source’s own text, and it is the slowest check by a wide margin. It is also the one most likely to be skipped, and worth understanding properly.
What StudyRef does with this
The Assignment Checker reads your brief and your document together and does the rule checking for you: the word count under the exclusions your brief actually states, required sections, referencing style consistency, source counts and recency, and every in-text citation matched against your reference list. That layer runs free, including without an account, because it works entirely from the two files you provide.
The layers that need to look outside your files — resolving each source against publisher and registry records, judging whether a source suits the claim, and reading a source’s text to see whether it supports your sentence — are part of a Full Assignment Scan or a Pro plan, because each one costs real work per run.
What it does not do is the judgement column. Nothing here can tell you whether you have evaluated rather than described, whether your argument is any good, or what your marker cares about most. Those are yours, and the point of finishing the mechanical rows quickly is having time left for them.
Check a draft against your brief
Upload the assignment and the brief. The rule checks come back with the requirement each one refers to.
Check my assignment against the briefRelated guides
- A final checklist for the hour before you submit — once the requirements are mapped, this is the sweep that catches what moved since.
- Matching in-text citations to your reference list — the rule check that most often turns up something.
- Count an assignment with the reference list excluded — free, and it reads the real .docx rather than pasted text.