The spreadsheet that became a system when no one was looking, how a workbook turns into critical infrastructure

There is a spreadsheet in your business that everyone is a little afraid to touch. You probably know exactly which one as you read this.

How it happened

It started innocently. Someone needed to track a few things, so they opened a workbook. It worked, so they added a tab. Then a formula that referenced the first tab. Then a second person started using it, then a third, and at some point a process that the whole team depends on quietly moved inside a grid of cells that one person understands and nobody documented.

That is the pattern. A spreadsheet does not announce the day it stops being a spreadsheet. It just gradually takes on more weight until it is holding up part of the business, and the moment you notice is usually the moment something goes wrong.

The tells

The tells are consistent. One wrong paste and a column of numbers is gone, with no version history to recover them. A single person really understands how the formulas connect, and when they are on leave the work stops or, worse, carries on with mistakes nobody catches. New starters are told to be careful with it rather than shown how it works, because no one fully remembers anymore.

None of this means spreadsheets are bad. They are a brilliant place to start, precisely because they are so easy to begin. The problem is not the tool. It is that a tool meant for quick, personal calculation has been promoted, without anyone deciding to, into shared infrastructure it was never designed to be.

What it is missing

What it now lacks is everything a real system has. There is no audit trail, so you cannot see who changed what or undo a bad edit. There is no validation, so a typo becomes a fact. There is no separation between the people who need to read the numbers and the people who can break them. And there is no backstop when the one person who understands it is unavailable.

The fix is smaller than the fear

The good news is that the fix is almost always smaller than the fear. The logic inside the workbook is usually sound. It captures real knowledge about how the business runs, often better than any official document. What it needs is not replacing but rehoming: moving that logic somewhere with history, permissions, and a backup, so the knowledge survives a wrong paste or a holiday.

That move does not have to be dramatic, and it rarely means throwing the spreadsheet away on day one. It means recognising that the workbook has been doing a system's job without a system's safety net, and giving it one before the day it lets you down.

If you have a workbook like this in mind, that is a good place to look first. Our automation audit will help you see how exposed it really is, and what the smallest safe step away from it looks like.