BIM Clash Detection Workflow for Estimators — MEP Coordination Guide

Why Estimators Need Clash Detection

Traditional MEP estimating assumes the systems shown in drawings will fit in the available space. In reality, clashes between ductwork, piping, conduit, and structure are common — particularly in congested ceiling plenums, riser shafts, and mechanical rooms. When an estimator ignores coordination risk, the result is change orders when ductwork must be rerouted around beams or piping must be lowered below ceiling.

BIM clash detection transforms estimating by allowing estimators to identify coordination conflicts before bidding. Instead of assuming perfect coordination, the estimator can quantify the rerouting cost, additional materials, and labor impact of known conflicts. This turns coordination risk from a contingency line item into a quantified scope item.

Based on analysis of 500+ coordinated MEP projects, approximately 65% of drawing sets contain at least one clash that would materially affect bid pricing if left unresolved. The most common high-impact clashes involve ductwork vs. structural beams, electrical conduit vs. plumbing piping, and medical gas routing vs. HVAC duct.

Clash Detection Workflow for Estimating

The estimator's clash detection workflow differs from the coordinator's workflow. While coordinators focus on resolving every clash to achieve a conflict-free model, estimators focus on identifying clashes with cost impact potential. The recommended workflow:

• Step 1: Model Federation — Aggregate architectural, structural, and MEP models into a federated model in Navisworks or Revit. Ensure all models are at comparable LOD (LOD 300 minimum for clash detection useful to estimating).
• Step 2: Automated Clash Run — Run hard clash tests for all MEP-to-structural combinations and MEP-to-MEP trade intersections. Set realistic tolerances: 6" for duct/pipe clashes, 2" for conduit clashes, 1" for sleeve/penetration clashes.
• Step 3: Cost-Impact Filtering — Filter clashes by potential cost impact. The estimator does not need to review every clash — only those that would require material cost increases, labor additions, or schedule changes. A general rule: clashes in ceiling plenums above 8 ft are usually resolvable within existing cost; clashes in shafts, mechanical rooms, and below-ceiling zones typically have cost impact.
• Step 4: Resolution Path Assignment — For each cost-impact clash, assign a likely resolution path: (a) reroute system A, (b) reroute system B, (c) structural modification, (d) accept and document as exclusion. The estimated cost of each resolution path is documented in the estimate scope log.
• Step 5: Bid Documentation — Include the clash log in the bid deliverable as a scope clarification. Each unresolved clash is documented with its potential cost impact, so the contractor understands the coordination risk in the bid price.

Clash Priority Matrix for Estimators

Not all clashes carry equal cost impact. Based on 500+ project analysis, the following matrix helps estimators prioritize which clashes to investigate:

• Critical priority — Duct vs. structural beam in main distribution trunk. Resolution cost: $2,000-$8,000 per clash. These require either structural coordination (beam penetrations) or duct rerouting with pressure drop recalculation.
• High priority — Riser shaft congestion between 3+ trades. Resolution cost: $5,000-$25,000 per shaft. Shaft coordination requires re-routing one or more systems out of shaft, often into finished space.
• Medium priority — Branch duct vs. lighting/sprinkler in ceiling grid. Resolution cost: $500-$3,000 per clash. Typically resolved by adjusting ceiling grid layout or re-routing minor branches.
• Low priority — Small conduit vs. pipe insulation. Resolution cost: under $500. Typically documented and resolved during coordination without cost impact.

For a more detailed breakdown, see our Clash Resolution Priority Matrix developed from 500+ coordinated projects.

Translating Clashes to Cost Impacts

The estimator's unique value is translating a model clash into a quantified cost impact. The key cost drivers affected by unresolved clashes include:

• Additional material — Rerouting adds extra duct, pipe, conduit, fittings, and supports. A typical reroute of a 24" supply duct adds 20-40 LF of duct, 4-6 fittings, and 2-4 supports. Estimated material cost: $800-$2,000 per clash.
• Additional labor — Field rerouting is 30-50% less productive than shop-fabricated routing due to limited access, coordination with other trades, and unplanned conditions. Additional labor: $1,500-$4,000 per clash.
• Schedule impact — Each major clash resolved in the field adds 2-5 days to the MEP schedule through coordination meetings, RFI processing, and revised installation. Schedule delay cost at typical GC general conditions: $5,000-$15,000 per day for large projects.
• System performance impact — Rerouted ductwork with additional elbows and longer runs increases static pressure, potentially requiring larger fans or AHU modifications. Electrical conduit rerouting may increase voltage drop, requiring larger conductors.

LOD Responsibility and Estimate Clarity

The Level of Development (LOD) specified in the BIM Execution Plan directly affects estimate accuracy. For MEP estimating purposes:

• LOD 200 (schematic design) — Generalized systems with approximate sizes. Suitable for order-of-magnitude estimates only. Do not rely on LOD 200 models for clash analysis.
• LOD 300 (design development) — Specific equipment and routed systems with approximate sizes. Minimum LOD for meaningful clash detection. About 70% of coordination conflicts can be identified at LOD 300.
• LOD 350 (construction documents) — Systems with clearances, insulation, and supports modeled. Nearly all clashes (95%+) identifiable. Preferred LOD for estimate-driven clash analysis.
• LOD 400 (shop drawings) — Fabrication-ready models with exact routing, connections, and hangers. Highest accuracy but typically not available during bid-stage estimating.

For a complete BEP framework including LOD responsibility matrices, see our BIM Execution Plan Sample.

Software Tools and Integration

The primary software tools used for estimator-driven clash detection include:

• Autodesk Navisworks Manage — Industry standard for model federation and clash detection. Clash detective tool allows grouping, filtering, and reporting clashes by priority, trade, and location.
• Autodesk Revit — Built-in interference check for basic clash detection within the authoring environment. Limited for cross-discipline federation.
• Autodesk BIM 360 Glue/Coordinate — Cloud-based coordination for distributed teams. Useful when estimator, GC, and subcontractors are in different locations.
• Solibri Office — Advanced rule-based checking beyond hard clash detection. Can identify clearance violations, accessibility issues, and code compliance gaps.

Estimator FAQ