BESS Thermal Runaway Emergency Response Plan

It covers the immediate response to a battery energy storage system thermal runaway event, including emergency alert wording, site isolation, safe shutdown, responder coordination, and accountability steps. The template is built to help communicate the hazard clearly to operations, security, fire responders, and incident command. It also includes guidance for vent gas concerns and updates during the incident. It is meant for a real response scenario, not a routine maintenance notice.

Use it when a BESS has entered thermal runaway, is suspected of entering thermal runaway, or has produced smoke, heat, fire, or vent gas that requires emergency response. It is also useful when the site must be evacuated, access restricted, or responders need a clear action plan. Do not use it for normal alarms, inspection reminders, or non-urgent equipment notices. If there is no immediate safety threat, a standard maintenance or operations message is more appropriate.

This alert should be activated by the site incident commander, emergency coordinator, operations lead, or another designated responder with authority to initiate emergency communications. In many facilities, security and EHS teams also help distribute the message through SMS, voice, push, and email channels. The key is that one person or role owns the message so the instructions stay consistent. The template supports clear assignment of who issues the alert and who confirms receipt.

Review it on a scheduled basis, after any drill, and after any real incident or near miss involving the battery system. It should also be updated when site layouts change, contact lists change, or emergency procedures are revised. Because this is a high-consequence event, stale contact information or outdated isolation steps can create confusion. A regular review keeps the alert language and response roles aligned with current site conditions.

Yes, it is designed to support emergency response coordination, hazard communication, and site accountability in a way that aligns with common fire code and workplace safety expectations. It does not replace a site-specific compliance program, engineering controls, or local authority requirements. Instead, it helps document the immediate actions, who is affected, and how updates are communicated. Final procedures should be validated against your site plan and local emergency response requirements.

The most common mistakes are using vague language, giving conflicting instructions, or failing to state the exact location and immediate action. Another frequent issue is marking the alert as urgent without including who is affected, what to do now, and where to get the next update. Teams also sometimes forget to include acknowledgment or safety check-in requirements when accountability matters. This template helps prevent those gaps by structuring the message around action, location, and follow-up.

Yes, it should be customized for the specific battery chemistry, enclosure layout, site access points, shutdown sequence, and responder contacts at your facility. You can also tailor it for containerized systems, utility-scale yards, microgrids, or co-located industrial sites. Vendor-specific isolation steps, fire department access notes, and site maps can be added as needed. The template is a starting point, not a substitute for site engineering documentation.

An ad-hoc message is faster to draft, but it often misses critical details like immediate action, affected area, update timing, and accountability. This template gives responders a repeatable structure so the alert is clear under pressure and easier to distribute across channels. It also reduces the chance of contradictory instructions during a fast-moving incident. For emergency events, that consistency is usually more valuable than improvisation.

Useful integrations include mass notification systems for SMS, voice, push, and email, plus incident management tools that track acknowledgments and safety check-ins. Some sites also connect the template to on-call rosters, access control workflows, and emergency contact directories. If your organization uses a command center or dispatch process, the template can support that handoff as well. The goal is to move from alert to confirmed action without losing time.