Why spreadsheets fail at thesis supervision
Almost every department starts the same way. One coordinator opens a spreadsheet, adds a column for each student, a column for each milestone, and shares the link. For a single supervisor with five students, it works.
It keeps working right until it doesn't — and the failure is rarely dramatic. Nothing crashes. The sheet just stops being true, and nobody notices until somebody needs it to settle a dispute.
The four failures, in the order they arrive
1. The sheet stops matching reality
A spreadsheet records what someone typed, not what happened. A student submits a chapter on Thursday; the coordinator updates the sheet the following Tuesday, or forgets. By mid-semester the sheet and the shared drive disagree, and there is no way to tell which one is wrong.
The moment your tracker has to be manually synced with the actual work, it has stopped being a source of truth and become a second thing to maintain.
2. Feedback lives somewhere else
The sheet tracks status. It cannot hold the actual supervision — the comments on chapter three, the reason an extension was granted, the discussion about scope that happened over email in March.
That content ends up scattered across inboxes, WhatsApp threads, and margin comments in files that get overwritten. When a student asks "what did you want me to change?", the answer exists, but finding it takes twenty minutes of searching.
3. Nothing is provable
This is the failure that actually hurts.
A file on a shared drive has one timestamp: when it was last modified. Overwrite it and the previous version is gone, along with any evidence of when it first appeared. So when a student says they submitted on time and a supervisor says they didn't, there is no record — only two accounts and a file whose date has moved.
Most departments resolve these disputes on trust and memory. That works until the stakes are high enough that someone escalates.
4. It does not survive a handover
Supervisors go on leave. Coordinators change. The person who designed the column layout graduates or moves on. What is left is a sheet whose conventions nobody remembers — half-filled columns, a colour code with no legend, three tabs that may or may not be current.
Institutional memory that lives in one person's spreadsheet is not institutional memory.
What the department actually loses
Each failure costs something specific:
- Disputed deadlines — resolved by argument rather than record
- Lost feedback — the same guidance given twice because the first time is unfindable
- Invisible risk — a student four weeks behind is indistinguishable from one on track until the viva
- Audit gaps — no defensible answer when an examination board asks what happened and when
None of these are spreadsheet bugs. They are the consequence of using a document as a system of record when a document cannot timestamp, cannot version, and cannot enforce.
What replaces it
The fix is not a better spreadsheet. It is moving the three things a sheet cannot hold into something that can:
- The submission itself, stored immutably and checksummed at the moment it lands — so its existence and timing are facts, not claims
- The feedback, attached permanently to the version it refers to rather than living in an inbox
- The timeline, computed from real events rather than typed in by hand
Once those three are in one place, the spreadsheet's remaining job — showing who is where — becomes a view of the data rather than the data itself. And a view that is generated cannot drift out of date.
That is the whole argument for a dedicated supervision platform. Not that spreadsheets are bad tools, but that supervision needs a record, and a spreadsheet was never designed to be one.
Supervizo keeps every submission immutable and checksummed, with feedback threaded onto the exact version it addresses. See how it works, or look at the plans.