BIM coordination vs. clash detection: turn model findings into decisions
Distinguish BIM coordination from detecting clashes. Track model issues through ownership, resolution and issued documents before relying on an estimate assumption.
Author
Ido Gedanken, CEOPublished

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.
Book a demo- Type
- Guide
- Read
- 2 min
- Published
On this page
A clash report identifies a potential geometric conflict. Coordination decides whether it matters, who must resolve it, what the resolution changes and how the team will verify closure. A clear model report alone is not proof that the design is buildable, that every required clearance was checked or that the revised work is included in the bid.
buildingSMART's BIM Collaboration Format description uses a beam and duct example to illustrate assigning an issue, discussing it and tracking its resolution. The format supports communication; the project team still decides the solution.
Establish what was checked
Record model authors, versions, dates, coordinate alignment, included trades, model detail and check rules. A check of physical intersections may not test access for maintenance, insulation thickness, installation sequence or components absent from the model. Ask the model manager what was included before interpreting a clean report. Compare the model to current contract documents and read between the drawings where the design information is incomplete.
Work the issue through a decision
Illustration: a duct intersects a beam above a corridor. The mechanical trade proposes a lower duct; the ceiling subcontractor warns that this would reduce ceiling clearance. The coordinator assigns the designer to decide the route and the structural engineer to evaluate any proposed structural change. Neither a clash marker nor a trade suggestion authorizes a beam penetration.
| Stage | Record | Required next action |
|---|---|---|
| Detected | Duct and beam locations plus model versions | Check actual clearance and document scope |
| Assigned | Designer and affected mechanical and structural trades | Compare feasible alternatives |
| Priced | Reroute length, fittings, ceiling and access changes | Get revised trade prices and schedule effect |
| Closed | Accepted design revision and updated models | Verify affected bids and estimate reflect the decision |
If the accepted route adds fittings and requires a ceiling adjustment, request separate price revisions and check whether the original mechanical and ceiling carries already cover the work. Assign MEP coordination interfaces so that a solution does not leave another trade unassigned. If a response is pending at bid, record the assumed route, pricing basis, risk owner and decision deadline.
Close against documents, not a colored status
Record the design response, affected drawing revision, model update, proposal revision and estimate adjustment. Trace drawing revisions into the estimate, and reopen the issue if a later change invalidates the solution. For an equipment change requiring shop drawings, carry the accepted decision into construction submittals and the procurement schedule. A coordination log is a decision record, not a substitute for the governing design documents.
Related reading
MEP coordination in preconstruction: assign the interfaces before comparing trade prices
MEP coordination can reveal responsibilities beyond one trade’s drawings. Review supports, openings, controls, access, testing and complete package coverage.

The most underestimated skill in estimating: reading between the drawings
Reading between the drawings means pricing implied design intent (trade interfaces, structural supports, and constructability) when the documents are still incomplete. That skill separates quantity extraction from real risk mitigation.

What Changed? How Drawing Revisions Cascade Through Scope, Bids, and the Estimate
A drawing revision is not only a sheet delta. Trace what it does to trade scopes, live bids, and the estimate before bid day locks the number.

Construction submittals: build the register before procurement commitments
Build a submittal register from project requirements and connect review, procurement and installation dates to the cost and schedule assumptions in the bid.

Piper removes manual review from the critical path and brings project data, company knowledge, and expert checks into every preconstruction decision and workflow
See Piper on your project
Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.