A project is due in three weeks. For most of those three weeks, the only visible milestone is the final date. The student can therefore feel on schedule while very little usable work exists.
A deadline detects failure late. A checkpoint is designed to reveal whether the work is becoming possible while there is still time to change it.
Checkpoints should describe usable states
“Twenty-five per cent done” may be difficult to interpret. “Research question agreed and two relevant sources checked” tells the next stage whether it can begin. “Complete rough draft ready for feedback” creates another useful state.
Choose checkpoints around dependencies and learning decisions, not arbitrary fractions of the calendar.
A checkpoint is not another deadline for decoration
If the student can satisfy the checkpoint cosmetically without making later work easier, it has little value. A folder of downloaded sources is not equivalent to sources that have been read enough to support the intended claims.
Define what the next stage needs to receive. The group-project guide on Why Group Projects Run Late calls this a receiving condition.
Use checkpoints to expose uncertainty
An early outline may reveal that the argument has no evidence. A first graph may reveal inconsistent units. A practice section may reveal a prerequisite gap. These are successful checkpoint outcomes because they identify work that still needs doing.
Do not mark the checkpoint as failure simply because it found a problem. Finding the same problem on the final evening would be worse.
Place checkpoints before response time is needed
If a teacher needs to clarify an approach, the relevant checkpoint must occur while there is a normal opportunity to ask. If group members need time to integrate contributions, their handoff checkpoint must precede final assembly.
The guide on Why Students Do Not Plan for Help to Take Time explains why support itself is a timed dependency.
Do not create too many checkpoints
Every checkpoint has overhead. Students should not spend more time reporting progress than making progress. Use the smallest number that exposes major risk transitions.
A short assignment may need none beyond an early encounter and final check. A substantial project may need several. Match the control to the complexity.
A simple project sequence
For an illustrative report: first checkpoint, question and requirements understood; second, evidence sufficient for the planned argument; third, complete rough version; fourth, corrections made and submission package ready. Each checkpoint enables a different next action.
These stages are examples, not a universal template. A Mathematics investigation, oral presentation or creative task may need different states.
When a checkpoint is missed
Recalculate immediately. What remains? Which later stage depends on the missing work? Can scope be reduced within the brief? Does another person need to know? Waiting for the final deadline to acknowledge the delay defeats the purpose of the checkpoint.
Keep the response factual. A missed checkpoint is information about the project state, not proof that the learner is irresponsible.
The deeper lesson
A final deadline tells you whether you arrived. Intermediate checkpoints tell you whether the route is still working while alternatives remain.
Use them to discover problems early enough that discovery is still useful.
Continue through the Learning and Study Skills Library or read Why Students Confuse Deadlines With Start Dates.
Continue through the Parent Learning Support Directory for connected study, reasoning and learning diagnostics.
