Authority workflow
AHJ Contact Checklist
A checklist for preparing concise AHJ questions, recording responses, and keeping jurisdiction direction attached to fire protection worksheets.
AHJ contact checklist fire protection4 checks5 form fields
Priority
3
Authority inputs
Checklist
4
Review checks
Source refs
3
Official/source-class entries
Source priority
Record the source that controls the project before relying on worksheet or calculator output.
| Source | Use | Record |
|---|---|---|
| Fire marshal or fire prevention bureau | Confirm fire code interpretations and fire protection submittal expectations. | Office, contact, date, and response summary. |
| Building department | Confirm permit path, adopted building code, and plan review process. | Department contact and permit notes. |
| Water purveyor or utility | Confirm hydrant flow data, backflow, meter, and service constraints. | Utility contact and water supply comments. |
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 |
|---|---|---|---|---|
| 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 |
|---|---|---|
| Question list prepared before contact | Numbered AHJ question log | Project lead |
| Code section or project condition attached to each question | Drawing note, code section, or worksheet field reference | Designer |
| Response recorded with date and source | Email, meeting minutes, plan review note, or call log | Permit coordinator |
| Worksheet assumptions updated | Related worksheet input or QA gate note | Engineer of record |
Form fields
Fields to retain in the project record or worksheet notes.
| Field | Purpose | Required |
|---|---|---|
| AHJ office | Identifies the approving office or reviewer. | Required |
| Contact method | Records whether the response came from email, meeting, call, or plan review comment. | Required |
| Question | Keeps the request narrow and tied to a project condition. | Required |
| Response | Records direction without relying on memory. | Required |
| Affected worksheet field | Connects AHJ direction to the calculation workflow. | 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 |
AHJ contact record
Turn informal AHJ communication into a traceable project decision record.
| Field | Record to keep | Required | Evidence |
|---|---|---|---|
| AHJ office and reviewer | Office name, reviewer name if available, role, and contact channel. | Required | Email signature, meeting invite, plan review portal, or call log |
| Question asked | Specific project condition, code basis, drawing note, or worksheet assumption being asked. | Required | Numbered AHJ question log |
| Response received | Direction received, limitations, date, and whether it is written or verbal. | Required | Email, meeting minutes, plan review comment, or call note |
| Written confirmation status | Confirmed in writing, pending written confirmation, or verbal only. | Required | Email thread or plan review record |
| Affected tool assumption | Worksheet field, calculator input, reference selection, or submittal note changed by the response. | Conditional | Updated worksheet or drawing revision note |
Source evidence
Retain the source trail used to support the authority decision without publishing unsupported legal conclusions.
| Field | Record to keep | Required | Evidence |
|---|---|---|---|
| Fire marshal or fire prevention bureau | Office, contact, date, and response summary. | Required | Confirm fire code interpretations and fire protection submittal expectations. |
| Building department | Department contact and permit notes. | Required | Confirm permit path, adopted building code, and plan review process. |
| Water purveyor or utility | Utility contact and water supply comments. | Required | Confirm hydrant flow data, backflow, meter, and service constraints. |
Review closeout
Record the pass/fail status of each stop point before moving calculator or worksheet output forward.
| Field | Record to keep | Required | Evidence |
|---|---|---|---|
| Traceable response | AHJ direction includes date, office, and project context. | Required | Treat as informal until written confirmation exists. |
| Scope match | The answer applies to the same occupancy, system, and permit scope. | Required | Re-ask with narrower project facts. |
| Worksheet update | Affected worksheet assumptions are updated or flagged. | Required | Keep calculator output in screening status. |
Closeout records
Keep these items with the project file before treating the authority workflow as complete.
| Record | Status |
|---|---|
| AHJ contact 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 |
|---|---|---|
| Traceable response | AHJ direction includes date, office, and project context. | Treat as informal until written confirmation exists. |
| Scope match | The answer applies to the same occupancy, system, and permit scope. | Re-ask with narrower project facts. |
| Worksheet update | Affected worksheet assumptions are updated or flagged. | Keep calculator output in screening status. |
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 AHJ contact 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.