Fire Prevention Inspection Software: When the Reinspection Never Happened and the Permit Fee Never Got Billed

The overdue list nobody can produce

Ask a fire marshal how many Group A assembly occupancies in the jurisdiction are past due for their annual, and watch what happens. In most divisions the answer lives in a workbook with a tab per inspector, last reconciled when the previous prevention chief retired. Some occupancies have been inspected twice this year because two inspectors both thought they owned the plaza on the north side. A handful of high rises have not been touched in three years because the inspector who carried them left and his tab went with him.

Then a fire kills someone in a building where a violation was written eighteen months ago and never reinspected. Now the question is not operational, it is legal, and the answer is a spreadsheet, a folder of Word notices and an inspector's memory. That gap is why cities fund this system, and it is why the requirement is a defensible record rather than a to do list.

Revenue leaks out of the same gap

Prevention divisions are usually fee funded, and the fees are the part that breaks first. Operational permits for hot work, hazardous materials storage, assembly occupancy and pyrotechnics get issued in the field and invoiced by whoever remembers. Plan review fees get collected at the counter under a schedule that was updated by ordinance last spring, though half the staff are still quoting the old numbers. False alarm ordinances almost always fail in the same way: the first two responses are free, the third one triggers a fee, and the system that counts responses is the CAD while the system that bills is city finance, and no one joined them.

The money is real. A mid sized city writing a few hundred operational permits and running a false alarm ordinance across thousands of monitored properties is carrying a five to six figure annual gap between what the ordinance authorises and what the treasurer actually receives. That is generally the number that unlocks budget for this project, and it is the number you should put in front of the finance director rather than a story about inspection cycles.

Your rules come from local ordinance, not from a product roadmap

This is the thing prevention software gets wrong most consistently. The adopted code edition is a local decision, so one county may be on a recent International Fire Code edition while the city inside it adopted an older one with amendments, and both are correct. Occupancy classification drives inspection frequency, and every jurisdiction sets its own frequency table, often risk based, often amended after an incident. Violation language has to cite the adopted section correctly or the notice fails at the hearing. Correction periods, the notice of violation format, the escalation to an administrative citation, the appeal window and the fee schedule all come from ordinance, and a council can change any of them at a Tuesday meeting.

Any product that models this as a fixed checklist with a vendor maintained code library is going to be wrong for you somewhere, and it is going to be wrong in the place where you need it to be right, which is the notice you hand to a property owner who has a lawyer.

Where First Due, ESO, ImageTrend and CentralSquare stop

These are credible products and several of them are genuinely strong at the field inspection experience. Be precise about their limits before you sign.

• Ordinance level configuration. Fee schedules, escalation steps and appeal timelines tend to be settings the vendor controls or configuration deep enough that the division stops touching it. When your council amends the false alarm ordinance, you want to change a table that afternoon.
• The finance connection. Most of these systems can produce an invoice. Very few of them post a receivable into Tyler, BS&A, Springbrook or whatever your city runs, apply the payment back, and let the treasurer chase the delinquency through the normal process. That gap is where fee revenue dies.
• Offline behaviour. A strip mall basement, a rural propane facility and a parking structure all have no signal. Products differ widely here, and the honest test is to take the app into your worst building and write a full inspection with photos, then close the app and reopen it.
• Sharing occupancy data with operations. Your inspection record contains the best knowledge in the department about hazards, alarm panel locations and knox box placement, and it should be reaching the CAD and the mobile data terminals as preplan data. In most deployments it stays inside prevention.
• Enterprise permitting overlap. If your city already runs Accela, CityView or similar for building permits, a separate fire product means two vendors, two vendor relationships and a contractor who has to deal with both.

What a custom build has to include

Start with the occupancy, not the inspection. The occupancy is the durable record: address, classification, square footage, systems installed, hazards, contacts, permits held, history. Tenants change, owners change, businesses close and reopen, and the record has to survive all of it without losing the fire history of the building. Then attach a cycle rule to each occupancy driven by classification and risk, so the overdue list is computed rather than maintained.

The field app has to work with no connectivity and sync cleanly when it comes back, including photos taken at full resolution. The violation library carries the code citation, the standard correction language and the default correction period, and it is editable by the fire marshal when the jurisdiction adopts a new edition. Every notice is generated from that library, so the language on the notice matches the citation and both are reproducible years later.

Reinspection is scheduled automatically the moment a violation is written, and escalation is a state machine: correction period expires, reinspection, still in violation, administrative citation, escalating fee, referral to the city attorney. Each transition records who, when and on what evidence. Permits and fees post to the city financial system rather than living in a fire division spreadsheet, and the false alarm count comes from the CAD automatically so the third response triggers a billable event without anyone counting.

Finally, push the occupancy data out to operations, because the whole department has been paying for prevention to collect it.

What it costs and how long it takes

Across this category, our delivery experience is a first release at $60,000 to $140,000 in 10 to 16 weeks, covering the occupancy inventory with cycle rules, the offline inspection app, the violation library with citation aware notices, reinspection scheduling and the overdue dashboard. That is the piece that closes the liability gap and it is worth doing first on its own.

The full program at $180,000 to $400,000 over 6 to 12 months adds operational permits with renewals, plan review routing with markup, the false alarm ordinance engine fed from CAD, hearings and appeals tracking, the finance system integration and a public facing portal where a business owner can see their permit status and pay.

Cost drivers specific to prevention: the state of your existing occupancy list, which is usually the single biggest unknown and often requires a physical canvass in phase one. The financial system on the other end, since posting receivables into a municipal ledger is a real integration with real accounting rules attached. Whether plan review is in scope, because document markup and routing between fire, building and planning is its own project. And whether the county or neighbouring cities want in, since multi jurisdiction means multiple adopted codes and fee schedules running side by side in the same system.

When buying is the right call

Buy if your division inspects a few hundred occupancies a year with one or two inspectors and your city has no meaningful false alarm or permit revenue. The overhead of owning software will exceed the benefit and a hosted product with a decent field app is the correct answer.

Buy if your city already runs a full permitting and licensing platform that community development uses, and fire can be added as another record type with your inspection checklists. Two systems that both hold a business address is a data problem you will regret. The exception is when that platform cannot handle your offline field work or your notice language, which does happen, and then you build the fire piece and integrate the occupancy record.

Build when the fee gap alone pays for it, when your adopted code and fee schedule change more than once a year, when inspectors are losing work in buildings with no signal, or when you have already been asked in a deposition to produce the inspection history of a specific address and the answer took a week.

How to choose a developer

Ask them to model an occupancy that changes tenants twice and owners once over five years while keeping its violation history intact. If they draw a business record, they will build you a licence tracker, and you will lose the building.

Ask how the notice of violation is produced. The correct answer involves a violation library with code citations and correction periods that the fire marshal edits, generating a document that is stored as issued, immutable, with proof of service. If the answer is a Word template, the notice will drift from the citation and your hearings will get harder.

Test offline with your own worst building before contract. Not a demo environment, your building. Write a real inspection with ten photos, kill the connection, reopen the app and see what survived.

Ask what municipal financial systems they have posted to and name yours. Tyler Munis, BS&A, Springbrook and Caselle are different problems, and the difference between producing an invoice and posting a receivable that the treasurer can collect is the whole point of the fee side.

Ask who owns the code and get it in writing before kickoff, including the hosting accounts and the database. At Digital Heroes it is yours from the first commit. Then, before anything else, have someone pull a count of how many occupancies in your jurisdiction are currently past due. Whatever number comes back, and however long it takes to produce, is your business case.