Skip to content
DebugSwift

Automating the busywork

Why does my spreadsheet keep breaking?

By Rijaul Sk · · 6 min read

Short answer

A spreadsheet breaks because it was never a system — it was a calculation that quietly became one. Nothing enforces the rules, so every person fills it in slightly differently, and one dragged cell can rewrite a month. The file is not the problem. The problem is what you are asking it to be.

A hand-drawn process flowchart on paper, with steps boxed and arrows connecting them

The short version

  • A spreadsheet has no idea what a valid entry looks like, so every rule it follows is one a person is remembering.
  • The breakages cluster in the busiest weeks, because that is when people stop double-checking.
  • You can tell whether the file has become a system by asking what happens when the person who built it is away.
  • Most spreadsheets should stay spreadsheets. The ones worth replacing are the ones other people depend on.

Say you run a small builders' merchant. Someone built a stock sheet four years ago — a few columns, a couple of formulas, nothing clever. It worked.

Last Tuesday it said you had eleven bags of a product you'd sold out of on Friday. Someone had inserted a row halfway down and a SUM range didn't follow it. Nobody noticed for four days, because nothing about the file looks wrong when it is wrong.

That is the whole shape of the problem. The spreadsheet is not broken — it did exactly what it was told. It simply has no idea what it is for, so it cannot tell when the answer stops making sense.

It stopped being a spreadsheet a while ago#

Almost every one of these files starts as a calculation. One person, working something out, keeping a note of it.

Then somebody else needs the number. Then a column gets added so it can answer a second question. Then a tab appears for last year. Then someone builds an invoice from it. At no point does anyone decide to build a system — but by the end, three people depend on a file that was designed for one.

Nobody notices the crossing point, which is why nobody plans for it. The file that broke on Tuesday had been a system for about three years.

Why it breaks when you are busiest#

Notice when these failures actually happen. Not on quiet Wednesdays — during the week everyone was flat out.

That is not bad luck. A spreadsheet's rules live in people's heads: paste values not formulas, add rows above the total, use the dropdown, always fill in the date column. Every one of those is a thing someone is remembering. Remembering is the first thing to go when you are behind.

Software has the opposite property. A form that refuses to submit without a date is just as stubborn in December as in June. That is genuinely the whole difference — not that software is cleverer, but that it does not get tired.

  • No validation. The file will happily accept "tomorrow" in a date column, or a negative quantity, or a supplier that doesn't exist.
  • No audit trail. When a number is wrong, there is usually no way to find out when it changed or who changed it.
  • Formulas that move. Insert a row, drag a corner, sort a column with one cell selected — each of these can silently rewrite the file's logic.
  • One author. The rules were never written down because the person who knew them was always in the room.

The question that tells you which kind you have#

Most spreadsheets are fine and should be left alone. Only one kind is worth spending money on, and there is a quick way to tell them apart.

Work out whether your file has become a system

  1. 01

    Name everyone who opens it

    Not who could — who actually does, in a normal month. One person is a spreadsheet. Three is a system.

  2. 02

    Ask what breaks if it is wrong for a week

    Nothing much, or an order goes out short and a customer finds out before you do? The second one is a system.

  3. 03

    Ask what happens when its author is on holiday

    If the honest answer is that everyone waits, or that someone makes a copy and works in that, the rules live in one head and the file is already fragile.

  4. 04

    Count the manual steps between it and the money

    Every retype between the sheet, the invoice and the accounts is a place a number can change on the way. Count them. That count is your real risk, and it is a number you can act on.

A typical result: two of the four point one way and two the other. That usually means the file is on the crossing point right now — which is the cheapest moment to do something, and the moment almost everyone waits past.

What replacing it actually looks like#

Not a rebuild of everything. The useful version is narrow: take the process the sheet is holding together, write it down properly — often for the first time — and give it somewhere to live that enforces its own rules.

OptionWhat it fixesWhat it doesn't
Tidy the spreadsheetLocked formulas, dropdowns, one shared copy — an afternoon's workNothing chases anyone, nothing is recorded, one head still holds the rules
An off-the-shelf toolProper validation and history, no build costYour process has to bend to fit it, and the last 20% usually doesn't
A small custom toolThe process as you actually run it, with the rules enforcedCosts more than an afternoon, and is overkill for a file two people use
The three honest options, and what each one really buys you.

The order matters. Tidying first is nearly always right, because it is cheap and it tells you whether the mess was the file or the process. If it breaks again a month later, you have learned something worth knowing.

When this isn't worth buying#

Often it genuinely is not, and it is cheaper to hear that now.

  • One person uses it. A file you use to think with is a spreadsheet doing its job. Leave it alone.
  • The process changes every month. Automate a process after it settles, not before — otherwise you are paying to set the wrong thing in concrete.
  • It has never actually cost you anything. If it goes wrong twice a year and someone spots it the same day, that is a working system with rough edges, not a problem worth a budget.
  • You haven't tried locking it down yet. Do the afternoon's work first. Sometimes that is the whole fix, and it costs nothing to find out.

Replacing a spreadsheet that was never really a problem is one of the more expensive ways to feel organised.

So: how many people opened it last week?#

Open the file and look at the sharing list, or just think about who asked you for a number from it.

If the answer is one, this is not your bug and you have just saved yourself a purchase. If the answer is three, and one of them invoices from it, you are running the business on a document that cannot tell you when it is wrong — and you found that out in under a minute.

If you would rather work out whether it is worth fixing at all before spending anything, the free diagnosis does exactly that, and quite often the answer is to tidy the file and leave it be.

Common questions

What if we've already outgrown two tools?

Then the useful question is which 20% they each missed, because that is usually the same 20% — and it is a description of the thing you actually need. Bring both tools and the spreadsheet to the conversation; the pattern is normally obvious within twenty minutes.

Do we lose the history in the sheet?

No. Importing what is already there is part of the job, not an extra. A tool that starts empty asks everyone to keep the old file open beside it, and then you have two systems instead of one.

Still wondering

Would moving it to Google Sheets fix this?

It fixes one thing — several people can be in it at once without emailing versions around. It doesn't fix any of the rest, because the file still has no idea what a valid entry looks like. If your problem is version chaos, that move is worth making today and costs nothing. If your problem is that the numbers are wrong, it changes nothing.

Can't I just lock the cells?

You can, and you should — protecting formula cells and adding dropdown validation to the columns people type in will stop a good share of the damage in an afternoon. What it won't do is make the file tell you something is missing, chase anyone, or keep a record of who changed what. Locking is a patch on a good spreadsheet, not a way to make it software.

How do I know it's time to replace it?

When someone other than its author depends on it being right. A file one person uses to think with is a spreadsheet doing its job. A file three people update and a fourth invoices from is a system, and it's being held together by everyone remembering the same set of unwritten rules on their busiest day.

What's slowing your business down?

Twenty minutes, one honest answer, no invoice.

We'll tell you what we'd fix first — and if the answer is “nothing yet”, we'll say that too.

Share

Keep reading

More on automating the busywork

New posts by email

One email when something worth reading goes up.

No schedule, no newsletter filler, no selling your address on. If a month goes by with nothing worth sending, nothing gets sent.