Migration
Moving from Excel to automated timetabling
Spreadsheets are not a stupid way to build a timetable. They are a way that stops working at a predictable size, for reasons worth understanding before you replace them.
Why Excel works, until it does not
A spreadsheet is flexible, universally understood, and imposes no structure you did not ask for. For a small institution with one administrator who holds the whole picture in their head, it is genuinely efficient.
It fails on three specific things, all of which arrive together as an institution grows: it cannot check constraints, so clashes are found by eye; it has no single source of truth, so the version circulated on Tuesday and the version edited on Thursday diverge; and it cannot answer questions, so nobody knows what room utilisation is.
The practical threshold is usually somewhere around forty teaching staff or the moment a second person needs to edit the same timetable.**
What you have to prepare
The software is not the work. The data is.
- Room inventory with real capacities. Estates usually has better numbers than the timetabling office. Check them against a refurbishment list.
- Programme and module structure. Usually extractable from your student information system, and usually messier than expected.
- Staff records with departments and teaching loads. HR holds these, and they will not match what the timetabling office believes.
- Your constraint list, classified. Most institutions have rules written down somewhere. Almost none have classified them as hard or soft.
- Last year's timetable. Useful as a sanity check even if you do not carry it forward.
What genuinely gets harder
Honesty is more useful here than enthusiasm. Two things do get harder, at least initially.
First, you have to make implicit rules explicit. In a spreadsheet, the knowledge that a particular professor never teaches before ten lives in the administrator's head. In a system, it has to be written down — which is better in every long-term respect and considerably more work in month one.
Second, exceptions require a decision rather than a keystroke. Overriding a constraint is deliberate and recorded, where in a spreadsheet you simply typed something different. That is the point, but it feels like friction at first.
What you gain
- Clashes detected as they are created rather than found by eye
- One version, so nobody works from a stale copy
- Availability collected by lecturers themselves instead of by email
- Regeneration in under a minute when something changes
- Room utilisation and workload figures you can put in front of a committee
- Publication to web, mobile, signage and email from one source
- Change notifications that reach exactly the people affected
A sensible way in
Do not migrate everything at once. Take one faculty, ideally one with a moderately awkward timetable, and run it in parallel for one cycle. You will discover your data problems on a manageable scale, and you will have a working example to show the departments that are resisting.
Export one faculty's courses, rooms and lecturers to Excel and import that — our support team helps trial users map columns at no charge. Download the trial.
Want to see this working?
Book a 45-minute online presentation and we will walk through it against your institution's own scheduling problem.