Switch course ▾
Session 4. Feedback and Marking at Scale
Objective. Build a weekly marking and feedback plan for 40 pupils that takes realistic minutes, keeps feedback specific and gives pupils time to act on it.
Feedback is one of the most useful things a teacher gives, and in a large class it is also the easiest way to burn out. The way out is not to give less care but to give it in the right size: the whole class hears what most need, pupils check what they can check, and your deep reading goes where it matters. This session looks at different kinds of mistakes, how to train pupils to check work, and how to keep your judgement in the loop.
Key ideas
Do the arithmetic first
- Forty notebooks at 3 minutes each is 120 minutes, two hours, for a single task. Over a week of several tasks the full-marking habit cannot be kept.
- The goal is not to give less feedback but to give feedback that pupils use. A long comment that nobody reads has no value.
- Feedback works best when it is specific, about the task and how to improve, and when pupils get time to act on it. Praise of the person alone helps least.
Whole-class feedback
- Read a sample of eight to ten pieces of work, or all of them quickly. Note the three or four most common errors and one thing done well, and sort the work into piles if you wish.
- Next lesson, spend 5 to 8 minutes: show one anonymous example of each error, re-teach it briefly and let pupils correct their own work with a different-colour pen.
- Do not name pupils in front of the class. Pupils who made the error recognise it themselves, and you have written the comment once, not forty times.
Codes and success criteria
- Agree a code sheet with pupils: U for unit, W for working missing, C for conversion, S for spelling. Write the code at the line; the pupil finds and fixes the error.
- Give two or three success criteria before the task, such as 'unit written, working shown'. Pupils check themselves before handing in, and you mark only against those.
- A grade alongside a comment often draws the eye away from the comment. Give the comment first, and the mark later or not at all for practice tasks.
Rotation and peer checks
- Rotate: read eight notebooks in depth each day, so every pupil gets close attention once in five days. Scan the rest quickly for the codes.
- Let pupils check closed answers with a key on the board and open answers with the success criteria in pairs. Train them with two practice rounds before relying on it.
- Always keep teacher judgement in the loop: spot-check peer marks, and use peer assessment for practice, not for final grades.
Layers of feedback in a class of 40
Not every error needs the same response
Separate slips from misunderstandings. A slip is a careless mistake the pupil can fix alone, such as a missing unit or a copying error. For a slip, a code or a mark in the margin is enough: 'there is an error in this line'. A misunderstanding is different: the pupil does not know the idea. Here a hint or a question works better than the correct answer, for example 'What is 1000 g in kilograms?'.
This sorting also shows where whole-class feedback is the right tool. If six pupils make the same misunderstanding, teach it once to everyone. If one pupil keeps making slips, a short talk and a self-check habit may be enough. Pupils also need time to respond: five minutes of correction in the lesson often does more than a long comment nobody reads.
Training pupils to check work
Pupils can check work well only after they have been taught. Show an anonymous example on the board, go through the success criteria one by one, and mark it together. Then let pupils mark one item in pairs, and compare their marks with yours. Repeat this for two or three lessons before you rely on peer checks.
Keep peer marks for practice, not for the final grade, because pupils may be too generous or too harsh. Ask for one thing done well and one thing to improve, with a reason. Spot-check five or six papers a day to see how the method works. This keeps the teacher's judgement in charge and shows pupils that their feedback matters.
Examples from the classroom
Codes on a Russian-language page
Scene. Malika teaches Grade 7 Russian language in Fergana to 40 pupils. She and the class agree five codes: S spelling, P punctuation, E ending, W word choice, ? unclear. On a dictation she writes only the code at the line. Pupils have six minutes to find and correct each error with a green pen. She reads eight corrected notebooks in full that evening.
Insight. A code points to the fix and hands the correcting work back to the pupil.
Three piles in Bukhara
Scene. Jasur reads a quick sample of ten Grade 5 science notebooks about the water cycle. He finds that six pupils wrote that water 'disappears' instead of becoming vapour, and that four mixed up evaporation and condensation. Next day he spends seven minutes on these two points, with a diagram on the board. Pupils correct their own page. He writes no individual comments that night.
Insight. One class-wide mini-lesson replaced ten similar comments and used lesson time for correction.
One star and one step
Scene. Aziz teaches Grade 9 Uzbek literature in Tashkent. Pupils write a six-sentence paragraph about a poem. With three criteria on the board (a claim, a quote, a reason), partners mark each other with one thing done well and one thing to improve. Aziz spot-checks five papers and notes that two pupils were too generous. He shows both examples at the start of the next lesson.
Insight. Training and spot-checks keep peer assessment honest and useful.
Common pitfalls
- Writing long comments that pupils do not read or answer.
- Giving a grade and a comment together, so pupils see only the grade.
- Using peer marks for final grades before pupils are trained.
- Marking everything yourself because letting go feels like lower standards.
Mark Less, Mark Better
- Read the task and the eight sample answers in your Activity Kit (Grade 5, adding masses in kilograms and grams).
- Alone (5 min): sort the eight answers into piles by the type of error and count each pile. Which two errors are the most common?
- In pairs (15 min): write a whole-class feedback note: two or three common errors, one success, a 3-minute mini-lesson idea and a correction task. Add the codes you would write on the notebooks.
- As a group (10 min): fill in the marking planner for 40 notebooks (full marking versus rotation). Compare the minutes with another pair and agree on a plan you could keep for a month.
Your facilitator will guide you through this activity in the session.
Questions to discuss
- How many minutes did your plan save compared with marking everything in detail? What did you give up, and was it worth it?
- When will pupils have time in the lesson to act on your feedback?
- What would you need to train pupils to do before peer checking works?
Reflect
- How many minutes did you spend marking last week, and how many of those comments did pupils act on?
- Which comment do you write over and over?
- Which task could pupils check themselves with a key or criteria?
Try it tomorrow
- After your next written task, read ten notebooks and write the three most common errors on a card.
- Give five minutes at the start of the next lesson for pupils to correct their own work.
- Agree on four marking codes with your class and use them on the next task.
Further reading and links
Mark less, mark better: sort the errors, speak to the whole class, use codes and criteria, rotate your deep reading and give pupils time to act.