The gaps a CMMS solves

Almost no company decides to roll out a CMMS as a strategic move. It’s decided because specific gaps have piled up, each one small, that together describe an operation that no longer fits in anyone’s head.

This is the inventory of those gaps, with what solves each one. It works as a diagnosis: if you recognize five or six, you already know where you stand.

1. Work that never gets recorded

It doesn’t disappear by oversight: it never existed as a record in the first place. Someone told someone else something, it got done, and nothing was left. When it needs to be invoiced or proven, there’s nothing to pull from.

What solves it. Making everything come in through one place: as an incident with its type, priority, client, address and affected asset, or as a work order generated by the plan.

2. Requests coming in through three different channels

One over WhatsApp to a technician, another by phone to the team lead, and another by email to admin. That’s three jobs nobody can count together, and what can’t be counted can’t be prioritized.

What solves it. Getting every channel to land in the same list. A request can come in from the backend, from the client access with a photo, or from a mailbox the system turns into incidents.

3. Nobody knows what’s pending

The list of open work lives scattered across several people’s heads. That way, what’s urgent eats what’s important every single day.

What solves it. A single list, with priorities and a maximum time tied to each status, so what’s overdue is visible instead of guessed at.

4. Checks that go missed without anyone noticing

Preventive work is the first thing to give when an urgent job comes in, because nothing is demanding it. A task that only lives on a calendar falls through silently.

What solves it. Having preventive maintenance generate real orders with an owner and a date, checking beforehand whether the day is a holiday and whether the technician is available.

5. Warranties paid for twice

A unit still under warranty gets repaired, and the repair gets paid for. It’s an avoidable, silent cost: avoiding it means having the installation date and warranty end date on hand when the order is opened.

What solves it. The asset record with its installation date, its cost, its warranty end date and its serial number, and the order flaggable as warranty work.

6. Stock that never adds up

The part used on Tuesday gets logged on Friday, or never gets logged. Actual stock and system stock have been two different things for weeks.

What solves it. Making consumption a consequence of closing the order, not a separate entry. Items carry their minimum stock, their cost and their batch when needed, and each technician’s van can be set up as its own warehouse.

7. Visits that have to be repeated

Going back because the part was missing, because nobody knew the equipment model, or because nobody had the key. It’s paid for twice: the trip and the hour.

What solves it. Minimum stock that warns in advance, the asset’s history on the phone, and the pending-material and needs-return-visit statuses, which keep that work from living in a notebook.

8. Hours logged from memory

At the end of the day, and always on the low side. With that you can’t calculate the cost of a job or know if a contract is profitable.

What solves it. The stopwatch built into the order itself, in the technician app, which also works without signal and syncs afterward.

9. Documentation that never turns up

Manuals, drawings, certificates and old reports scattered across the general archive, shared folders and someone’s memory. Every lookup costs a call or a trip.

What solves it. Having the document hang off the thing it belongs to —asset, client, order, incident— with its visibility set and its expiry date. The document manager checks daily for what’s about to expire and alerts.

10. Knowledge that leaves with people

What needs checking on each piece of equipment is known by two people with twenty years at the company.

What solves it. Checklists by equipment family, with their reference values. Defined in cascade —asset, model, subfamily, family— they’re not a documentation project.

11. Clients who call just to ask

A good part of the calls a maintenance company gets aren’t requests: they’re asking how things are going.

What solves it. A dedicated access point where the client opens incidents with a photo, tracks their orders, downloads their reports and sees their upcoming preventive visits on a calendar. Since licenses are unlimited across all three plans, giving the whole client base access isn’t a financial decision.

12. Not knowing what anything costs

The underlying gap, and the one that justifies the rest. How much it costs to maintain this machine, whether it’s worth repairing again, whether this contract makes money.

What solves it. Nothing, if the previous eleven haven’t been recorded first. With them recorded, reports give cost per asset, hours per technician and per client, downtime, MTBF and MTTR, annual plan execution and anomalies.

What a CMMS doesn’t solve

Worth saying, because it explains most rollouts that go wrong.

A process that doesn’t exist. If today nobody decides who handles what or with what priority, the system will just record the same disorder more precisely.

Technical judgment. How often to check a piece of equipment is set by the manufacturer, the standard or experience, not the software.

Regulatory compliance. The system records and proves what was done. The company is the one that complies.

Where to start

With the gaps that hurt most, not all of them. Usually that’s 4, 6 and 8 —preventive work falling through, stock that doesn’t add up and invented hours— and all three are tackled with the same thing: critical assets set up, check routines with their frequency, and logging in the field.

If you want to see which of these twelve actually affect you, you can request a demo on your own case.