Key takeaways
- Manual placement still fits small, stable schedules with one expert planner.
- Alternatives range from spreadsheet templates to established generators and AI-powered planning workspaces.
- Pilot one campus or program in parallel before school-wide rollout.
- Smootables keeps planners in control with validation, generation, and AI-assisted editing.
Who should read this guide to manual timetabling alternatives?
If your school still builds timetables by hand, with printed cards, whiteboards, or weeks in an Excel workbook, this page is for you. Manual placement, spreadsheet templates, established generators such as aSc Timetables, and suites such as Untis and WebUntis sit on a spectrum; this guide compares them fairly. For small, stable schedules with one planner who knows the constraints, 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. For the structured workflow that replaces fully manual placement, see how to create a school timetable.
When does manual timetabling still work, and when does it stop?
Manual placement still works for small, stable schedules with one expert planner; it stops scaling under multiple campuses, mixed cohorts, and frequent change. The two columns below show when hand-built timetables in print, Microsoft Excel, or Google Sheets still beat a Smootables-style automated workflow, and when they no longer do.
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.
What are the alternatives to manual timetabling, in order of effort?
Alternatives to manual timetabling sit on a spectrum of effort (including automatic school timetabling once data is structured): spreadsheet templates in Microsoft Excel, established automatic generators such as aSc Timetables, broad suites such as Untis and WebUntis, and AI-powered planning platforms like Smootables. The cards below order them by setup effort.
Spreadsheet templates
Lower effort than blank Excel, still manual placement. Useful for small schools and as an export format.
Established automatic generators
Solver-based generation built around settings, modules, and constraint dialogs. Strong once configured; setup and tuning are most of the work.
Established timetable suites
Broad ecosystems with publication, substitution, web access, and daily-operations modules. Setup and learning curve deserve careful evaluation.
AI-powered planning platforms
Planning, generation, and editing share the same model. Planners reshape plans and timetables in natural language without bypassing constraints. Newer category; Smootables sits here.
What are the signs you have outgrown manual timetabling in 2026?
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 from setup to publication
- Teachers find conflicts after publication and have to be re-allocated
- Mixed cohorts and individual pathways are tracked in a separate document
- Teacher workload planning conversations happen only after the timetable is published
How do manual timetabling alternatives compare in 2026?
The table compares four common approaches: manual or Excel placement, established generators such as aSc Timetables, suites such as Untis, and AI-powered school timetabling platforms like Smootables. It focuses on setup effort, automation, validation, and where planner time goes.
| Dimension | Manual / Excel | Established tools (aSc, Untis) | Smootables |
|---|---|---|---|
| Setup effort | Low to start, grows each term | Settings, modules, and constraint dialogs before generation | Guided setup on a structured planning model |
| Automation | None; every placement is manual | Strong solver once configured | Solver plus a built-in AI planner assistant |
| Validation | Errors usually found after publication | Testing, verification, diagnostics, and conflict checks around generation | Pre-solve validation with infeasibility reports |
| Individual pathways | Tracked in a separate document | Student-choice support depends on the product model and licensed modules | Group, individual, and per-placement exemptions |
| Where planner time goes | Manual rebuilding each cycle | Tuning settings between runs | The plan itself, not the tool |
What is a low-risk path from manual to assisted timetabling in 2026?
Moving off manual placement does not have to be risky. The low-risk path below pilots one scope in a tool that combines planning and generation, such as Smootables, alongside your existing manual or spreadsheet process, so you can compare results before committing.
- 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.
How do established tools compare to a modern planning workspace?
Established timetable suites such as Untis and aSc Timetables are capable tools. Untis supports weighting-based optimization, diagnostics, manual scheduling, modules for cover and publishing, MultiUser workflows, and WebUntis access. aSc Timetables offers a broad constraint catalog, testing and verification before generation, automatic generation, manual editing, online and desktop options, and student-course features.
The tradeoff is setup style. Reviews of Untis and aSc both mention learning curve and up-front configuration, especially when schools use advanced constraints and modules. Smootables takes a different path: a structured planning model, validation that explains gaps before generation, and an AI planner assistant in the same workspace.
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 handles bulk updates and large changes that would take hours by hand, while the planner stays in control.
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 an established generator?
Established generators are strong at the solve step. Smootables is designed to keep planning, workload, generation, and individual pathways in one model.