Homework Tracking for Teachers: How to Know Who Has Actually Done It

The Education Endowment Foundation's Teaching and Learning Toolkit puts homework at roughly five months of additional progress a year, with a bigger effect at secondary than at primary. That figure assumes the homework gets done. Since the Department for Education withdrew its national homework guidelines in 2012, English schools have set their own policy, which means what a class actually completes each week comes down to one teacher and whatever system that teacher has for noticing.

What does homework tracking need to record beyond "set" and "marked"?

Three states, not two.

Take Naomi Ferris, who teaches Year 8 English at a comprehensive in Bristol. She has 62 students across two classes and sets one piece of written work a week for each. Over a 39-week year that is around 2,400 individual pieces of homework, from one teacher, in one subject.

Her school's MIS records that homework was set on Monday and, eventually, that it was marked the following week. Between those two entries there is nothing at all: no record of who handed in on time, who handed in late, who handed in something unreadable at the classroom door, and who has not produced a piece of writing since half term.

Naomi knows most of it, of course. She just knows it in her head, per class, in a job where she teaches five other groups. When a parent asks in March how their son has been getting on with homework, the honest answer is a recollection rather than a record.

The third state, submitted, is the one that changes behaviour, because it is the only one that exists while the week is still running.

Why does the school MIS not answer "who has done it"?

Because it was not bought to. A management information system is built to hold the things a school must be able to produce on demand: attendance codes, behaviour records, assessment points, safeguarding logs, and the data that ends up in reports home and in front of inspectors.

Homework sits in that architecture as an event that was set and later as a mark that was awarded. The submission itself is entered retrospectively, during marking, by a teacher with a stack of books at 21:00 on a Wednesday.

That timing is the whole problem. Data recorded after the fact is reporting; data recorded before the lesson is a tool. The first tells your head of department what happened in the autumn term. The second tells you, on Thursday evening, that six students have not started and there is still an evening in which that can change.

We would go further: chasing homework at the point of marking is not tracking at all, it is archaeology. It produces an accurate account of a problem you can no longer act on, and it is why so many well-run departments have detailed homework data and falling homework completion at the same time.

Should the deadline be the start of the lesson or the night before?

The night before. We would put it at 20:00, and we would argue about it.

The case for a lesson-start deadline is that it matches how the work is used: the homework feeds the lesson, so the lesson is when it is due. That is tidy and it is also why so much of the first ten minutes of a lesson gets spent finding out who has nothing to work from.

A deadline the evening before gives you a window. You look at the list at 20:05, see four names, and send four short messages. Some of those students do the work that night. The ones who do not have told you something useful before you walk into the room, which is a very different lesson to plan than one where you find out at 09:05.

The objection is fair: it pushes a teacher's attention into the evening. Our answer is that it does not add work, it moves the moment of visibility, and it replaces eight minutes of lesson time and a whole-class reminder with about three minutes of tapping. A teacher who genuinely will not look at a phone after six should set the cut-off at 17:00 instead. The principle is the window, not the hour.

How do you chase without posting a list of names?

Post the task to everyone. Send the chase privately. Never the other way round.

A message in the class group that names who has not handed in is a weekly public verdict, refreshed every Thursday, on the students least likely to recover from it. It is the same mistake as publishing any comparative list into a group, and it has a second cost: the 26 students who did the work read the reminder too, learn that most group messages are not for them, and stop reading the ones that are.

In Bitir the assignment widget holds the task, the deadline, and a per-student submission state that only the teacher and that student's own family can see. The teacher sees a count and a list of who has not answered. One tap sends a private nudge to exactly those students. Nothing comparative ever lands in the class feed, which stays for the task itself, resources, and the occasional whole-class notice, the same discipline that keeps a register useful rather than punitive.

Teachers we speak to describe the change in almost identical terms: "I used to lose the first eight minutes of every lesson working out who had nothing in front of them. Now I know by nine o'clock the night before, and the lesson starts on the work."

What does a week of homework tracking actually look like?

Naomi's loop takes about ten minutes across the whole week, per class.

Monday, in the lesson. The task goes up with the deadline attached and one sentence defining done: "three paragraphs, handwritten or typed, on why Sheila changes her mind in Act 2". Ambiguity about what counts as finished is responsible for more non-completion than laziness is.

Thursday, 20:00. The cut-off passes. Naomi opens the list, sees five non-submitters, and sends the same two-line message to each of them. Two hand in that night.

Friday, in the lesson. She marks knowing exactly who to expect nothing from, and marks are entered into the MIS as the school requires. No lesson time is spent on a register of shame.

Every half term. She reads the completion rate per student across the last six tasks. Anything below four out of six triggers a call home that week, before it becomes a term-long pattern and before parents' evening turns into a surprise. Each family sees their own child's record and nobody else's, which is the same boundary described in our guide to teacher and parent communication.

Two details make this survive contact with a real timetable. The first is that the teacher never assembles the list by hand; if the chase requires scrolling a chat thread on Thursday night, the system will be abandoned by October. The second is that the completion history follows the student rather than living in one week's message, so the half-term review takes a minute rather than an evening.

Related reading: how a Plymouth youth theatre took off-book compliance from 41% to 86% by tracking line learning the same way, and how a Norwich primary teacher rebuilt parent communication around one private class group.