Downed Power Line Make-Safe Response SOP

This template is for dispatchers, first responders, incident commanders, utility crews, and any competent person assigned to secure an energized downed conductor scene. It works best when one role owns scene control and another owns utility coordination. If your organization uses mutual aid, you can assign the same steps across agencies without changing the core sequence. It is not a substitute for utility switching procedures or local emergency authority.

It covers reports of downed overhead conductors, suspected energized lines on vehicles or structures, and scenes where public access must be controlled before the utility arrives. It is useful when the priority is isolation, guarding, notification, and hazard verification rather than repair. If the line is already confirmed de-energized and released by the utility, a separate recovery or restoration SOP may be more appropriate. The template also helps when secondary hazards such as fire, traffic, or damaged poles are present.

Use it every time a downed power line is reported, even if the caller believes the line is dead. Review it during drills, after any real incident, and whenever your utility contact list or traffic-control process changes. Many agencies also review it during seasonal storm preparation. The goal is to keep the first actions consistent under stress.

Yes, it is written to support documented response control, hazard communication, and scene isolation practices that align with ISO 9001-style documented information, OSHA process safety expectations, and ANSI Z535.6-style warning language. It also fits emergency response planning where permit-to-work discipline, escalation, and verification matter. The template does not replace local electrical codes or utility lockout/tagout procedures. It should be adapted to your jurisdiction and agency authority.

The biggest failures are approaching too closely, allowing bystanders to self-rescue, assuming a line is de-energized, and forgetting to control traffic in both directions. Another common miss is not checking for secondary hazards such as energized vehicles, broken poles, or fire spread. This SOP also reduces confusion about who calls the utility and who maintains the exclusion zone. Clear role assignment prevents duplicated or delayed actions.

Yes, and it should be customized by role. Fire and EMS can emphasize scene safety, patient access limits, and rescue boundaries, while police can emphasize traffic control and perimeter enforcement. Utility crews can add switching, grounding, and verification steps that only qualified personnel may perform. Keep the core sequence intact so every agency follows the same hazard-control logic.

An ad hoc response depends on memory and local habit, which is risky when the scene is noisy, wet, dark, or under public pressure. This SOP gives responders a repeatable sequence: classify, stop, isolate, warn, notify, and verify. That reduces missed steps and makes handoff between agencies clearer. It also creates a documented record of what was done and when.

Pair it with dispatch call scripts, utility contact lists, traffic-control maps, site sketches, and incident reporting forms. Many teams also link it to a permit-to-work or scene log so every notification and verification is recorded. If your organization uses digital checklists, this SOP can be the parent workflow with role-specific substeps. Photos, radio logs, and utility reference numbers are useful attachments.

Replace generic roles with your actual titles, add local utility escalation numbers, and define the minimum safe distance or exclusion-zone method your authority uses. You should also specify who can declare the scene safe, who documents the incident, and what to do if the utility cannot immediately respond. Test the wording with dispatch and field supervisors before publishing. A short tabletop exercise usually reveals missing contacts or unclear handoffs.