A fire safety inspection business doesn’t sell inspections. It sells a defensible record that an inspection happened, was performed by someone competent, found specific things, and that the deficiencies were tracked to closure.
That distinction is why so many fire protection contractors end up running a general field service platform alongside a spreadsheet and a folder of PDFs. The platform handles the visit. It doesn’t handle the thing the business actually produces.
What makes this trade different
Deficiencies have a life of their own. A finding raised in March is still open in September until someone fixes it and it’s re-verified. It needs an owner, a severity, a history, and a link back to both the original inspection and the retest. Generic job management treats a finding as a note on a completed job, which is precisely the wrong model — the job closes, the deficiency doesn’t.
The asset outlives the customer. Buildings change hands. Contracts move between contractors. The extinguisher, the sprinkler system, the alarm panel, the emergency lighting circuit — each has a service history that should survive both. Software organised around customers loses that history at every handover, which is exactly when you most need it.
Competency is enforceable. Depending on jurisdiction and system type, work may only be signed off by someone holding a current qualification. If your system happily lets you dispatch an unqualified technician, it will eventually help you create a problem you cannot argue your way out of.
The document is the product. A certificate or report with the right fields, in the right format, with a signature and a number, retained for a defined period. Everything else in the software exists to produce that artefact correctly.
The standards shape the software
Inspection regimes differ by country and system type — sprinkler systems, portable extinguishers, alarms, emergency lighting and passive protection each have their own requirements, and the applicable standard depends on where you operate and what you’re servicing. Any software you buy has to accommodate the specific standards you work to rather than a generic checklist.
Practical implication: the form must be versioned. When a standard is revised, historical records need to remain as they were issued, while new inspections use the updated form. If a platform edits forms in place, your archive silently becomes inconsistent — and that’s the archive you’ll be asked to produce.
Verify the current requirements with your national body or accreditation scheme rather than relying on any vendor’s claim of compliance. “Compliant software” is a marketing phrase; compliance is something your process achieves, and software either supports it or obstructs it.
What to require in a demo
Ask the vendor to do these, with your data, not theirs:
- Open one asset and show its full history, including inspections carried out under a previous site owner.
- Raise a deficiency, close the job, then show me the deficiency still open — with its due date and owner.
- Schedule the retest and show how it links back to the original finding.
- Produce our actual certificate, with our fields, our numbering, and a technician signature.
- Complete an inspection with photographs on a device in airplane mode, then sync. Watch the photographs specifically.
- Try to assign a technician whose qualification has expired. It should refuse.
- Export everything — assets, history, documents, images — and open the export.
Most platforms handle one to four. Five to seven are where the differences appear, and they’re the ones that cost you later.
Recurring scheduling is harder than it looks
Fire work is dominated by recurring obligations at different frequencies against different assets on the same site — monthly, quarterly, annual, five-yearly, each with its own window.
Weak scheduling shows up as: an inability to schedule from an asset’s due date rather than a customer’s contract date; no concept of a compliance window (due within a period, not on a day); no way to see what’s about to fall out of compliance next month; and no handling of the common case where one visit services eight different assets on three different cycles.
Ask to see a forward compliance view — everything due in the next 60 days, by site, by asset, by frequency. If that view doesn’t exist, the operational planning stays in your spreadsheet regardless of what you’ve bought.
Build, configure, or buy
Buy if you service common system types under a common regime and a product already models assets, deficiencies, and certificates properly. Several do.
Configure if the model fits but forms and certificate templates need shaping to your scheme. Budget for it as a project, not a setting.
Build if you operate in a niche where the regime is specific enough that nobody has bothered — some regional schemes, some industrial contexts, some combined inspection-and-remediation businesses — or where your inspection methodology is itself the thing clients buy. The case strengthens considerably if you’re already paying per-seat for a platform you’re working around.
Mistakes that cost money
- Migrating only current assets. The history is the asset. Migrating without it means you’re back to the old system whenever a client asks a real question.
- Letting technicians opt out. Parallel paper processes destroy the record’s integrity. Involve them in the trial; if the mobile app is slow on a real device in a basement, it will not be used.
- Choosing on price per seat. The cost that matters is the hour per week per technician spent fighting the tool, plus the day lost every time a client requests an audit pack.
- Assuming “compliant” means anything. Ask which standard, which version, and how form versioning works.
Frequently asked questions
Can I use a general field service platform? For scheduling and invoicing, yes. For deficiency tracking, asset history, competency enforcement and certificate production, most operators end up supplementing it — which is the cost to weigh.
How long should records be retained? Retention is set by your jurisdiction, your scheme, and often your client contracts, and it frequently exceeds the life of the contract. Confirm the requirement that applies to you, then check the software can enforce it — including after a customer leaves.
What about clients who want their own portal? Increasingly expected, especially by facilities managers with multiple sites. Ask whether a client can self-serve their compliance status and download certificates without contacting you. It removes a surprising amount of admin.
Is offline capture really necessary? If your technicians work in plant rooms, basements or risers — yes, and test it before buying.
Internal links: #9 field service buyer’s guide, #14 custom vs off-the-shelf, /industries, /contact. External references: your national fire safety authority and accreditation scheme (e.g. NFPA in the US, BAFE/FIA schemes in the UK) for the inspection standards that apply to your work. CTA: “If your regime isn’t served by anything on the market, we build software for exactly this kind of operation.” → /contact