Key takeaways
- Spreadsheet risk starts when timetable data has no audit trail.
- Conflicting versions across people and departments make the current record hard to prove.
- Manual conflict checks are slow and can miss double-bookings until late.
- Use concrete clash and version evidence before deciding how to change the process.
Why does no audit trail matter?
Without an audit trail, planners cannot easily prove who changed timetable data, when the change happened, or which version should be trusted. That matters when departments hold different copies of the same teacher, room, class, or period data.
The risk is not that a spreadsheet cell exists. The risk is that the planning team cannot trace decisions when files diverge.
What risk signals should planners look for?
Look for evidence that the same timetable data exists in more than one active place.
- More than one current spreadsheet in use
- Different departments keeping their own copies of timetable data
- Manual checks used to find teacher or room clashes
- Late discovery of double-booked teachers or rooms
- Disagreement over which file is authoritative
- Rework after week-one conflicts appear
How do you run a simple risk review?
Keep the review factual. The aim is to find where version and clash risk enters the planning process.
- List every spreadsheet used for timetable planning.
- Record who updates each file and which department uses it.
- Mark places where the same teacher, room, or class data appears twice.
- Collect recent examples of late clashes or double-bookings.
- Identify which file is treated as current when copies disagree.
- Decide which risks must be fixed before migration or the next planning cycle.
How should sourced examples be used?
Use examples as warning patterns, not as universal statistics. A teacher double-booked into Room 104 and the Gym shows the kind of error a spreadsheet may not understand. The 2,000-student case shows that long manual work in Excel can still leave week-one conflicts.
Do not turn those examples into a rule for every school. Use them to ask whether your own files can detect the same type of clash before publication.
What should be fixed before a process change?
First, reduce conflicting versions. Then make clash evidence visible. If manual checking is the only way to find a teacher or room conflict, record where that check happens and who is responsible for it.
This gives the planning team a cleaner starting point for data preparation or a later migration plan.
What question does this guide answer?
This guide answers one question: where does spreadsheet use create timetable risk before migration? It does not decide whether a school should keep Excel, move to software, or use a hybrid process.
For capability evaluation, use the linked Excel comparison page. For process work, keep the focus on audit trail, conflicting versions, and late clash detection.
Questions planners ask about spreadsheet risk
What is the main timetable risk in spreadsheets?
The verified risk is loss of control: no audit trail, conflicting versions, and clashes found late through manual checks.
Is this only a problem after publication?
No. The risk builds during planning when different people or departments work from different versions of the same data.
What evidence should we collect first?
Collect examples of conflicting files, double-booked teachers or rooms, and clashes that were found only after manual checking.