Loading...
operations

Utility Strike Damage Investigation Report

Document a utility strike in one place with ticket status, locate accuracy, strike details, damage assessment, and root cause. Use it to capture the facts, support follow-up, and reduce repeat excavation errors.

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Construction · Utilities · Telecommunications · Civil Engineering

Overview

The Utility Strike Damage Investigation Report template captures the facts needed after contact with a buried facility. It organizes the incident into five parts: the incident overview, facility and locate details, excavation and strike details, damage assessment and immediate actions, and root cause with follow-up. The attachments and acknowledgment section helps preserve photos, witness input, and submitter confirmation in one record.

Use this template when excavation, trenching, boring, or potholing results in damage, service interruption, or exposure of a buried utility. It is also useful for near-miss events when the crew discovers inaccurate markings, unclear locate conditions, or a strike that did not yet cause a full outage. The form is designed to support a clear audit trail without collecting unnecessary PII.

Do not use this template as a general daily excavation log or as a broad safety incident form unless the utility strike is the event being investigated. If no buried facility was contacted, a pre-job checklist or near-miss report may be a better fit. The form works best when completed promptly, with conditional logic for injury, environmental release, and notification fields so the reporter only sees the sections that apply.

Standards & compliance context

  • Use data minimization by collecting only the incident details needed for investigation, notification, and corrective action.
  • If witness or submitter information is collected, disclose how it will be used and stored, and avoid unnecessary PII fields.
  • Design the form to be accessible under WCAG 2.1 AA with clear labels, keyboard navigation, and readable validation messages.
  • Use progressive disclosure for injury or environmental release follow-up so the form does not overwhelm the reporter with irrelevant fields.
  • Maintain an audit trail for edits, acknowledgments, and notifications so the investigation record remains traceable.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

What's inside this template

Incident Overview

This section establishes the who, when, where, and what of the strike so the rest of the report has a reliable starting point.

  • Date of strike (required)
    Select the date the buried facility was contacted.
  • Time of strike
    Approximate time of the contact or damage event.
  • Project or work area (required)
    Enter the project name, site name, or work area where the strike occurred.
  • Incident type (required)
    Choose the closest match. Additional fields will appear based on the incident type.
  • Brief incident summary (required)
    Describe what was struck, how the contact occurred, and any immediate effects.

Facility and Locate Details

This section documents the buried asset and the locate conditions that should have guided the excavation.

  • Facility owner (required)
    Name of the utility or facility owner.
  • Facility type (required)
  • Locate ticket status (required)
    Indicate the status of the locate ticket at the time of work.
  • Locate ticket number
    Enter the ticket or request number if available.
  • Locate accuracy (required)
    Assess how well the marks matched the actual buried facility location.
  • Marking conditions observed
    Select all conditions that affected locate visibility or reliability.

Excavation and Strike Details

This section shows how the work was performed and exactly how the contact occurred.

  • Excavation method (required)
  • Depth at strike (inches)
    Enter the approximate depth where contact occurred.
  • Planned excavation depth (inches)
    Enter the intended depth before the strike occurred.
  • Strike location on site
    Describe the area, station, grid, or reference point where the strike occurred.
  • Was potholing or daylighting completed before digging? (required)
  • Potholing / daylighting details
    Describe the verification method used before excavation.

Damage Assessment and Immediate Actions

This section records the severity of the damage and the first response steps taken on site.

  • Damage severity (required)
  • Was service interrupted? (required)
  • Immediate actions taken (required)
    Select all actions taken immediately after the strike.
  • Other immediate actions
  • Did anyone get injured? (required)
  • Was there any spill, leak, or release? (required)

Root Cause and Follow-Up

This section turns the incident into corrective action by identifying why it happened and what must change.

  • Primary root cause (required)
  • Contributing factors
    Select all factors that contributed to the incident.
  • Corrective actions (required)
    Describe actions to prevent recurrence, including training, process changes, or additional verification steps.
  • Are external notifications required? (required)
    Use this to route the report for compliance or utility notification review.
  • Notification details
    List agencies, utility owners, or other parties notified and the time of notification.

Attachments and Acknowledgment

This section preserves supporting evidence and confirms who submitted the report.

  • Photos of damage and site conditions
    Upload any photos, sketches, or supporting documents.
  • Witnesses or involved parties
    Add only the minimum necessary contact details for follow-up.
  • I confirm the information provided is accurate to the best of my knowledge. (required)
    Submitting this report creates an audit trail for investigation and corrective action tracking.

How to use this template

  1. 1. Enter the incident date, time, project name, incident type, and a short summary so the report starts with the basic facts of the strike.
  2. 2. Record the facility owner, facility type, ticket status, ticket number, locate accuracy, and marking conditions to show what was known before excavation began.
  3. 3. Document the excavation method, planned depth, depth at strike, strike location, and whether potholing was completed so reviewers can compare the plan to the actual work.
  4. 4. Describe the damage severity, service interruption, immediate actions taken, injury status, and any environmental release so response steps are captured while details are fresh.
  5. 5. Identify the root cause, contributing factors, corrective actions, and any required notifications so the report supports follow-up and prevention work.
  6. 6. Attach photos, list witnesses, and complete the acknowledgment so the record is ready for review, audit, and internal routing.

