Inspection reports and submittals

A rejected submittal is not a paperwork problem. It is a truck problem. When the fire marshal's office bounces a report, someone drives back to re-verify a gauge reading, re-sign a page, or collect the serial number the form needed the first time. You pay a technician twice for a job you billed once. The pages in this section exist to make the first submission the last one: which form the jurisdiction actually wants, what each field expects, and what gets reports kicked back.

The inspection report is not the record of completion

The inspection report documents periodic inspection, testing, and maintenance of an existing system, on cycles set by NFPA 25 (2023 edition) for water-based systems and NFPA 72 (2022 edition) for fire alarms. The record of completion documents a new installation or an alteration; NFPA 72 Chapter 7 treats it as the system's birth certificate. The two get conflated constantly, and filing one where the jurisdiction expects the other is a rejection cause all by itself.

Official forms are linked, never mirrored

Every form page here links to the current version at the government host that owns it: state fire marshal, county, or city portal. We never host copies. NFPA standards and the forms built on them are copyrighted, and a mirrored PDF goes stale the day the jurisdiction revises it. The official link is the only version worth filling out.

Where the rejection guidance comes from

The rejection causes listed on these pages are first-party operational data: patterns from reports Plaw files and tracks for the contractors it operates for, labeled as such wherever they appear. Nothing is scraped from forums or guessed from the form layout. Jurisdiction-specific filing rules live in the jurisdictions section. The terms these forms lean on, ITM to AHJ, are defined in the glossary.

The authority having jurisdiction has the final word. Where any page here and your AHJ disagree, follow the AHJ.