How Fire Authority Interpretations Vary Across Jurisdictions

The biggest risk to a BESS plant layout is not the fire code itself. It is the timing of fire authority feedback. The Authority Having Jurisdiction (AHJ) response typically arrives months into development, after the layout has been shared with investors, used for CAPEX modeling, submitted to the grid operator for connection studies, and locked into civil works quantities. A 2 m increase in separation distance at that stage is not a minor adjustment. It cascades: capacity numbers change, cable lengths change, transformer pad locations shift, access roads move, and the financial model that secured funding no longer matches the site plan.

The code is a starting point. The AHJ is the final answer. And the AHJ answers late.

The Timing Problem

Most developers sequence fire authority engagement as a permitting step — something that happens after layout design, after equipment selection, after financial close. The logic seems reasonable: produce a compliant design, submit it, receive approval. In practice, this sequence creates maximum exposure to redesign risk.

NFPA 855 sets prescriptive minimums and requires a Hazard Mitigation Analysis (HMA) that evaluates product-specific UL 9540A test data against site conditions. The AHJ reviews the HMA and applies professional judgment. That judgment varies. Two fire marshals reviewing the same HMA for the same product in adjacent counties can reach different conclusions about acceptable risk. One accepts the prescriptive distances. Another doubles them. Neither is wrong under the code — NFPA 855 grants the AHJ discretion, and they use it.

The problem is not that the AHJ might impose stricter requirements. The problem is that this information arrives after the layout has been treated as final by every other workstream on the project.

Six Areas Where Interpretations Diverge

1. Which Code Edition Is Adopted

A jurisdiction may be operating under IFC 2018, IFC 2021, or IFC 2024. Each edition contains different energy storage system provisions. Some jurisdictions adopt NFPA 855 directly. Others reference it through the IFC, which may incorporate portions of NFPA 855 while adding or modifying requirements. Some municipalities lag several years behind the latest edition. Others adopt local amendments that override the base code entirely.

The consequence: a layout designed to meet NFPA 855 (2023) may be reviewed against a 2018 IFC edition that does not recognize the same provisions. The designer assumes one set of rules. The AHJ applies another.

2. Whether UL 9540A Test Data Is Required — and at What Level

UL 9540A includes four levels of testing: cell, module, unit, and installation. Some AHJs mandate installation-level testing before approving a project. Others accept module-level data as sufficient. Some accept equipment manufacturer declarations without reviewing underlying test reports.

If the chosen product has only module-level data and the AHJ demands installation-level results, the project faces either a 6-12 month testing delay or a product substitution that triggers a full layout revision. Installation-level testing requires a physical test setup at a qualified laboratory, coordinated with the equipment manufacturer. It cannot be fast-tracked.

3. Prescriptive vs. Performance-Based Distances

NFPA 855 includes prescriptive distance tables and also permits performance-based design where a qualified engineer demonstrates that alternative distances provide equivalent safety. How AHJs interpret this dual pathway varies widely.

Some enforce prescriptive table distances as absolute minimums — no analysis can reduce them. Others allow performance-based analysis through the HMA to justify reduced distances where UL 9540A data supports it. Others treat the prescriptive tables as a floor that the HMA can raise but never lower.

A project that designs to performance-based distances without confirming the AHJ accepts that pathway may discover, months into permitting, that the jurisdiction treats prescriptive distances as mandatory minimums. The layout must be redrawn at those minimums or larger.

4. Additional Setback Requirements

Beyond the code's prescriptive distances, many AHJs impose supplemental requirements based on local experience, risk appetite, or site-specific conditions.

Some California fire marshals require a 3 m minimum between energy storage units regardless of what UL 9540A data shows. Certain New York jurisdictions require thermal radiation modeling at the property line to demonstrate that radiant heat flux remains below a specified threshold. Denmark requires 10 m from containers to property boundaries for systems exceeding 2,000 kWh. UK guidance suggests 6 m between units and 25 m to occupied buildings.

These requirements are not found in NFPA 855. They exist in local amendments, fire department policies, planning conditions, or guidance documents published by national fire authorities. They are discoverable only through direct engagement with the AHJ — often before a formal application is submitted. A designer working from the published code alone will not find them.

5. Fire Suppression Requirements

