NFPA in USA

Authority workflow

Inspection and Testing Forms Workflow

A workflow for organizing inspection, testing, maintenance, water supply, alarm circuit, and deficiency records before NFPA 25 or NFPA 72 review.

fire protection inspection testing forms workflow4 checks5 form fields

Priority

3

Authority inputs

Checklist

4

Review checks

Source refs

4

Official/source-class entries

Source priority

Record the source that controls the project before relying on worksheet or calculator output.

SourceUseRecord
Adopted NFPA 25 or NFPA 72 editionIdentify inspection, testing, and documentation basis.Standard edition and adopted source.
Facility recordsCompare current readings with prior tests and known impairments.Prior report, deficiency log, and test date.
AHJ or owner requirementsCapture local form, frequency, and reporting expectations.Required form template or reporting portal note.

Source directory

Official entry points and source classes used to verify the authority record. These links do not replace state, local, or AHJ confirmation.

SourceClassUseLimitChecked
Local AHJ, building department, or fire prevention bureauJurisdiction source classPrimary verification source for local amendments, permit path, and approval expectations.Requires project address or jurisdiction; local amendments can override generic assumptions.2026-06-19
NFPA 25 standard page Official NFPA standard entryOfficial NFPA entry point for inspection, testing, and maintenance edition-basis context.Do not copy standard text; use only as an official source link and edition-basis record.2026-06-19
NFPA 72 standard page Official NFPA standard entryOfficial NFPA entry point for fire alarm and signaling code context.Do not copy standard text; use only as an official source link and edition-basis record.2026-06-19
Project specifications, owner criteria, insurer, and listingsProject source classCaptures requirements that may exceed adopted code or baseline calculator assumptions.Project-specific; cannot be generalized across all users or states.2026-06-19

Checklist

Use this as a workpaper checklist before submittal, AHJ coordination, or final design reliance.

ItemEvidenceOwner
System and test scope identifiedRiser, panel, circuit, pump, hydrant, or system IDTechnician
Measurements recorded with unitsFlow, pressure, voltage, current, time, or status readingTechnician
Deficiencies classifiedDeficiency note, impairment status, or corrective actionInspector
Retest or follow-up assignedResponsible party and due dateFacility or contractor

Form fields

Fields to retain in the project record or worksheet notes.

FieldPurposeRequired
Inspection dateSets the record date for recurring inspection history.Required
System IDIdentifies the tested system or circuit.Required
Measured resultStores the field value used by worksheets or calculators.Required
Deficiency statusSeparates pass, impairment, repair, and retest actions.Required
Next action dateKeeps unresolved work visible.Conditional

Project record worksheet

Use these record sections to keep project identity, workflow inputs, source evidence, and closeout status together.

Project identity

Tie the authority record to one project, jurisdiction, system, and review date.

FieldRecord to keepRequiredEvidence
Project nameProject identifier used on drawings, calculations, and submittal logs.RequiredProject title block or permit application
Project addressStreet address or campus/location identifier for jurisdiction routing.RequiredPermit application, drawing title block, or owner record
JurisdictionState, city, county, fire district, or other enforcing jurisdiction.RequiredPermit application or AHJ directory
System scopeSprinkler, fire alarm, water supply, pump, inspection/testing, or mixed scope.RequiredDrawing scope, test report, or worksheet name
Record dateDate this authority record was prepared or last reviewed.RequiredRecord issue date

Inspection and testing record

Retain field measurements, deficiency status, and retest actions for NFPA 25 or NFPA 72 review context.

FieldRecord to keepRequiredEvidence
Inspection or test eventInspection date, test type, technician, and system or circuit ID.RequiredInspection report or service ticket
Measured valuesFlow, pressure, voltage, current, time, status, or other measured result with units.RequiredField readings, meter output, or test form
Deficiency classificationPass, deficiency, impairment, repair required, or retest required.RequiredDeficiency log or inspection report finding
Retest or follow-upResponsible party, due date, corrective action, and retest requirement.ConditionalCorrective action log or owner notification
Worksheet comparisonWater supply, alarm circuit, pump, or worksheet value affected by the test record.ConditionalLinked worksheet or calculator result

Source evidence

Retain the source trail used to support the authority decision without publishing unsupported legal conclusions.

FieldRecord to keepRequiredEvidence
Adopted NFPA 25 or NFPA 72 editionStandard edition and adopted source.RequiredIdentify inspection, testing, and documentation basis.
Facility recordsPrior report, deficiency log, and test date.RequiredCompare current readings with prior tests and known impairments.
AHJ or owner requirementsRequired form template or reporting portal note.RequiredCapture local form, frequency, and reporting expectations.

Review closeout

Record the pass/fail status of each stop point before moving calculator or worksheet output forward.

FieldRecord to keepRequiredEvidence
Record completenessTest date, system ID, measured values, and technician are recorded.RequiredDo not archive as a final ITM record.
Deficiency handlingDeficiencies have responsible party and next action.RequiredEscalate as open issue.
Worksheet handoffWater supply or alarm values are linked to the related worksheet.RequiredEnter readings into the appropriate worksheet before comparison.

Closeout records

Keep these items with the project file before treating the authority workflow as complete.

RecordStatus
Inspection forms record issue date and reviewer.Retain with project file
Source links or source-class notes used for the project decision.Retain with project file
Open AHJ, local amendment, or project-specification conflicts.Retain with project file
Related worksheet, calculator, reference, or standard hub used after this authority record.Retain with project file

Acceptance gates

Stop points that prevent calculator output from being treated as final without authority context.

GatePass conditionFail action
Record completenessTest date, system ID, measured values, and technician are recorded.Do not archive as a final ITM record.
Deficiency handlingDeficiencies have responsible party and next action.Escalate as open issue.
Worksheet handoffWater supply or alarm values are linked to the related worksheet.Enter readings into the appropriate worksheet before comparison.

Workflow handoffs

Open the project workflow after the authority record is documented.

TypeLinked workflowOpen
WorksheetHydrant Flow and Water Supply WorksheetOpen
WorksheetFire Alarm Battery and NAC WorksheetOpen
ReferenceUS Code Adoption and AHJ CheckpointsOpen
ReferenceAWG Wire Resistance Table for Fire Alarm CircuitsOpen
ReferenceSprinkler Pipe Internal Diameter ReferenceOpen
Standard hubNFPA 25 Flow Test and Water Supply CalculatorsOpen
Standard hubNFPA 72 Fire Alarm CalculatorsOpen
Engineering disclaimer
NFPA in USA provides engineering workpapers, calculation checks, and reference tables for project screening and coordination. Final design decisions, code interpretations, submittals, and acceptance records must be completed by qualified professionals and verified against the adopted code, project criteria, listings, and Authority Having Jurisdiction requirements. This site does not issue signed or sealed engineering documents.

FAQ

What is the inspection and testing forms workflow for?+
It keeps jurisdiction, AHJ, adopted edition, submittal, and inspection records visible before calculator or worksheet results are used on a project.
Does this replace the AHJ or adopted code?+
No. It is a project record workflow. Always verify adopted codes, local amendments, required editions, and approval requirements with the applicable Authority Having Jurisdiction.
Why is this separate from a calculator?+
A calculator produces a number. Authority records explain whether that number is being used under the correct jurisdiction, standard edition, review path, and project criteria.