Inspection software for fire protection contractors: what to look for
What a fire protection contractor actually needs from inspection software: NFPA 25, 72 and 10 frequencies scheduled per device, offline field work, evidence a customer can check, and a record that survives an AHJ visit. The evaluation criteria, and the questions that separate real options from demos.
By Hovermarks team
Quick answer. A fire protection contractor's software has to do four things well: schedule NFPA 25, 72, 10 and 110 frequencies per device across every customer site, work with no signal in a mechanical room, produce a record the building owner and their AHJ can check without calling you, and keep a per-asset history that answers "when was this last tested" in seconds. Everything else is preference. This guide is the evaluation criteria, in the order they matter.
Most software written for this trade started as either a work-order system with inspections bolted on, or a forms app with no idea what NFPA 25 is. The difference shows up in month three, when the schedule has drifted and nobody can produce last year's records for a specific riser.
The four criteria that decide it
1. Frequency scheduling per device, not per job
NFPA frequencies attach to equipment, not to visits: a wet-pipe system carries monthly gauges, quarterly alarm tests, semi-annual main drains, an annual inspection and a 5-year internal. A dry system adds weekly air-pressure checks. Extinguishers run monthly, annual, 6-year and hydro on their own clocks. Multiply that across every customer site.
Ask a vendor: can each asset carry its own next-due date, and can I see everything overdue across all customers on one screen? If the answer is "you'd create a recurring job", the schedule will drift the first time an engineer reschedules.
Our ITM schedule builder shows the shape of the calendar a mixed site actually generates.
2. Offline that genuinely works
Sprinkler risers live in basements; generators live in plant rooms; neither has signal. "Offline mode" that queues a form but loses photos, or that needs the app opened online first that morning, fails in the field.
Ask: what happens if the engineer opens a cold device with no signal, does three inspections with photos, then drives home? The honest answer includes local drafts, compressed photos held on-device, and sync on return.
3. Evidence the customer can check without you
The building owner's insurer or AHJ asks for evidence. If every request means your office digging out PDFs one at a time, you are the bottleneck.
Ask: can a third party check a whole period's records, with who did each inspection and when, without a login and without contacting us?
4. A per-asset history an AHJ can walk
The question at inspection is never "show me your jobs". It is "show me the last test of this device". If the system files by work order, you spend the visit searching.
Ask: can I scan a device and see its full history right there?
Questions that separate real options from demos
- What happens when a customer changes contractor: can they take their data?
- Are inspections and reports capped or metered per month?
- Can subcontractors be given access limited to their own inspections and assigned work?
- What does the AHJ see when they scan a tag?
- Does the price include the templates, or is NFPA content an add-on?
- Is storage of inspection photos metered?
Where Hovermarks fits
Hovermarks was built for the per-asset shape of this work: QR-tagged devices each carrying its own schedule and next-due date, an installable phone-browser app that holds an in-progress submission through a signal drop, compressed photos, branded PDF reports with the technician's sign-off signature, auditor packs that put a period's records in one PDF for an AHJ or insurer, and unlimited storage on every plan so evidence is never the thing you ration. Pricing starts at $19 per user per month with a 30-day trial, unlimited assets while you evaluate, and no card required.
See the fire inspection solution for the workflow, or pricing for the plan detail.