Outage Restoration Field Switching Log

This template is used to log each field switching action taken during outage restoration, along with the time, status, and confirmation. It helps the control center and field crews maintain a single, accurate view of system state. Use it as the working record for restoration switching, not as a general outage report.

Use it any time crews are opening, closing, isolating, transferring, or re-energizing equipment during restoration. It is especially useful when multiple people are coordinating switching steps across a live system. If the work is a simple repair with no switching sequence, this template may be more than you need.

The DRI is usually the control center operator, switching supervisor, or field lead who is coordinating the restoration sequence. The person running it should be able to verify each step, capture timestamps, and confirm status with the crew. If your process requires dual confirmation, the log should reflect both the operator and the field verification step.

Entries should be made for every switching action as it happens, not after the restoration is complete. This is a task type that works best as a simple, event-driven log with no recurrence unless you reuse it for scheduled drills or planned outages. Delayed entry is a common pitfall because it creates gaps between the actual system state and the recorded state.

Yes, it supports OSHA-style field safety discipline and utility switching practices by creating a clear record of actions, confirmations, and handoffs. It also fits ITIL-style runbook thinking when restoration involves coordinated operational steps and verification. It should complement, not replace, your approved switching orders, lockout/tagout process, or local safety rules.

The most common mistakes are combining multiple switching actions into one checklist item, skipping timestamps, and failing to record who confirmed the step. Another issue is marking a step complete before the verification step is finished. Keep each entry independently verifiable so the log can be trusted during handoffs.

Yes, and you should tailor it to your equipment names, switching terminology, approval chain, and restoration sequence. You can add fields for feeder, circuit, device ID, clearance status, or radio confirmation if those are part of your process. Keep the core structure focused on one action per entry so the log stays usable under pressure.

Yes, it can be paired with incident tickets, dispatch notes, SCADA event records, or outage management system updates. The log works well as the field-side timeline that supports those systems with human-confirmed actions. If you integrate it, make sure the source of truth for each step is clear so teams do not duplicate or contradict entries.

An ad hoc notes document usually mixes observations, instructions, and outcomes, which makes it harder to verify the exact switching state. This template is structured around discrete checklist items, timestamps, and confirmations so the sequence can be audited and handed off cleanly. That reduces confusion when multiple crews or shifts are involved.