Report the incident according to workplace procedures when an EWP contacts power lines.

When an Elevated Work Platform (EWP) comes into contact with power lines, chaos is the last thing you want to deal with. The hum of electricity, the sudden drop in the air’s temperature, the way your heart rate climbs—these are all telltales that this is not a moment for guesswork. On a busy job site, cool heads and clear actions matter more than anything. And the single most crucial thing to do right away is to report the incident according to your workplace procedures. It sounds simple, but it’s the backbone of real safety, compliance, and learning that actually prevents repeats.

Let me explain why that reporting step matters so much

Safety is a system, not a solitary act. When a tall machine brushes a power line, the risks aren’t just about what you felt in the moment. There’s a cascade: potential electrocution, electrical fires, equipment damage, and the possibility that nearby workers could be exposed. Following established procedures gives everyone a shared map to handle the situation—who to notify, what to shut down, what to document, and how to review the event later. Without that map, adrenaline can push people to improvise, and improvisation on a live electrical site is a risky bet.

Plus, there’s a legal and regulatory layer to consider. Workplaces aren’t just trying to keep people safe; they’re also collecting a record of incidents to prove compliance, to learn from them, and to improve training and controls. The written report becomes a trail the regulators can follow, and it helps the company show due diligence if questions arise later. That’s not about blame; it’s about accountability and continuous improvement.

What the reporting should cover (and what it means for you on the ground)

Here’s the core idea: document the incident the way your workplace procedures require. This isn’t a lecture about feelings or opinions; it’s a precise, fact-based account of what happened, where, when, and with what equipment. The objective is clarity and completeness, so a safety officer—or an regulator—can understand the event quickly and act.

What to include, in practical terms:

• The basics of the incident: date, time, exact location on site, and the EWP model and serial number if possible. If a nearby crane or other equipment was involved, note that too.

• The sequence of events: what the machine was doing, how it contacted the line, and what alarms or indicators sounded. Include whether the operator had been following standard operating procedures at each step.

• The environment: weather, working surface, proximity to lines, any barriers or warning systems in place. Note if the lines were visibly energized and whether a work clearance or permit was in effect.

• Immediate actions taken: were emergency shutoffs activated, was the area isolated, were other workers moved away, did anyone receive medical attention, were utility crews contacted?

• The equipment condition: any visible damage, electrical indications, fluid leaks, or unusual sounds. If relevant, note whether PPE was used and whether it remained secure after the incident.

• People involved: operator, spotter, ground crew, supervisors, witnesses. Record names and roles, not just “a few teammates.”

• Follow-up actions: investigations planned, training updates anticipated, repairs scheduled, and changes to procedures or controls.

This is where the balance between professional jargon and plain language pays off. You want the report to read as if a person who was not there could still reconstruct the scene. Avoid esoteric terms unless they’re standard in your organization’s glossary, and explain them if necessary.

What not to do when you report (and why)

• Don’t focus on “how I felt.” While your feelings matter for personal safety awareness, the incident report is not the place for subjective reflections. Those feelings have their outlet in debriefs or counselling—not the official record.

• Don’t limit the report to the equipment alone. The gear matters, but the incident often hinges on procedures, communications, and the plan of work. If you keep the report centered on the machine without addressing human factors and process steps, you’ll miss the bigger picture.

• Don’t delay. Delaying reporting, even for a few minutes, can allow secondary hazards to emerge or prevent timely medical checks. If someone is injured or at risk, act now in line with your procedures.

• Don’t rely on memory. In a high-stress moment, memory can blur. Use checklists, take notes as soon as it’s safe, or capture details with devices your organization supports. Verifying facts later is harder than getting them right in the moment.

• Don’t get lost in blame. The goal is safety and prevention, not finger-pointing. The report should focus on what happened, why it happened (root causes, not people), and how to stop it from happening again.

The value of a consistent reporting routine

When an EWP touches a power line, a consistent reporting routine turns uncertainty into a clear path forward. It creates a documented chain of safety actions, a timeline that others can follow, and a basis for learning. That learning isn’t abstract. It translates into better training modules, refined permit-to-work processes, safer distances from live lines, and improved equipment positioning practices.

Think of it like maintaining a car. If you notice a strange sound and you ignore it, the problem can become a breakdown waiting to happen. If you log the symptom, inspect the vehicle, and address it with the right repair, you reduce the chance of a roadside failure. The same logic applies on a construction site: record, review, and revise.

Digressions that actually circle back to safety

On many sites, teams rotate through tasks that require sharp focus. You might be changing attachments, moving around obstacles, or positioning the EWP for a lift. It’s easy to assume “we’ll cover it in the debrief,” but the truth is that a structured report turns feedback into data you can act on. Some teams even incorporate quick digital checklists right after an incident, which helps bridge the gap between memory and record.

And yes, the practical world isn’t always pristine. You’ll hear stories of near-misses where someone joked, “It could’ve been worse.” Those moments aren’t excuses; they’re reminders. A proper report captures those reminders in black and white, so management can close the gaps—like improving line clearances, increasing buffer zones, or adopting stricter permit controls.

A few notes on preparedness and culture

• Training is ongoing. It’s not a one-and-done session. Regular refreshers help crews remember exact steps, from keeping a safe distance to calling the right emergency numbers.

• Communication is king. A clear line of communication means the operator knows who to alert, and witnesses know how to document what they saw.

• The site culture matters. If crews feel safe to report mistakes or close calls without fear of blame, you’ll get accurate, timely information that leads to real improvements.

• Real-world tools and practices: many sites use simple incident-report templates, digital forms, or mobile apps to speed up the process and ensure no details slip through the cracks. Some teams track near-misses and incidents together to identify patterns over time.

A practical, field-ready checklist you can keep handy

• Immediately secure the area and call for help if needed.

• Notify the supervisor and the safety officer as described in your procedures.

• Document: date, time, location, equipment, operator name, witnesses.

• Describe the sequence of events and the actions taken.

• Note environmental factors and any potential hazards that remain.

• Record injuries (even minor ones) and medical evaluations.

• Initiate the official incident report using your workplace form or system.

• Review the incident in the follow-up meeting and outline corrective actions.

• Verify that repairs, inspections, and training updates are scheduled and completed.

Closing thought: one clear report shapes a safer future

In the moment of contact between an EWP and power lines, what you report—and how you report it—sets the tone for safety that follows. Reporting the incident according to workplace procedures isn’t just ticking a box. It’s a decisive act that protects people, preserves compliance, and drives improvements that keep your crew safer down the line.

If you ever find yourself on a site where power lines are close, remember this: the procedure is your roadmap, not a formality. It guides you through the danger, helps you capture the facts, and pushes the organization to tighten controls so the next time you lift, you lift with greater certainty. And that, more than anything, is worth aiming for.