Most lesson planning tools are document managers. You create a plan, you save it, you find it again when you need it. The connection between "this plan" and "this slot in my timetable on Thursday" is something you track in your own head, or in a separate spreadsheet, or in the paper planner sitting next to your laptop.
Timetable integration changes this. When your lesson plans are linked to actual timetable slots, several things that used to require manual effort happen automatically.
What timetable integration actually does
In ScholaPlan, you set up your timetable once: classes, days, times. From that point, your teaching diary shows your week as a grid of actual slots — Monday Period 2 is Year 9 English, Tuesday Period 4 is Year 10, and so on. When you plan a lesson, you place it into a specific slot. When you open the diary, you see each day populated with the lessons you've planned for it.
This sounds simple, but it removes a significant category of mental overhead: the constant cross-referencing between "what have I planned" and "when am I teaching it". The two things are in one place.
Bumping lessons forward
Every teacher has experienced the assembly that runs long, the fire drill, the class that needed more time on last lesson's topic. The lesson you'd planned for Thursday doesn't happen. Now you have a gap in your sequence, and everything downstream needs to shift by one.
In a paper planner, this means manual re-entry or a tangle of arrows and asterisks. In ScholaPlan, you bump the lesson forward — it moves to the next slot in the sequence, and subsequent lessons shift accordingly. The sequence is preserved; the only thing that changed is when each lesson falls.
Units and timetable integration together
The most powerful combination is unit plans linked to timetable slots. In ScholaPlan, you build a unit — a sequence of lessons for a topic — and push it to your timetable. The unit's lessons populate your diary slots in order, automatically.
If you update the unit plan later — a new activity for lesson three, a changed objective for lesson five — those changes flow through to the scheduled lessons. You edit once; every instance updates.
For a teacher with multiple classes studying similar content at different paces, this is the difference between managing one version of the truth and managing six separate copies that slowly diverge from each other.
Copying plans between classes
If you teach the same topic to two different year groups or sets, timetable integration lets you copy a lesson from one class's slot to another and then adapt it for the different class profile. The copying is deliberate — you still make the differentiation decisions — but you're starting from an existing plan rather than a blank page.
The cumulative time saving
None of these features saves large amounts of time individually. Bumping a lesson forward takes thirty seconds. Pushing a unit to the timetable takes two minutes. Copying a plan across classes takes five minutes.
But these tasks happen multiple times per week, for every week of the school year. The cumulative saving across a full academic year is measured in hours. And the reduction in cognitive load — the mental energy previously spent tracking the relationship between plans and schedule — is harder to quantify but equally real.
Try ScholaPlan free for 30 days
AI-generated lesson plans for any subject, any year group. No credit card required.