Skip to content
allanninal.dev/build
Collaborate

Part 4 of 7 · Equipment maintenance scheduler series ~5 min read

Which jobs cannot be deferred

Some inspections are not the manufacturer’s advice; they are legal requirements with dates, and the consequence of missing one is not a broken machine but an unusable one and a difficult conversation.

Key takeaways

  • Statutory inspections go in a separate track with no deferral action available.
  • The interval is set by regulation, not by the manufacturer or by usage.
  • The certificate is the artefact; store it with the record and make it findable.
  • Equipment past its inspection date should be marked out of service, not just overdue.
  • Warn at ninety days, not at seven. Inspectors need booking.

A separate track

Three types of maintenance work and how statutory work is separatedThree boxes stacked on the left. Manufacturer schedule, covering oil, filters and belts, labelled deferrable. Condition-based work found on inspection, labelled deferrable. And Statutory work covering lifting equipment, pressure systems and electrical testing, labelled not deferrable. All three converge on Two different lists, never merged, and that leads down to Different rules and different consequences. A note says one list with a flag on some items is how the flag gets missed at half past four.Manufacturer scheduleoil, filters, beltsdeferrableCondition-basedfound on inspectiondeferrableStatutoryLOLER, pressure,electricalnot deferrableTwo different listsnever mergedDifferent rulesand different consequencesOne list with a flag on some items is how the flag gets missed at half past four.
Fig 1. Why statutory work is kept physically separate rather than flagged within one list. The separation is the safeguard.
  • Compute
  • Security & identity
  • Analytics

Why not just a flag

A single list with a do-not-defer flag works until somebody is working through forty items at the end of a difficult week. Two separate lists, with the statutory one much shorter and reviewed differently, means the mistake is structurally harder to make.

It also matches how the work is actually organised. Statutory inspections are usually done by an external inspector on a booked date, which is a different kind of planning from an internal service, and combining them makes both harder to see.

Ninety days, not seven

How a statutory inspection date is managed from ninety days outA vertical chain of five steps entered by a box labelled An inspection due date, taken from the last certificate. Step one, ninety days out, books the inspector. Step two, sixty days out, asks whether it is booked; if not it exits to Chase, noting some are booked months ahead. Step three, fourteen days out, prepares access. Step four asks whether the date has passed with no certificate; if so it exits to Mark out of service, not merely overdue. Step five stores the certificate and computes the next date from it. A note says the fourth exit is the one that matters, because overdue is a status and out of service is a fact.AWS ACCOUNTAn inspection due datefrom the last certificate90 days outbook the inspector60 days outbooked?Chasesome are booked months aheadno14 days outprepare accessDate passed?no certificateMark out of servicenot merely overdueyesCertificate storednext date computed from itThe fourth exit is the one that matters. Overdue is a status; out of service is a fact.
Fig 2. The statutory reminder ladder. It starts far earlier than a maintenance reminder because booking an external inspector has its own lead time.
  • App integration
  • Machine learning
  • Security & identity
  • Management
  • People

Out of service means something

Equipment whose statutory inspection has lapsed should not be used, and the system’s role is to make that unambiguous rather than to enforce it, which it cannot. A status that reads out of service, visible wherever the equipment is booked or assigned, is considerably harder to overlook than a red row on a maintenance list.

It is also the honest position. A lifting accessory past its thorough examination date is not slightly overdue; it is equipment that should not be in use, and softening that in the interface serves nobody.

The certificate

What gets stored, and why

  • The certificate itself, as a file, immutably, with the equipment record.
  • The inspector and their body, because that is asked about.
  • The date of the examination, which is not always the date on the certificate.
  • Any defects noted, as their own records, because those become jobs.
  • The next due date, computed from the examination, not from when the paperwork arrived.
  • Findable in ten seconds, because the moment somebody needs it is not a relaxed one.

The last line is the practical test. A certificate stored in an email folder, a shared drive and a filing cabinet is a certificate that does not exist when an inspector asks for it on a Tuesday morning.

Defects become jobs

An inspection that finds a defect produces two things: a certificate with a condition on it, and a piece of work. Those need to become real records rather than a note in a PDF that somebody reads once.

Defects with a stated timescale — remedy within twenty-eight days is common — inherit that timescale as a hard date and go into the statutory track rather than the general one, because they carry the same consequence.

Next: what the history tells you.

All posts