NFPA in USA

Authority workflow

Fire Protection Submittal Checklist

A submittal readiness workflow for keeping drawings, calculations, device data, water supply records, and AHJ notes organized before review.

fire protection submittal checklist4 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
Permit application requirementsIdentify required submittal documents and review format.Permit checklist and jurisdiction instructions.
Project specificationsCapture owner, insurer, and engineer requirements beyond baseline code.Specification section and submittal matrix.
AHJ commentsClose review comments before resubmittal.Comment response log and revised sheet/calculation reference.

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 13 standard page Official NFPA standard entryOfficial NFPA entry point for the sprinkler system installation standard.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
Drawings match calculation assumptionsSheet index, revision, design area, circuit, or riser referenceDesigner
Calculation worksheets includedHydraulic, battery, water supply, pump, or hazard worksheet outputEngineer or contractor
Product data supports inputsSprinkler listing, device current sheet, pump curve, or panel dataSubmittal coordinator
AHJ notes resolvedResponse matrix and revised document referenceProject lead

Form fields

Fields to retain in the project record or worksheet notes.

FieldPurposeRequired
Submittal package IDConnects documents, calculations, and revisions.Required
Drawing revisionPrevents calculations from being reviewed against stale drawings.Required
Calculation worksheet linksIdentifies supporting worksheet records.Required
Product data basisShows that listed data supports typed inputs.Required
Open commentsKeeps unresolved AHJ or reviewer issues 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

Submittal package record

Confirm drawings, calculations, product data, and AHJ comments are aligned before submittal or resubmittal.

FieldRecord to keepRequiredEvidence
Package ID and issue dateSubmittal package name, issue date, and resubmittal number if applicable.RequiredSubmittal transmittal or document control log
Drawing revision basisSheet index, revision date, and system area covered by the calculation.RequiredDrawing title block and sheet index
Calculation attachmentsWorksheet outputs, calculator results, hydraulic calculations, battery calculations, or water supply records included.RequiredCalculation package table of contents
Product data matchSprinkler listing, device current sheet, pump curve, panel data, or listing basis supporting inputs.RequiredManufacturer product data and listing sheets
Open AHJ/reviewer commentsUnresolved comments, responsible owner, and next action.ConditionalComment response matrix

Source evidence

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

FieldRecord to keepRequiredEvidence
Permit application requirementsPermit checklist and jurisdiction instructions.RequiredIdentify required submittal documents and review format.
Project specificationsSpecification section and submittal matrix.RequiredCapture owner, insurer, and engineer requirements beyond baseline code.
AHJ commentsComment response log and revised sheet/calculation reference.RequiredClose review comments before resubmittal.

Review closeout

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

FieldRecord to keepRequiredEvidence
Document matchDrawings, calculations, and product data reference the same system and revision.RequiredHold submittal package for coordination.
Calculation traceabilityEach calculation result links back to input source and worksheet gate.RequiredReturn to worksheet before submittal.
Comment closureAHJ comments are answered or assigned.RequiredDo not mark package ready.

Closeout records

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

RecordStatus
Submittal checklist 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
Document matchDrawings, calculations, and product data reference the same system and revision.Hold submittal package for coordination.
Calculation traceabilityEach calculation result links back to input source and worksheet gate.Return to worksheet before submittal.
Comment closureAHJ comments are answered or assigned.Do not mark package ready.

Workflow handoffs

Open the project workflow after the authority record is documented.

TypeLinked workflowOpen
WorksheetNFPA 13 Hydraulic Design WorksheetOpen
WorksheetFire Alarm Battery and NAC WorksheetOpen
WorksheetFire Pump Selection WorksheetOpen
ReferenceUS Code Adoption and AHJ CheckpointsOpen
ReferenceFire Sprinkler K-Factor TableOpen
ReferenceAWG Wire Resistance Table for Fire Alarm CircuitsOpen
Standard hubNFPA 13 Sprinkler System 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 submittal checklist 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.