Fire inspection app
- Technician hours this building needs in a year
- 34.2
- Of which the twelve monthly extinguisher visuals
- 17.6
- Of which the annual round
- 15.3
The inspection intervals on these pages come from 29 CFR 1910 subpart L, the federal floor for portable extinguishers, standpipe and hose systems, automatic sprinklers, fixed extinguishing systems and fire detection, read from the eCFR and linked on the page that uses them.
A fire inspection app is not a job app with a fire icon. The unit of work is not a job somebody scheduled, it is a system in a building with an interval attached to it, and the app's real job is to know what falls due next and what is still open. That is why the general field service products, which are built round a work order, make a fire contractor keep a second spreadsheet: the work order says what was done, and nothing in it says what has to happen in eleven months. This page sets out what a fire inspection app has to hold to be worth carrying into a plant room, and what it should do with each of those records afterwards.
Open the Fire inspection hours and cost Free to use. No account, no card, no trial clock.
Put the building in, then the systems in it
Not a customer and a job: a building, and the systems it carries. A sprinkler system, a standpipe class, an alarm panel, a kitchen suppression system, a count of extinguishers. Everything after this hangs off that list, and it is the part a job-shaped product has nowhere to put.
Attach the interval, and stop scheduling by memory
Each system carries the interval it is held to: the monthly extinguisher visual, the annual maintenance check, the annual main drain flow test, the inspector's test valve every two years, containers weighed at least semi-annually. Once the interval is on the system the next date is derived, and next quarter's route is a query.
Record the visit against the system, not the invoice
A visit tests systems, and each test has a result and a date. Recording it against the system is what makes the history readable a year later; recording it against the invoice is what makes a contractor open a filing cabinet when the fire marshal asks.
Raise deficiencies as things that stay open
A deficiency is not a note on a closed work order. It belongs to its system and stays open until a later visit clears it, because that list is the return work the inspection contract exists to generate and the one most often lost between a notebook and a van.
Produce the report before you leave
The owner gets the report on the day, not next week: what was tested, what was found, what is deficient and when each system is due again. Doing it on site is also the only reliable way to make sure the record matches what the technician actually saw.
Keep the year, because somebody will ask for it
The annual extinguisher maintenance record has to be retained for a year and produced on request, and an AHJ asking about a building will want more than that. A year of reports against a building, searchable, is the difference between answering in a minute and answering in a week.
Ask us about the Fire inspection app
Tell us how many buildings you inspect and what you are running the schedule on now.
What contractors ask about the Fire inspection app
What is the difference between a fire inspection app and field service software?
The unit of work. Field service software is built round a job: scheduled, done, billed. A fire inspection business is built round a system with an interval on it, and the next visit is derived from the last one rather than entered by a person. Everything else, the mobile forms, the photos, the invoicing, is available in both.
Does it work offline in a plant room?
It has to. Sprinkler risers and electrical rooms are exactly where signal is not, so a fire inspection app that cannot record a test and sync it later is one a technician will stop using inside a week.
What about barcode or QR tags on each device?
Useful, and a separate decision: tagging every device makes the walk faster and the record unambiguous, and it also means buying and applying tags to hundreds of devices before the benefit starts. Start with buildings and systems, add device-level tagging where the count justifies it.
How many buildings before software is worth it?
There is no number, but there is a symptom: the first missed annual. A contractor with forty buildings and a spreadsheet is usually fine until somebody leaves, and then a year of due dates leaves with them.
Will it tell me whether a system passes?
No, and be wary of anything that says it will. Whether a system complies is decided by the standard your AHJ has adopted and by the licensed inspector in front of it. What software can do is make sure the test happened, on the date it was owed, and that the result is written down.
Hydrantly Pro
Keeping the round: due dates, deficiencies and the file the AHJ asks for
Pro keeps the round: the buildings, the systems, the due dates and the deficiencies, so the schedule builds itself and nothing falls off the end of a year.
- TODO: what keeping this means to the buyer, one line (document.download_file)
- TODO: what keeping this means to the buyer, one line (document.remove_watermark)
- TODO: what keeping this means to the buyer, one line (document.save_and_reopen)
- TODO: what keeping this means to the buyer, one line (document.brand_own_logo)
- TODO: what keeping this means to the buyer, one line (document.bulk_export)
- TODO: what keeping this means to the buyer, one line (messaging.send)
- TODO: what keeping this means to the buyer, one line (payments.connect_stripe)
- TODO: what keeping this means to the buyer, one line (integrations.connect_books)
$49per month, whole team
Start Hydrantly Pro PricingHydrantly Pro is $49 a month for the whole business. It renews on the same day each month at the same price until you cancel, and the price and renewal date are shown again before you pay.