Summative assessment data arrives
when it can't change anything.
The fundamental problem with summative assessment as the primary data source for teaching improvement is timing. When a student scores 54% on the end-of-unit test, what should the teacher do? The unit is over. The class has moved on. The teacher can note it as a planning consideration for next year — but they cannot act on it this year, for this cohort.
Most curriculum assessment is designed to produce this kind of data: accurate, comparable, delayed. Useful for reporting. Useless for iteration.
Agile-compatible curriculum assessment is designed for the opposite: less accuracy, less comparability, but sufficient timeliness to produce action within the current teaching cycle. If the curriculum plan only schedules assessment at the end of units, teachers who want to iterate mid-unit are improvising assessment tools that weren't designed for the context. If the curriculum plan includes mid-unit formative checkpoints with clear action protocols, agile teaching is structurally supported.
End-of-lesson. Mid-module.
End-of-unit.
Agile-compatible curriculum operates assessment at three timescales simultaneously. Each level serves a different purpose and produces data that feeds a different part of the agile loop.
The end-of-lesson level is covered in C3. This article focuses on the mid-module level — the least common and most valuable for in-curriculum agile teaching, because it produces data at the moment when the teacher still has time to change what happens within the current module.
What it looks like and where
in the plan it sits.
The mid-module check should not be a quiz or a test. Tests produce grades, not diagnostic signals. The mid-module check should be a task that requires students to apply the concepts covered in the first half of the module to a novel scenario — one that wasn't covered in those lessons. If students can complete it, the first half of the module has produced transferable understanding. If they cannot, specific gaps can be identified before the module's second half.
The mid-module check sits between the 'introduction and first examples' phase and the 'application and extension' phase of the module. This placement means: if the check reveals a significant gap, the teacher can address it before the application phase, rather than discovering it at the end when the gap has compounded through applied work.
The curriculum plan should include, alongside the mid-module check, a decision protocol: 'If fewer than 60% of students complete Q2 correctly, insert consolidation lesson X before proceeding to Lesson N. If more than 80% complete all three questions correctly, skip consolidation lesson and proceed directly to extension activity.' This protocol is the link between assessment and adaptation.
Combining-concepts tasks
in 30 seconds.
Flex lessons and pacing guides:
the structural layer.
A2 has covered assessment design. A3 covers the other structural element that makes agile teaching possible at the curriculum level: pacing guides that use ranges rather than fixed lesson counts, and the 80% planning rule that builds flex capacity into every unit before teaching begins.