Most departments that adopt NFPA 1620 do it for the same three reasons: ISO scoring, accreditation, and — most often — because an inspector or a chief has seen a post-incident report where a pre-plan would have changed the outcome. The standard itself is short and unambiguous about what must appear in a pre-incident plan. What it is not prescriptive about is how a department keeps that information accurate year-over-year across hundreds of occupancies.
This guide walks through what NFPA 1620 actually requires, how a working department turns those requirements into a repeatable inspection workflow, and the operational signals to look for when evaluating fire department pre-plan software to keep the standard intact.
For a product-level view of that workflow, see our NFPA 1620 pre-incident planning overview covering the six element groups, field review, and reportable plan output.
What NFPA 1620 is — and why departments adopt it
NFPA 1620 is the Standard for Pre-Incident Planning. It defines the data a fire department should capture about an occupancy before an incident, and the format that data should take when crews read it on scene. The standard is engineering guidance, not law, but adoption signals to your community, your ISO reviewer, and your mutual-aid partners that your department runs to a recognized professional standard.
Departments most often adopt NFPA 1620 alongside an ISO re-rating cycle, an accreditation push (CFAI or ProBoard records cross-referencing pre-plan coverage), or a regional mutual-aid agreement where neighboring departments want a shared baseline for pre-plan content.
The six required elements at a glance
The core of NFPA 1620 is the pre-plan record itself. The standard organizes the required content into six element groups. A compliant pre-plan has, at minimum, a populated field for each of the following:
- Construction and layout — building construction type, square footage, floor plans, occupancy class, and the usual paths of travel for occupants and crews.
- Hazardous materials and special risks — identified hazmat inventory, unusual process risks, and any prior incidents the department has responded to at the address.
- Water supply and hydrant coverage — the nearest hydrants, their flow rates, the static and residual pressures, and any drafting locations.
- Access and egress — driveways, apparatus positioning, key boxes (Knox), and the points crews should avoid when approaching under fire conditions.
- Utility controls — gas, electric, and water shutoffs, including the location and the tool required to operate each.
- Occupancy-specific tactical considerations— anything that does not fit the five categories above but materially affects the first-due officer’s size-up: solar arrays, elevator banks, commercial kitchens, residential sprinkler overrides, and so on.
How software keeps the standard intact across inspections and incidents
A pre-plan binder is only as good as its last update. The deeper problem NFPA 1620 solves is not "what does a pre-plan look like" but "how does a department make sure the pre-plan on file still matches the building on the day of the fire." Most departments that have adopted the standard and struggled to stay compliant report the same failure mode: an inspection cycle lives in one place, a paper pre-plan lives in another, and the two fall out of sync within a single year.
Purpose-built fire department pre-plan software addresses that handoff. The software does not invent new required elements — it organizes the six NFPA elements into fields a fire inspector can update from a tablet, surfaces the same fields to a first-due officer on the phone, and ties every record change back to a date and an inspector. Departments running fire-department pre-plan software built around NFPA 1620 typically see the time between an inspection and a pre-plan refresh shrink from weeks to a day, and the percent of pre-plans past their annual review date drop into the single digits.
The downstream effect is what matters at the incident: when the first-due officer opens the pre-plan, the data inside is current to within a year, not three.
What to look for in a pre-plan platform
If you are evaluating pre-plan software for a department that has adopted (or is adopting) NFPA 1620, the platform should pass five working tests.
- NFPA 1620 checklist built in. Every required element group is a structured field, not a free-text note. The checklist stays visible during an inspection and on the post-incident reader.
- Mobile-first, with conditional offline.Inspectors do the bulk of their work in occupancies with poor signal. A platform that turns into a spinning loader the moment a basement cuts Wi-Fi is a platform inspectors stop opening.
- CAD and map layers on the same record. Hydrants, water flow, and apparatus positioning only matter if crews can see them on a map at the address. A pre-plan without a CAD or map layer is missing one of the six required elements by default.
- An audit trail anchored to a person. Every record change should show who made it, when, and what was changed. A year-over-year compliance review is a five-minute conversation when that trail exists.
- Pricing that maps to your district count. A platform whose pricing scales with the number of occupancies or stations you cover — not per-seat inspector fees that punish volunteer departments for sending every inspector into the field on the same revision cycle.
Closing: from binder PDF to a pre-plan your crew can actually use
The point of adopting NFPA 1620 is not the binder on the shelf — it is the information in the first-due officer’s hand at the front door. A pre-plan that sits in a station file cabinet and is reviewed once a year is technically compliant and operationally useless. A pre-plan that updates from an inspection on Tuesday and shows up on a phone on the way to a Wednesday structure fire is what the standard is actually for.
If your department is evaluating where the gap sits — between the binder and the crew — the most useful next step is to pilot a pre-plan platform against one district for a single inspection cycle. You will learn more from one district’s full seasonal review than from a feature comparison across three vendors.