Why Your Maintenance Schedule Is Fiction

There is a preventive maintenance schedule. It lists the assets, the intervals and the responsible contractor. It was built carefully and it is largely a work of fiction.

Pull ten items at random and check the last completed date against the interval. In most portfolios, three or four will be overdue and at least one will be overdue by more than a year.

Nothing tells you when it slips

A missed service generates no event. No alarm, no notification, no visible change. The asset carries on working, which is the entire problem, because working is not the same as maintained.

So the schedule and reality drift apart continuously and silently. The gap is discovered in one of three ways, and all three are expensive: something fails, an insurer asks, or a regulator inspects. By then the question is not whether you intended to do it. It is whether you can evidence that it was done.

Why it slips in the first place

Rarely negligence. Four ordinary causes, none of which anybody would defend but all of which are understandable.

Reactive work always wins. A tenant with no heating today outranks a filter change due this week, every time. Preventive work is by definition never urgent, so it is permanently second in a queue that never empties.

The contractor came and nobody recorded it. Frequently the work was done and the certificate is in somebody’s inbox, which for evidential purposes is the same as it not happening.

The asset register is out of date. Equipment was replaced, a unit was decommissioned, a new plant room was added. The schedule describes a building that has changed.

Nobody owns the whole picture. Each site knows its own position roughly. Nobody can answer the portfolio question without ringing eleven people.

The evidence problem is the real one

Doing the work matters. Being able to prove it matters commercially and legally, and the two are not the same thing.

After an incident, the question is whether a competent system was in place and being followed. A folder of certificates in mixed formats, some emailed, some photographed, some filed under a contractor name that changed in 2023, is not an answer. It is a week of work to assemble under exactly the conditions where you have no spare week.

The same applies to insurance renewals, to institutional landlords conducting diligence, and to any tenant of size reviewing their own supply chain. Increasingly they ask, and increasingly the answer decides the contract.

What AI checks on arrival

The reason this stayed manual is that certificates arrive as unstructured documents in every possible format, and until AI could read them reliably, that required a person who never had time.

It reads whatever comes in. A photographed certificate, a scan at an angle, a PDF from a contractor portal, an emailed job sheet. It identifies the asset, the work done, the date, the engineer and the next due date, whatever layout the contractor uses.

It updates the schedule from the evidence, rather than from somebody remembering to tick a box. That single AI step closes most of the gap, because the drift was always between what happened and what got recorded.

It tracks due dates forward. Chasing the contractor before the date rather than discovering the lapse afterwards, across the whole portfolio rather than the sites somebody happens to be thinking about.

It flags what does not add up. A certificate for equipment not on the register, a date that predates the last visit, a signature missing, a scope that does not match the contract. Those are the discrepancies nobody catches by hand, and each one is either an error or something worse.

What reaches a person is the small set that genuinely needs judgement, with the reason attached.

The register comes first

One honest caution. None of this works on top of an asset register that does not describe the buildings.

If the list is three years out of date, start there. It is unglamorous work and it is a few weeks rather than a few months, and every system built on top of it inherits its quality. A schedule generated from a wrong register produces confident, well presented, incorrect compliance reporting, which is worse than knowing you have a gap.

The contractor relationship changes too

An underrated effect, and for some portfolios the one that pays largest.

When certificates are read on arrival, you can see which contractors return documentation within a week and which take two months, which ones consistently attend within the agreed window, and which invoice for scope that does not match what was recorded.

None of that is visible today, because nobody is comparing eleven contractors across four hundred visits. It becomes visible automatically once the documents are being read, and it is the strongest position you will ever have going into a contract renewal.

What good evidence looks like

Worth defining, because most portfolios aim at the wrong target.

Not a complete archive of every document ever received. A single view that answers, for any asset on any date, what was due, what was done, who did it, and where the certificate is. That is what an insurer, an inspector or a purchaser is asking for, and it is a much smaller thing than the folder most businesses have accumulated.

Aim at the question rather than at the storage, and the project gets considerably smaller.

The check to run this month

• Pick ten assets across three sites and find the last completed certificate. Not the schedule entry. The document.

• Time how long it takes. That number is your answer to an insurer or an inspector, and it is usually the finding that gets a decision made.

• Count how many are overdue against their stated interval.

• Check whether any belong to equipment that no longer exists. There is nearly always one.

An afternoon, ten assets, and you will know whether your schedule is a system or a document.

AI Optimize reads the certificates whatever form they arrive in, updates the schedule from the evidence rather than from memory, and chases what is due before it lapses. That work sits under Document Intake & Validation.