Public Safety Power Shutoff (PSPS) Execution Checklist
A Public Safety Power Shutoff (PSPS) Execution Checklist for coordinating de-energization, field patrols, customer notifications, and safe restoration of distribution circuits during a wildfire-risk event.
Trusted by frontline teams 15 years of frontline software
Built for: Electric Utilities · Public Power Agencies · Municipal Utilities · Transmission And Distribution Operations
Overview
This Public Safety Power Shutoff (PSPS) Execution Checklist is a task template for managing the operational sequence around de-energizing and re-energizing distribution circuits during a wildfire-risk event. It is built for the work that must happen in order: confirm the event trigger, notify affected customers and stakeholders, execute switching and isolation, dispatch field patrols, verify line and equipment conditions, and restore service only after clearance is documented.
Use this template when the work is time-sensitive, safety-critical, and shared across operations, field crews, and communications. It helps teams keep blocking steps visible so restoration does not move ahead until patrols, approvals, and verification steps are complete. It is also useful for drills and seasonal readiness reviews when you want the same sequence without the pressure of a live event.
Do not use this checklist as a substitute for your utility's approved switching orders, emergency operations plan, or regulatory filings. It is not the right fit for routine planned maintenance, isolated single-device outages, or customer service follow-up that does not affect energization decisions. If your process is mostly informational rather than operational, a simpler incident log or notification tracker may be a better fit. This template is strongest when the event has clear handoffs, a defined DRI, and a need to prove that each step was completed before the next one began.
Standards & compliance context
- This template supports disciplined utility operating practices by documenting the sequence of de-energization, patrol, and restoration approvals.
- It should be aligned with your approved switching orders, emergency operations procedures, and any applicable PSPS notification requirements.
- Use it to preserve an auditable record of who verified each blocking step before re-energization, especially where safety or public risk is involved.
- Do not use the checklist to replace required regulatory filings, engineering review, or formal authority to energize.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- 1. Define the PSPS event scope, the affected circuits, and the DRI before the checklist is started so the team knows which work is blocking and which updates are informational.
- 2. Add the circuit-specific switching, patrol, and notification items that apply to the event, and keep each checklist item to one independently verifiable action with a clear yes, no, or N/A outcome.
- 3. Assign each item to the appropriate operator, field lead, or communications owner, and set the priority to critical only for steps that affect safety, compliance, or restoration approval.
- 4. Run the checklist in sequence during the event, confirming completion of each verification step before moving to the next blocking action such as patrol clearance or re-energization.
- 5. Review the completed checklist after restoration, capture any missed handoffs or delayed steps, and update the template so the next PSPS event reflects the actual operating procedure.
Best practices
- Keep switching, patrol, notification, and restoration approval as separate checklist items so one failure does not hide another.
- Mark only safety- or compliance-sensitive steps as critical, and leave routine coordination items at normal priority to avoid priority inflation.
- Use a clear blocking or non-blocking distinction so crews know which items must be finished before re-energization can proceed.
- Require a verification step for every restoration gate, especially patrol clearance, equipment status confirmation, and supervisor approval.
- Write each item as an imperative action, such as verifying a patrol route or confirming customer notification completion, rather than as a vague status question.
- Keep the checklist aligned to the actual circuit topology and operating area so field crews are not forced to interpret generic steps during an active event.
- Record exceptions and N/A items with a reason so the event log explains why a step was skipped instead of leaving an ambiguous gap.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this PSPS execution checklist cover?
This checklist covers the operational steps needed to take distribution circuits out of service for a Public Safety Power Shutoff and bring them back online safely. It typically includes pre-shutoff notifications, switching and isolation, field patrols, restoration verification, and post-event documentation. It is meant to track the work that must happen in order, with clear checklist items and verification steps. It is not a planning policy or a customer communication template.
Who should run this checklist during a PSPS event?
The DRI is usually a grid operations lead, switching coordinator, or incident commander who can coordinate dispatch, field crews, and customer communications. Individual checklist items may be assigned to substation operators, line crews, patrol teams, and communications staff depending on the utility's operating model. The key is that each step has one accountable owner and a clear verification step. This template works best when the assignment is explicit at import time or during event setup.
How often is this checklist used?
This is a recurrence-driven operational checklist that is used whenever a PSPS event is declared and again during restoration. It is not a daily or weekly routine unless your utility uses it for drills, tabletop exercises, or seasonal readiness reviews. Many organizations keep a separate training version for exercises and a live version for active events. If you do both, keep the live checklist focused on blocking work that must be completed before re-energization.
Is this checklist tied to regulatory or compliance requirements?
Yes, it supports the documentation and procedural discipline expected in utility safety operations, outage management, and emergency response. It can help teams show that notifications, patrols, switching, and restoration checks were performed in a controlled sequence. It should be aligned with your utility's approved switching orders, emergency operations plan, and any applicable state or local PSPS requirements. It does not replace legal review or system-specific operating authority.
What are the most common mistakes when using a PSPS checklist?
A common mistake is combining multiple actions into one checklist item, which makes it hard to verify completion. Another is marking every item as critical, which hides the steps that truly affect safety or compliance. Teams also sometimes skip the restoration verification step or fail to record who confirmed field patrol clearance. This template works best when each item is independently verifiable and the blocking steps are clearly separated from non-blocking follow-up work.
Can this checklist be customized for different circuits or operating areas?
Yes, it should be customized for your circuit topology, patrol zones, switching boundaries, and customer notification channels. You can add items for substations, reclosers, critical facilities, or mutual-aid coordination if those are part of your process. Keep the checklist items specific to the work that must happen, and avoid turning it into a generic incident log. If you have multiple service territories, create one version per operating area so the verification steps match local practice.
How does this compare with an ad-hoc outage call sheet or email thread?
An ad-hoc call sheet can move information around, but it is easy to miss a switching step, lose ownership, or restore a circuit before patrol clearance is confirmed. This checklist creates a repeatable sequence with a DRI, task types, and explicit verification steps. It also makes it easier to separate blocking items from non-blocking updates so the team knows what must be finished before the next action. For high-risk restoration work, that structure matters more than a free-form thread.
What integrations are useful with this template?
This checklist pairs well with outage management systems, incident management tools, field dispatch, and customer notification platforms. It can also be linked to GIS maps, crew assignment records, and restoration approval workflows. The most useful integration is one that preserves the checklist item status and the verification step in a shared event record. That way, operations, field crews, and communications teams are working from the same source of truth.
How should we roll this out to operators and field crews?
Start with a single PSPS event or drill and have the operations lead walk the team through each checklist item before use. Confirm which steps are blocking, which are non-blocking, and who is responsible for each verification step. Then review the checklist after the event to remove duplicate items, clarify wording, and adjust the sequence to match how work actually happens. A short pilot is usually better than a broad rollout because it exposes gaps in switching, patrol, or notification handoffs.
Related templates
Ready to use this template?
Get started with MangoApps and use Public Safety Power Shutoff (PSPS) Execution Checklist with your team — pricing built for small business.
