Who Owns Your Fire Inspection Records? (Hint: Not Your Contractor)

Here is a story that plays out somewhere in this country every week.

A property manager — call her Dana — runs a portfolio of eleven buildings. Her fire protection contractor has serviced them for six years: quarterly sprinkler inspections, annual main drain tests, the fire pump flow test every spring. The relationship is fine until it isn't. Pricing creeps up, response times slip, and Dana does what any competent manager does: she bids the work out and switches vendors.

Thirty days later, her access to the old contractor's customer portal stops working. She emails to ask for copies of the inspection history. She gets a polite reply saying they'll "look into it," then silence. The old contractor has no contractual obligation to spend staff time exporting reports for an ex-customer, and no commercial incentive either.

Four months after that, one of Dana's buildings has a small electrical fire. Nobody is hurt; the sprinkler system does its job. Then the insurance carrier's adjuster asks for three years of inspection, testing, and maintenance records for that system.

Dana has invoices. She does not have records.

What the standard actually says

Most property managers assume the inspection records belong to whoever wrote them — the contractor performed the test, the contractor keeps the paperwork, and the contractor produces it if anyone official ever asks.

NFPA 25 — the standard governing inspection, testing, and maintenance (ITM) of water-based fire protection systems — sees it differently. Chapter 4 places the responsibility for maintaining the systems, and for keeping the records that document that maintenance, on the owner of the property or the owner's designated representative. In a managed building, that designated representative is the property manager. The standard also spells out (in §4.3.2) exactly what each record must contain, and expects records to be retained and made available to the fire marshal — the authority having jurisdiction, or AHJ — on request.

Notice what's absent from that arrangement: the contractor. NFPA 25 treats the contractor as the qualified party who performs the work. The duty to hold the history never leaves the owner's side of the table. When the AHJ writes a violation for missing records, it goes to the building. When the insurer questions a claim over documentation gaps, the policyholder — not the contractor — absorbs the consequence.

The industry's tooling, though, is built the other way around. Inspection software is overwhelmingly sold to contractors. The reports live in the contractor's system, formatted the contractor's way, exported at the contractor's convenience. The party with the legal duty holds a login that works only as long as the business relationship does.

Five steps to take ownership

The fix isn't dramatic. It's a series of small, boring moves that most managers simply never get around to — until a records request makes it urgent.

1. Request your complete history today, while the relationship is good

Email your current contractor and ask for a full export of every inspection and test report for every building — as PDFs, not portal access. A good contractor will hand this over without friction. Do this now, not during a dispute or a vendor transition, when you have the least leverage and they have the least motivation.

2. Inventory your systems and map the required frequencies

You can't spot a gap in records you don't know you're supposed to have. Walk each riser room, list the systems — wet or dry sprinklers, standpipes, fire pumps, tanks, backflow preventers — and map each to its NFPA 25 intervals. Our plain-English frequency chart covers every water-based system from weekly to 5-year.

3. Set up a system of record that you control

Minimum viable version: a cloud folder per building, per system, per year, that your team owns. Better: a purpose-built system that ties each record to its required frequency, so a missing quarterly is visible as a gap instead of as an absence nobody notices. The test is simple — if your contractor vanished tomorrow, would your records still exist?

4. Write record delivery into the next contract

One paragraph fixes the incentive problem permanently: reports delivered as PDF within ten business days of service; all inspection data is the property of the owner. No reputable fire protection contractor will object. The ones who object are telling you something.

5. Put reminders on the frequencies, not on the contractor

The contractor's scheduler is optimized for their route density, not your compliance. Track every due date — especially the 3-year and 5-year tests that outlive vendor relationships and staff tenure — on a calendar your organization owns, and let the contractor respond to your schedule.

The ending Dana deserved

None of this is exotic. It's the same discipline you already apply to leases, insurance certificates, and elevator permits — applied to the records that carry the most liability per page of anything in your filing system.

That's the entire reason FireCode 360 exists: it's the system of record from step 3, the frequency map from step 2, and the reminder engine from step 5 in one place — where contractors are invited guests who feed your account, and every completed inspection becomes a photo-stamped PDF with the five §4.3.2 data points, permanently yours. Start a free trial — the first building takes about ten minutes.

FireCode 360 is a record-keeping tool and does not certify code compliance. Requirements paraphrased with section references only; verify against the current edition of NFPA 25 and your AHJ.