Authority workflow
State and Local Code Adoption Workflow
A project intake workflow for documenting adopted state code, local amendments, referenced NFPA editions, and AHJ confirmation before using fire protection tools.
fire code adoption by state AHJ workflow4 checks5 form fields
Priority
3
Authority inputs
Checklist
4
Review checks
Source refs
5
Official/source-class entries
Source priority
Record the source that controls the project before relying on worksheet or calculator output.
| Source | Use | Record |
|---|---|---|
| State code agency or state fire marshal | Identify adopted building and fire code editions. | State code title, edition, effective date, and source link. |
| City or county code office | Find local amendments and permit-specific enforcement notes. | Local ordinance, amendment section, and jurisdiction contact. |
| Project AHJ | Confirm required code path, submittal expectations, and edition interpretation. | AHJ name, office, date, and documented direction. |
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 CodeFinder discontinued notice | NFPA source boundary | Documents that NFPA CodeFinder should not be treated as an active adopted-code database. | Use as a source-boundary note only; do not extract adoption facts from this page. | 2026-06-19 |
| ICC code adoption map | Model code adoption starting point | Starting point for researching I-Code adoption by state or jurisdiction. | Not a substitute for state, local, and AHJ verification; do not publish legal conclusions from this alone. | 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 |
|---|---|---|
| State adopted code edition identified | State code agency page or official code text | Designer or code consultant |
| Local amendments checked | Municipal code, fire prevention bureau page, or plan review note | Permit coordinator |
| Referenced NFPA editions confirmed | Adopted code text, project specification, or AHJ direction | Engineer of record |
| Project-specific criteria logged | Owner criteria, insurer comments, hazard report, or design narrative | Project lead |
Form fields
Fields to retain in the project record or worksheet notes.
| Field | Purpose | Required |
|---|---|---|
| Project jurisdiction | Identifies the state, city, county, or fire district for enforcement. | Required |
| Adopted building code | Sets the building code basis that may reference fire protection standards. | Required |
| Adopted fire code | Sets operational and fire prevention requirements. | Required |
| Local amendment notes | Captures stricter or modified local requirements. | Conditional |
| AHJ confirmation date | Records when assumptions were checked. | Required |
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 |
State and local adoption record
Document the code basis before a worksheet or calculator result is treated as project-ready.
| Field | Record to keep | Required | Evidence |
|---|---|---|---|
| State adopted building code | Code title, edition, effective date, and state source. | Required | State code agency or state fire marshal source |
| State adopted fire code | Fire code title, edition, effective date, and state source. | Required | State fire marshal or official state code source |
| Local amendment check | City, county, or fire district amendment status and source. | Required | Municipal code, local fire prevention bureau, or permit checklist |
| Referenced NFPA editions | NFPA 13, NFPA 72, NFPA 25, or other edition referenced by adopted code or AHJ. | Required | Adopted code text, project specification, or AHJ direction |
| Unresolved jurisdiction note | Any missing edition, local amendment, or conflicting authority path. | Conditional | Open issue log or AHJ question list |
Source evidence
Retain the source trail used to support the authority decision without publishing unsupported legal conclusions.
| Field | Record to keep | Required | Evidence |
|---|---|---|---|
| State code agency or state fire marshal | State code title, edition, effective date, and source link. | Required | Identify adopted building and fire code editions. |
| City or county code office | Local ordinance, amendment section, and jurisdiction contact. | Required | Find local amendments and permit-specific enforcement notes. |
| Project AHJ | AHJ name, office, date, and documented direction. | Required | Confirm required code path, submittal expectations, and edition interpretation. |
Review closeout
Record the pass/fail status of each stop point before moving calculator or worksheet output forward.
| Field | Record to keep | Required | Evidence |
|---|---|---|---|
| Jurisdiction basis | State and local adopted code sources are recorded. | Required | Do not finalize worksheet assumptions. |
| Edition basis | NFPA standard editions are identified or flagged as AHJ-required. | Required | Keep calculation output out of the project record until the edition basis is resolved. |
| Amendment review | Local amendments are checked or marked not found with source. | Required | Escalate to AHJ or code consultant. |
Closeout records
Keep these items with the project file before treating the authority workflow as complete.
| Record | Status |
|---|---|
| Code adoption 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 |
|---|---|---|
| Jurisdiction basis | State and local adopted code sources are recorded. | Do not finalize worksheet assumptions. |
| Edition basis | NFPA standard editions are identified or flagged as AHJ-required. | Keep calculation output out of the project record until the edition basis is resolved. |
| Amendment review | Local amendments are checked or marked not found with source. | Escalate to AHJ or code consultant. |
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 | Hazard Classification and Density Setup 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 code adoption 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.