Feedback is the part of teaching with the strongest evidence base and the widest gap between effort and effect. Academics pour hours into detailed comments that students glance at, or never open at all, once they have seen the grade. The problem is rarely the amount of feedback; it is that most feedback is written as a justification of the mark rather than as instructions the student can use on the next piece of work.
This matters everywhere — in a small honours seminar in the UK, a 500-student first-year unit in India or Nigeria, or an online cohort spread across time zones. Students who cannot act on feedback do not improve, and educators who write feedback no one uses burn out. The techniques below make feedback both more useful to students and faster to produce, which is the combination every teacher actually needs.
Why most feedback is never used
Decades of research point to a few consistent failures. Feedback arrives too late to inform the next task, so students file it away. It focuses on what went wrong without saying what to do differently, leaving the student with a verdict but no map. It is written in academic shorthand — "unclear", "develop", "weak analysis" — that names a problem the student cannot see and does not know how to fix. And it is disconnected from any future action, so even willing students have no moment to apply it.
The shift that changes everything is to treat feedback as part of learning rather than the end of it. A grade closes a task; good feedback opens the next one. If you only change one habit, change this: for every weakness you identify, give one concrete, actionable step the student could take next time. For the wider assessment picture this sits within, explore our Teaching & Assessment guides.
Write feedforward, not just correction
Feedforward reframes each comment from the past to the future. Instead of "your argument is unclear", write "state your main claim in the first sentence of each paragraph, then use the rest of the paragraph as evidence for it — try this on paragraphs two and four." The student now has a specific, repeatable technique rather than a diagnosis. Aim for a small number of high-leverage points — typically two or three — rather than exhaustively annotating every line, which overwhelms the student and hides the signal in noise.
Balance is important but must be honest: name genuine strengths so the student knows what to keep doing, then prioritise the one or two changes that would most improve the next piece. A useful structure is "what worked, what to change, and how" — the last word, how, is the one most feedback omits and the one students most need. The Advance HE assessment and feedback resources collect the underpinning evidence, and our guide to coordinating a marking team shows how to keep feedforward consistent across multiple markers.
Anchor feedback to the rubric
When feedback and the marking rubric use different language, students cannot connect the comment to the criterion or the criterion to the grade, and the whole system feels arbitrary. Anchor every substantive comment to a specific rubric criterion: if the rubric rewards "critical evaluation of sources", your comment on that dimension should name it explicitly and show what a higher level would have looked like. This does three things at once — it makes the grade transparent, it teaches the vocabulary of the discipline, and it dramatically reduces grade appeals, because the student can trace exactly how the mark was reached.
Share the rubric before the assessment, not after, and where possible walk students through an annotated exemplar so they can see the difference between adjacent grade bands in real work. Students who understand the standard before they submit produce better work and need less remedial feedback afterwards — the most efficient feedback is the kind you never have to write because the expectation was clear up front.
Get the timing and volume right
Feedback has a half-life. Comments returned within a week, while the task is still fresh and before the next assessment, are acted on; comments returned after the module has effectively moved on are not. Where your workload makes fast individual feedback impossible, use faster channels that still help: a short whole-class "common issues" note released within days, a five-minute audio summary, or a live debrief in the next session. These reach every student quickly and cost a fraction of individual comments.
Volume matters as much as speed. A page of dense annotation on a failing script rarely helps; the student cannot absorb thirty corrections at once. Prioritise ruthlessly — the two or three changes that would move the work up a grade band — and say so explicitly ("focus on these two things first"). Less, sharper feedback delivered sooner beats more, later, every time.
Design tasks that make students act on it
The most reliable way to make feedback count is to build a moment where students must use it. Two-stage assessments, where feedback on a draft or an early task directly informs a later submission, produce the largest gains because the feedback has an obvious purpose. Ask students to submit a short cover note with their next piece explaining how they responded to previous feedback; even this small step roughly doubles the chance that comments are read and applied. Where a formal draft is impractical, a low-stakes formative task early in the term serves the same function.
This is also where feedback connects to the students' own progression — the habit of acting on critique is exactly what serves them in the workplace and in further study, a theme we develop across our Careers & Getting Hired guides. Feedback that has nowhere to go is a gift with no recipient; design the recipient in.
Mark faster without lowering quality
Sustainable feedback is efficient feedback, and efficiency comes from systems, not speed-reading. Build a comment bank of your most-used feedforward points, phrased as actionable steps, and reuse them — this is not lazy, it is consistent, and it frees your time for the student-specific comment that a bank cannot supply. Mark against the rubric criterion by criterion rather than re-reading holistically, which is faster and fairer. Use audio or screen-recorded feedback for complex work, where two minutes of speech conveys more nuance than fifteen minutes of typing. And front-load your effort into clear task design and exemplars, which reduces the volume of remedial feedback you have to write at all. The AcademicStaff workload calculator and feedback planner helps you budget realistic marking time per cohort and spot when an assessment design is quietly generating unsustainable marking load — the early-warning sign of the burnout that ends good teaching. Marking done this way stays humane, and humane marking is the only kind that lasts a career.
The Feedforward Comment Bank & Marking-Time Planner
A ready-to-use library of 40 actionable feedforward comments mapped to common rubric criteria, plus a spreadsheet that estimates realistic marking hours per cohort so you can flag unsustainable assessment designs early.
Want the full article?
Enter your email for free access to the rest of this guide and our TEQSA resource library.
Frequently asked questions
How much feedback should I write on a single piece of work?
Less than most academics think. Prioritise the two or three highest-leverage changes that would most improve the next piece, phrased as concrete actions, and name a strength or two. Exhaustive line-by-line annotation overwhelms students and hides the important points in noise.
Students ignore my written comments — what works better?
Build a moment where they must use the feedback, such as a two-stage assessment or a cover note explaining how they responded to previous comments. Feedforward phrased as future actions, returned quickly and tied to the rubric, is far more likely to be read and applied than a verdict on past work.
How do I give good feedback to a very large cohort quickly?
Combine a fast whole-class common-issues note with a reusable comment bank of actionable feedforward points, and mark criterion by criterion against the rubric. Audio feedback also conveys more in less time for complex work. Speed and quality both improve when you systematise rather than free-write.
The AcademicStaff editorial team writes practical, evidence-based guidance for university staff — drawing on sector reporting, funder guidelines and the lived administrative reality of academic work. Every guide is reviewed for accuracy against current Australian higher-education practice.