Testing week arrives, the bell schedule shrinks every period to thirty minutes to make room for the test blocks, and by Wednesday every non-tested class has quietly become a study hall with a movie playing, because thirty minutes isn't enough time to actually start anything new and nobody planned for that specific problem. The tested classes get their disruption addressed by definition — they're the ones testing. Every other class just absorbs the chaos with no plan at all.
Why the default response is to just pause everything
Building a real lesson for a compressed, unpredictable period feels like more work than it's worth for four days, so the easy move is a worksheet packet or a video, treated as a placeholder until the "real" schedule resumes. The problem is that testing week isn't four days, it recurs multiple times a year, and treating each one as dead instructional time adds up to a real chunk of the calendar spent on autopilot.
Building the modified schedule with intent
1. Map the actual compressed time block by block before the week starts, not the morning it begins. Thirty minutes on a testing-week Tuesday needs a different kind of task than a normal fifty-minute period — know exactly how much real time you have for each of your classes before deciding what goes in it.
2. Pick tasks that are genuinely productive in a short, interruption-prone block. A short discussion, a single skills-practice set, or continuing independent work from a longer project are all real options in thirty minutes. Starting a new multi-day unit is not — that's the trap that pushes teachers toward a study hall by default.
3. Plan for the students not in your room that day. Testing pulls different students out of different classes at different times during the week. A modified-schedule lesson has to work whether you have twelve kids or twenty-six in the room on a given day, which usually means independent or small-group work rather than anything that requires the whole class present at once.
A quick before/after
Before: "Testing week starts Monday, we'll figure out what to do with the short periods." Tuesday's thirty minutes becomes a worksheet packet handed out with no plan for collecting or using it. By Thursday, the class has effectively lost four real instructional days.
After: a written modified-week plan built the week before — Monday's short block continues the current reading with a specific comprehension task, Tuesday's is independent practice tied to the unit skill, Wednesday's is a structured small-group discussion that doesn't require every student present. Four days of shortened periods, four days of actual instructional purpose.
Building the modified plan with AI
Once you have the actual bell times for testing week, turning them into a real short-block plan is fast to draft, especially across several classes at once:
- "Here's my testing-week bell schedule: [list of period lengths per day]. Build a short lesson plan for each compressed period that doesn't require a full class present, connects to [current unit], and can be picked up independently by a student pulled out for testing that day."
Build the modified week inside the [unit plan tool](/unit-plan) so it stays connected to the actual unit sequence rather than existing as a disconnected one-off week, and if you're coordinating the compressed schedule across the testing block itself, keep the timing details in the [assessment blueprint tool](/assessment-blueprint) alongside the test structure so both pieces live in one place.
What still needs your judgment
- Don't force a full lesson into a fifteen-minute block. Some periods really are too short for anything beyond a quick check-in or a single practice problem — plan for that honestly rather than cramming.
- Communicate the modified plan to students in advance, not as a surprise each morning. A posted week-at-a-glance for the short periods cuts down on the "wait, what are we doing today" drift that eats into the little time you have.
- Revisit the plan after the week, not just before it. Note which short-block tasks actually worked and which fell flat, so the next testing week's plan improves instead of starting from the same guess.
