BIM Clash Detection and MEP Coordination: Finding the Pipe That Doesn't Fit Before It's Already Installed
Building Information Modeling (BIM) has become standard on most commercial and institutional construction projects. The core use case is clash detection — finding conflicts between different building systems (HVAC ducts, plumbing pipes, fire sprinklers, electrical conduit, structural elements, architectural features) in the model before they become field problems. Well-executed BIM coordination resolves thousands of conflicts in the model phase, each of which would have been an RFI, rework event, or change order in the field.
The problem is that BIM can also be expensive paperwork — models built to satisfy contract requirements but not used actively to drive coordination. This post describes the workflows that produce actual value from BIM coordination and the decisions that separate effective coordination from theater.
Effective coordination requires a federated model — a combined model with each trade's BIM content overlaid:
Federation model components
- Architectural model — walls, floors, ceilings, openings
- Structural model — columns, beams, slabs, foundations
- HVAC model — ductwork, equipment, air distribution
- Plumbing model — domestic water, sanitary, storm, vents
- Fire protection model — sprinkler piping, heads, standpipes
- Electrical model — conduit, cable tray, equipment, lighting fixtures
- Specialty systems — medical gas, pneumatic tubes, vacuum, lab gas, etc.
Federation is typically done in a tool like Navisworks (industry standard), Revit (with link federation), Solibri, or similar. Each trade contributes their model; the BIM coordinator federates and runs clash detection.
Not all clashes are equal. A practical categorization:
Clash category hierarchy
- Hard clashes — physical interference between elements (pipe through beam, duct through wall)
- Soft clashes — clearance violations (conduit within minimum clearance of panel, duct without service space)
- Workflow clashes — sequencing issues (install sequence doesn't work given other systems)
- Access clashes — installed position accessible for maintenance
Hard clashes are the easiest to identify — geometry interference is unambiguous. Soft clashes require defined clearance rules applied programmatically. Workflow and access clashes often require human review and judgment.
Raw clash reports typically show thousands of items — too many to resolve individually. Priority ranking focuses work:
Clash priority factors
- Severity — is this a structural issue, a major system conflict, or a minor interference
- Location — high-activity areas vs low-impact areas
- Criticality — structural elements that can't move vs flexible routing
- Installation sequence — early trades have precedence over later
- Cost of field resolution — expensive if missed vs easily fixable in field
Prioritization lets the coordination team focus on the clashes that matter most. Trying to resolve every clash with equal effort produces coordination exhaustion and misses the critical ones.
Coordination happens in regular meetings, typically weekly during active coordination:
Coordination meeting structure
- Weekly meeting during coordination phase — 2-4 hours depending on project size
- All major trades' BIM leads attend — not just observers
- Specific zones reviewed each week — not whole building every time
- Clash items reviewed and assigned for resolution
- Action items with owners and due dates
- Decisions documented in meeting minutes
Effective meetings involve actual problem-solving. Subs agree on who moves what, what's rerouted, whether the design needs modification, or whether a design issue needs RFI. Meetings that just review clashes without making decisions don't produce progress.
The single most important person in coordination is the BIM coordinator who runs the meetings — typically a senior construction professional with modeling fluency. A coordinator who can drive decisions across trades produces efficient meetings; a coordinator who just presents clashes and asks others what to do produces hours of meeting for minimal progress.
Each clash has a resolution lifecycle:
Clash resolution lifecycle
- Identified — clash appears in detection report
- Reviewed — coordination team triaged and prioritized
- Assigned — trade(s) responsible for resolution identified
- Proposed solution — trade proposes how to resolve
- Approved — team agrees on resolution
- Implemented — model updated
- Re-checked — clash verified as resolved in next detection cycle
- Closed — clash logged as complete
Tracking tools (Navisworks' clash test, BIM 360, BIMcollab, or similar) maintain the resolution state. A clash not properly closed can reopen if subsequent model changes recreate the conflict.
Coordination depends on consistent modeling standards:
BIM modeling standards
- Level of detail (LOD) specified — LOD 300 for coordination is typical
- Coordinate system and location consistent across models
- Model content boundaries clear — each trade's scope in their model only
- Naming conventions and element classifications standardized
- File exchange format and cadence established
- Version control — which model version is current for coordination
Inconsistent modeling wastes coordination effort. A project where trades use different coordinate systems or conflicting classification systems produces false clashes (geometry that appears to conflict but doesn't in reality) that burn coordination time to investigate and dismiss.
Get AP insights in your inbox
A short monthly roundup of construction AP + accounting posts. No spam, ever.
No spam. Unsubscribe anytime.
Field Integration
BIM coordination produces value only if field work follows the coordinated model:
Field integration practices
- Trade contractors installing per the coordinated model, not per uncoordinated original drawings
- Field-to-model feedback — issues discovered in field update the model
- As-built tracking — actual installed locations documented
- Mobile BIM access — field crews can see the model on tablets
- Shop drawing development from the coordinated model
- Prefabrication assemblies based on coordinated dimensions
A field that doesn't use the coordinated model wastes the coordination effort. Effective teams ensure the coordinated model becomes the field's source of truth, not a parallel workstream that fields work around.
Coordinated BIM enables prefabrication:
Prefabrication enabled by BIM
- MEP racks prefabricated to exact dimensions from coordinated model
- Wall panels fabricated with coordinated openings and sleeves
- Modular bathroom pods built offsite per coordinated design
- Curtain wall units fabricated with exact structural connection points
- Mechanical rooms prefabricated as assemblies
Prefabrication shifts work from jobsite to factory — faster, cheaper, better quality, safer. But prefab only works when dimensions are reliable, which requires coordinated BIM. The prefab business case and the BIM business case reinforce each other.
BIM models have value beyond construction:
Owner handoff BIM value
- As-built BIM — accurate record of what was installed
- Equipment specifications embedded — model linked to product data
- Maintenance access documented — space and access requirements preserved
- Facility management integration — model feeds FM systems
- Future renovation basis — starting point for later modifications
Owners who value BIM handoff include it in contract requirements. Projects that produce high-quality BIM for coordination and then preserve the model for handoff deliver long-term value beyond the construction phase.
Coordination that doesn't deliver value typically has specific failure modes:
BIM coordination failure modes
- Models built but not integrated — each trade's model sits in isolation
- Clash detection run but clashes not resolved — reports produced without action
- Low engagement from trade leads — modeling done by back-office staff who don't own the work
- Late start — coordination attempted when field work is imminent
- Inadequate time allocation — coordination expected to happen alongside other work, but really needs focused attention
- No authority to make decisions — coordination meetings without decision-makers
- Field ignores coordinated model — work installed per original uncoordinated drawings
Each failure mode is fixable, but the fix requires recognizing that BIM is a construction process, not a modeling exercise. The models exist to drive field coordination; treating them as an end in themselves produces no value.
BIM clash detection and MEP coordination deliver substantial value when executed as active construction processes — federated models, prioritized clash detection, weekly coordination meetings with decision authority, systematic resolution tracking, consistent modeling standards, field integration that follows the coordinated model, and prefabrication that leverages coordinated dimensions. Done well, BIM coordination replaces thousands of field RFIs and change orders with model-phase resolution that's faster and cheaper. Done badly, BIM becomes expensive paperwork that doesn't prevent field problems. The difference isn't in the modeling tools or the model quality — it's in the human processes wrapped around them. Contractors who treat BIM coordination as construction management in a digital environment get real value; contractors who treat BIM as an IT deliverable usually don't.
Written by
Marcus Reyes
Construction Industry Lead
Spent twelve years running AP at a $120M general contractor before joining Covinly. Lives in the world of AIA G702/G703, retainage schedules, and lien waiver deadlines. Writes about the construction-specific workflows that generic AP tools get wrong.
View all posts