The Asset Maintenance Cycle
A multi-year map, not a due date. How to hold several live obligations against one asset without losing all but the nearest one.
Used by
- Service Coordinator
- Compliance Officer
- Maintenance Planner
How to get this live in your business
Free. The Compliance Calendar Build Standard: the objects, the checks in order, and the pass test.
Ready for
Most maintenance systems give an asset one due date. Fire and electrical assets do not have one. A single item can owe a monthly visual check, a six-monthly test, an annual service and an overhaul years away, each from a different clause, each live at the same time. Put that in one field and the system keeps the nearest obligation and silently forgets the rest, which is exactly the set nobody notices until an audit.
In short
What this is
The compliance calendar standard applied to a fire and electrical asset register. The specification is the parent standard; this is what changes in this trade.
The core rule
An asset has many live obligations, each derived from its own dated rule. The asset does not have a due date.
What it does not do
It schedules and surfaces. Whether an asset passed is a competent person's determination and is recorded, not computed.
The hard part
Blocked access. The obligation stays live, the clock does not roll forward, and somebody has to be told.
Take the spec to Claude, ChatGPT or Copilot. The sentence to paste is one click away.
Want the whole thing by email?
This paper, plus the rest of the library. One click to stop them.
1. Read the parent standard first
The specification lives in the compliance calendar build standard: store the rule with an effective date, derive the due date, never store a due date as a fact. Everything it says holds here. This paper covers the three things a fire and electrical register does that a rent roll does not, and nothing else.
2. Many obligations, one asset
The first change is structural. In the parent standard an obligation hangs off a subject. Here you need several at once, and they are not variations of each other: a monthly check and a five-year overhaul have different lead times, different competency requirements, different evidence, and are done by different people.
The practical consequence is that coverage is not a property of an asset. An asset is covered for its annual service and uncovered for its overhaul at the same time, and the report that says otherwise is the report that lets the overhaul slip. Measure coverage per obligation class, not per asset, and be ready for the first honest number to be lower than anyone expects.
Frequencies also do not all anchor to the same event. Some run from the last pass, some from installation or manufacture, and some from a commissioning date that predates your involvement with the site. An unknown anchor is a state that has to surface, not a blank that defaults to today, because defaulting to today produces a schedule that looks complete and is fiction.
3. Four buckets, and only one of them books work
| Bucket | What it holds | What happens |
|---|---|---|
| Due soon | Inside the booking window, access is known good | Book it. This is the only bucket that should feed the run sheet |
| Due later | Derived and live, outside the window | Nothing yet. Its job is to prove coverage exists |
| Overdue | The date passed and the work did not happen | A different workflow, not a louder version of booking. It goes to the overdue book |
| Blocked | No access, occupied tenancy, disputed ownership, site closed | The obligation stays live and the clock does not move. Carries who, since when, and the next review date |
Keeping overdue out of the booking run is the part people argue with, and it is the part that matters. Overdue work has a different conversation attached: why it was missed, whether the site is still under agreement, whether anyone has been told. Mixing it into the booking list means the awkward calls sit at the bottom forever while the easy ones get made.
4. Blocked access is the failure mode worth designing for
A technician attends and cannot get to the asset. The tenancy is occupied, the room is locked, the site is closed, the ceiling space is inaccessible, the owner would not let them in. This happens constantly and almost every system handles it the same wrong way, by rescheduling.
Rescheduling moves the due date. Once the due date moves, the obligation is no longer overdue, the coverage report goes green, and the fact that a life-safety asset has not been tested becomes invisible. Do the opposite: the obligation stays exactly where it was, the asset moves to blocked with a reason and a date, and a review date is set for the next attempt. The site now appears in two places, the coverage gap and the access queue, which is correct because it is two problems.
The access queue is also the one that produces a paper trail worth having. A building owner who has declined access three times is a conversation you want dated and recorded, and it is not a conversation software should be having on your behalf.
5. When the rule changes
Standards get new editions and states issue variations. The parent standard already requires dated rules so that a change recomputes future obligations without rewriting history. The addition here is that in this trade somebody competent has to accept the change before it takes effect on your register, because the interpretation is a professional judgement and not a data migration.
That acceptance step is specified in the cited answer build standard, which covers how a change feed works and who is allowed to sign off on it. If you run an internal assistant that answers questions about the standards, the same accepted change should update both, or you now have two versions of the rule in the business.
6. The check worth running this week
Pick one site you service under agreement. List every asset on it, and for each one list every obligation currently derived against it with the rule it came from. Two things usually turn up. Some assets carry exactly one obligation where the standard implies several, which is the nearest-date problem. And some obligations trace back to no rule at all, because somebody typed them in years ago and nobody has questioned them since.
Both are fixable. Neither is visible from a report that only counts visits completed on time.
7. What is ready-made today
The register is yours to hold, and this paper is the method for it. The part we run for fire and electrical businesses is the phone: Booked After Hours answers out of hours on your number, sorts the call into emergency, routine or quote, and writes the job into ServiceM8 or Simpro before the caller hangs up, so the building manager asking about a due test gets a record tonight rather than a promise. Hear our voice agent.
Technical? The build standard is open. Take it.