The timetable: two weeks of work that should take an afternoon
Every school has one person who builds the timetable on paper, understands all of it, and cannot go on leave in August. That is a risk, not a skill to celebrate.
Engineering·27 August 2026·6 min read
In most schools, the timetable is built by one senior teacher over a fortnight, using large sheets of paper, pencil, and a great deal of institutional memory. It is genuinely skilled work, and it is a single point of failure that the whole academic year rests on.
Write the constraints down first
The reason timetable software disappoints is almost always that the constraints live in someone's head and were never stated.
Before generating anything, collect them: teacher availability and part time days, subject periods per week per class, room and lab requirements, shared resources, section splits, and the informal rules such as no double periods of the same subject after lunch.
Writing them down has value even if you never buy software, because it makes the school's real scheduling policy visible for the first time.
Generate a draft, then apply judgement
A generator gets you to a valid, conflict free draft in minutes. What it cannot know is that one teacher is carrying an unusual load this term, or that a particular pairing of classes is a bad idea for reasons everyone remembers.
So the workflow that works is generate, review with the people who know, adjust, and publish. Two hours instead of two weeks, and the knowledge is now in the system rather than only in a person.
Substitution is the daily version of the same problem
This is where schools feel the benefit most often, because it happens every day rather than once a year.
- Who is absent today, known early rather than at the bell.
- Which periods need cover.
- Who is genuinely free, according to the timetable rather than memory.
- Fair distribution, so the same helpful teacher is not covering four periods a week.
- A record of who covered what, which matters for workload and for pay.
Publishing is not an afterthought
A timetable change that reaches the staff room notice board but not the teachers' phones will be missed by somebody.
When the timetable lives in the same system as staff and students, a change publishes to everyone at once, including parents where relevant, and yesterday's printed copy stops being the source of truth.
Where it sits in the school system
SchoolPilot keeps the timetable alongside the student information system, attendance and staff records, so periods, teachers, rooms and substitutions all reference the same data, and attendance is taken against the class that is actually running.
The timetable is too important to depend on one person's fortnight. Capture the constraints, generate the draft, keep the judgement, and make daily substitution a two minute task instead of a corridor negotiation.
Frequently asked questions
Can software generate a timetable automatically?
It can generate a valid one quickly, which is most of the work, but the last ten percent usually needs human judgement about preferences and fairness that no school writes down. Treat automatic generation as a strong first draft you adjust, not as a finished product.
What usually breaks a generated timetable?
Constraints nobody mentioned: a teacher who leaves early on Fridays, a hall shared with another section, a lab that needs setup time between classes, a subject that must not be last period. Collect these before generating, because adding them afterwards means starting again.
How should daily substitutions be handled?
By the system, in the morning, against who is actually free. Substitution decided on paper at the staff room door produces double booked teachers and classes left unsupervised, and nobody can reconstruct afterwards who covered what.