Fire protection service software: what a small extinguisher shop actually needs

Start with what the records have to show

Any fire extinguisher inspection software is only useful if it captures what your state and your customers' inspectors expect to see. A few examples from rule text you can read for free:

• Florida, rule 69A-21.241: the service tag must show "Do Not Remove", the extinguisher serial number, the name of the person who did the service ("Initials are not acceptable"), that person's permit number, the type of service, the type of extinguisher, the servicing company's name, street address and phone number, and the month and year of service shown "by means of perforation." The rule allows a tie-on tag or a pressure sensitive label or decal, and a new one goes on "each time a service is performed."
• Florida, rule 69A-21.251: invoices must show the business name, physical address and license number, and the license number "shall coincide with the permit number on the tags." Invoices must also list each extinguisher's serial number with the services performed and parts replaced for that unit, which may be on an attached sheet.
• Texas, 28 TAC 34.520(c): the tag carries "DO NOT REMOVE BY ORDER OF THE STATE FIRE MARSHAL", the firm's name, address, phone and certificate-of-registration number, the licensee's name, license number and signature ("a stamped signature is prohibited"), punched month, year and type of work, the service performed, the name and address of the owner or occupant, and the extinguisher type, size and location.
• Federal OSHA, 29 CFR 1910.157(e)(3): for covered workplaces, the employer "shall record the annual maintenance date and retain this record for one year after the last entry or the life of the shell, whichever is less."

In Florida and Texas the tag itself is a physical tag or adhesive label with the month and year punched or perforated, and Texas prohibits a stamped signature. Software does not replace the tag. What it can do is hold the same data per unit, so the tag, the customer report and the invoice all agree.

That last point matters most in Florida, where the invoice has to match the tag permit number and itemize work by serial number. If your software produces the invoice from the same per-unit service record the tech entered in the field, the serial numbers and work items carry over instead of being retyped at night.

Features that matter for a 1 to 10 tech shop

1. Per-unit tag records: serial number, type, size, location, service performed, parts, tech name and permit or license number, date. This is the core of any fire inspection app.
2. Customer reports: a clean PDF per site visit the building owner can hand to a fire inspector, listing every unit and any deficiency.
3. Invoices built from the service record: line items per serial number, which is how Florida rule 69A-21.251 asks invoices to itemize work.
4. QuickBooks Online sync: if your bookkeeper lives in QuickBooks, check exactly what syncs (customers, items, invoices, payments) and in which direction. "Integrates with QuickBooks" can mean anything from a one-way invoice push to full two-way payment status.
5. Recurring inspection reminders: annual service, 6 year maintenance and hydrostatic test due dates rolled into a monthly list of who is due, by customer and by route.
6. Offline phone use: techs work in basements, mechanical rooms and kitchens with no signal. Inspections should save on the device and sync later. Also check which devices are supported: some apps run only on iPad or iPhone.
7. Kitchen hood and emergency light coverage: if your shop also services hood suppression and emergency lights, one system should cover all three schedules (see below).
8. Pricing you can predict: per technician, per user, or flat monthly, plus any minimum team size or contract term.

Kitchen hoods and emergency lights run on different clocks

Extinguishers, hood suppression systems and emergency lights each follow a different standard and interval, so the reminder engine has to handle more than one schedule per customer. Two examples, as summarized by state agencies:

• Kitchen hood suppression: a Minnesota Department of Health guide, citing NFPA 96 (2011 edition) section 11.2.1, says the system must be serviced by trained, qualified persons at least every 6 months, in addition to monthly inspections. It cites section 11.2.4 for replacing metal-alloy fusible links at least semiannually.
• Emergency lighting: a South Dakota Department of Health test log, citing NFPA 101 (2000 edition) section 7.9.3, calls for a functional test at 30-day intervals for at least 30 seconds, and an annual test of battery-powered units for at least 1.5 hours. Check which edition your local authority has adopted.

In practice this means one customer site might have extinguishers due in March, a hood system due in March and September, and emergency lights on a 30-day test plus an annual 1.5-hour test for battery units. Software built only around extinguishers will leave the other two on a spreadsheet.

Comparing the three kinds of tools

Some named examples, using only what each vendor says on its own site:

Team-size floors matter. A one or two tech shop may fall below a platform's stated minimum, and per-technician pricing grows every time you hire. A flat monthly price is easier to budget but may cap features. Ask each vendor for the total monthly cost at your current headcount and at your headcount plus two.

Questions to ask in a demo

• Can I see one extinguisher's full history by serial number, and does the invoice pull from that record?
• Does the customer report show the tech's permit or license number the way my state requires?
• What exactly syncs to QuickBooks Online, in which direction, and how are payments matched?
• Does the app work offline on the phones my techs already carry, Android included?
• Can it track hood systems and emergency lights on their own schedules at the same site?
• Is pricing per technician, per user or flat, and is there a minimum team size or annual contract?
• If I leave, can I export all my customer, unit and service data?