PowerData

  • Consulting
  • Training
  • PRIAM Platform
  • Articles
  • About
  • Let’s Talk
  • Consulting
  • Training
  • PRIAM Platform
  • Articles
  • About
  • Let’s Talk
Let's Talk →
Health Check

From Near Miss to Better Practice: Incident Learning in Electric Utilities

By Murray S. · November 19, 2026 · 4 min read
From Near Miss to Better Practice: Incident Learning in Electric Utilities

A tree-trimming contractor’s bucket comes closer to an energized line than the job briefing allowed. Nobody is hurt, and the foreman mentions it to the line superintendent at the end of the day. Whether that near miss changes anything depends on what happens to the report next, and in many small utility companies it ends with that conversation.

Why this matters for electric utilities

Small electric utilities, such as municipal systems and cooperatives, cover wide territories with a few crews, a control room or dispatcher, and contractors for trimming, construction and metering. Field work carries serious hazards, and the people who see an incident are rarely the ones who decide what to change. Reports have to travel from the field to the office and back out to every crew.

A contractor reports a near miss at a substation, a crew discovers a damaged access point, or an equipment event interrupts a planned activity. If the report stays in a supervisor’s inbox, the organization may miss patterns across locations or fail to document who owns the follow-up.

Take a cooperative where two crews, months apart, find the same type of padmount enclosure unlocked in public areas. Each crew locks it and tells their foreman. Neither event is written down in a shared place, so nobody notices that both enclosures were serviced by the same contractor, and the third one is found open by a member’s child.

What a workable approach looks like

A practical incident workflow

  1. Give every report a consistent minimum record: location, time, event type, immediate controls, owner, and next review date.
  2. Capture near misses and procedural breakdowns as well as events that caused damage or interruption.
  3. Review incidents by site, event type, contractor, and recurring contributing factor—not only by severity.
  4. Close the loop with a documented action and a check that the change was communicated to affected teams.

Connect the records, not just the paperwork

At a utility, one incident report can lead through all four kinds of record. A contractor’s near miss with minimum approach distance is the incident. The review finds that contractor crews weren’t given the utility’s job-briefing checklist, so the contractor-briefing procedure is updated and every crew lead reads and acknowledges it. The risk review raises the score for contractor work near energized lines, and the asset record shows which bucket truck and crew were on the job.

Record near misses with the same care as injuries and outages, and always note the location and whether a contractor was involved. Your regulators, insurer and mutual-aid or contractor agreements may set their own reporting requirements: meet those first, then close the record once the fix has been checked in the field.

A useful first step

For the next quarter, ask every crew and every contractor to report near misses in one place, with the location and the type of work. Review the list at each monthly safety meeting with the line superintendent and the contractor coordinator. Three months of consistent reports will show which sites, tasks or contractors need attention first.

A consistent incident record doesn’t replace a crew’s judgment in the field, a required report or an emergency response. It carries what one crew learned to every other crew, and shows who owns each follow-up until it is done.

How PRIAM can support the work

In PRIAM, crews and office staff report incidents, including near misses, in one place, and a manager assigns each one to a person and a team. Every status change and comment up to the resolution is recorded with who made it.


Editorial note: This article is general operational guidance, not legal, safety, engineering, clinical, or regulatory advice. Requirements vary by organization and jurisdiction; confirm applicable obligations with qualified professionals.


Want to see how PRIAM handles this in practice? Book a walkthrough

Murray S.
Murray specializes in risk assessment, cybersecurity, and business process improvement. Before launching PowerData, he spent 20+ years helping organizations (both private & government sectors) to improve and streamline operations. Between 2002 and 2019 he built and restructured the IT infrastructure operation of multiple state government agencies, and enhanced the cybersecurity operations. He also led various projects that resulted in strengthening Mayo Clinic's data security protocols and better protecting patient data. Murray holds a bachelor’s degree in Computer Information Systems and a Master’s degree in business administration.

Related Insights

Ready to act?

Stop juggling spreadsheets.

Schedule a 30-min walkthrough and find out how PRIAM can simplify your operation.

Book a Walkthrough → Learn About PRIAM
PowerData

Practical cyber protection training, business planning consulting, and PRIAM — simple software for policies, risk, incidents, and assets. Built for small business owners.

Offerings
  • Training
  • Consulting
  • PRIAM Platform
Company
  • About
  • Articles
  • Let's Talk
  • LinkedIn ↗
PRIAM
  • Overview
  • priamtiv.com ↗
  • Book a walkthrough ↗
© 2026 PowerData Solutions Inc. All rights reserved.
Privacy Terms