Effective Feedback Strategies That Students Actually Use: The ART Framework

You spend your Sunday evening with a stack of notebooks. You write careful comments in the margins. You circle errors, add suggestions, and finish each page with a line of encouragement. On Monday, you hand the work back. Students glance at the grade, flip through the pages, and close the book.

Two weeks later, the same mistakes come back.

If that feels familiar, you are not doing anything wrong. You care, you know your subject, and you put in the hours. The problem sits somewhere else. In a recent Suraasa webinar, Manish Pandey, Teacher Career Mentor and Associate Director at Suraasa, joined by fellow mentor Bhavya Jain, made a case that changes how you look at that Sunday stack. The question is not how much feedback you give. The question is whether your feedback is usable.

This guide walks through the ideas Pandey shared: why so much feedback goes nowhere, the three stages every comment must survive, and the ART framework (Anchor, Route, Trigger) that turns vague corrections into concrete next moves. You will also find subject examples, ways to scale feedback across large classes without burning out, guardrails for using AI as a drafting assistant, and how all of this builds students who eventually need you less. That last part is the real goal of effective feedback strategies.

The Feedback Paradox: Why Students Read Comments but Do Nothing

Pandey opened with a finding that should unsettle anyone who marks for a living. He cited a study of 937 lower-secondary learners and translated it into a picture every teacher can see: a typical class of 30.

Read that middle row again. Fourteen students out of thirty do what you asked. They go back to the work. They make changes. And the work does not get better.

This is the feedback paradox. We usually blame the six who ignore comments. But the bigger group is the one that tries and fails. As Pandey put it:

“Some learners do not fail because they ignore feedback. They try, and it still does not work.” Manish Pandey

That reframes the problem completely. If students are trying, then motivation is not the bottleneck. The bottleneck is the comment itself. “Develop your argument further.” “Show your working.” “Be more careful.” These lines make perfect sense to the person who wrote them. To a 13-year-old, they describe a destination without a map.

Pandey was clear that this is not a failure of teacher effort or subject knowledge. Most teachers write too much, not too little. The gap lies in design. A comment can be accurate, kind and well intentioned, and still give the student nothing to do on Tuesday morning.

Research has pointed in this direction for years. John Hattie and Helen Timperley's widely cited review, The Power of Feedback, argued that feedback works best when it answers three questions for the learner: where am I going, how am I going, and where to next. Most margin comments answer only the second. The Education Endowment Foundation's guidance report on teacher feedback makes a similar point: what matters is how pupils receive and act on feedback, not the volume or method a teacher uses.

So the paradox has a way out. If the comment is the problem, the comment can change.

The Three Stages Every Feedback Comment Must Survive

Pandey compared feedback to a medical prescription. A doctor can diagnose correctly and write the right medicine. But the prescription only works if three things happen. The patient has to read it. The patient has to understand it. And the patient has to take the medicine, correctly, at the right time.

Feedback follows the same path. Every comment you write has to survive three stages:

1. Noticed. The student actually sees and reads the comment. A grade at the top of the page often kills this stage. Once students see a number, many stop reading.
2. Understood. The student can decode what you mean. “Weak conclusion” assumes the student already knows what a strong one looks like. If they knew, they would have written it.
3. Used successfully. The student takes action, and the action leads to improvement. This is where those fourteen students fall off. They act, but the action is the wrong one, or too vague to land.

Think of each stage as a filter. A comment that fails the first filter never reaches the second. A comment that passes the first two but gives no clear action still fails the third. Most feedback dies somewhere along the way, and the teacher never sees where.

This three-stage lens is useful on its own, before you adopt any framework. Pick up a recent piece of marked work and ask of each comment: would a student notice this? Could they explain it back to me in their own words? Do they know exactly what to do next, and will they have the time to do it?

If you want to hear Pandey walk through these stages and the research behind them in his own words, the full session below is worth your time, especially the section where he unpacks the 30-student breakdown.

The three stages also explain why feedback connects so closely to the purpose of assessment itself. When you treat a task as a checkpoint for learning rather than a final verdict, the comment becomes the most important part of the task. If that distinction is new to you, our guide on assessment for learning vs assessment of learning lays it out clearly.

