Who this page is for
If your school still runs its timetable in Excel — or Google Sheets, or a combination of both — this page is for you. It is not an argument that spreadsheets are wrong. They are flexible, familiar, and cheap. For some schools they will be the right tool for years.
It is a comparison for the moment a planner starts to feel that the spreadsheet is no longer the right place for the plan: when version control breaks, when conflicts are hard to see, when one teacher's change cascades through three sheets, or when the team has grown beyond the one person who understands the formulas.
Where Excel works well, where it breaks down
Where Excel still works
Small schedules, one or two planners, a stable structure, infrequent changes, and a team that already knows the spreadsheet by heart.
It is also a strong export format. Many schools that move planning into a dedicated tool keep Excel for monthly reports, audits, and ad-hoc sharing.
Where it starts to hurt
Multiple campuses, mixed cohorts, individual pathways, frequent changes, more than two planners working at once, or any constraint complex enough to need a formula nobody trusts.
The failure mode is rarely a single broken cell. It is a slow erosion of confidence in the data, until nobody can answer 'is this current?' without checking with the planner.
How Smootables is different
Smootables is designed to replace spreadsheet-based planning across academic years, terms, courses, resources, timetable generation, publishing, and daily changes. Spreadsheets can remain an import and export format — many schools keep them for reporting — but planning decisions and data live in Smootables instead of scattered files.
The planning model is structured: years, terms, courses, teachers, rooms, equipment, groups, and individual students are first-class entities with relationships, constraints, and validation. The solver works on the same data, so generation is not a separate export step. AI helps planners run validated commands, explain tradeoffs, and improve schedules without bypassing hard rules.
Comparison on the dimensions that usually decide it
| Dimension | Manual Excel / Sheets | Smootables |
|---|---|---|
| Best fit | Small or local planning where flexibility matters more than automation | Schools needing structured planning, flexible periods, individual pathways, solver generation, and AI-assisted workflows |
| Collaboration | Version control depends on file-naming and discipline | Multi-planner collaboration with presence, permissions, and audit logs |
| Validation | Formula errors hide silently; conflicts can ship to a published timetable | Pre-generation validation explains missing data, overloads, and infeasibility before any solve |
| Timetable generation | None, unless you build custom scripts or macros | Solver-based generation with hard and soft constraints, infeasibility reports, and a waiting area |
| Individual pathways | Possible only through manual spreadsheet discipline | First-class group, individual, and per-placement exemption support |
| Daily changes | Each change is a manual edit across dependent sheets | Substitutions, comments, audit logs, and recovery connected to the master timetable |
| Cost | Low tool cost, high planner time cost as complexity grows | SaaS cost offset by less manual rework, fewer errors, and faster regeneration |
Evaluation checklist for your school
If you are deciding whether to move off spreadsheets, this checklist usually points the answer one way or the other:
- More than two planners actively editing the timetable at the same time
- Individual pathways, exemptions, or mixed cohorts that do not fit cleanly into a class grid
- Specialist rooms, workshops, or equipment that have their own constraints
- A formula or macro that only one person fully understands
- Spreadsheet errors that reached teachers, students, or parents in the last year
- Year planning data that is not currently being used as timetable input
A phased migration path
Most schools that move from Excel to Smootables do it in phases, not in one weekend.
- Run one term in parallel. Keep Excel as the published source of truth while you model the same period in Smootables.
- Use Smootables for the next year's plan — multi-year planning, workload, and resourcing — before you commit to switching timetable generation.
- Switch timetable generation for one campus, program, or period. Keep Excel for reporting and audits.
- Roll out to the rest of the school once one full cycle has been published from Smootables.
- Keep Excel as an export format for reporting and audits. The plan no longer lives there, but the workflows that depend on Excel can continue.
Questions about moving off spreadsheets
Do we have to stop using Excel completely?
No. Excel can stay as an import, export, and reporting format. The shift is moving the planning model itself out of spreadsheets, not abandoning the format.
How long does migration usually take?
Most schools we work with run one term in parallel before switching the published source of truth. Smaller schools can move faster; multi-campus schools usually take longer.
Can we keep our existing column structure?
Smootables supports structured import with column mapping and AI-assisted extraction for messy files. You do not need to clean the spreadsheets perfectly before importing.
What if our planner leaves?
Knowledge that lives in a planner's head and a private spreadsheet leaves with them. A structured planning model, audit logs, and role-based access make handover possible.
Is this overkill for a small school?
Possibly. Spreadsheets remain a reasonable choice for small, stable schedules. Smootables is built for schools that have outgrown that — see the manual timetabling alternatives page for the wider spectrum.