Switch course ▾
Session 4. Feedback at Scale and Monitoring Progress
Objective. Give useful feedback to 35 pupils in about 15 minutes of marking, build a comment bank with codes, and keep a one-page tracker whose simple rules tell you whom to group, stretch or reteach.
Marking 35 exercise books with a thoughtful comment in each is one of the largest hidden costs in a teacher's week, and often the least used by pupils. This session asks a different question: what feedback will pupils actually act on, and how can a teacher offer it at a scale that is sustainable? It combines whole-class feedback, comment codes and a very simple tracker, so that your marking time feeds directly into the next lesson instead of ending in a closed book.
Key ideas
Where feedback pays for the time
- Thirty-five books with a one-minute comment each is more than half an hour for a single set. Feedback works when it tells pupils what to do next on the goal and arrives while they can still act on it. Evidence summaries find that these principles matter more than whether feedback is written or spoken.
- Plan a rotation: detailed comments for six to eight pupils per set (different pupils each time) and whole-class feedback for everyone. Over a term, all pupils get personal attention without burning you out.
The whole-class feedback sheet
- Read all 35 pieces of work quickly (about 10 minutes) and tally only the two or three most common issues and one or two strengths. Then write a one-page sheet: what went well, the issue, a model sentence or worked line, and a five-minute fix-it task.
- Show one or two anonymous examples on the board. Next lesson, pupils fix their own work first, then you meet only those who still need you. Pupils learn from their own correction, not from your red pen.
Comment codes and a comment bank
- Number the six to eight most common errors. Write the code on the work and put the numbered comment bank on the wall or in the exercise book. Each comment says what to do ('Add because and link the fact to its effect'), not just 'wrong'.
- An AI tool can draft a first bank for the common errors of a task (see course 8.7). You edit it for accuracy, tone and Uzbek or Russian wording. Never paste real pupil work or names. Without a tool, write the bank from last term's errors.
A one-page tracker with simple rules
- Use a grid: pupil numbers down the side, the last four to six checks across, and three symbols: + secure, ~ nearly, 0 not yet, and A for absent (absent is not 0). Record only the checks you already do, such as diagnostics and exit tickets.
- Decide the rules in advance: three or more 0s means a small group; three + in a row means a stretch route; more than a third of the class at 0 in one check means reteach everyone, because the problem is in the teaching, not the pupils. Keep the tracker in your own folder.
Feedback and tracking cycle
Feedback that is read, understood and used
Feedback helps when pupils know what the goal is, where they are now and what to do next, and when they have a chance to act on it soon. Long written comments often arrive after the topic has gone, and the pupil sees a mark and closes the book. A short comment that points to one next step, followed by a few minutes of lesson time to act on it, is usually more effective than a long comment with no time to respond.
Whole-class feedback applies this idea to many pupils at once. When you tally the commonest issues, you find the two or three things that will move most pupils forward. Personal comments then go where they matter most: to pupils with unusual issues and, in rotation, to a few pupils each time.
A tracker is a decision aid, not a record for its own sake
Teachers often keep marks that nobody reads. A tracker earns its place only if it changes what you do. The rules in this session do that: three or more 0s send a pupil to a small group, three + in a row opens a stretch route, and a third of the class at 0 on one check tells you to reteach everyone. Writing the rules before you look at names guards against impressions, tiredness and favourites.
Keep it light: pupil numbers, four to six checks you already run, and three symbols. Treat an absence as an absence, not as a 0. Look at columns as well as rows: a column with many 0s points to the teaching, a row with many 0s points to a pupil who needs you. Keep the tracker on paper in your own folder.
Examples from the classroom
Dictation errors in Grade 5
Scene. Jasur in Bukhara marks 36 Uzbek dictations in 15 minutes by tallying only. He finds that 20 pupils missed the same spelling pattern. The next lesson he shows two anonymous sentences, explains the pattern with three examples, and pupils spend five minutes correcting their own words. Only the 7 pupils who still fail get a comment from him the following day.
Insight. When many pupils share one error, one class response saves hours and gives pupils something to do at once.
Comment codes in Grade 10 physics
Scene. Malika in Samarkand lists the six most common errors in problem solutions: no units, wrong formula, arithmetic slip, missing diagram, no final sentence, wrong conversion. She numbers them and pins the bank in the room. She writes only '2, 5' on a solution. Pupils look up the comment and rewrite the weak part, so she is marking at a pace of about one minute per notebook.
Insight. Codes keep feedback specific and let pupils do the work of reading it.
The column that gave it away
Scene. Dilnoza in Tashkent updates her tracker after a diagnostic. Check 3 is the first after a week of school holidays, and 14 of 33 present pupils show 0 where most had ~ or + before. She does not blame the pupils. She reteaches the topic to the whole class with a new example, and checks again two days later; the 0s fall to 4.
Insight. A column with many 0s signals a teaching problem or a gap in time; the right response is a whole-class reteach.
Common pitfalls
- Writing long comments that arrive after the unit has moved on and that pupils do not need to act on.
- Giving feedback about the pupil ('careless') instead of about the work and the next step.
- Treating an absence as a 0 in the tracker, which hides pupils who simply missed the lesson.
- Building a tracker with too many columns and symbols, so that it is never updated.
Write a Class Feedback Sheet and Read a Tracker
- Open the Activity Kit: ten anonymised answers to one Grade 7 geography question. In pairs, read them and tally the codes A, B, C, E and D on the tally sheet (15 min).
- Pairs (20 min): choose the two issues for the whole-class sheet. Write the sheet: strength, issue, model sentence, five-minute fix-it task, and the two examples you will show.
- Whole group (10 min): compare sheets. Would this take 10 minutes with 35 real papers? Which codes deserve personal comments, and for whom, this week?
- Second short activity (15 min): apply the three tracker rules to the sample tracker of 12 pupils. List who goes to the small group, who gets the stretch route, whom you only watch, and whether the class needs a reteach.
- Alone (10 min): write your school-based task from the Kit and the date you will start your own tracker.
Your facilitator will guide you through this activity in the session.
Questions to discuss
- Which issue did you leave for personal comments, and why?
- Did the tracker rules agree with your own feeling about the pupils? Where not, which is right?
- What would you stop doing in marking if the whole-class sheet worked?
Reflect
- How long does a set of 35 take you now, and what do pupils do with your comments?
- Which marking habit is for pupils and which is only for show?
- Which pupils might look weak in your tracker only because they were often absent?
Try it tomorrow
- Next time, read all books once and tally only the top two issues before you write any comment.
- Write a one-page class sheet with a model sentence and run a five-minute fix-it task at the start of the next lesson.
- Start a paper tracker with the checks you already have and apply the three rules at the end of the month.
Further reading and links
Read all, tally the top issues, give the class one sheet, give a few pupils personal comments, and let a simple tracker with fixed rules decide the groups.