Who this page is for
If your school still builds timetables by hand — printed cards, whiteboards, or a single planner working through a spreadsheet for weeks — this page is for you. It is not an argument that manual is wrong. For small, stable schedules with one planner who knows every constraint, manual placement is often the simplest answer.
It becomes the wrong answer when manual effort starts to crowd out other work, when one absent planner means the timetable is stuck, or when the change rate outpaces the rebuild rate.
When manual still works, when it stops
When manual still works
Small schedules, one or two planners, a stable structure, few cross-cohort dependencies, and a team that already knows every constraint by heart.
Manual placement is also a useful baseline. Many schools that adopt automation keep the option of manual edits for the last few percent of a timetable — pinning critical placements and letting the solver work around them.
When it stops being viable
Multiple campuses, mixed cohorts, frequent changes, individual pathways, or any cohort big enough that gap-hour balancing stops being something a person can hold in their head.
The failure mode is rarely one bad timetable. It is the cumulative cost: weeks of planner time, fragile knowledge concentrated in one person, and a backlog of fixes that lands on teachers in the first week of term.
The alternatives, in order of effort
Spreadsheet templates
Lower effort than blank Excel, still manual placement. Useful for small schools and as an export format.
Legacy automatic generators
Solver-based generation built around traditional settings, modules, and constraint dialogs. Strong once configured; setup and tuning are most of the work.
Legacy enterprise suites
Broad ecosystems with publication, substitution, and communication modules. Steep learning curve and slow real-world optimization cycles.
AI-native planning platforms
Planning, generation, and editing share the same model. Validated AI commands assist planners without bypassing constraints. Newer category; Smootables sits here.
Signs you have outgrown manual
If two or three of these are true, manual placement is probably costing more than it saves:
- Building the next term takes longer than the previous one did
- Late changes cause cascading conflicts that take days to clean up
- Only one person in the school can finish a timetable end-to-end
- Teachers find conflicts after publication and have to be re-allocated
- Mixed cohorts and individual pathways are tracked in a separate document
- Workload conversations happen only after the timetable is published
A low-risk path from manual to assisted
- Pick one campus, one program, or one period as a pilot scope.
- Model that scope in a tool that supports planning and generation in one workspace.
- Run the existing manual process and the new workflow in parallel for one cycle.
- Compare results: time spent, conflicts caught, late changes handled.
- Expand to the rest of the school in subsequent cycles, keeping manual edits as a fallback for last-mile placements.
Why Smootables is the assisted option, not a black box
Automated timetabling has a reputation problem with planners — partly earned by older tools that produced opaque results and asked planners to trust them. Smootables is designed for the opposite stance: the solver respects hard constraints, pre-solve validation explains gaps before the run, infeasibility reports explain failures after the run, and planner edits, branches, undo, and audit logs keep the planner in control.
The AI assistant works the same way. It uses validated planner commands, runs scenario comparisons, and explains tradeoffs — it does not silently apply changes.
Questions about moving away from manual timetabling
Will the planner lose control?
No. The planner defines the data, priorities, and constraints. The solver places lessons that fit; the planner edits, pins, and approves. The AI assistant works through validated commands, not direct changes to school data.
Do we have to change everything at once?
No. The migration steps above are designed to keep manual placement as a fallback while you validate the assisted workflow on a scoped pilot.
What about constraints we have never written down?
Schools often discover unwritten constraints when they try to model them. That is part of the value: the constraints become explicit, reviewable, and reusable next year.
Is automatic generation slower than manual for small schedules?
For very small schedules, manual can be faster in absolute terms. The benefit is repeatability and resilience — the next term, the next year, or the next change does not start from scratch.
How does this compare to a legacy generator?
Legacy generators are strong at the solve step but treat planning, workload, and individual pathways as adjacent problems. Smootables is designed to keep them in one model.