Prevent.
Prove.
Operate.



IS YOUR BESS DEPLOYMENT COMPLIANT?


This site is written for teams who have to get BESS deployed safely and approved quickly: developers, EPCs (Engineering, Procurement, and Construction), integrators, owners/operators, safety managers, and compliance leads.

It is also useful for reviewers and stakeholders who evaluate safety posture: AHJs, fire marshals, building officials, utilities, and insurers.


What does BESS compliance look like?

BESS compliance is primarily an implementation problem: aligning codes, standards, reports, and field evidence into a coherent safety case. This guide is organized around the lifecycle and the review points where projects commonly stall.

  • Core codes and standards used in North American projects, plus how adoption and amendments change requirements
  • Safety and risk topics that drive design controls, emergency planning, and insurer requirements
  • Permitting packages and the documentation AHJs typically request during plan review and inspections
  • Design and siting considerations that frequently determine whether a site is approvable

Common blockers

  • Missing or unclear UL 9540A evidence for the proposed configuration.
    Note: If your data is older than March 2025, update to 5th Edition for NFPA 855/IFC compliance.
  • HMA not tied to specific design controls, interlocks, and procedures.
  • Ventilation, exhaust, and gas detection not mapped to credible scenarios.
  • Separation distances not supported by test data or AHJ-accepted method. Note: NFPA 855 (2026) is the current reference.
  • Operations evidence incomplete at commissioning and turnover.

What's next?

Use the site as a structured checklist for what you must produce, not as a substitute for engineering design or code analysis. Each topic is written to help you answer three questions quickly.

  • What is typically required for approvals and insurance acceptance?
  • What evidence is expected and where it usually comes from?
  • What field verification and records you need to retain?

Then use the standards pages to build your project-specific compliance pack: design basis, code edition assumptions, test evidence, commissioning plan, O&M procedures, and emergency response information.



If your BESS work also touches battery product compliance and lifecycle obligations:



Not legal advice.
Use this guide to organize requirements, evidence, and communication with AHJs, utilities, and insurers. Always follow your adopted codes, local amendments, OEM instructions, and licensed professional judgment.