You marked all weekend. By Tuesday morning the pile was back.
I've done this more times than I can count. For years I treated the marking pile as a personal failing. If I were faster, more organised, better at guarding my evenings, I'd stay on top of it. I never did. Nobody I work with does either.
The pile keeps coming back because of how marking gets spread across a term, not because of how fast you move through it. Every class hands something in around the same time. Every faculty sets assessments to the same calendar. And the quiet expectation is that you'll absorb the volume in your own time.
Most workload advice misses this. It tells you to mark faster, set a timer, batch your sessions, write shorter comments. Those help a little at the edges. They don't touch the pile, because the pile is built by the system you mark inside, and that system doesn't change when you speed up.
Why the pile keeps coming back
Three things keep it topped up, and none of them are about your competence.
Assessment design creates peaks. Most faculties set assessments at the same points in the term: end of unit, before reports, before exams. So every teacher in the school hits peak marking at once. Last year my Year 12 Ancient History extended responses landed in the same fortnight as my Year 11 source analyses and the whole faculty's pre-report deadline. The pile doesn't build gradually. It arrives in one fortnight, every 6 to 8 weeks, with a turnaround window that's always too short.
Feedback takes far longer than scoring. Putting a band or a mark on a piece of work is quick. Writing feedback specific enough to move the student is slow. "More analysis in your second paragraph, you've got the Treaty terms but not what they did to Weimar politics" takes real thought. Writing that 30 times on a Sunday night is the part that empties you, and it's nothing like the speed of assigning the mark.
Marking has no natural end. A lesson ends at the bell. A meeting ends when the agenda's done. Marking ends when you decide to stop, which means the decision is always yours, always made while tired, and always shadowed by the sense that you should keep going. That's structural. The job hands you an open-ended task with no signal for when it's finished.
What doesn't fix it
A few things get recommended a lot. I've tried them.
Marking faster cuts the time per script but leaves the volume and the thinking untouched. In practice it just lowers the quality of the feedback, which means it helps the student less, which makes the whole exercise feel more pointless on top of being exhausting.
Shorter comments only help if short still means specific. "Good analysis" is short and useless. A comment that names exactly what the student did and what to do next ("your point is an argument now, but your evidence is still vague: give the figure, not 'a lot of land'") takes nearly as long as a long one, because the thinking is the work, not the typing.
Batching and timers are worth doing, and I use both. They protect your evenings. They don't close the gap between how much marking there is and how many hours you have to do it well.
What actually fixes it
The pile shrinks when the thinking load of each script drops without the feedback getting worse.
That means a consistent framework gets applied to every script before you bring your own judgement to it. The heavy analytical pass, does this meet the criteria, where exactly does it fall short, what does this student do next, gets done systematically instead of from a cold start 30 times in a row.
That's what I built MarkMate to do. It reads each piece against your marking criteria, assigns rubric scores, and writes structured feedback across the whole class set. Then you review. You override where your read of the student says to: when I ran my 30 Ancient History essays through it, I changed two bands because I knew those students had lifted across the term, and I let one mark stand because MarkMate had caught source integration I'd missed. You add the context only you have. The student who's been struggling. The one who's finally clicked. The one whose ambition outran her execution this time.
The marking doesn't vanish, and your judgement stays in charge of it. What goes is the base layer: applying the rubric from scratch, one cold start after another, until you can't see straight.
What it doesn't replace
I won't pretend it's the whole job. You'll still sanity-check the scores, still plan the reteach the cohort summary points to, still make the calls only you can make. But the part that drains the most for the least thinking is handled.
What teachers tell me after the first class set is almost always the same. Not that it was quicker. That it stopped feeling like it would never end.
Start before the next pile lands
The time to fix a marking system is before the next assessment comes in, not in the middle of it.
The demo on the homepage lets you paste up to 500 words of student writing and see what MarkMate does, no sign-up needed. If you'd rather test a real set, the free plan covers two assignments a month, enough to run the workflow above on a small Year 7 or 8 task before you trust it on a senior cohort.
If this sounds like someone in your faculty, share it with them. The system problem doesn't get better alone.
