Spreadsheets are one of the best tools ever made. They are flexible, familiar and fast. That is exactly why they end up running things they were never meant to run.
The trouble is that nobody decides to build a system in a spreadsheet. It just happens, one helpful formula at a time. Here are seven signs it has already happened.
1. There is a "master version"
If your team has a naming convention to tell which file is the real one (final, final_v2, final_USE_THIS), the spreadsheet is acting as a database without any of the protection one provides.
2. Only one person really understands it
When someone goes on holiday and a process quietly stops, you have a single point of failure disguised as a file.
3. Colours and comments carry meaning
Yellow means "waiting for approval", red means "urgent", and a cell comment says who is dealing with it. Those are statuses and assignments, which means you have a workflow with no way to enforce it.
4. People copy data in from somewhere else
Every manual copy is a chance for an error and a delay. If the data comes from another system, that is an integration waiting to happen.
5. You email it around
The moment a spreadsheet is attached to an email, you have multiple versions and no audit trail. Nobody can say who changed what.
6. You are afraid to touch it
If nobody dares add a column in case something breaks, the file has become fragile infrastructure.
7. It has outgrown a single screen
Hundreds of rows, a dozen tabs, lookup formulas that reference other files. At that point you are fighting the tool.
Why this keeps happening
Spreadsheets win because they are instant. Nobody needs approval, a budget or a developer, so a clever person builds something useful on a Tuesday afternoon. That is a strength. The trouble comes later, when twenty people depend on that Tuesday-afternoon file and the person who made it has moved on, or the business has doubled in size.
A quick self-assessment
Count how many of the seven signs apply to your most important spreadsheet. Then ask three more questions: what would happen to the business if this file vanished tomorrow? How many people could rebuild it from memory? And how many hours a week does your team spend feeding it, checking it, or fixing it? If the answers are uncomfortable, you already know.
What to do about it
Not every spreadsheet needs replacing. If one or two signs apply, tidy it up, document it and carry on. If four or more apply, it is probably worth asking whether a small, purpose-built system would save more time than it costs.
What replacement involves
Replacing a spreadsheet system rarely means a giant project. Often it is a small, focused tool that does the three or four things the spreadsheet does badly: enforcing who can change what, keeping one version of the truth, sending reminders, and showing a clear status. Many teams keep exporting to a spreadsheet for analysis, and that is fine. The aim is to stop using it as the system of record. If you are weighing it up, our guide to custom software vs off-the-shelf shows how to decide.
The best first step is cheap: write down what the spreadsheet actually does, who uses it, and what would happen if it disappeared tomorrow. That description is also the start of a good software brief.