When should a spreadsheet become a system?

Almost every organisation runs on at least one spreadsheet that started as a quick list and grew into something everyone relies on. Admissions, attendance, donations, jobs, rotas, fees. At some point it stops being a convenient tool and becomes a risk. This guide is about recognising that point.

First, a word in favour of spreadsheets

Spreadsheets are cheap, flexible and understood by almost everyone. For working out a budget, exploring a set of figures or keeping a list that one person maintains, nothing beats them. If your spreadsheet works, nobody complains about it and it does not hold anything sensitive, leave it alone.

The trouble starts when a spreadsheet is used as a shared database: many people, live records, decisions made from it, and nobody quite responsible for it.

Seven signs your spreadsheet has become a system

1. Several people edit it, and nobody trusts which version is right

Copies named “final”, “final v2” and “use this one” are a symptom. So is a rule like “only Sarah edits column F”.

2. The same information is typed in more than once

A form arrives by email, someone copies it into the sheet, then into the finance package, then into a letter. Each copy is a chance for a mistake.

3. Simple questions take an afternoon

“How many applications are waiting?” “Who has not paid this term?” If answering needs filters, pivot tables and a careful eye, the data is there but the system is not.

4. Access is all or nothing

Anyone who can open the sheet can see every row and every column, including personal details they have no need to see. Hiding columns is not access control.

5. Nobody knows who changed what

A value is wrong and there is no way to tell when it changed or who changed it. For money, safeguarding or exam results, that matters.

6. It only works because one person understands it

The formulas, the colour codes and the hidden tabs live in one person’s head. When they are on leave, the process slows down or stops.

7. Work happens around it, not in it

Approvals in email threads, documents in a shared drive, reminders in someone’s calendar. The spreadsheet holds part of the truth, and people chase the rest.

One or two of these signs is normal. Four or more, on a spreadsheet that holds personal data or money, is a strong signal that it is time to change.

Your options, from smallest to largest

A better spreadsheet

Sometimes the right answer is structure: one row per record, data validation on key columns, a separate tab for reference lists, protected ranges and a clear owner. This costs a few days of someone’s time and can buy a year or two.

An automation

If the main problem is retyping, connecting the tools you already have may be enough. A form can create the row, send the confirmation and update the finance package without anyone copying anything. See our automation service for what this involves.

An off-the-shelf tool

If your process is common (a CRM, a booking system, a school management system), a product may already do most of it. Check that it fits how you actually work, what it costs per user as you grow, and whether you can export your data if you leave.

A bespoke system

Build something when your process is particular to your organisation, when off-the-shelf tools would need so many workarounds that staff avoid them, or when you need tight control over who sees what. A bespoke system gives you proper sign-in and roles, an audit trail, forms that write directly to the records, and reports that are always up to date. See client portals and internal systems.

A simple way to decide

Write down three things:

The hours. Roughly how long people spend each week typing, checking, chasing and fixing around the spreadsheet.
The risk. What happens if a row is wrong or the file is shared with the wrong person. Think about data protection, money and reputation.
The change. How often the process changes. A process that changes every month suits a flexible tool; one that is settled suits a system.

If the hours are significant and the risk is real, the case for a system usually makes itself. If both are low, improve the spreadsheet and revisit in a year.

How to move without disruption

The fear with replacing a spreadsheet is the switch-over. Done carefully, it is undramatic:

Map the columns to records. Every column either becomes a field, is calculated, or is dropped on purpose.
Import a copy first. Run the import on a copy of the data and check that totals and counts match the spreadsheet.
Run both for a short time. Staff use the new system while the old sheet stays available, read-only.
Switch off the old sheet. Archive it, restrict access and point everyone to the new system.