A complete fire district compliance tracking system

It is the first thing worth asking. The honest answer is that a filing costs us storage and a little compute, and there is nothing else to recover.

• Nothing your finance office has to approve. No license, no per-seat fee, no implementation project, no minimum volume and no renewal. There is no contract value to defend at budget time because there is no contract value.
• The contractor pays per filing, and pays less than they do today. They are already paying a per-report fee to file into whatever your district uses now. That fee is what funds this.
• There is no field sales team and no per-district implementation. That is most of what a system like this normally has to charge for. Your buildings are loaded from county data and your settings are screens you fill in yourself.
• The surcharge is how your district shares in it rather than us keeping the difference. You set the rate.

The full rate card, a month worked through, and a plain account of how we make money are on the pricing page.

A per-filing amount your district sets, added on top of our fee. The contractor pays it and your district receives it.

• You set it, from your own screen, in dollars. Not a quote, not a contract amendment, not a request to us. Setting it to zero is also an option.
• A change never rewrites history. A new rate supersedes the old one from the day you set it; it is never edited in place and never backdated. Filings already made keep the amount they were charged, so an invoice from March still reconciles in November.
• We do the invoicing, not you. Contractors are billed once a month, itemized by building, date and fee, and we collect it. Your district raises no invoice, chases no payment and reconciles nothing. Your surcharge is totaled for you as it goes, kept separate from what has been billed and what has been paid, so you can always see which is which.
• It is fenced to your district. A contractor filing in three districts gets one invoice carrying all three surcharges, and each district sees only its own share.

Districts do not inspect the same things. Every check on every form can be switched off, re-graded, or given your own code reference, and you can add your own.

• Add a check, or something you simply want recorded. “Where is the Knox box” has no pass and no fail. Set that as a recorded field and it prints on the report, where an officer standing at the building at three in the morning can read it.
• Re-grade anything: deficiency or observation. A failed check either puts the building on your deficiency list or becomes a note on the report. You decide which, per item, with your own citation attached.
• Switch off what you do not inspect. A check your district has turned off will not show up on an inspection report.
• Changes never reinterpret a report you already accepted. They apply to new filings only, and every change is logged with who made it and what it was before, so two reports a year apart carrying different checks have an explanation.

14 forms, 232 graded checks between them:

• Fire Alarm System
• Sprinkler System
• Fire Pump
• Standpipe System
• Private Fire Hydrants
• BDA / Emergency Radio Communication
• Smoke Control System
• Gas Detection System
• Special Suppression System
• Backflow Prevention Device
• Exit Sign & Emergency Lighting
• Portable Fire Extinguishers
• Kitchen Hood Suppression
• Fire & Smoke Dampers

Multi-step, saves as it goes, resumes on another device, takes photographs, collects a signature, and prints a preview before anything is filed. See one being filled in, and the report it produces, in the guided demo.

This is what the standard form buys you. A deficiency arrives as a record naming a building, a system, a finding and a date, instead of a sentence buried in a scan. So the list of deficiencies for a building is immediately updated, and the notice email to the property manager is sent without someone needing to verify a picture of a document.

• Compliant, deficient, delinquent, never inspected, and due soon. Five working views over the same filings, so the conversation can happen before the date passes rather than after.
• Notices go out on their own, under your name and crest. Naming the actual findings and the date each one is due, not a count. Property owners get a detailed list of inspection deficiencies that they need to fix and when.
• One notice per missed deadline, not one a night. The system checks every night, but it remembers who it has already emailed. A property manager gets one notice when a deadline is missed, not the same email every day until the work is done.
• A deficiency is closed by an inspector going back. Open findings are shown to an inspector before they start the inspection, so they can focus on what was broken last time.

The system comes loaded with nine different reports, all designed to give insight into the whole district’s compliance reporting ecosystem.

• The reports: program coverage · compliance by system type · delinquency aging · cure performance · filing activity · commonest findings · contractor activity · surcharge by contractor · notices sent and who could not be reached.
• Every one of them exports. Each one saves as a CSV file you can open in Excel or attach to an email.
• Need it cut a different way? Tell us the shape your board prefers and we will build that report for your district.

A device list is a fact about the building, not a contractor’s work product. So it stays with the building when the company servicing it changes.

• The next inspector opens a list, not last year’s PDF. Whoever inspects next pre-loads the equipment already recorded, so a building with 711 detectors is cataloged once. Identity only: what the device is and where it is. Nothing about how it tested ever carries forward, just the existence of it, so it does not have to be re-discovered.
• Your officers can pull up a building’s whole equipment list. Every system at once, with what each device is, where it is and how it tested on the last standing filing, and it exports.
• Every report says how much of the building was actually tested. Tested against listed, for each type of device: forty of sixty smoke detectors, not just “smoke detectors: pass”. A partial inspection is a real thing that happens, and the report says so on its face instead of reading like a complete one.
• It is never published. An equipment list is a map of a building’s fire protection, so it is treated as confidential information.

Every filing renders a PDF, which is hashed and stored exactly as it was filed. The row behind it refuses to be edited or deleted. That is enforced by the database, not by a policy somebody has to follow.

• A correction is a new record that supersedes the old one. Never an edit. The history says what was believed and when, which is the question a dispute actually asks. Corrections cost the contractor nothing.
• The stored PDF is the artifact, not a regeneration. Report layouts change. A report regenerated three years later would carry sections that did not exist when it was filed. We keep the bytes so the file is untouched by changes.
• Your crest and colors, and the inspection company’s own mark. Both sit in the report header: yours says whose records it was filed into, theirs says who performed the inspection and signed for it. Frozen into each PDF at the moment of filing, so rebranding next year does not restyle last year’s records. Contractor marks are yours to switch off.

There is no signed district yet. That is the offer: you would be the first, and being first is what buys you influence over how this works.

• You describe what your inspections need and it gets built. Not filed against a roadmap you will never see, and not quoted as custom development. The same goes for anything that turns out to be wrong.
• There is nothing to migrate and nothing to unwind. Your buildings come from county data, contractors register themselves, and if it does not suit you, you stop.
• You are not calling a support queue. You are talking to the person who wrote the thing you are asking about.

Questions: get in touch. Or walk the whole product first, in the guided demo.