BESS Approval or Denial
BESS permitting stalls are rarely about one missing form. They are usually about uncertainty: the reviewer cannot determine what the credible hazards are for the installed configuration, or cannot verify that mitigations are real, complete, and testable. This page lists the most common stall and denial drivers and how to address them.
The core reason: reviewers cannot close risk
Permitting is a risk-closure process. If a package does not provide an install-specific safety case that can be evaluated, reviewers default to conservative interpretation, requests for more information, or denial.
Top stall and denial drivers
| Failure mode | What it looks like in review | Root cause | Fix |
|---|---|---|---|
| Evidence not mapped to installation | Listings and test reports look generic or mismatch the deployed product | No test-to-install mapping and no configuration boundary definition | Provide a mapping memo and identify all installed options and constraints |
| Ventilation and gas plan is vague | General statements without sizing basis, discharge analysis, or verification | Gas hazard treated as secondary rather than primary | Provide a ventilation design basis, discharge location evaluation, and commissioning checks |
| Separation distances not justified | Distances shown without scenario basis or exposure rationale | No explicit scenario definition or exposure analysis | Tie distances to scenario basis and cite evidence and mitigation assumptions |
| HMA is not actionable | Hazards listed, but mitigations are not tied to drawings and controls | Narrative disconnected from implementation | Reference where each mitigation exists and how it is verified in commissioning |
| ERP is generic | No site map, no access plan, no scenario actions, no contacts | ERP treated as a paperwork item | Make ERP site-specific and align with detection actions and exclusion zones |
| Inconsistent documentation | Drawings, manuals, and narrative conflict on configuration and operating limits | No single source of truth and no controlled revision process | Create a master configuration summary and controlled submittal set |
The five most common “review comments”
- Provide evidence that the installed system is listed and installed per listing constraints.
- Provide UL 9540A results and explain how they apply to the installed configuration.
- Clarify ventilation and exhaust design: basis, discharge location, and abnormal modes.
- Provide separation distances, setbacks, and emergency access on the plan.
- Provide an actionable ERP with site map, contacts, and scenario actions.
Where projects stall by deployment type
| Deployment type | Most common stall topic | Why |
|---|---|---|
| Indoor, building-integrated | Ventilation and exhaust, gas management, egress | Enclosed volumes concentrate gas hazards and interact with building systems |
| Outdoor container yard | Separation distances, exposures, access routes | Exposure management drives site layout and responder tactics |
| Rooftop or constrained sites | Access, structural and building interfaces, discharge routing | Physical constraints limit mitigation options and increase reviewer conservatism |
A practical “denial prevention” workflow
The fastest way to reduce permit churn is to submit a package that closes risk in the reviewer’s language. This workflow is intentionally simple:
| Step | What to do | Deliverable |
|---|---|---|
| 1 | Define the credible hazard scenarios for the installation type | Scenario basis memo used across all documents |
| 2 | Map safety evidence and listing constraints to the installed configuration | Test-to-install mapping memo |
| 3 | Tie mitigations to drawings and controls and define verification steps | HMA with verification plan and commissioning checklist |
| 4 | Annotate the plan with distances, exposures, and responder access | AHJ-ready plan set |
| 5 | Produce a site-specific ERP aligned to the scenarios and mitigations | ERP with site map, contacts, and scenario actions |
A small checklist of “stall-proof” details
- Explicitly name the installation type: indoor room, outdoor yard, rooftop, or mixed.
- State which hazard scenarios are in-scope and which are out-of-scope, and why.
- Show separation distances and access routes on the plan, not only in narrative.
- Provide ventilation basis and discharge evaluation, including abnormal mode triggers.
- Provide an alarm and action matrix: detect, isolate, ventilate, notify.
- Provide a commissioning checklist that verifies the above assumptions in the installed system.
Disclaimer. Informational guidance only. Not legal advice. Validate requirements against applicable codes, standards, product listings, and AHJ requirements.