Preventive maintenance with a spreadsheet vs. a CMMS

Almost every preventive maintenance plan starts in a spreadsheet, and many run there for years. Worth acknowledging that before comparing anything, because the useful question isn’t whether the spreadsheet works — it does — but where its ceiling is.

This article is about that: what a spreadsheet can do, what it can’t, and what exactly changes when you move to a system.

What a spreadsheet does well

Keeping the equipment list with its basic data.

Noting what gets done to each one and how often.

Keeping a review calendar with planned dates.

Marking what’s been done, with a column or a color.

With few pieces of equipment, one site, and one person running everything, that’s enough. And it’s free.

The five exact limits

These aren’t opinions: they’re concrete things a spreadsheet can’t do.

1. It doesn’t complain. The most important limit. A date in a cell doesn’t protest when it passes: the March review goes undone, the cell stays where it is, and nobody notices until there’s a breakdown.

2. It doesn’t record in the field. The technician isn’t going to open a spreadsheet on their phone in a boiler room, so they write it on paper and someone enters it later. That means hours always come in low and values get rounded off.

3. It doesn’t work as evidence. A cell gets changed without leaving a trace. Facing a complaint, a claim, or an inspection, it proves nothing.

4. It doesn’t scale by family. If you have two hundred identical pieces of equipment and change the checklist, you have to touch two hundred rows. In practice, it doesn’t get touched.

5. It doesn’t relate things. It can’t tell you how much it’s cost to maintain a piece of equipment, because the cost is in another sheet, or whether yesterday’s breakdown had been giving warning signs, because the measured values aren’t anywhere.

What changes with a system

Point by point, against the five limits above.

The plan complains. The checklist gets attached to the asset, its model, or a family, the frequency gets defined, and preventive maintenance generates work orders with an owner and a date. And it checks beforehand whether the day is a holiday and whether that person is available.

The record happens where the work happens. Stopwatch inside the order itself, material consumed, checklist completed, photos, and signature, from the app and without coverage.

The proof stays. With date, author, and values, and no way to modify it without a trace. Statutory maintenance rests on exactly that.

It’s configured by family. Checklists resolve in cascade — asset, model, subfamily, family — so two hundred identical units mean one configuration.

Everything is connected. The order hangs off the asset, consumption off the warehouse, hours off the technician. That’s where reports come from.

And two things a spreadsheet can’t even attempt

Usage-based frequency. An asset can carry a counter — hours, cycles, kilometers — with a limit and a warning percentage, so when a reading that exceeds the threshold gets logged, the order generates automatically. In a spreadsheet, that requires someone watching the counters by hand, and it doesn’t happen.

Detecting trends. If checklist fields have a minimum and maximum value, an out-of-range reading gets logged as an anomaly, and a series of readings lets you see that a piece of equipment had been getting worse. It’s real predictive maintenance without sensors, and impossible to maintain in a spreadsheet.

The in-between case: several spreadsheets

Before the spreadsheet fully runs out of road, there’s usually an in-between phase worth recognizing, because it’s the one that eats the most time without anyone counting it: one sheet per thing.

One for the review calendar, another for the inventory, another for spare parts stock, another for hours, and a separate document for expiring certificates.

Each one works. The problem is that nothing’s connected: to know how much a piece of equipment has cost you have to cross-reference three, and to know whether its certificate is still valid, open a fourth. And as soon as two people are maintaining them, different versions start appearing.

That phase is, in practice, the most reliable sign you’ve hit the ceiling.

When the spreadsheet has fallen short

The signs are concrete. If you recognize three or more:

• A review was missed and nobody noticed.
• Someone asks when a piece of equipment was reviewed and you have to call a person.
• Hours get written down from memory at the end of the day.
• A client disputed a report and it was hard to find, or it never turned up.
• There are two versions of the spreadsheet circulating.
• Nobody knows what it costs to maintain a specific piece of equipment.

What also changes outside preventive maintenance

Once you make the move, three things show up that weren’t part of the initial comparison and that usually end up valued more than the plan itself.

Material stops being a surprise. Consumption gets recorded when closing the order, and items carry minimum stock in warehouses and items, so you get warned before running out of the part a job needs.

Expiry dates give warning. Certificates, contracts, and insurance policies with their expiry date in the document manager, with a daily check of what’s about to lapse.

The client stops calling. With their own dedicated access they see the status of their orders, download their reports, and check their upcoming preventive visits.

None of the three is the reason you make the move, but all three are noticeable in the first week.

What doesn’t change when you make the move

Worth saying so as not to create false expectations.

The work of deciding is still yours. Which equipment is critical, what gets checked, and how often. That work exists whether you use a spreadsheet or a system, and it’s what takes the longest.

Technical judgment doesn’t come from the software. It’s set by the manufacturer, the regulation, or experience.

And the process still needs to be agreed on. If nobody decides who handles what and at what priority, the system will just record the same disorder more precisely.

The cheap way to make the move

Not by migrating the whole spreadsheet. Through critical assets — the ones that stop production or service if they fail — with their families, checklists, and frequency. Within days, preventive work is being generated and orders are closing with real data.

The rest of the list comes in later, and the spreadsheet can keep coexisting for a few weeks without a problem.

One last practical note: the spreadsheet you already have isn’t wasted work. The equipment list and the record of what gets done to each one and how often is exactly what needs to be loaded, and it’s the part that takes the longest. Arriving with that already done cuts the rollout time in half.

If you want to see how your current plan would look in a system, you can request a demo.