Writing rubric descriptors that markers agree on
Show contentsHide contents
When two tutors give the same essay a 58 and a 71, the rubric is usually part of the cause. Descriptors like "good critical analysis" feel precise to the person who wrote them and mean something different to everyone else. This guide shows how to rewrite descriptors so that markers can point to evidence in the script, and gives a set of before and after rewrites to work from.
Why vague descriptors cause disagreement
Most disagreement between markers is not about standards. Experienced tutors usually agree on which scripts are strong and which are weak. They disagree about the middle, and about which words in the rubric the script satisfies.
Vague descriptors cause this in three ways.
- Evaluative adjectives with no anchor. "Clear", "thorough", "sophisticated" and "appropriate" all depend on what the marker is comparing against. A new sessional tutor and a unit coordinator with ten years of scripts behind them will read "sophisticated" differently.
- Quantity words. "Some", "several", "most" and "limited" invite counting, and markers count differently. Is three references "several"?
- Levels separated only by intensity. If the difference between Credit and Distinction is "good" versus "very good", the marker has no way to decide except gut feeling.
What an observable descriptor looks like
An observable descriptor names something the marker can find in the work. It usually answers one of these:
- What does the student do? (compares, justifies, identifies, applies)
- Where does it appear? (in the introduction, in each paragraph, in the discussion)
- What is present or absent? (a counterargument, a limitation, a unit of measurement)
- How is it connected? (evidence linked to a specific claim, recommendation follows from findings)
You do not need to remove judgement. "Explains why the evidence supports the claim" still needs a marker to decide whether the explanation works. But it tells them what to look for, and that is where most agreement comes from.
Before and after rewrites
| Criterion | Vague descriptor | Observable rewrite |
|---|---|---|
| Argument (Distinction) | Presents a sophisticated argument | States a position in the introduction, develops it through each section, and responds to at least one serious objection |
| Argument (Pass) | Argument is present but underdeveloped | States a position, but sections mostly describe rather than advance it |
| Use of evidence (Credit) | Good use of relevant literature | Links each main claim to a specific source and says what the source shows |
| Use of evidence (Pass) | Some use of literature | Cites sources, but mainly to restate them rather than to support a claim |
| Critical analysis (HD) | Excellent critical thinking | Identifies an assumption or limitation in the sources and explains how it affects the conclusion |
| Structure (Credit) | Well organised | Each paragraph has one main point, and the order of sections follows the argument rather than the order of readings |
| Lab report: results (Distinction) | Results are clearly presented | Tables and figures are labelled with units, referenced in the text, and show the data needed to support the conclusions |
| Lab report: discussion (Pass) | Adequate discussion | Compares results to expected values and names at least one source of error |
| Reflection (Credit) | Shows good self-awareness | Identifies a specific action of their own, explains why it happened, and links it to a principle from the unit |
| Presentation delivery (Distinction) | Confident and engaging delivery | Speaks to the audience rather than reading, keeps to time within 30 seconds, and handles questions by addressing what was asked |
| Referencing (Pass) | Referencing is mostly correct | Every quotation and paraphrase has an in-text citation; the reference list may have formatting errors |
Notice what the rewrites do. Some replace adjectives with actions. Some specify location. Several describe what separates this level from the one below. None of them are longer than two lines.
Techniques that work
Write the difference between levels, not the level alone
Put two adjacent descriptors side by side and ask: what would I see in a Distinction script that I would not see in a Credit script? Write that difference into the higher descriptor. If you cannot name it, you may have one level too many.
Replace counts with functions
Instead of "uses at least five sources", say what the sources should do: "uses sources to support each main claim, including at least one that challenges the position". If a minimum number really matters, state it as a requirement outside the rubric so it does not distort the levels.
Describe the fail level by what is missing
"Does not meet the requirements" gives neither marker nor student anything to work with. "No clear position is stated, or the position changes between sections" does.
Keep one idea per cell where you can
A descriptor that bundles three features ("clear, well evidenced and critically engaged") forces a marker to decide what to do when a script has two out of three. If the features matter separately, they may belong in separate criteria. If they genuinely go together, say which one is essential.
Borrow the words students will see
If the assessment brief asks students to "evaluate two policy options", the rubric should talk about evaluating two policy options, not about "critical engagement with alternatives". Matching language helps students and markers read the rubric the same way.
Testing whether descriptors work
The only real test is to have more than one person use them.
- Choose four or five scripts that span the range. Past submissions (with permission and identifiers removed) or samples you write yourself both work.
- Ask two or three markers to mark them independently, recording the level per criterion and, briefly, the words in the descriptor they relied on.
- Compare. Where markers agree, move on. Where they differ by a level, ask each to point to the evidence they used.
- Rewrite the descriptor so that the evidence one marker used is named explicitly.
A useful sign that a descriptor is still too vague: when asked to justify their level, markers reach for different words from the ones in the cell. If three tutors all say "it didn't really answer the question", that phrase probably belongs in the rubric.
A short worked example
A second year history rubric had this Credit descriptor for "Use of primary sources": "Makes good use of a range of primary sources." In calibration, one tutor gave a script Credit because it quoted six primary sources; another gave it Pass because every quote was used as illustration, not analysed.
The team rewrote the ladder:
| Level | Rewritten descriptor |
|---|---|
| Pass | Quotes or refers to primary sources to illustrate points |
| Credit | Comments on what the primary sources show, beyond quoting them |
| Distinction | Considers who produced a source, for whom, and how that shapes what it says |
| High Distinction | Uses the source's origin and purpose to build or qualify the argument |
On the next calibration round, the same two tutors placed that script at Pass, and the conversation took two minutes instead of fifteen.
Keep the rubric readable
It is possible to overcorrect and write descriptors so long that nobody reads them. Aim for one or two lines per cell. If you need more, the extra detail can go in a marker guide that sits beside the rubric: worked examples, common borderline cases, and notes on what not to penalise. Students see the rubric; markers see both.
Common questions
- Are adjectives like "clear" or "thorough" ever acceptable in descriptors?
- They are fine when paired with something observable that shows what "clear" means for this task. On their own they leave each marker to supply a standard, which is where disagreement starts.
- How long should a rubric descriptor be?
- One or two lines is usually enough. Longer descriptors tend to bundle several features, which makes it harder to decide the level when a script has some but not all of them.
- What if markers still disagree after rewriting?
- Some disagreement is normal. Use moderation to resolve individual scripts, and keep a short marker guide with borderline examples so the shared interpretation carries into the next round.
Related guides
- How to write a marking rubricA practical method for building a marking rubric: choosing criteria, setting levels, writing descriptors and weighting, with a complete worked example rubric.
- Moderation and marker consistency for teaching teamsHow to keep marks consistent across a teaching team: calibration sessions, sample double marking, resolving disagreements and a simple moderation workflow.
- Analytic vs holistic rubrics: which to useWhen to mark with an analytic rubric and when a holistic one fits better, with the trade-offs in speed, consistency and feedback, and examples of each.
DeepMarking marks against your rubric and lets you review every mark. Try it free.