Multi-crew storm operations create reporting blind spots that single-crew jobs never encounter. Crews rotate every 16 hours, home utility employees work alongside mutual-aid contractors, and information has to move from the field to incident command without delay.

‍

The best-performing utilities solve these challenges by following a set of proven incident reporting best practices. These practices standardize reporting across crews, reduce communication gaps, meet OSHA reporting requirements, and help prevent repeat incidents during restoration.

‍

This guide covers six incident reporting best practices every utility and storm contractor should implement before the next major storm event.

‍

Best Practice #1: Understand Why Incident Reporting Is Different During Multi-Crew Storm Operations

A blue-sky day has one crew, one supervisor, and one reporting chain. A storm event can have hundreds of crews pulled from the home utility's own linemen, mutual-aid partners, and third-party storm restoration contractors, all working under a single incident command structure.  

‍

During recent major restorations, utilities have deployed well over 100 crews simultaneously, PSE&G reported more than 170 crews working around the clock during its July 2026 New Jersey restoration, drawn from its own workforce, contractors, and out-of-state mutual aid.

‍

That scale creates three specific reporting problems:

• Fragmented chains of command.  

A contractor crew reports to its own foreman, who reports to a storm broker, who reports to the utility's staging manager. An incident can pass through three or four hands before it reaches anyone with authority to act on it.

• Inconsistent forms and terminology.  

Every company that shows up to a storm has its own incident report format. Without a shared template, near misses get logged inconsistently or not at all — a gap covered in more detail in KYRO's guide to near-miss reporting versus incident reporting.

• Crew turnover mid-storm.  

Linemen rotate out under fatigue and hours-of-service rules, and the crew that discovers a hazard often isn't the crew still on-site when the paperwork gets filed.

‍

Best Practice #2: Build OSHA Reporting Deadlines Into Every Storm Response Workflow

Regardless of how many companies are on a job, OSHA's reporting clock under 29 CFR 1904.39 doesn't pause for storm chaos. Employers must report a work-related fatality within 8 hours of learning about it, and any in-patient hospitalization, amputation, or loss of an eye within 24 hours of the incident.  

‍

The clock starts the moment the employer or any of its agents learns of the event, not when the paperwork is finished.

‍

Two details trip up storm operations specifically:

• If a crew doesn't learn an injury was work-related until days later, the 8- or 24-hour clock restarts from that discovery, not from the original incident.

• Several state plans are stricter than federal OSHA — California's Cal/OSHA, for example, requiring serious injury reporting within 8 hours, not 24 hours. Contractors working on a multi-state mutual-aid deployment need to know which state's clock applies before the storm hits, not during it.

For a full breakdown of what must be logged versus reported, see KYRO's OSHA recordkeeping requirements guide. Utilities operating under NERC reliability standards should also cross-reference NERC EOP-011 compliance, which governs operating-emergency communications separately from OSHA's injury-reporting rules.

‍

Best Practice #3: Standardize Incident Reports Across Every Crew and Contractor

The single highest-leverage fix for multi-crew storm operations is a shared reporting template that every crew home utility, mutual aid, and subcontractor, uses from the first mobilization order.

‍

A standardized incident report should capture:

1. Crew and circuit identifiers. Which crew, which circuit or feeder, which company, and who the crew's tailboard supervisor was at the time.

2. Time-stamped sequence of events. Not a summary — a timeline. Investigators reconstructing a multi-crew incident need to know what each party knew and when.

3. Equipment and PPE status. Especially relevant where lockout-tagout procedures span a hazard boundary shared by two crews.

4. Witness statements from every company present, not just the crew directly involved.

5. Immediate corrective action taken on-site, separate from the root-cause analysis that follows later.

‍

Storm brokers and general contractors managing sub-networks should push this template down to every subcontractor at onboarding, not after the first incident exposes the gap.

‍

Best Practice #4: Use Real-Time Incident Reporting to Prevent Repeat Hazards

