How to write report comments faster (without them reading generic)

Most of the time goes to three sinks: the blank box, the constant flicking back to your markbook, and second-guessing tone. Each one has a fix.

Written by the Markpilot team, practising secondary teachers · July 2026

A class set of report comments is hours of work, and very little of it is typing. It is deciding what to say about student fourteen when students one through thirteen have drained everything you had, re-opening the markbook to check whether it was Ava or Amelia who bombed the measurement test, and rewriting a sentence four times so it is honest without being harsh. The workflow below attacks those three sinks directly. It will not make the judgment easier, but it stops you paying for the same judgment twice.

1. Gather the evidence before you write anything

The single biggest speed-up is refusing to write until the evidence is in one place. For each student, you want three things visible on one screen or one sheet:

• their results by topic or strand, not just an overall mark;
• one concrete observation (a piece of work, a habit, a moment) if you have one;
• anything promised earlier in the year ("we agreed to focus on...") that the family will expect you to close the loop on.

This is an argument for keeping marks by question or by strand during the semester rather than as single test totals. "71% overall" produces a generic comment; "strong in algebra, dipped on unit conversions" produces a specific one in the same number of words. If your markbook only has totals, twenty minutes reconstructing strand-level patterns for the class pays for itself several times over during writing.

2. Fix your structure once, then stop deciding

Decide the shape of every comment before you start: evidence, judgment, one next step, in that order, three or four sentences. (Worked examples are in our report comment examples guide.) The point of a fixed structure is not uniformity for its own sake. It is that structure-deciding is the invisible cost of every comment written from a blank box, and you only need to pay it once per reporting cycle, not thirty times.

3. Write in passes, not student by student

Writing each student's comment start to finish means switching mental modes constantly: recall, judgment, phrasing, tone, thirty times over. Batching by pass is faster:

• Pass one: for every student, jot the evidence sentence only. This is transcription from your markbook, and it is quick.
• Pass two: the judgment sentence for everyone. You are now making thirty similar decisions consecutively, which keeps your internal standard consistent as well as fast. (The student you mark at 11pm should get the same tone as the one you marked at 4pm.)
• Pass three: the next step for everyone. With the whole class in view you will also catch yourself before giving eleven students the identical next step.

4. Reuse skeletons, never sentences

A comment bank of finished sentences produces the reports parents roll their eyes at. A bank of skeletons is different: "lifted from X to Y, clearest gains in Z" is reusable across every improver you ever teach, because the specifics are what fill it. Keep a personal list of five or six skeletons that match your voice. The test for whether something belongs in your bank: if the sentence still works with no numbers or topics filled in, it is wallpaper; cut it.

5. Proofread for the mistakes that matter

Do a final pass that checks nothing except names and pronouns. A wrong name is the single most damaging report error there is: it tells the family the comment was recycled, and it is the error spell-check will never catch. Read only the names and pronouns, every comment, top to bottom. It takes a few minutes for a full class and it is the cheapest insurance in this whole guide.

Where AI honestly fits

We build an AI marking tool, so discount accordingly, but here is our honest view from using these systems on our own classes.

Drafting from real evidence is the legitimate use. If a system has your actual markbook, per-question marks, strand patterns, growth across the semester, it can produce a first draft of the evidence and judgment sentences that is genuinely anchored to the student, and editing thirty drafts is much faster than writing thirty comments. That is the workflow worth having.

What to watch for:

• Invented specifics. A generic chatbot with no access to your marks will happily fabricate plausible ones. Never use a tool that cannot show you where a claim came from.
• Praise inflation. Left alone, AI drafts drift warm. If every student is "a delight", the comment means nothing. Edit against your own judgment, not the draft's.
• Voice drift. Parents have read your comments before. If this semester's read like a press release, they will notice. Redraft anything you would not say aloud at parent-teacher night.

The rule that keeps all three in check: never send a comment you could not defend line by line, with evidence, to the family across a table.