Make your school year plans solid before timetable generation
A timetable usually fails before anyone presses the generate button in your timetable optimization tool.
The visible failure might come later: a teacher double-booked in September, a workshop group with no suitable room, a part-time teacher placed on a non-working day, or an option block that just cannot be build.
But the cause often sits earlier in the school year plan.
Timetable generation places agreed lessons into periods. It should not invent the curriculum structure, repair staffing assumptions, or guess which room can support a workshop. If those decisions are still unclear, the timetable solver inherits the uncertainty.
That is why the planning stage matters.
Before generation, the school needs a staffed and feasible curriculum structure. The best way to do this is to map it in a visual editor that spans across multiple academic years. That includes:
- term dates, holiday weeks, exam windows, and day profiles
- courses, subjects, modules, groups, and pathways
- teacher contracts, availability, skills, and target loads
- rooms, labs, workshops, equipment, and campus rules
- option blocks, bands, sets, and fixed points where the school uses them
- policy constraints such as lunch, breaks, gaps, and pinned commitments
In many schools, those decisions live across multiple spreadsheet files, emails, previous-year files, and some in the timetable tool. That split creates the familiar planning season problem: the timetabler is expected to produce a clean grid from inputs that were never pulled together.
A planning-first workflow to your timetabling problem changes the order, and solves both: the planning problem and the timetabling problem.
The school builds the year model first. Then it proves the model is ready for timetable placement. After this, you don’t even need hundreds of timetable optimization settings and preferences anymore, just a click of a “generate timetable” button should be enough.
Get Juho Isola’s stories in your inbox
Join Medium for free to get updates from this writer.
A typed plan is not the same as a feasible plan.
In real timetable work, planners use checks such as block build, combing chart, clash table, conflict matrix, and trial timetable runs.
Each check answers a different question:
- Block build: can this block work internally without a teacher or room being needed twice?
- Combing chart: can blocks fit together without double-booking a teacher?
- Clash table or conflict matrix: which blocks across year groups are compatible?
- Trial timetable: does the proposed structure work with next year’s real staff?
They protect the timetable from carrying structural errors into placement.
Automatic timetable generation is really useful and saves a lot of time when it works from a clear model. The planner still decides what is fixed, what can move, and which commitments matter most. A sports afternoon may be locked. A workshop may need a specialist room. A part-time teacher may only be available on certain days. A course may need double periods rather than single periods.
Those decisions should be explicit before the solve.
If they sit in an Excel file on someone’s desktop computer or in one planner’s memory, the timetable tool has to rediscover them through failed runs and manual cleanup.
Smootables treats school year planning and automatic timetabling as one data model. Most timetabling tools handle the school-year planning phase poorly or even ignore it completely expecting the school to suddenly appear with complete and polished spreadsheets.
In Smootables, the same visual and easy to use workspace holds your academic years, terms, courses, groups, teachers, rooms, equipment, workloads, constraints, and pathway assignments across multiple campuses. Pre-generation validation can then flag gaps before the timetable solver runs.
That matters because the best time to find a missing teacher, impossible workload, or unavailable workshop is before the school waits for a solve.
All timetables in Smootables are of course still editable after the automatic optimization. If planners need to move lessons, pin commitments, resolve waiting-area lessons, and compare alternatives, all of that is still doable. But those edits are just final polishing instead of trying to make the impossible timetable possible, when the underlying plan stays connected to the timetable.
Check out how Smootables handles the school year planning at https://smootables.com/en/school-year-planning
Originally published at https://www.linkedin.com.