The real risk in multi-crew storm operations isn't the first incident. It's the second one, on a different crew, at the same location, because nobody told the next shift what happened.  

‍

A hazard identified by Crew A at 6 p.m. needs to reach Crew B before Crew B rolls up to that same span of line at 6 a.m.

‍

This is where paper-based or end-of-shift reporting fails multi-crew operations specifically. If an incident report doesn't surface until the next morning's debrief, three or four crews may have already worked the same hazard overnight.  

‍

Digital, mobile-first reporting, where a crew can log an incident or near miss from the truck and have it visible to command staff and incoming shifts immediately, closes that window.  

‍

KYRO AI's Health & Safety tools and StormShield platform are built around this real-time visibility, syncing crew-level safety data across every company on the job so hazard information travels with the shift change instead of lagging behind it.

‍

This same logic underpins the case for advanced crew coordination technology more broadly. The utilities that cut restoration downtime are usually the same ones that closed the field-to-office communication gap, a theme explored in KYRO's piece on bridging communication gaps in storm response.

‍

Best Practice #5: Clearly Define Incident Reporting Ownership Before Storm Season

Ownership confusion is the most common reason multi-crew incidents go underreported. The safest structure assigns three layers of ownership:

• The crew's direct employer owns the initial report and immediate corrective action, regardless of which utility's circuit the crew is working.

• The utility's storm manager or incident command owns cross-crew visibility — making sure a hazard reported by one contractor reaches every other company staged in that area. The role of this position is detailed in KYRO's guide to what a storm manager does.

• The utility's safety and compliance team owns regulatory reporting to OSHA and any applicable state agency, since the 8- and 24-hour clocks apply to the utility as the controlling employer on many job sites, not just the crew's direct employer.

Written mutual-aid and subcontractor agreements should specify this ownership before storm season starts, not during an active mobilization.

‍

Read more: Near miss vs incident Reporting for Utilities

‍

Best Practice #6: Track Leading Indicators, Not Just Reportable Incidents

Reactive incident reports tell you what already went wrong. Leading indicators like near-miss rates, tailboard completion rates, PPE compliance checks tell you where the next incident is likely to happen.  

Multi-crew operations benefit disproportionately from leading-indicator tracking because they aggregate risk signals across companies that would otherwise never compare notes. KYRO's guide to safety leading indicators and its companion piece on TRIR vs. DART walk through which metrics matter most and how to benchmark them across a mixed workforce of employees and contractors.

Pairing leading indicators with the seven-checklist framework KYRO AI recommends for storm crews gives command staff a real-time risk picture instead of a lagging one.

‍

Implement These Incident Reporting Best Practices Before the Next Storm

Multi-crew storm operations leave little room for reporting delays or inconsistent processes. Standardized templates, clear reporting ownership, real-time communication, and proactive safety metrics help utilities protect crews while staying compliant with OSHA requirements.

Organizations that establish these incident reporting best practices before storm season are better equipped to coordinate mutual-aid crews, reduce repeat hazards, and keep restoration efforts moving safely.

‍

‍

FAQ:

‍

How fast must a fatality be reported to OSHA during a storm event?  

Within 8 hours of the employer learning about it, regardless of how many companies are working the storm.

‍

Do mutual-aid crews follow the home utility's incident reporting process or their own employer's?  

Both. The crew's direct employer owns the initial report, but the controlling utility's safety team typically owns regulatory reporting and cross-crew hazard communication.

‍

What's the difference between a near-miss report and an incident report in storm operations?  

A near miss captures a hazard that didn't result in injury or damage but could have; an incident report documents an event that did. Storm operations benefit from capturing both, since near misses are the earlier warning signal across a large multi-crew workforce.

‍

Can paper-based incident reports keep up with a large storm mobilization?  

Generally, not at scale. With crews rotating every 12–16 hours across multiple companies, hazard information needs to reach the next shift before that shift starts work — something real-time digital reporting handles far more reliably than end-of-shift paperwork.