Authority workflow
NFPA 13, 72, and 25 Edition Basis Worksheet
A worksheet for recording which NFPA 13, NFPA 72, and NFPA 25 editions apply by adoption, contract, listing, owner criteria, or AHJ direction.
NFPA edition basis worksheet4 checks5 form fields
Priority
3
Authority inputs
Checklist
4
Review checks
Source refs
6
Official/source-class entries
Source priority
Record the source that controls the project before relying on worksheet or calculator output.
| Source | Use | Record |
|---|---|---|
| Adopted code text | Identify referenced NFPA edition for enforceable requirements. | Code section and referenced edition. |
| Project specifications | Identify contract-required standards and stricter project criteria. | Specification section and issue date. |
| AHJ direction | Resolve conflicts between adopted code, current edition, and project requirements. | AHJ response and date. |
Source directory
Official entry points and source classes used to verify the authority record. These links do not replace state, local, or AHJ confirmation.
| Source | Class | Use | Limit | Checked |
|---|---|---|---|---|
| NFPA 13 standard page | Official NFPA standard entry | Official 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 entry | Official 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 |
| NFPA 25 standard page | Official NFPA standard entry | Official 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 |
| State code agency or state fire marshal | Jurisdiction source class | Primary verification source for adopted state building or fire code edition. | Requires project state; this site must not infer the answer without a cited state source. | 2026-06-19 |
| Local AHJ, building department, or fire prevention bureau | Jurisdiction source class | Primary verification source for local amendments, permit path, and approval expectations. | Requires project address or jurisdiction; local amendments can override generic assumptions. | 2026-06-19 |
| Project specifications, owner criteria, insurer, and listings | Project source class | Captures 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.
| Item | Evidence | Owner |
|---|---|---|
| NFPA 13 basis recorded | Adopted edition, specification, or AHJ note | Sprinkler designer |
| NFPA 72 basis recorded | Adopted edition, specification, or AHJ note | Fire alarm designer |
| NFPA 25 basis recorded | Adopted edition, owner program, or AHJ note | ITM provider |
| Edition conflict resolved | Decision note where adopted, current, and specified editions differ | Engineer of record |
Form fields
Fields to retain in the project record or worksheet notes.
| Field | Purpose | Required |
|---|---|---|
| Standard | Identifies NFPA 13, NFPA 72, NFPA 25, or another referenced standard. | Required |
| Edition year | Records the edition used for worksheet assumptions. | Required |
| Basis type | Distinguishes adopted code, specification, listing, owner requirement, or AHJ direction. | Required |
| Source note | Captures the source section, document, or contact. | Required |
| Conflict note | Explains edition differences or unresolved interpretation. | 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.
| Field | Record to keep | Required | Evidence |
|---|---|---|---|
| Project name | Project identifier used on drawings, calculations, and submittal logs. | Required | Project title block or permit application |
| Project address | Street address or campus/location identifier for jurisdiction routing. | Required | Permit application, drawing title block, or owner record |
| Jurisdiction | State, city, county, fire district, or other enforcing jurisdiction. | Required | Permit application or AHJ directory |
| System scope | Sprinkler, fire alarm, water supply, pump, inspection/testing, or mixed scope. | Required | Drawing scope, test report, or worksheet name |
| Record date | Date this authority record was prepared or last reviewed. | Required | Record issue date |
NFPA edition basis record
Document the edition basis for each applicable NFPA standard before final worksheet reliance.
| Field | Record to keep | Required | Evidence |
|---|---|---|---|
| NFPA 13 edition basis | Edition year and basis type for sprinkler design assumptions. | Required | Adopted code reference, specification, listing, or AHJ direction |
| NFPA 72 edition basis | Edition year and basis type for fire alarm and signaling assumptions. | Required | Adopted code reference, specification, listing, or AHJ direction |
| NFPA 25 edition basis | Edition year and basis type for inspection, testing, and maintenance records. | Required | Adopted code reference, facility program, contract, or AHJ direction |
| Edition conflict note | Difference between adopted edition, current edition, project specification, listing, or AHJ direction. | Conditional | Decision log or AHJ question response |
| Stop gate status | Whether edition basis is verified, pending AHJ response, or unknown. | Required | Authority record closeout note |
Source evidence
Retain the source trail used to support the authority decision without publishing unsupported legal conclusions.
| Field | Record to keep | Required | Evidence |
|---|---|---|---|
| Adopted code text | Code section and referenced edition. | Required | Identify referenced NFPA edition for enforceable requirements. |
| Project specifications | Specification section and issue date. | Required | Identify contract-required standards and stricter project criteria. |
| AHJ direction | AHJ response and date. | Required | Resolve conflicts between adopted code, current edition, and project requirements. |
Review closeout
Record the pass/fail status of each stop point before moving calculator or worksheet output forward.
| Field | Record to keep | Required | Evidence |
|---|---|---|---|
| Edition traceability | Each applicable NFPA edition has a source and basis type. | Required | Hold worksheet output as preliminary. |
| Conflict review | Edition conflicts are resolved or assigned to AHJ/project lead. | Required | Escalate before submittal. |
| Tool alignment | Calculator assumptions and worksheet QA gates reference the same edition basis. | Required | Revise worksheet inputs before relying on results. |
Closeout records
Keep these items with the project file before treating the authority workflow as complete.
| Record | Status |
|---|---|
| Edition basis 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.
| Gate | Pass condition | Fail action |
|---|---|---|
| Edition traceability | Each applicable NFPA edition has a source and basis type. | Hold worksheet output as preliminary. |
| Conflict review | Edition conflicts are resolved or assigned to AHJ/project lead. | Escalate before submittal. |
| Tool alignment | Calculator assumptions and worksheet QA gates reference the same edition basis. | Revise worksheet inputs before relying on results. |
Workflow handoffs
Open the project workflow after the authority record is documented.
| Type | Linked workflow | Open |
|---|---|---|
| Worksheet | NFPA 13 Hydraulic Design Worksheet | Open |
| Worksheet | Fire Alarm Battery and NAC Worksheet | Open |
| Worksheet | Hydrant Flow and Water Supply Worksheet | Open |
| Reference | US Code Adoption and AHJ Checkpoints | Open |
| Standard hub | NFPA 13 Sprinkler System Calculators | Open |
| Standard hub | NFPA 72 Fire Alarm Calculators | Open |
| Standard hub | NFPA 25 Flow Test and Water Supply Calculators | Open |
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 NFPA edition basis 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.