HVAC to Structural Conflicts Explained

A duct routed straight through a beam is one of the most common coordination failures on a construction document set, and also one of the most expensive to discover late. It's worth understanding why it keeps happening even on well-run projects.

Why This Specific Conflict Is So Common

Mechanical engineers typically design ductwork routing based on load calculations, air handling unit placement, and ceiling space constraints. Structural engineers design framing based on load path, beam depth requirements, and lateral force resisting system needs. Both disciplines are solving their own problem correctly in isolation. The conflict shows up specifically at the intersection, where a duct sized for a required airflow rate needs a certain amount of vertical clearance, and a structural beam sized for a required span needs a certain depth, and nobody explicitly checked whether both fit in the same ceiling cavity.

This gets worse on tight floor-to-floor heights, common in renovation work or in projects where structural depth was value-engineered late in design development without a full recheck of MEP clearances above the ceiling.

Where in the Process This Usually Gets Caught, or Doesn't

In a well-coordinated BIM environment, this kind of clash shows up in a federated model clash detection report. In a lot of real-world 2D drawing sets, especially where mechanical and structural aren't modeling in a shared environment, this conflict doesn't get caught until a coordination meeting, or worse, during rough-in, when a subcontractor discovers the duct literally can't fit where it's drawn.

What Structured AI Checks Here

Overlay finds every sheet across mechanical and structural drawings covering the same area of the building and aligns them automatically, even when the two disciplines are drawn at different scales. That surfaces above-ceiling clashes and structural penetrations before the set leaves the office, which is exactly the kind of conflict general contractors and MEP engineers report as a recurring source of field RFIs.

Beyond the overlay itself, checks like MECH-5 Volume Damper BIM Check and MECH-6 Volume Damper Check catch related ductwork coordination issues, while MAC-7 Architectural Clash Coordination checks for broader cross-discipline conflicts beyond just the mechanical-structural pairing.

Why Catching This Early Matters So Much

A duct-to-beam conflict caught during design development costs a redrawn routing path. Caught after the duct is fabricated and delivered to site, it costs demolition of installed ductwork, potentially cutting or reinforcing the structural member if a penetration becomes necessary, and schedule delay while the fix gets designed, approved, and executed. The underlying error is identical at every stage. The cost is not.

FAQ

Is this only a problem in older buildings with tight floor-to-floor heights? No, though tight floor-to-floor conditions make it more likely. It shows up on new construction too, particularly when structural depth gets value-engineered late without a full recheck of mechanical clearances, or when ductwork sizing changes late in design without a corresponding structural recheck.

Does BIM coordination eliminate this problem? It significantly reduces it when both disciplines model in a shared, properly coordinated environment, but a lot of real projects still have gaps, either because not every discipline is modeling at the same level of development, or because some coordination still happens across separate 2D drawing sets.

What's the difference between a hard clash and a clearance issue here? A hard clash is the duct and beam literally occupying the same space. A clearance issue is when they technically don't overlap but leave insufficient space for insulation, hangers, or code-required clearances, which is a softer but still real problem.