Faster Grading and Feedback Template
Three documents and three sheets that mine your own marking for the comments you keep retyping, then price what banking them saves.
Free download · No account needed
Marking a script is four activities of very different sizes, and a generic phrase bank saves nothing because it does not match where the time goes. On the worked cohort in this pack, a fictional writing course with 138 scripts, the per-script breakdown came out at 4.2 minutes reading, 6.1 minutes writing comments, 1.4 minutes scoring against the rubric and 0.9 minutes admin. That is 12.6 minutes a script and 29.0 hours for the cohort.
Comment writing is 48.4 per cent of it, and it is the only block with slack, because most of the comments are repeats. Extract every comment from a marked cohort and cluster them by the error they name and the shape is stark: 1,742 comments across 138 scripts collapse into 47 distinct types, and twenty of those types cover 1,166 comments. The single most common comment appeared on 118 of the 138 scripts, composed from scratch every time.
So the bank is those twenty, each written once with the criterion, the error, the fix and a next step. Four hours to build, 4.86 hours saved per round, taking the cohort from 29.0 hours to 24.1. That is a 16.8 per cent reduction rather than a transformation, and the honest number is the point: a feedback bank does not halve marking, it removes the retyping. The bigger win is the second artifact the same clustering produces.
What is in the pack
Feedback Bank
Twenty entries, clustered out of a real cohort's comments rather than written from imagination. Each carries the rubric criterion, the error described in what the script does rather than what it lacks, a fix specific enough to act on, and the next step for the next piece of work. The 27-type tail is deliberately left unbanked, because a comment used twice does not repay being written well.
Common Error Register
The same clustering with a different job. Any error appearing on more than half the cohort's scripts is a teaching gap rather than a marking issue, and the register names the class session that gains the content. One high-frequency error deliberately does not go to teaching: a citation present in the text and missing from the reference list is a checking failure, and it goes to a submission checklist.
Marking Time Tracker
Reading, comment writing, rubric scoring and admin measured separately, because only one of the four has slack in it. Both seconds-per-comment assumptions are written into the sheet, so the 4.86 hour saving and the 4.0 hour build cost are arguable numbers rather than a promise.
How the Feedback Bank Is Built
The mechanism doc and the arithmetic. Why the bank is built backwards, why it is the top twenty types rather than the top five or all 47, and why the eleven seconds a banked comment costs is eleven rather than two. Personalisation is counted into the model, so a bank used without it is worth less than nothing.
Marking Procedure
The order the work happens in. Three scripts marked against the rubric before anything is recorded, marking in one pass rather than two, every comment named to a criterion, and a hard cap of three sentence-level style notes per script. Marking every instance of a recurring style error costs an hour a cohort and teaches nothing the first three did not.
Moderation Guidance
A deliberate sample rather than a random one: the first five marked, the last five, everything within two points of a boundary, and both extremes. Then four checks, including whether the comments alone predict the band. Order drift gets scripts remarked rather than adjusted by a constant, because a constant moves the correct scripts too.
How it works
- 1
Send a previous cohort's marked work
Annotated PDFs, an LMS comment export, a rubric tool's log or Word files with tracked comments, plus the rubric they were written against. Volume matters more than recency, and one full cohort is enough.
- 2
Cluster the comments by the error they name
Not by wording. Two comments are one type when the same fix answers both. The output is four numbers: total comments, distinct types, the share the top twenty cover, and the share of scripts your single most repeated comment appeared on.
- 3
Bank the top twenty and price the change
Each written once with criterion, error, fix and next step. Then the time model against your own measured minutes, quoting the reduction as a share of total marking time rather than of comment-writing time.
- 4
Route the recurring errors out of marking
Anything above half the cohort goes to a class session or a submission checklist with a named owner. The rubric pack is where a criterion that turned out to be hard to apply gets rewritten.
Frequently asked questions
Is this template free?
Yes. Download the three documents and three sheets as Word and CSV files with nothing to sign up for. Opening it as a working space, where the clustering runs against your own marked scripts and the time model recomputes, needs an account. The rest sit in the template library.
What format are the downloaded files?
Three Word documents and three CSV sheets in one zip. The sheets open in Excel, Numbers or Google Sheets and arrive carrying the worked cohort, so the clustering shape and the four-stage time model are visible before you replace them with your own numbers.
Does a feedback bank make feedback worse?
It does if a banked comment goes out unchanged, which is why that is a rule in the space rather than advice. The banked text carries the criterion, the error and the fix; the marker adds one sentence naming what this script actually did. Students compare feedback within a day.
How much time does this actually save?
On the worked cohort, 4.86 hours a round against a 4.0 hour build cost, taking 138 scripts from 29.0 hours to 24.1. That is 16.8 per cent of total marking time. Quoting the comment-writing figure instead would have looked like 34.6, which is the number to distrust.
Why does an error on half the scripts leave the bank?
Because writing it 118 times is the most expensive way to address it available. The Department for Education's marking review argued that marking should be meaningful, manageable and motivating, and a cohort-wide error fails the first test as individual feedback.
We have no record of how long marking takes. Can we still start?
Yes, but time the first twenty scripts of the next round, because every claim in this space rests on that number. Without it, the bank is still worth building from the clustering alone, and the saving is a guess rather than a measurement.
How is this different from an item analysis?
An item analysis works on objective questions and asks which items discriminate. This works on written comments and asks which you keep retyping. For exams, item analysis review is the right tool, and the question bank pack rewrites the items. Whether the marking lands consistently once more than one person applies the rubric is a separate check, in grade analysis and moderation.
Find the comment you wrote a hundred times
Send a previous cohort's marked scripts with the comments still on them. The first pass clusters every comment by the error it names and tells you what share of your marking was retyping.
Mine a real cohort