← All white papersIndustry map · September 2026

Fire and Electrical Compliance: The Five Jobs That Leak Cash

The recurring compliance agreement is the rent roll of this industry. Here is where it leaks, which published standard covers each leak, and the one thing in this trade that must never be automated.

9 min read·Published by AI Pathway

Used by

  • Operations Manager
  • Compliance Officer
  • Service Manager

A fire protection or electrical compliance business does not really sell visits. It sells the promise that every asset on a site will be tested when the standard says, recorded so the record survives an audit, and certified by somebody whose licence is on the line. Almost every way this kind of business loses money is a failure of that promise rather than a failure of the work.

In short

  • What this is

    A map, not a new specification. Five jobs, each pointing at the published standard that covers it. The first, the after-hours call, is one we run for you.

  • The core rule

    The book is the asset register, not the job list. A visit is something that happened to an asset, and an asset with no future obligation has fallen out of the book.

  • What it does not do

    Nothing here certifies, signs or determines compliance. Every one of those stays with the licensed person who carries it.

  • The hard part

    Not the schedule. The site you could not get into, where the obligation stays live and the due date must not quietly move.

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.

The five jobs

These are the same five jobs we publish for every industry. The names change because the work does, and the standards underneath do not.

JobWhat sits overnightStandard
Get the enquiry inThe after-hours call about an alarm that will not silence. The web form asking whether an extinguisher is in date.After-hours triage
Get the contract outThe site walk is done and the recurring maintenance agreement has not been sent.No standard yet. This is usually a build
Keep the site on its cycleThe next monthly, six-monthly, annual or five-year service is in somebody's head or somebody's spreadsheet.The asset cycle
Stop rejected paperworkThe visit happened. The record fails later: no photo of the tag, no certificate of electrical safety, a signature on the wrong line.The service pack
Work the book you already ownAssets that came due and were never booked. Agreements that lapsed. Sites that changed hands.The overdue compliance book

Three things this industry does not share with the others

Most of what we publish transfers between trades without much editing. Three things here genuinely do not, and each one breaks a system that was designed for a simpler business.

The obligation is a multi-year map, not a next date

An asset can carry a monthly check, a six-monthly test, an annual service and an overhaul years out, all live at once, all derived from the same standard. A system with one due-date field per asset cannot represent that, and what it does instead is quietly keep the nearest one and lose the rest.

Evidence is part of the work, not a report about it

A test that happened and was not recorded against the right asset did not happen, as far as an auditor, an insurer or a building owner is concerned. That makes the binding step, the one that locks a photo and a result to an asset identity before the job can close, the difference between a service business and a liability.

Somebody signs

Certification carries a named person and their licence. That is the line this industry draws and it is not negotiable by software. Everything in this map exists to put a complete, correct, evidenced record in front of that person faster. None of it replaces them.

What not to automate here

Our standing rule is that where a named human signs, lodges or certifies, the work stays theirs and we do not offer to take it. In this industry that rule does more work than anywhere else we publish, so it is worth being specific.

  • Issuing, signing or implying a certificate of compliance, a certificate of electrical safety, or any statement that an installation conforms.
  • Determining that an asset passed. A model can record the result a competent person gave. It cannot be the competent person.
  • Advice to a member of the public about making safe something that is currently unsafe.
  • Deciding that a defect is acceptable, or that an isolation can stand without a retest date.
  • Anything that would let work be assigned to somebody whose competency for that class has expired.

None of that is caution for its own sake. Each one is a place where automating the step transfers a risk somebody else is licensed to carry onto a system nobody can cross-examine.

Where to start

Start with the book you already own rather than a new tool. In practice that means one question: can you produce, today, the list of every asset under agreement that has no future obligation derived against it? The size of that list is the size of the problem, and it is usually the first genuine surprise.

After that, the order that tends to pay is the cycle, then the pack, then the overdue book. The cycle tells you what should be happening. The pack makes what happened provable. The overdue book turns the gap between the two into work. Triage and the knowledge layer are worth doing once those three are true, and are frustrating before.

The first job on the map is the one that will not wait for any of that. An alarm that will not silence at 11pm is a call somebody has to answer, sort into life-safety or not, and get onto the job list before morning.

Related reading

The one job on this map we run for you

Booked After Hours answers your number out of hours, in your name, says it is an AI first, and writes the job into ServiceM8 or Simpro before the caller hangs up. Emergencies wake the on-call phone; nothing on the call certifies anything. $119 a month, flat, no call caps.

Technical? The build standard is open. Take it.