The fixed pacing problem

An optimistic fiction that collapses
under contact with reality.

A curriculum that assumes every class will learn every topic in exactly the same number of lessons is not a realistic plan. It is an optimistic fiction. Some classes will master Concept A in 4 lessons; others will need 6. Some will sail through the application phase; others will need an extra consolidation cycle. These are not exceptional circumstances — they are normal variation in how learning works.

A fixed pacing guide responds to this normal variation by creating a binary choice: either stay on the plan and leave learning gaps unaddressed, or depart from the plan and fall behind schedule. Both options are bad. The teacher who stays on plan is aware that students haven't mastered the concept but proceeds anyway. The teacher who takes more time is now behind, which creates pressure on every subsequent topic.

Agile-compatible pacing guides eliminate this binary by building the variation into the plan. “Topic 3: 4–6 lessons” means a class that masters it in 4 lessons is on schedule. A class that needs 6 lessons is also on schedule. The schedule is designed for both outcomes, not just the optimistic one.

A curriculum that assumes every class will learn every topic at the same speed is not a realistic plan. It is an optimistic fiction.
P6 · Agile teaching — C7 · Curriculum for agile
The 80% rule

Schedule 80% of lessons.
Leave 20% as planned flex.

The practical implementation of agile-compatible pacing is the 80% rule: when planning a term's curriculum, schedule 80% of available lessons as specific lesson plans. Leave 20% unscheduled — labelled as flex lessons in the pacing guide.

Flex lessons are not empty lessons — they are planned contingencies. Each flex slot in the pacing guide is labelled with its purpose: consolidation for Topic X if needed; extension for students who completed Topic Y early; or topic-bridging activity if two topics need more connection. The flex slot is a lesson the teacher has planned — they just haven't decided yet whether to deploy it or skip it, pending the formative data from the preceding lessons.

Element
Fixed pacing
Agile pacing (80% rule)
Total available lessons
30
30
Scheduled as specific lesson plans
30
24
Reserved as flex lessons
0 (improvised as needed)
6 (planned in advance)
When extra time is needed
Teacher departs from plan (feels like failure)
Teacher deploys a pre-planned flex lesson (feels like execution)
When class moves faster
Unplanned extension, or early end
Pre-planned extension activity from the flex slot
End-of-term coverage
Often rushed to catch up
Consistent — flex absorbed within planned structure
💡Naming flex lessons properly
In the curriculum plan, flex lessons should be named by their purpose, not labelled “spare lesson.” “Flex 1 — Topic 3 consolidation: use if Q3 application correct for fewer than 60% on Lesson 5 exit ticket” is specific, deployable, and non-stigmatising. “Lesson 27 (spare)” produces confusion about when and why to use it.
Writing pacing ranges

How to convert fixed lesson counts
to agile-compatible ranges.

1
Start from exit criteria, not lesson counts
How long does it take for most classes to demonstrate this ability?

Estimate the lesson range by thinking backward from the exit criterion: how many lessons has it typically taken for a class to reach the point where they can answer the module's Q3 application question correctly? Base this on experience with previous cohorts, not theoretical content volume.

The right question
Not: "How much content is in this topic?" But: "How long does it take a typical class to reach the point where they can transfer this concept to a novel scenario?" These are different questions and produce different lesson estimates. The second is the right one.
2
Add 25–30% to the minimum
The minimum is when everything goes well. The maximum allows for normal variation.

If your experience suggests the minimum is 4 lessons for a well-prepared class, the range maximum should be 5–6 lessons (25–50% above minimum). This range covers one standard deviation of variation in class progress. Classes outside this range are indicating something beyond normal variation — a curriculum design issue or an unusually strong/weak prior knowledge distribution.

What the range covers
"4–6 lessons" means: a class that masters it in 4 is on schedule. A class that needs 6 is on schedule. A class that needs 8 is telling you something about the curriculum design or their prior knowledge — and requires a different response than a flex lesson.
3
Label the flex lesson within the range
Which lesson in the range is the flex lesson?

In a range of 4–6 lessons, Lesson 5 and 6 are the flex lessons. Label them explicitly: 'Lesson 5 (FLEX): consolidation if needed, extension if not. Lesson 6 (FLEX): as Lesson 5 if still needed; otherwise topic bridge activity.' Both lessons are written. Both have a clear deployment criterion. Neither is improvised.

Naming flex lessons properly
"Flex 1 — Topic 3 consolidation: use if Q3 application correct for <60% on Lesson 5 exit ticket. Contains: additional worked examples, guided practice set, and the same exit ticket from Lesson 5 for comparison." This specificity is what separates planned slack from unplanned drift.
You've finished C7

The curriculum is agile-ready.
The AI tools compress the time to build it.

C7 has covered the three structural decisions that make a curriculum agile-compatible: modular design (A1), assessment that feeds the loop (A2), and flexible pacing (A3). The practices are clear. The design decisions are well-defined.

What remains is the production cost of building curriculum that embeds all three. C8 covers how AI compresses that production cost — lesson regeneration, exit quiz generation, and differentiation from a single prompt. The curriculum creator or school curriculum team who uses both C7's design principles and C8's AI tools produces better curriculum faster than either approach alone.

Continue to C8: AI tools →← Back to A2