Your department spends a remarkable amount of time writing feedback. A marker will typically spend twenty to forty minutes per script producing comments designed to move you up a band. The overwhelming majority of that effort is wasted, because most students read the mark, skim the comments once while feeling either relieved or crushed, and never return to the file.
Feedback is the cheapest source of improvement available to you, and it is personalised in a way no study guide can be. This article sets out how to decode the language markers use, how to sort comments so they become actionable, and how to build a checklist that quietly raises your marks over a whole year.
Why most feedback is wasted
Three things go wrong. The first is timing: feedback arrives with a mark, and the mark triggers an emotional response strong enough to prevent reading. Nobody absorbs analytical advice in the ninety seconds after seeing 58 when they hoped for 65.
The second is abstraction. Comments such as 'needs more critical analysis' or 'structure could be clearer' are accurate but not instructions; the student cannot see what to do differently on Tuesday. Without translation, the comment is filed away as vague criticism rather than as a fixable problem.
The third is timing again, in a different sense: feedback on one module arrives after that module is finished, so there is nothing to apply it to. Unless you deliberately carry it forward, it evaporates. All three problems have the same solution — a process that separates reading the mark from using the comments.
Decode the marker's vocabulary
Feedback has a house style, and the same phrases recur across departments and institutions. Learning what they actually mean converts a vague comment into a specific instruction. The translations below cover most of what appears on UK feedback sheets.
If a phrase is still unclear after translation, that is a legitimate question for office hours — and a much better one than 'how can I improve?', because it can be answered in two minutes with reference to a specific paragraph.
- 'Too descriptive' → you told me what the sources say; you did not tell me what to make of them.
- 'Needs a clearer argument' → I could not find your position stated in one sentence anywhere.
- 'Underdeveloped' → the point is right but stops one or two sentences too early.
- 'Signposting' → I could not tell where I was in your argument or why this section followed the last.
- 'Engage more with the literature' → you cited sources but never made them disagree with each other.
- 'Unsupported assertion' → this claim needs evidence and a citation, and currently has neither.
- 'Address the question more directly' → your essay answers a related question, not the one set.
- 'Proofread more carefully' → surface errors were frequent enough to interrupt my reading.
Sort every comment into three buckets
Open your feedback with three headings on a blank page: mechanical, structural and analytical. Put every comment into one of them. This takes ten minutes and it immediately shows you where your marks are actually going.
Mechanical problems — referencing errors, typos, formatting, word count — are cheap to fix and worth doing first, because they are pure lost marks requiring no new skill. Structural problems — weak signposting, unbalanced sections, no clear thesis — need a change to how you plan, and are fixed at the outline stage of your next piece rather than in the writing.
Analytical problems — insufficient criticality, thin engagement, unsupported claims — are the slowest to shift and the most valuable. They usually require deliberate practice on a specific move: comparing two sources in one sentence, or evaluating a method. Pick one per assignment rather than trying to fix everything, because attempting all three categories at once tends to produce a worse essay than concentrating on one.
The sorting also reveals patterns across modules. If 'mechanical' fills up every time, your problem is process and a checklist will fix it. If 'analytical' dominates, no amount of extra reading will help until you change how you write about what you read.
Turn comments into a personal checklist
The output of the sorting exercise should be a single document you keep for the whole degree: your personal checklist. Every recurring comment becomes a line, written as an action rather than a criticism.
'Too descriptive' becomes 'highlight every non-contestable sentence before submitting; rewrite any paragraph that is more than half highlighted'. 'Referencing inconsistent' becomes 'check every entry against the department guide, and confirm every in-text citation appears in the list'. 'No clear thesis' becomes 'write the one-sentence answer at the top of the document before drafting'.
Run the checklist as the final hour of every assignment, and keep it short — no more than eight lines. When a line has produced no comments for two consecutive assignments, retire it and add a new one. Over a year this quietly changes what you produce, without ever requiring you to overhaul how you write in a single week.
- Write it as an action you perform, with a time and a trigger.
- Keep it to eight lines maximum, ordered by the size of the mark at stake.
- Retire lines that have stopped generating comments; add the next-most-frequent one.
- Review it against your marking criteria once a term, not just against feedback.
How to ask for feedback that is actually useful
You can get far better feedback by asking better questions, and most students never ask at all. 'How can I improve?' invites a general answer. 'You wrote that my third section was descriptive — could you show me what an analytical version of this paragraph would look like?' invites a specific one, and takes your tutor two minutes.
Bring the artefact. Take the actual paragraph, printed or on a screen, to office hours. Tutors give markedly more concrete advice when looking at text than when discussing an essay from memory, and the conversation becomes collaborative rather than evaluative.
Ask before the deadline too, within whatever rules your department sets. Most will look at a plan, an outline or an opening paragraph even where they will not read a full draft — and a five-minute conversation about a plan is worth more than a page of feedback after submission, because you can still act on it.
Close the loop before the next deadline
The final step is the one that makes the difference, and it takes fifteen minutes. Before you start your next assignment — not while writing it, before — open the last three sets of feedback and read only the comments, ignoring the marks.
Write the two most frequent points at the top of your new document, where you will see them every time you open it. Then plan the piece with those two points in mind: if signposting was flagged twice, build the signposting into your outline rather than hoping it appears in the prose.
Then check your work against the marking criteria before submitting, not just against the feedback. Rubrics are published for a reason and are the most under-read documents in higher education. Reading the descriptor for the band above your current mark tells you, in the department's own words, exactly what you are being asked to do differently.
Key takeaways
- Separate reading the mark from reading the comments; leave 48 hours between the two.
- Feedback phrases are a house style — learning the translations turns criticism into instruction.
- Sort comments into mechanical, structural and analytical, and work on one category at a time.
- Convert recurring comments into an eight-line personal checklist you run before every submission.
- Read the marking criteria for the band above yours; it describes exactly what to change.