When a spreadsheet stops being enough
A spreadsheet runs a maintenance schedule adequately for longer than vendors suggest. The thresholds that force a change are specific.
A great many maintenance departments run on a spreadsheet: assets down the rows, months across the columns, a colour when something is due. It costs nothing, everyone understands it, and it can be reshaped in an afternoon. For a separate product-side perspective on ways timer data can be distorted, this related article provides additional detail.
It also has real limits, and they arrive in a predictable order. Knowing which one you have hit prevents both a premature purchase and a late one.
Four thresholds
- History. A spreadsheet records what is due, not what was found. Once you need to answer 'how many times has this failed and what was done', the schedule and the record have become different problems.
- Field access. When technicians cannot see the job or record the outcome where the work happens, everything is transcribed twice and the second transcription is from memory.
- Evidence. When statutory certificates, readings and photographs need to be attached to an asset and retrievable years later, a folder structure stops being sufficient.
- Volume of change. When assets, tenants and contractors change often enough that keeping the sheet current is itself a job, the sheet has become the work rather than the tool.
The schedule half of a spreadsheet works for a long time. The record half fails early, and its failure is invisible until somebody asks a question about the past. For a wider operational and compliance reference, consult CISA cybersecurity performance goals.
What a spreadsheet still does well
Budget modelling, lifecycle projections, one-off analysis, anything requiring a calculation nobody anticipated. Departments with a full system keep spreadsheets for these, quite correctly.
The distinction worth holding is between the system of record — one authoritative place for each fact — and working files, which are disposable. Problems begin when a working file quietly becomes the record because it was easier to update.
The intermediate step
Between a spreadsheet and a full maintenance management system there is a workable middle: a shared cloud sheet with one authoritative version, a structured document store for certificates organised by asset, and a simple mobile form for recording job outcomes.
This addresses history and evidence — the two thresholds that usually arrive first — without a migration project. For a small in-house team with most specialist work contracted out, it is frequently the right answer for years.
Do not buy for an estate you do not have
Maintenance systems are sold against future growth and their pricing assumes a department with someone to administer them. Buying capability sized for a large estate means configuring modules against a structure you have not decided and paying for reporting nobody will read.
Buy for the problem you have now. These systems are easier to change later than the sales process implies.
The migration is the real cost
The subscription is the visible price. What surprises people is the data: the asset register has to be accurate before it is loaded, historical records have to be classified, and locations have to be standardised.
Budget for it honestly, and treat it as an opportunity. A migration is the only occasion on which someone will go through every asset record, and it is the natural moment to do the physical survey that has been deferred for three years.