---
title: 'BIM coordination vs. clash detection: turn model findings into decisions'
url: 'https://piper-ai.com/resources/bim-coordination-vs-clash-detection'
description: 'Distinguish BIM coordination from detecting clashes. Track model issues through ownership, resolution and issued documents before relying on an estimate assumption.'
contentTypes: [guide]
publishedAt: '2026-11-18T05:30:47.098Z'
updatedAt: '2026-11-18T05:30:47.110Z'
author: 'Ido Gedanken, CEO'
readingTime: 2
---

# BIM coordination vs. clash detection: turn model findings into decisions

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](https://info.buildingsmart.org/standards/bsi-standards/bim-collaboration-format/) 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](https://piper-ai.com/resources/reading-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](https://piper-ai.com/resources/mep-coordination-preconstruction-scope) 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](https://piper-ai.com/resources/drawing-revisions-cascade-scope-bids-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](https://piper-ai.com/resources/construction-submittal-register-prebid) and the procurement schedule. A coordination log is a decision record, not a substitute for the governing design documents.