Beyond Red Ink: Deconstructing the ART Feedback Framework

Before introducing ART, Pandey touched on a framework many school leaders already use for adult conversations: SBI, or Situation, Behaviour, Impact. When a coordinator observes a colleague's lesson, SBI keeps the conversation grounded. You describe the situation, name the observable behaviour, and explain its impact. It stops feedback from turning personal. If you lead peer observations, it pairs well with the reflective practices we discuss in our piece on classroom observation and teacher growth.

But students need something different. They need feedback that turns into a move they can make. That is what ART is built for.

A: Anchor

The anchor connects the comment to two things: a specific goal and specific evidence from the student's work. Instead of “Good effort, but needs more detail,” an anchored comment says something like: “Our goal was to support each claim with evidence. In paragraph two, you make the claim that the policy failed, but you do not show how you know.”

The anchor does the work of the first two stages. It makes the comment noticeable because it points to a real place on the page. It makes the comment understandable because it names the goal the student was aiming for.

R: Route

The route gives one high-value next action. Not five. Not a list of everything wrong. One step that will improve the work most.

“The comment does not need more words. It needs a route.” Manish Pandey

This is the heart of the framework. A route is concrete enough that a student could start on it immediately: “Add one statistic or quotation from the source sheet that proves your claim, then write one sentence explaining what it shows.”

Choosing one action feels uncomfortable. You can see six things wrong. But a student given six corrections often fixes the easiest one and ignores the rest, which is how revision happens without improvement. One well-chosen route beats a crowded margin.

T: Trigger

The trigger is the part most teachers skip. It means allocating classroom time, right away, for students to act on the feedback. Pandey's practical recommendation was to set aside 5 to 10 minutes of lesson time immediately after returning work.

Without a trigger, feedback becomes homework that competes with every other piece of homework, and loses. With a trigger, the third stage (used successfully) happens in front of you. You can circulate, check that routes make sense, and catch students who are revising in the wrong direction.

Here is how one comment changes when it passes through ART:

Pandey summed up the shift in a line worth putting above your marking desk: you do not measure feedback by how much you write; you measure it by what the learner can do next.

Applying ART Across Subjects: English, Math, and Science Examples

Pandey demonstrated that ART adapts across subjects. The examples below are our own illustrations of how that looks in practice, so you can see the pattern and build your own.

English

The work: A Grade 8 persuasive essay on whether school uniforms should be compulsory. The student has strong opinions but every paragraph repeats the same point.

• Anchor: “Our success criterion was to use at least two different reasons. Paragraphs two and three both argue that uniforms save time in the morning.”
• Route: “Replace paragraph three with a new reason. Choose one from cost, equality or school identity, and give one example.”
• Trigger: “Draft the new paragraph in the first 10 minutes today. Underline your new reason.”

Mathematics

The work: A Grade 7 student solving linear equations gets the method right but makes a sign error when moving terms across the equals sign, on three out of five questions.

• Anchor: “The goal was to solve equations with variables on both sides. Your steps are correct, but in questions 2, 4 and 5 the sign changes incorrectly when you move a term.”
• Route: “For each of these, rewrite the step by doing the same operation to both sides (for example, subtract 3x from both sides) instead of moving terms. Then check your answer by substituting it back.”
• Trigger: “Redo question 4 now using this method and substitute to check. Then try question 5.”

Notice that the route here is not “be careful with signs.” That comment would pass stage one, maybe stage two, and fail stage three. The route gives a method that prevents the error.

Science

The work: A Grade 9 lab report on how temperature affects the rate at which sugar dissolves. The conclusion states the result but never refers to the data.

• Anchor: “Our goal was to write a conclusion supported by data. You say sugar dissolves faster in warm water, which is correct, but you do not use any numbers from your table.”
• Route: “Add one sentence comparing two specific results, for example the time at 20°C and the time at 60°C.”
• Trigger: “Rewrite your conclusion in class today before we start the next practical.”

