Office operations
Why Schools Outgrow Spreadsheets (And What Actually Replaces Them)
Spreadsheets are not the villain of this story. They are the reason most school offices function at all. But there is a specific, recognisable point where a workbook stops being the right home for a school’s records — and it has nothing to do with being old-fashioned. This post names that point, is honest about what spreadsheets still do best, and shows how to move without a big-bang switch.
Spreadsheets are why your school runs at all
Before anyone says a word against spreadsheets, let us say something for them. Excel and Google Sheets are two of the most successful tools ever put in front of a school office. They cost almost nothing, they bend to any process, and the person who needs a tracker can build one in an afternoon without asking anyone’s permission. The admissions tracker, the fee register, the staff leave sheet — in most Indian schools these exist because someone in the office cared enough to build them. That deserves respect, not a sales pitch.
So this post will not tell you spreadsheets are outdated. They are not. A well-kept workbook is a serious piece of work, and a school that runs on workbooks is usually running on the dedication of two or three people who know them cell by cell. If that is your school, nothing here is aimed at you. It is aimed at a moment — a specific, recognisable moment — when the tool stops fitting the job it has been quietly doing for years.
That moment has nothing to do with fashion or technology cycles. It comes from four structural limits built into what a spreadsheet is: no row has an owner, no cell has a history, copies multiply the moment a file is shared, and the knowledge of how it all works lives in one person’s head. Each limit is invisible while a school is small. Each one becomes expensive as it grows. The rest of this post walks through them one at a time.
Nobody owns a row, so stalled work stalls silently
Open your admissions tracker. Somewhere in it there is an enquiry from six weeks ago — documents partially received, follow-up column blank, status still marked ‘pending’. Whose job is that row? The honest answer in most offices is: whoever happens to notice it. A spreadsheet can record that a case exists, but it cannot assign the case to a person, and it cannot object when nobody moves it. Accountability — knowing exactly who is responsible for finishing a piece of work — is not a column you can add.
You can see the symptom in the tracker itself. Columns added by four different people across four admission seasons: one for ‘called?’, one for ‘remarks’, one for ‘remarks 2’, one that nobody remembers adding. Each column is a well-meant attempt to make the sheet carry responsibility. None of them works, because a cell saying a particular clerk should follow up does not notify that clerk, does not remind them, and does not escalate to anyone when the week passes. The sheet holds information. It cannot hold anyone to anything.
The cost is quiet. There is no crash and no error message — just an enquiry that goes cold, a transfer certificate that sits unissued, a concession request a parent has to raise three times. Small schools absorb this because everyone knows everything. Past a few hundred students, ‘everyone knows everything’ stops being true, and the rows with no owner start turning into phone calls to the principal — usually during admission season, when open cases are at their peak and the office’s attention is at its thinnest.
A spreadsheet cannot tell you who changed a number, or why
Every school has one workbook that only one person truly understands, and it is usually the fee register. Somewhere in it, a student’s concession is different from what the trustee remembers approving. When was it changed? By whom? On whose authority? The spreadsheet cannot answer, because a cell holds only its current value. The old value is gone, the editor’s name was never captured, and the reason was never written anywhere. In software language, the missing thing is called an audit trail: a running record of who changed what, when, and why.
This matters most exactly where spreadsheets are used most: money. Fee disputes are rarely about dishonesty. They are about two honest people with two honest memories and no record to settle between them. When a parent insists the office quoted something different, or an auditor asks why one student’s dues differ from the published fee structure, the only evidence is the current state of the sheet — which is precisely the thing in question. Data integrity, meaning the confidence that a number is what it claims to be, cannot be reconstructed after the fact. It has to be recorded at the moment of change.
To be fair: Google Sheets does keep a version history, and it is better than nothing. But it records that the file changed, not why, and reading it is archaeology — scrolling timestamps, comparing snapshots, guessing intent. It is not something a clerk can produce during a fee dispute at the counter, and it vanishes entirely the moment someone downloads the file and continues working in Excel. A history you cannot practically use in front of a parent or an auditor is not really a history.
Every copy you share becomes its own version of the truth
Here is a morning that will be familiar. A class teacher photographs the attendance sheet and forwards it on WhatsApp to the coordinator. The coordinator types the numbers into her own sheet and mails a summary to the office. The office copies the totals into the master workbook. Three careful people, three copies — and by the time a correction is made in the classroom original, the other two copies are already wrong. Nobody lied and nobody was careless. The truth simply forked.
Spreadsheets fork because sharing a spreadsheet usually means copying it. The file named ‘final_v3_updated_NEW.xlsx’ is not a joke about sloppiness; it is what naturally happens when four people need to work on the same data and the tool’s only answer is ‘send me the file’. A single source of truth — one agreed place where the official version lives, which everyone reads and updates — is exactly what is lost with every forward. And once truth has forked, merging it back is slow, manual, error-prone work that always lands on whoever is most conscientious.
- The word ‘final’ appears in more than one filename for the same register.
- Two desks quote a parent two different fee balances in the same week.
- Monthly reporting begins with someone asking on WhatsApp which sheet is the latest.
- A correction must be made in more than one place, and someone keeps a mental list of those places.
- Totals in the master workbook are checked against the source sheets by hand, every single time.
The knowledge lives in one head, and it leaves with the person
Think of the most experienced person in your office — the one who built the fee workbook years ago and has grown it ever since. The lookups that pull a student’s transport slab, the colour codes that separate ‘partially paid’ from ‘cheque pending’, the hidden sheet holding last year’s structures: all of it makes sense to her, and much of it makes sense only to her. That workbook is not a file. It is her professional memory, written in formulas. And when she retires, resigns, or is simply on leave during fee week, the school discovers what it was actually depending on.
This is the limit that hurts institutions most, because it looks like loyalty right up to the day it becomes risk. Knowledge held in one head cannot be inspected, cannot be handed over in a week of shadowing, and cannot be recovered once it walks out of the gate. A process, by contrast, lives outside any individual: the steps are visible, the rules are written into the system, and a new person can take it over in weeks rather than years. Schools rarely lose data when a key person leaves. They lose the ability to use it.
What replaces a spreadsheet is one official home for each record
The replacement for a workbook is not a flashier workbook. It is a system of record — which simply means the one agreed place where the official version of something lives. When a school can say ‘the fee ledger in the system is the truth, and everything else is a copy or a report’, it has a system of record for fees. The phrase sounds like jargon, but every school already understands the idea: it is what the hard-bound admission register was, before the photocopier. Software did not invent the concept. Shared files quietly eroded it.
What separates a real system of record from a shared workbook maps exactly onto the four limits above — and this is the checklist to hold against anything you evaluate.
Notice what kind of thing this describes. It is not ‘just an ERP’ with more modules; it is a governed operating layer — some call it a School Operating System — that acts as the institution’s decision layer: the place where records are owned, changes are accountable, and leadership reads one truth instead of adjudicating between sheets. The label matters far less than the properties. Whatever you look at, SquareCampus included, test it against the four limits, because those are what you are actually buying your way out of.
- Ownership: every open case — an enquiry, a refund, an unissued certificate — is assigned to a named person, with reminders and escalation, so nothing stalls silently.
- History: every change carries who, what, when, and ideally why, so a fee dispute is settled by a lookup instead of an argument.
- One copy: everyone works on the same record, with permissions deciding who may see and change what — so there is nothing to reconcile, because nothing forked.
- Shared process: the rules live in the system rather than in one person’s formulas, so a new staff member inherits a working process instead of a mystery.
Keep your spreadsheets for the work they are genuinely best at
None of this means the spreadsheet leaves the building. It means the spreadsheet goes back to the job it is brilliant at: thinking, not remembering. A spreadsheet is a superb calculator and a poor register. Modelling next year’s fee structure across three scenarios, checking whether a proposed transport slab covers its costs, slicing an export of exam results before a staff meeting — this is one-off analytical work, exactly what the tool was built for, and no school system will ever match its flexibility there.
A workable dividing line: if a file is something you calculate with and then throw away, keep it in a spreadsheet. If it is something the school would need to produce in a dispute, an audit, or a handover, it is a record — and records need an owner, a history, and one home. Applying that one test to the files in your office will sort them faster than any vendor brochure.
- One-off modelling: fee restructures, salary scenarios, the arithmetic of adding a section.
- Ad-hoc analysis of data exported from your systems — slice it, chart it, discard it.
- Personal working notes and checklists that concern nobody else.
- Anything exploratory, temporary, or private to one person’s thinking.
Move one record at a time, without a big-bang switch
The move that fails is the big-bang switch: every register, every workflow, one go-live date, usually in peak season. The move that works is boringly incremental. Pick the single record that causes the most disputes — for most schools that is fees, for some it is admissions — and make the system the official home of that one record. Keep the old sheet running alongside it as a parallel check, and retire the sheet only when the office trusts the system more than the sheet, not on a date circled in advance.
Be equally clear about what is not being replaced. If your school already runs an ERP, a payment gateway, or a learning platform that works, nothing here argues for ripping it out. Those systems stay authoritative for what they do; the gap being closed is the set of records that live only in workbooks and in one clerk’s memory. A bounded deployment can sit alongside what you have, and consolidating genuinely fragmented tools is a later choice the institution makes for itself — never a condition someone imposes on day one.
- Start with one record, chosen by dispute count, not by a vendor’s module list.
- Move the current academic year first; migrate history later, once the office trusts the new home.
- Run old and new in parallel for an agreed period, and compare totals every week.
- Name one owner for the cutover — a person, not a committee.
- Only then pick the second record, informed by what the first move taught you.
Where SquareCampus fits
SquareCampus is built as the governed operating layer this post describes: one system of record for Indian schools and trusts, where every case has an owner, every change carries its history, permissions decide who touches what, and process outlives any individual. What that looks like module by module is on the platform page at squarecampus.com/platform/, and a plain-language explanation of the category sits at squarecampus.com/what-is-squarecampus/.
The migration approach in the previous section is also how we actually deploy: a guided sequence agreed during scoping, starting with the record your office argues about most, running in parallel with your sheets, and coexisting with whatever software you already trust. That approach is written up at squarecampus.com/rollout/. And if you never buy anything from us, the advice still stands on its own: give your records an owner, a history, and one home — and keep your spreadsheets for thinking.
Bring your most-fought-over workbook to a demo
Book a guided demo and bring the register your office argues about most. We will show you what it looks like as a governed record — with an owner, a history, and one copy — running alongside everything you already use.