Best practices

  • Use conditional logic so injury, environmental release, and notification fields appear only when they apply.
  • Capture the ticket number and locate status before the crew leaves the site, not from memory later in the day.
  • Choose field types that match the data, such as date pickers, time fields, numeric depth inputs, and multi-select lists for contributing factors.
  • Document the exact strike location in relation to the trench, bore path, or pothole so the root-cause review can distinguish a direct hit from a sidewall contact.
  • Record whether potholing was completed and what it revealed, because skipped or incomplete verification is a common failure point.
  • Add photos at the time of the incident and label them clearly so reviewers can match images to the written findings.
  • Keep the form focused on facts and required follow-up, and avoid collecting unnecessary PII or unrelated incident details.

What this template typically catches

Issues teams running this template most often surface in practice:

Locate markings were missing, faded, or inconsistent with the actual buried facility path.
The ticket was expired, not verified, or not matched to the work area before digging started.
Potholing was skipped, incomplete, or not documented before mechanical excavation.
The excavation method or equipment used did not match the planned depth or clearance assumptions.
The strike occurred outside the expected alignment because the crew relied on assumptions instead of field verification.
Immediate actions were taken but not recorded clearly enough to support follow-up or notification.
Root cause was written too broadly, such as 'operator error,' without identifying the contributing process failure.

Common use cases

Civil contractor utility strike review
A roadwork crew hits a buried telecom line during trenching and needs a structured report for the project manager, locate provider, and subcontractor review. The template captures the ticket status, marking conditions, and corrective actions in one place.
Municipal water main damage report
A public works team damages a water main during excavation and must document service interruption, immediate containment steps, and notification details. The form helps preserve a clear audit trail for operations and follow-up.
Gas utility damage investigation
A contractor contacts a gas facility and needs to record the strike location, depth at strike, potholing status, and whether an environmental or safety response was triggered. The template supports fast escalation without collecting unnecessary fields.
Fiber cut on a utility corridor project
A crew cuts fiber during directional drilling and needs to show how locate accuracy, excavation method, and planned depth differed from the actual conditions. The report makes it easier to identify process gaps and prevent repeat damage.

Frequently asked questions

When should this report be completed?

Complete it as soon as the site is safe and the incident can be documented accurately, ideally the same day as the strike. The goal is to capture conditions before markings fade, equipment is moved, or witness details are lost. If the investigation is still open, submit the initial facts first and update the report later with follow-up findings.

Who should fill out the utility strike investigation report?

It is usually completed by the field supervisor, project manager, safety lead, or damage prevention coordinator. The best owner is someone who can gather facts from the crew, locate provider, and site records without rewriting the event from memory alone. If your process includes an audit trail, assign one person to submit and another to review for completeness.

What kinds of incidents does this template cover?

This template is for contact with buried facilities such as gas, electric, water, telecom, sewer, or fiber during excavation. It works for partial damage, full service interruption, near-miss strikes that exposed a facility, and cases where locate markings were missing or inaccurate. It is not meant for general workplace injuries unless the utility strike is the primary incident.

How often should this form be used?

Use it for every utility strike or suspected strike, not just major outages. Consistent use creates a reliable record of ticket status, locate conditions, and corrective actions, which helps compare incidents over time. If your organization has a separate near-miss process, this form can still be used when a buried facility is contacted or visibly damaged.

What are the most common mistakes when completing it?

Common mistakes include leaving out the ticket number, describing the strike in vague terms, and skipping the exact depth at strike. Another frequent issue is failing to document whether potholing was completed before excavation, which makes root-cause review harder. The form also works best when photos, witness names, and immediate actions are added before the crew leaves the site.

How does this template help with compliance and documentation?

It creates a structured record of what happened, what was known before digging, and what actions were taken after the strike. That supports internal safety review, contractor oversight, and utility notification workflows. If your process involves regulated reporting or insurance follow-up, the notification fields help preserve the audit trail without forcing extra narrative elsewhere.

Can this template be customized for different utilities or contractors?

Yes. You can add facility-specific fields for gas odor, pressure loss, fiber cut, water leak, or electrical arc indicators, and you can tailor the root-cause list to your excavation process. Many teams also add conditional logic so follow-up fields appear only when service interruption, injury, or environmental release is selected.

What should be connected to this form in a workflow?

This report often connects to incident management, corrective action tracking, photo storage, and notification workflows. It can also link to locate ticket records, crew assignment data, and subcontractor logs so reviewers can verify the sequence of events. If your team uses an approval step, route the completed report to safety, operations, and the utility coordinator.

How is this different from an ad-hoc incident note or email?

An ad-hoc note usually misses key fields, uses inconsistent wording, and makes later review difficult. This template standardizes the facts that matter most: locate status, excavation method, strike location, damage severity, and immediate actions. That makes it easier to compare incidents, assign corrective actions, and keep the record usable for follow-up.

Go deeper on the topic

Related concepts
  • A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
  • Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
  • A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
  • A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
Related guides

Ready to use this template?

Get started with MangoApps and use Utility Strike Damage Investigation Report with your team — pricing built for small business.

Ask AI Product Advisor

Hi! I'm the MangoApps Product Advisor. I can help you with:

  • Understanding our 40+ workplace apps
  • Finding the right solution for your needs
  • Answering questions about pricing and features
  • Pointing you to free tools you can try right now

What would you like to know?