Across all three subjects, the structure holds. The anchor names a goal the student already met in class. The route is small enough to finish in one sitting. The trigger makes the action happen while the learning is fresh. If you use quick in-lesson checks, many of the techniques in our list of 25 classroom assessment techniques work well as the trigger activity itself.

From Error Correction to Strategy and Knowledge Transfer

ART fixes the immediate problem. But Pandey pushed further. If every piece of feedback only corrects the current task, students stay dependent on you. They wait for the teacher to point out what is wrong. They never learn to see it themselves.

He described feedback moving through three levels:

1. Correction. Fixing a specific error in a specific task. “Your sign changed incorrectly in question 4.”
2. Strategy. Teaching a method the student can use on this kind of problem. “When you rearrange an equation, apply the same operation to both sides and then check by substituting.”
3. Transfer. Helping the student use that strategy in new tasks and even other subjects. “Checking your answer by putting it back into the problem works in physics calculations too. Try it on tonight's speed questions.”

Correction is necessary, especially early on. But a teacher who only corrects will correct the same error forever. Strategy feedback lasts longer because it travels. And transfer is where real learning shows up: the student meets a new problem and reaches for a tool you gave them weeks ago.

In practice, you can shift a route from correction to strategy with a simple question: is this action only useful for this one answer, or will it help with the next ten? “Add a comma here” is correction. “Read your sentence aloud and add a comma where you naturally pause” is strategy.

This connects closely with concept-based teaching, where the aim is understanding that moves between contexts. Our guide on concept-based teaching and transfer explores the same principle at the level of unit design.

Scaling Feedback: How to Manage Large Classes Without Burnout

Every teacher reading this is doing the maths. Forty students. Five sections. Detailed ART comments on every page? That is not a framework. That is a second full-time job.

Pandey addressed this directly, and his answer was blunt:

“Do not multiply feedback. Scale it.” Manish Pandey

Multiplying feedback means writing the same comment thirty times. Scaling it means recognising patterns and responding to them once. Here is what that looks like.

Restrict comments to one priority

ART already pushes you toward one route per piece of work. That is also the single biggest time saver. When you stop trying to correct every flaw, each script takes a fraction of the time. Pandey's guidance was to resist the urge to fix everything and select the single highest-value action. The student benefits too. One clear target beats a page of red ink.

Sort before you write

Before commenting, skim the full set and sort scripts into rough piles by the main issue. In a set of 40 essays, you might find that 15 students struggle with evidence, 12 with paragraph structure, 8 with conclusions, and 5 are ready for a stretch challenge. Now you are writing four routes, not forty.

Use codes linked to routes

Once you have identified the common routes, give each one a code. Write the code on the work. Display the full ART route for each code on the board or a shared sheet. Students find their code and read the matching action. You still personalise the anchor where needed with a quick underline or a line number.

Plan the trigger, not the comment

The time you save writing goes into the trigger: that 5 to 10 minute window in class. This is where your expertise matters most. You walk the room, check that routes make sense, and intervene with students who are stuck. Ten minutes of live feedback often does more than an hour of written comments.

Scaling is not cutting corners. It is putting your effort where it changes outcomes.

Using Whole-Class Feedback to Address Shared Misconceptions

Whole-class feedback is one of the most efficient tools Pandey recommended. When several students make the same mistake, writing that correction on each page wastes your time and theirs. Address it once, for everyone.

A simple whole-class feedback routine looks like this:

1. Read and note. As you read the set, jot down common errors, strong examples and misconceptions on one sheet. Skip individual comments for now.
2. Pick the top two or three patterns. These are the issues affecting the most students or blocking the most progress.
3. Show, do not just tell. Display an anonymous example of the misconception alongside an improved version. Ask students to spot the difference before you explain it.
4. Give a shared route. One action everyone checks for in their own work.
5. Trigger immediately. Students reopen their work and apply the route while you circulate.

Take a Grade 10 chemistry class where most students write that atoms “want” to gain electrons. Rather than correcting this on thirty reports, you project two anonymous sentences: one using “want,” one explaining the change in terms of a more stable electron arrangement. Students discuss which is more scientific and why. Then everyone finds the sentence in their own report where they explained bonding and rewrites it. Ten minutes. One misconception addressed across the class.

