Your Spreadsheets are Out of Control

There’s a spreadsheet somewhere in your organisation right now that is quietly causing you problems. You probably know which one. It’s the one that three people have edited this month. The one where a column got added six months ago and nobody’s quite sure what it tracks anymore. The one you’re going to need to print and defend in front of an auditor eventually.

Spreadsheets didn’t fail you. They did exactly what they were designed to do. They’re flexible, familiar, and free. For a handful of assets and a small team, they’re perfectly reasonable. The problem isn’t the tool — it’s what happens when the scale outgrows it, and that moment tends to arrive quietly, without announcement.

The version problem

Ask yourself: if someone needed to confirm the last inspection date for a specific piece of equipment right now, how confident are you in the answer they’d find? Is the spreadsheet on the shared drive the same one that was updated on someone’s laptop last week? Is the most recent copy the one that was emailed around in November? These aren’t hypothetical edge cases. They’re the daily reality of managing equipment compliance in a file-based system.

The single point of knowledge problem

Most organisations that rely on spreadsheets also rely, without realising it, on a single person who understands how the system works. They know which tab is current, what the colour coding means, which assets have been decommissioned but not yet removed from the list. That knowledge lives in their head. When they’re on leave, or leave the business, the spreadsheet becomes archaeology.

The audit problem

Spreadsheets feel like records. They look like records. But under LOLER, PUWER, or PSSR, “we have a spreadsheet” is not the same as “we have a compliance record.” An auditor or HSE inspector wants to see inspection history, certification status, who confirmed what and when. A spreadsheet with manually entered dates and no audit trail is a liability dressed up as evidence.

The cost you’re not counting

There’s also the invisible overhead — the hours spent maintaining the spreadsheet, cross-referencing documents, chasing inspection companies for certificates, manually updating status fields. Nobody invoices you for that time, so it never appears in a cost comparison. But it’s real, and it compounds.

None of this means you need a £50,000 enterprise system with a six-month implementation project. There’s a significant amount of space between “spreadsheet” and “full CMMS deployment,” and most mid-market operations belong somewhere in that space. The question isn’t whether to change — it’s what to change to.