CGA DIRT Field Submission Form
CGA DIRT Field Submission Form template for reporting excavation damage with incident details, root cause, and corrective actions. Use it to capture the fields needed for a cleaner DIRT submission and follow-up.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Utilities · Construction · Pipeline Operations · Telecommunications
Overview
The CGA DIRT Field Submission Form template is a structured workplace form for documenting excavation-related damage incidents before they are submitted or reviewed in a DIRT workflow. It captures the submission notice, incident summary, excavator information, facility and damage details, root cause, contributing factors, and corrective actions in a sequence that matches how field teams typically gather facts.
Use this template when you need a consistent intake record for a utility strike, near miss, or other excavation damage event. It works well for field supervisors, compliance teams, and incident investigators who need to collect the same core details every time, reduce back-and-forth, and create a clearer audit trail. The form also helps with progressive disclosure by separating basic incident facts from follow-up analysis, so users do not face a long wall of fields at the start.
Do not use this template as a general safety incident form or a broad employee complaint form. It is specific to DIRT-style damage reporting and should stay focused on the incident, the parties involved, the damage, and the corrective actions. If your process does not require contact details, keep those fields optional or use anonymous submission where appropriate. If you need medical, HR, or unrelated personal data, use a different form built for that purpose.
Standards & compliance context
- Keep the submission notice aligned with GDPR data minimization by collecting only the PII needed for incident follow-up and reporting.
- If the form is used in a public-facing or shared workflow, make the labels, validation, and error states accessible to WCAG 2.1 AA standards.
- Use the minimum-necessary principle when deciding whether excavator contact details or other identifying information are required.
- If the form is adapted for internal safety review, maintain an audit trail of edits, reviewer actions, and final submission status.
- Do not add unrelated medical or HR fields; if accommodation or injury details are needed, route them to a separate compliant intake form.
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
Submission Notice
This section sets the purpose of the report, explains consent and PII handling, and tells the user what will happen after submission.
-
Submission purpose
This form captures excavation damage details for CGA DIRT reporting and damage prevention analysis.
- I confirm the information provided is accurate to the best of my knowledge
-
PII notice
Collect only minimum necessary information. Avoid entering sensitive personal data unless required for the report.
Incident Summary
This section captures the core facts of the event so reviewers can place the damage in time, location, and incident context.
- Date of damage event
- Time of damage event
-
Incident location
Enter the worksite or nearest address where the damage occurred.
- State or province
- Incident type
Excavator Information
This section identifies the party and work context involved in the incident, which is essential for follow-up and accountability.
- Excavator company or organization
- Excavator type
- Type of work being performed
-
Excavator contact name
Optional contact for follow-up. Do not enter unnecessary personal data.
Facility and Damage Details
This section records what was damaged, how severe it was, and whether emergency response was needed.
- Facility type
- Facility owner/operator
-
Damage description
Describe what was damaged, how it was damaged, and any immediate impacts.
- Damage severity
- Was emergency response required?
Root Cause and Contributing Factors
This section helps the reviewer move from description to analysis by documenting why the incident happened and what influenced it.
- Root cause
- If other, describe the root cause
- Contributing factors
- If other, describe contributing factors
Corrective Actions and Follow-Up
This section turns the report into an action record by capturing immediate steps, prevention measures, and any required follow-up.
-
Immediate actions taken
Include notifications, site controls, repairs, and any safety measures taken after the event.
- Recommended preventive actions
- Is follow-up required?
- Follow-up notes
How to use this template
- Start by configuring the submission notice so users understand the purpose of the report, the consent language for any PII collected, and what happens after they submit.
- Set required fields for the incident summary and excavator information, and use date, time, and structured selection fields instead of free-text inputs where possible.
- Add conditional logic for root_cause_other, contributing_factors_other, and follow_up_notes so extra text fields appear only when the user selects an 'other' option or needs follow-up.
- Assign the form to the person who can verify the incident facts, then route the completed record to the compliance or operations reviewer for validation before submission.
- Review the completed submission for missing fields, inconsistent location details, and unclear corrective actions, then update the record with any final follow-up or closure notes.
Best practices
- Use a date picker for incident_date and a time field for incident_time so the report is easier to validate and compare later.
- Mark only the fields you truly need as required, and keep contact and follow-up details optional unless your process depends on them.
- Use conditional logic for 'other' fields and follow-up notes so the form stays short for straightforward incidents.
- Capture the incident location in a structured way that can be mapped to your internal asset or jurisdiction records.
- Separate immediate_actions from preventive_actions so the report distinguishes what was done on site from what will prevent recurrence.
- Write root cause options in plain operational language that field staff can select consistently without guessing.
- Include a clear submission confirmation line so users know whether the form creates an internal record, a DIRT draft, or a routed review task.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this template used for?
This template is used to collect the information needed for a Common Ground Alliance DIRT damage report. It organizes the incident summary, excavator details, facility and damage data, root cause, and corrective actions in one form. That makes it easier to submit a complete report and track follow-up. It is designed for field, safety, and compliance workflows.
Who should complete the form?
A field supervisor, damage investigator, utility coordinator, or safety/compliance lead usually completes it. The best owner is the person who can verify the incident facts and confirm the corrective actions. If multiple people contribute, use the form as the shared intake record and assign one reviewer before submission. That helps reduce missing fields and inconsistent entries.
When should this form be submitted?
It should be completed as soon as practical after the incident while details are still fresh and evidence is available. Many teams use it immediately after the site response and then finalize it after the initial review. If your process includes internal approval, keep the form open for updates until the report is ready. Delays often lead to incomplete root-cause entries and weaker corrective-action notes.
Does this form collect personal data?
It can, because it includes excavator contact details and may capture names tied to an incident. Keep the PII notice clear and collect only the contact information you actually need for the report and follow-up. If your workflow allows it, use anonymous submission for internal reporting steps that do not require identity. That supports data minimization and reduces unnecessary exposure.
What are the most common mistakes when filling it out?
Common mistakes include leaving the incident time vague, choosing an overly broad root cause, and skipping the corrective-actions section. Another frequent issue is using free text where a structured field would make the report easier to review later. Teams also miss the difference between immediate actions taken on site and preventive actions planned afterward. This template separates those fields so the report is easier to audit.
Can we customize the root-cause and damage fields?
Yes. You can tailor the root-cause options, damage severity scale, and facility type list to match your internal taxonomy or reporting process. If your organization uses conditional logic, show the 'other' fields only when needed to keep the form shorter. You can also add validation for dates, times, and required incident identifiers. That improves consistency without changing the core DIRT structure.
How does this fit with other systems or workflows?
This form can feed a ticketing system, incident log, or compliance tracker after submission. Many teams route the completed record to safety, operations, and asset-management owners for review and corrective action. If you use integrations, map the fields carefully so incident date, location, and facility type stay consistent across systems. A clean field structure makes downstream reporting much easier.
What should we avoid collecting in this form?
Avoid collecting unnecessary sensitive data such as SSNs, DOB, or unrelated medical details. For a damage report, the minimum-necessary principle should guide what you ask for, especially if the form is shared broadly. Use the submission notice to explain what will happen after submission and who will review it. That keeps the form focused on the incident rather than turning it into a general intake form.
Related templates
Go deeper on the topic
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
-
Manual HR data entry costs $4.78 per entry and introduces bias into pay decisions. Learn how automating performance data creates fairer, more accurate...
-
See how the Kansas City Chiefs unified communication for 600+ event staff with a branded app, achieving 90% adoption and reaching every employee on game day.
-
Discover how continuous feedback, dynamic goal-setting, and psychological safety replace annual review dread with a no-surprise performance culture that...
-
MangoApps 2026 Winter Release adds native shift scheduling, structural AI for surveys and wikis, and a redesigned search—unifying frontline operations in one...
Ready to use this template?
Get started with MangoApps and use CGA DIRT Field Submission Form with your team — pricing built for small business.