Whole-class feedback also lowers the emotional stakes. A student who sees their error presented anonymously, alongside the fact that many classmates made it too, feels less exposed. That matters. Feedback that feels like judgement often fails at stage one, because students avoid reading it.

Individual comments still have a place. Use them for students whose work does not fit the shared patterns: the ones far ahead, or the ones whose errors need a personal conversation.

Prompt Engineering and Guardrails: Supervising AI as a Feedback Assistant

Generative AI can draft feedback in seconds. That is both its promise and its risk. Pandey's position was balanced and firm. AI can serve as a drafting assistant. It cannot replace the teacher's judgement.

“AI will draft for you, AI will not be the right judge. A teacher is the right judge.” Manish Pandey

He recommended structured prompts with explicit constraints: a clear role, the success criteria, and guardrails. Here is an example of how that structure might look.

Even with a strong prompt, three checks stay with you:

• Verify accuracy. AI can misread a student's answer, misstate a fact, or praise an error. Read every draft against the actual work.
• Adapt for the student. You know that this student shuts down at long comments, or that one needs a stretch challenge. AI does not.
• Keep the judgement. Deciding which route matters most for this learner, right now, is a pedagogical choice. That choice is yours.

Privacy matters as well. Before pasting student work into any tool, check your school's policy and remove names and identifying details. UNESCO's guidance on generative AI in education and research emphasises a human-centred approach and attention to data protection, which supports exactly this kind of teacher-led use.

If you want to build stronger prompts more broadly, our guides on ChatGPT for teachers and AI tools for educator productivity go deeper into prompt structure and verification. For the bigger picture on what AI means for the profession, see AI in education and what teachers should do about it.

Developing Feedback Literacy and Student Agency in the Classroom

Everything so far leads to one long-term goal. Pandey closed the session by connecting actionable feedback to feedback literacy and learner agency. Over time, consistent, usable feedback helps students internalise what good work looks like. They start to spot gaps in their own work before you do. They take charge of their own growth.

Researchers David Carless and David Boud describe student feedback literacy as the understanding, capacities and dispositions students need to make sense of feedback and use it. That is not something students arrive with. You build it, deliberately, through routines like these:

• Make the criteria visible. If students never see the success criteria, they cannot evaluate their own work against them. Share criteria before the task, not just in the comment afterwards.
• Ask students to find their own anchor. Before you return work, ask: “Which success criterion do you think you met least well? Point to the line.” Then compare their answer with yours.
• Let students write their own route. Once ART is familiar, give the anchor and ask students to propose the next step. You check and adjust.
• Use structured peer feedback. Students give each other ART comments using the shared criteria. Explaining a route to a classmate sharpens their own understanding.
• Track routes over time. A simple log at the back of the notebook where students record each route and whether they achieved it. Patterns become visible to them, not just to you.

This is also where adaptive teaching comes in. When you read feedback trends across a class, you learn what to reteach, what to skip and who needs a different approach. Feedback stops being something you do at the end of a lesson. It becomes information that shapes the next one.

The shift is gradual. In the first term, you do most of the anchoring and routing. By the end of the year, students should be doing much of it themselves. That is when you know your feedback has worked. Not when the margins are full, but when students no longer need you to fill them.

Where This Leaves You

You already give feedback. You already care whether it lands. What the ART framework offers is a way to make sure your effort reaches the student as something they can use.

Start small. Pick one class and one upcoming task. Before you mark, write the success criteria at the top of your page. As you read, sort scripts by the main issue. Write one anchor and one route per student, or one shared route for each group. Then protect 10 minutes of the next lesson for the trigger. Watch what students do with it.

Skills like these sit at the core of what it means to teach well, and they deserve the same structured attention as any other part of your craft. At Suraasa, we build our teacher development around exactly this kind of practical, classroom-tested thinking, because we believe the system should start with the teacher and stay with them. If you are weighing how to formalise your growth, our comparison of B.Ed and the Professional Graduate Certificate in Teaching and Learning (PgCTL) is a good place to begin.

Your students try. Give them a route.

For the Love of Teaching.