NFPA 855 generally does not require fire suppression systems for outdoor, non-walk-in energy storage installations. The reasoning is that properly separated outdoor units present a contained fire risk where intervention focuses on exposure protection rather than suppression.

Some AHJs require suppression systems regardless of what the code says. Some require a water supply on site to support defensive firefighting operations. Others require a fire department connection and standpipe without requiring a full suppression system. Each requirement adds cost, space, and civil works. A water supply requirement can mean a 100,000-liter tank, a pump house, and piping runs that consume site area and add months to construction scheduling.

6. Fire Department Access Requirements

Fire apparatus access roads must support the weight, width, and turning radius of the responding equipment. NFPA 855 and the IFC establish general parameters, but the responding fire department's operational procedures often add specifics the code does not address.

Required road widths range from 3.6 m to 6 m depending on jurisdiction. Some departments require through-access while others accept hammerhead turnarounds. Hydrant proximity requirements range from 90 m to 150 m. On constrained sites, fire access requirements can consume more area than the fire separation distances themselves — and they are among the last requirements to be confirmed, since they depend on which station responds.

The Insurance Layer

Fire code compliance and AHJ approval do not end the spatial analysis. If the project carries FM Global insurance, FM Data Sheet 5-33 imposes its own separation requirements that are often stricter than the fire code. For the specifics of FM Global distances and how they stack against NFPA 855 prescriptive requirements, see the companion post on NFPA 855 separation distance mechanics.

The key point for planning purposes: FM requirements apply regardless of what the AHJ approved. A layout that passes fire authority review but violates FM Data Sheet 5-33 will face insurance non-compliance, which most project finance structures do not tolerate. This creates a second layer of late-arriving constraints, since the insurer's review often follows AHJ approval.

Designing for Regulatory Uncertainty

The practical consequence of jurisdictional variation is that the final separation distances are unknown when the layout is first drawn. The AHJ may not respond for months. The insurer's review may follow even later. The designer must commit a layout before receiving the information that determines whether that layout is viable.

Three principles reduce the risk of late-stage redesign:

Build in Margin from the Start

Design with 20-30% above prescriptive minimums. On most sites, this costs 2-5% of the total footprint — a small premium against the cost of a full redesign. If the final approved distances are lower, the extra space becomes available for future augmentation capacity or wider maintenance access lanes. Projects that design to exact prescriptive minimums are projects that redesign when the AHJ responds.

Design the Layout So Distances Can Increase Without Starting Over

A layout where DC blocks are packed to exact minimums must be entirely redrawn when distances increase by even 0.5 m. The cable routes are wrong. The access roads are wrong. The civil works quantities are wrong.

A layout with modular spacing — where DC blocks are organized in groups with defined inter-group corridors — can absorb larger distances by removing a unit from each group or shifting a group without cascading changes to cable routes and access roads. The key is designing so that the spacing between groups is the variable that absorbs changes, not the entire site geometry.

Engage the AHJ Before Submitting

A pre-application meeting with the fire marshal is the single most effective action to reduce permitting risk. This is not the formal plan review. It is an early conversation — before the layout is finalized — to establish the jurisdiction's general expectations.

What "engage early" looks like in practice:

• Pre-application meeting. Most fire departments offer these. Request a 30-minute meeting to discuss a proposed BESS plant. Bring a preliminary site plan and a one-page project summary. The fire marshal will typically indicate their general expectations, any local amendments, and any supplemental requirements. This single meeting can eliminate months of uncertainty.
• Informal phone call. In smaller jurisdictions, a phone call to the fire prevention bureau can establish whether the jurisdiction has reviewed BESS projects before, which code edition applies, and whether they have any standing policies on separation distances.
• Review of precedent projects. Ask whether other BESS plants have been permitted in the jurisdiction. If so, the conditions imposed on those projects are a strong indicator of what the current project will face. Some jurisdictions will share prior plan review letters.
• Written pre-application inquiry. Where meetings are not available, a written inquiry with specific questions ("Does this jurisdiction require installation-level UL 9540A data? Does the fire department accept performance-based separation distances?") creates a documented baseline that the formal review is unlikely to contradict.

The cost of early engagement is a few hours of the development team's time. The cost of not engaging early is a layout redesign after financial close, an updated grid connection application, revised investor materials, and a construction schedule that slips by the duration of the permitting cycle.