Spreadsheets are not the enemy. In many higher education teams, they are the first tool that makes academic staffing manageable: fast to build, easy to edit, and flexible enough for messy real-world planning. But a spreadsheet becomes risky when it quietly stops being a working document and becomes the institution’s staff allocation system.
That is the hidden cost of managing academic staff in spreadsheets. The problem is not simply that someone might mistype a cell. The deeper issue is that staffing decisions become dependent on fragile files, undocumented judgement, disconnected feedback, and manual reconciliation. Spreadsheet risk is not hypothetical: researchers Stephen Powell, Barry Lawson, and Kenneth Baker studied operational spreadsheets and found errors in 0.8% to 1.8% of formula cells. Ray Panko’s long-running review of spreadsheet research reached a blunt conclusion: spreadsheet errors are common, hard to detect, and often underestimated by the people who build them.
In academic staffing, the consequences may not look like a financial scandal. They look like timetable delays, double-booked lecturers, overlooked preferences, uneven workload, missing context, and allocation decisions that are hard to explain later.
1. Spreadsheets Work Until They Become Infrastructure
A spreadsheet is useful when it is a temporary planning aid. It becomes risky when it becomes the main source of truth for staff availability, lecturer preferences, subject fit, campus constraints, survey signals, and final teaching allocations.
-
Version Drift: A coordinator may have one copy of the allocation file, an administrator may have another, and a lecturer may be responding to an older export. The issue is not just duplication. It is that no one can easily prove which version represents the current institutional decision.
-
Silent Errors: Spreadsheet mistakes often look normal until someone notices the result is wrong. The JPMorgan “London Whale” investigation is a well-known example outside education: a spreadsheet formula in a risk model divided by a sum instead of an average, contributing to understated risk reporting. Academic allocation is not investment banking, but the pattern is relevant: manual models can produce confident-looking outputs from fragile logic.
-
Hidden Decision Logic: In many staffing files, the most important reasoning is not in the table. It is in colours, comments, side notes, emails, and the memory of the person who built the sheet. That makes the decision hard to audit, hard to transfer, and hard to defend.
2. Staff Allocation Is a Constraint Problem, Not a Data Entry Task
Academic staff allocation looks simple only when viewed as a list of names beside classes. In reality, it is a recurring scheduling and assignment problem with hard constraints and soft preferences. A survey of university course timetabling research by Babaei, Karimpour, and Hadidi describes university timetabling as an NP-hard scheduling problem, where institutions must satisfy mandatory constraints while also trying to optimise preferences.
-
Hard Constraints: A lecturer cannot teach two classes at the same time. A class should not be assigned to someone who is unavailable. A campus-based class may require a lecturer who can physically attend that location. These rules determine whether an allocation is valid.
-
Soft Constraints: Subject preference, location preference, workload balance, teaching continuity, and past experience may not always be absolute, but they still matter. Ignoring them can create allocations that are technically valid but operationally poor.
-
Human Context: Not every valid allocation is the right allocation. Administrators often understand local context that a timetable alone cannot capture: staff development goals, recent workload pressure, student cohort needs, or a lecturer’s suitability for a particular subject.
This is why spreadsheets struggle as the allocation workload grows. They can store information, but they do not naturally enforce constraints, explain rankings, preserve decision history, or separate system suggestions from final human judgement.
3. The Cost Is Not Just Time. It Is Lost Traceability.
The obvious cost of spreadsheet-based allocation is administrative time: collecting availability, updating staff records, checking clashes, copying old files, and rebuilding the process every teaching period. But the deeper cost is traceability.
-
What Was Considered? If an administrator compared three possible lecturers for a class, was that comparison recorded anywhere? Or did it disappear once the final name was typed into the timetable?
-
Why Was Someone Chosen? A spreadsheet can show the final allocation, but it often cannot explain whether the decision was based on availability, subject fit, staff preference, workload balance, survey trends, or a manual override.
-
Who Changed the Decision? If an allocation changes after review, the institution should be able to see who changed it, when it changed, and why. NIST’s guidance on computer security log management makes the same broader point for enterprise systems: logs are not just technical noise; they support accountability, investigation, and reliable organisational processes.
In staffing workflows, auditability is not just a compliance feature. It protects institutional memory. It allows future administrators, account owners, and auditors to reconstruct the path from input data to recommendation to final allocation.
4. Disconnected Feedback Makes the Spreadsheet Problem Worse
Many institutions collect student feedback, but that feedback often lives in a different tool from the staff allocation process. This creates a second problem: the data exists, but it is not structurally connected to future decisions.
-
Feedback Becomes Detached: If survey results are stored separately from lecturers, subjects, classes, and terms, administrators must manually interpret and transfer that signal into allocation planning.
-
Feedback Can Be Misused: Student feedback can be useful, but it should not become the only measure of teaching quality. Uttl, White, and Gonzalez’s meta-analysis found no significant correlation between student evaluation ratings and student learning in multisection studies. Anne Boring’s research in the Journal of Public Economics also found evidence of gender bias in student evaluations of teaching.
-
Context Gets Lost: A raw score in a spreadsheet does not explain class size, subject difficulty, delivery mode, response rate, or historical pattern. Without context, feedback can become a misleading number rather than a useful signal.
The better model is not to ignore feedback. It is to connect feedback carefully: link it to the right lecturer, subject, class, and term, then treat it as one factor within a broader decision-support process.
5. Decision Support Is the Better Alternative to Spreadsheet Control
The goal is not to replace administrators with an algorithm. The goal is to remove unnecessary manual comparison while preserving human judgement. A 2024 Decision Support Systems study by Xue and colleagues on course scheduling and instructor assignment found that a decision-support model could reduce course sections by 14%, translate that into about $130,000 in annual savings, reduce new courses assigned to instructors by up to 81%, and reduce distinct course sections assigned to instructors by 29%.
-
Structured Inputs: Availability, subject preferences, location preferences, employment status, classes, survey aggregates, and historical allocations should be stored as structured records, not scattered across files.
-
Reviewable Recommendations: A system should generate ranked suggestions based on clear criteria, then let administrators inspect score breakdowns and reason codes before making the final decision.
-
Human Overrides: The top-ranked option will not always be the right real-world choice. A good allocation system should allow administrators to override recommendations, but it should also record the reason so the decision remains explainable.
Conclusion
Spreadsheets are excellent working tools, but they are weak institutional memory. They can help a coordinator think through a staffing problem, but they are not designed to manage constraints, preserve explanations, connect feedback, enforce access control, or maintain a reliable audit trail over time.
As academic staffing becomes more complex, institutions do not necessarily need a massive enterprise replacement. They need a focused decision-support layer: one that connects staff availability, lecturer preferences, class requirements, survey-linked feedback, recommendation logic, human approval, override reasons, and final allocation history. This is where platforms like StaffSense make sense: not because spreadsheets are useless, but because staffing decisions deserve more structure, traceability, and accountability than a spreadsheet can reliably provide.