The spreadsheet that became a system

Somewhere in your business there is a file with a name like Master Job List FINAL v7.xlsx. It began as a list. Then it grew a second tab, then a formula that reads the second tab, then colour coding that means something to two people. At some point a new starter was told, on their first morning, "whatever you do, don't sort it".

Nobody decided to build a system. But that is what it is now.

This is one of the most common jobs we are called in for, and the call rarely comes because the file broke. It comes because the person who understands the file handed in their notice, or because a second person started editing it and the numbers stopped agreeing. The file was fine. The arrangement around it was not.

How to tell the file has crossed over

A spreadsheet is a document: one author, one purpose, disposable. A system is different, and the difference is observable. The file has crossed over when a few of these are true:

It has users, not readers. People besides its author put data in, and they were trained to do it, informally, by someone who was trained the same way.
Other numbers depend on it. Invoices are typed from it. The month-end figures start from it. If a cell is wrong, the error leaves the file and lands somewhere with a client's name on it.
It has laws that live in memory. Don't touch column K. Never delete a row, strike it through. The rules are real, and they are written down nowhere.
It has opening hours. One person edits it, so nothing happens on the days that person is away.
People ask "is anyone in the file?" before opening it. That question is a lock, and you are the locking mechanism.

Two of these and you have a lively document. Four and you are running a system, with none of the things systems are built to provide: a history of who changed what, rules the software enforces rather than remembers, and more than one pair of hands.

This is not a story about carelessness

The spreadsheet grew because it worked. It cost nothing, it was already installed, and the person closest to the problem could change it the moment the problem changed. No procurement, no training course, no consultant.

A spreadsheet is the best rapid-prototyping tool most businesses will ever own, and the file in question is a working prototype of exactly the system you need. That is the useful way to see it: ten years of decisions about how your business actually runs, encoded in columns. The reason it never fitted any off-the-shelf package is the same reason it grew in a spreadsheet in the first place.

The file is a working prototype of exactly the system you need. The mistake is not building it. The mistake is running production on the prototype.

So none of what follows is a scolding. But prototypes have a property that matters here: they are built for the person who made them, and they fail when handed to anyone else.

What actually goes wrong

Not, usually, the dramatic thing. Files do corrupt, but rarely.

The failures we actually see are quieter. A sort applied to half the columns, so every row's dates now belong to a different customer, discovered weeks later. A formula overwritten with last month's value, so a total that used to calculate now merely sits there. Two copies emailed out, both edited, and an afternoon lost to working out which one is true.

And behind all of them, the big one: the file has a keeper, and the keeper is one person. When they are on holiday, the answers wait. When they leave, the file stays and the understanding goes. Every rule that lived in their memory has to be rediscovered by breaking it.

The cheapest exit is rarely the biggest

The wrong conclusion is "we need a proper system, get quotes". Some of these files should not be replaced at all, and most of the rest should be replaced with something smaller than the owner fears. In ascending order of cost:

01Keep it, deliberately: if it truly has one author and nothing downstream depends on it, it is a document. Leave it alone.
02Tidy it in place: split the data from the working, add validation on the columns people mistype, protect the formulas. An afternoon's work, and it buys a year.
03Buy the boring tool: if the file is really a customer list, a job diary or a stock count, that is a solved problem, and a modest subscription replaces the fragile half of it.
04Build the small system: when the file encodes a process that is genuinely yours, the exit is bespoke, and smaller than you think, because the spreadsheet already wrote the specification.

The honest test for the last two rungs is the one we use when deciding whether to replace or integrate any system: does the off-the-shelf description of the job match yours? If it does, buy it. If your file has twelve columns no package has a field for, those columns are your business, and they are the specification.

That is not a hypothetical class of work for us. The jobs our own Resource Planner does for renovation and fitting firms, lead capture, quoting, week-by-week project planning, are the jobs we most often find being done in a big, brave, load-bearing spreadsheet.

What moving actually involves

Less than the folklore says, if it is done in the right order.

The data moves once, at the end, mapped and checked before anyone switches. The system speaks the spreadsheet's language: the statuses, the abbreviations, the columns people already think in, because those were decisions, not accidents. And the file itself retires with honour, kept read-only as the historical record it genuinely is.

What does not survive the move is the arrangement where one person is the system. That is the point of the exercise. It is also the part the keeper of the file is quietly relieved by, in our experience. Being the only person who understands the thing stopped being fun some years ago.

If you have a file like this, the first conversation costs nothing, and "tidy it in place and leave it" is an answer we give happily when it is the right one.

We work with businesses across Knutsford, Alderley Edge, Wilmslow, Altrincham, Stockport and Warrington, and remotely for clients anywhere in the UK.