curriculum-development

The Curriculum Evaluation Cycle: How Strong Teams Improve Units Every Year

A curriculum is never finished. Here is the annual evaluation cycle — evidence, judgment, revision — that separates curricula that improve from curricula that merely repeat.

B

Bastien Dolce

September 25, 2026·9 min read
The Curriculum Evaluation Cycle: How Strong Teams Improve Units Every Year

Every curriculum is a hypothesis. It was written by people guessing what a group of not-yet-met students will need, in what order, at what pace. The difference between districts whose curriculum improves every year and districts whose curriculum merely recurs is not talent — it is whether anyone runs the experiment. A curriculum evaluation cycle is how you run it.

The Cycle, in Four Moves

  1. Evidence (during the unit): collect what the unit actually produced — assessment results, but also the quieter data: which lessons ran long, which tasks students misread, where the rubric could not distinguish strong from adequate. Keep it lightweight: a cover sheet on the unit plan with three prompts.
  2. Judgment (after the unit, fast): within two weeks, the teaching team asks three questions. What did students demonstrably learn? What did the design cause — as distinct from what one exceptional teacher compensated for? What would we predict would happen if we ran this unit unchanged with next year's students?
  3. Revision (while it is fresh): make the edits now, in pencil on the unit plan itself. Evaluation that is deferred to summer is evaluation that silently becomes nothing.
  4. Re-test (next year): run the revised unit and compare against the evidence that triggered the change. A curriculum you cannot compare across years is a curriculum you cannot improve.
The research on professional learning communities — Vescio, Ross, and Adams' review — found that teaching changed when teams analyzed real student work together against a shared plan. The evaluation cycle is the curriculum version of the same mechanism: the unit plan is the shared object, and the data is the meeting's agenda.
A curriculum team reviewing assessment data after a pilot unit

What to Evaluate: The Four Quality Questions

  • Coherence: did the unit's prerequisites actually precede it? (The Schmidt-style prerequisite audit: more units fail this than any other test.)
  • Alignment: did the assessment measure what the objectives claimed? Look for the objective-verb/assessment-verb mismatch — it is the most common and cheapest defect to fix.
  • Load: where did time actually go? A unit that consistently consumes 20% more time than planned is a pacing decision, not a teacher failure — fix the plan.
  • Equity of outcome: break the assessment data by student group before you break it by question. A unit that works only for the students who needed it least is the most expensive kind of failure, because it looks like success in the aggregate.

The Governance That Makes It Real

Teams that sustain this cycle share two boring commitments: a calendar slot (45 minutes within two weeks of each unit's end — protected like a parent-teacher night), and a rule of capture (every judgment becomes an edit on the plan before the meeting ends). Curriculum offices can help by making the unit plan itself the living document — versioned, annotated, comparable across years. The alternative, familiar to everyone, is the curriculum binder from 2019 that everyone protects and no one opens. The cycle is the difference between a curriculum that is aging and one that is maturing.

Tags:

curriculum evaluation
improvement cycle
assessment data
PLC

Share:

Comments (0)

Please log in to join the conversation

No comments yet

Be the first to share your thoughts on this article!