Finding clashes is only half the job. The other half is documenting them so clearly that they actually get resolved. A good clash report is easy to understand, easy to act on, and easy to track. Here's how to put one together.

Step 1: Set Up a Consistent Structure

Using the same format every time makes reports easier to use and track over time:

Header

Project name, report date, revision number, who wrote it

Executive Summary

Total clashes, broken down by severity and discipline

Clash Details

Individual clash documentation (see below)

Resolution Tracking

Status of clashes from previous reports

Appendix

Referenced drawings, notes on methodology

Step 2: Include Everything Someone Needs to Fix It

Each clash entry should have enough detail that someone can find and resolve it without asking you questions:

What to Include for Each Clash

Clash ID: A unique identifier like MECH-STRUC-001

Location: Grid lines, floor level, room or area name

Element 1: Description, size, elevation, which discipline

Element 2: Description, size, elevation, which discipline

Clash Type: Hard clash, soft clash (clearance issue), or 4D (sequencing)

Severity: Critical, major, or minor

Drawing Reference: Sheet numbers where these elements show up

Screenshot: A visual showing exactly where the conflict is

Step 3: Prioritize by Severity

Not every clash is equally urgent. Sort them so the important ones get attention first:

Critical

Can't be built as designed. Needs an immediate design change. Major cost or schedule impact if not resolved.

Major

Will require significant rework. Work can proceed for now, but must be resolved before affected areas start.

Minor

Can be worked out in the field with minor adjustment. Document it, but it's low priority.

Step 4: Assign an Owner to Every Clash

Clashes without owners don't get fixed. Make sure each one has someone responsible:

Name the primary discipline responsible for fixing it

Note any other disciplines that need to be involved

Set a target resolution date based on how severe it is

Identify who can approve the solution

Flag any cost implications that need owner sign-off

Step 5: Add Pictures

A picture really is worth a thousand words when it comes to clash reports. For each clash:

Include a screenshot of the plan view showing exactly where it is

Add markup highlighting the conflicting elements

Include a section or 3D view if you have one

Add dimension annotations showing why it's a conflict

Step 6: Track Where Each Clash Stands

Keep a running status for every clash you've identified:

New

Just found, waiting for someone to look at it

Assigned

Someone owns it, they're working on a solution

Proposed

Solution proposed, waiting for approval

Approved

Solution approved, waiting for updated drawings

Resolved

Updated drawings issued, clash is gone

Closed

Verified fixed in the latest drawing set

Step 7: Report on a Regular Schedule

Regular reports keep the pressure on to get things resolved:

Issue a new report after each major drawing milestone

Update status weekly during active coordination phases

Include a clash summary in your regular coordination meeting agenda

Escalate any critical clashes that sit unresolved too long

Archive resolved clashes but keep them for project history

Related Guides

How to Find Clashes in 2D Drawings

Detect coordination conflicts without BIM software.

How to Prepare for a Coordination Meeting

Run meetings that actually resolve issues.

Generate Reports Automatically

Articulate automatically creates clash detection reports from your drawings, complete with locations, screenshots, and severity classifications. Spend less time writing reports and more time fixing problems.

Try Automated Clash Reporting

How to Create a Clash Detection Report