MEP/structural drawing coordination conflicts aren't evenly distributed across a set. Some interface points generate a conflict on nearly every project of any complexity. Others show up rarely, but only because almost nobody is specifically checking them. Ranked by how often each one actually turns up once someone reads structural and MEP sheets against each other, the list looks different than a plan-view walkthrough would suggest.
That ranking matters for how a review gets scoped. A reviewer with limited time on a large set has to decide where to look first, and "where clashes are most likely" is a different question than "where clashes would be most dramatic if they existed." The interface points below are ordered by frequency — how often they actually generate a finding — not by how bad any single instance could theoretically get.
Structural-MEP Is Already the Single Most Common Clash Category
Before ranking specific interface points, it's worth establishing the baseline: structural-versus-MEP is not one clash category among many roughly-equal ones. A published clash-resolution study of BIM coordination data found that clashes between structural and MEP components were the single most frequent clash category identified, more common than any other discipline-pairing measured. The same study broke down root causes and found design error responsible for roughly half of all clashes identified, with design inconsistency and design discrepancy between documents accounting for most of the rest.
That root-cause split matters for how a review gets scoped. If most structural-MEP conflicts trace back to design error and cross-document inconsistency rather than one team simply drawing carelessly, the fix isn't "tell the engineers to be more careful" — it's a review step built specifically to compare what one discipline drew against what the other discipline drew, on the same set, before it's issued.
1. Duct and Pipe Runs Crossing Load-Bearing Framing
This is the highest-frequency interface point by a wide margin, and it's the one every experienced field superintendent already expects to see. A mechanical or plumbing line routed on the shortest path to the space it serves, drawn against a beam, girder, or joist placed on the grid that carries load most efficiently — the two logics collide constantly because they're solving different problems using the same physical volume. It's covered in more mechanical depth in our breakdown of where structural and MEP conflicts actually originate; the point here is narrower: of every interface point on this list, this is the one that turns up most often in an actual document read, hard clash or soft clearance violation alike.
2. Undersized or Unspecified Penetration Sleeves
This one is less discussed than the duct-through-beam clash, but it turns up almost as often once someone is looking for it. Structural drawings frequently show a generic penetration or sleeve detail — a typical detail referenced by a note, not a location- and size-specific callout — with the actual coordination pushed to a "coordinate with MEP" instruction. That instruction assumes someone, at some point, actually does the coordinating. In practice, the mechanical, electrical, and plumbing sheets are often finalized on a different schedule than the structural sheets, and the sleeve sizes and locations that end up needed don't match what the generic detail anticipated — sometimes because the final pipe or conduit run is larger than what was assumed when the structural detail was drafted, sometimes because the sleeve simply isn't shown where the final MEP routing actually crosses the member. On a cast-in-place or precast structural system, catching this on paper is the difference between a redline and a core-drilled penetration through installed concrete — the same gap between a paper fix and a field fix that turns a single missed duct-versus-beam clash into a six-figure change order when it's caught after steel or concrete is already in place.
3. Fire-Rated Assembly Penetrations
Every MEP line that crosses a fire-rated wall or floor assembly needs a firestop detail that matches both the assembly's rating and the specific penetrating item — and the structural or architectural drawings that establish the rated assembly aren't always cross-checked against the MEP sheets that show how many penetrations actually cross it, and where. This interface point fails often enough to be a distinct category worth naming on its own, and it tends to survive review longer than a duct-versus-beam clash because it isn't a physical clash at all — geometrically, the pipe fits through the wall. The conflict is a documentation gap: the rated assembly detail doesn't account for the penetration count or type actually shown crossing it on the MEP set, and it typically isn't caught until a special inspector or fire marshal reviews the installed condition against the approved assembly.
4. Rooftop and Mechanical Equipment Support Coordination
Rooftop units, condensing equipment, and other mechanical loads landing on a roof structure need the structural framing beneath them sized and reinforced for that specific load, at that specific location — and on a lot of sets, the mechanical equipment schedule and the structural roof framing plan are developed on separate timelines, with equipment weights and final locations sometimes settling after the structural drawings are already substantially complete. This interface point fails often enough on projects with any meaningful rooftop mechanical load that it belongs on this list on its own, distinct from the ceiling-plenum stack-up conflicts that get more attention. The fix, caught late, usually means added structural reinforcement retrofitted around installed roofing and equipment curbs — one of the more disruptive and schedule-sensitive corrections on this entire list.
5. Hanger and Support Attachment to Structural Members
The last interface point on this list is the one most likely to be missed by a document-only review, because it often depends on submittal-stage information that isn't finalized when the drawings are issued. Ductwork, piping, and cable tray all need to hang from something, and the structural members most convenient to hang from — bar joists especially — have manufacturer-specific limits on where and how much load can be attached without the joist manufacturer's written approval. A mechanical or plumbing system sized and routed without that constraint in mind can generate a hanger load the structural drawings never accounted for, discovered only when the joist manufacturer's submittal comes back with a rejection or a required reinforcement detail.
Key takeaways
- Structural-MEP conflicts aren't one clash type among many comparable ones — published clash-detection data identifies them as the single most frequent discipline-pairing, with design error and cross-document inconsistency as the leading causes.
- Duct and pipe runs crossing load-bearing framing remain the highest-frequency interface point, but three under-discussed categories — unspecified penetration sleeves, fire-rated assembly penetrations, and rooftop equipment support — fail often enough to warrant their own line item in a review scope.
- Fire-rated penetration conflicts are documentation gaps, not physical clashes, which is exactly why they tend to survive design review and surface at special inspection instead.
- Hanger and support attachment conflicts often depend on submittal-stage information (joist manufacturer approvals) that isn't finalized when the drawings are first issued, making them the hardest of the five to catch on a single document pass.
- Ranking interface points by how often they actually generate a finding — not by how severe a single instance could be — is what should drive where review time goes first on a set with limited turnaround.
Frequently Asked Questions
Which MEP/structural interface point causes the most conflicts overall?
Duct and pipe runs crossing load-bearing framing remain the single highest-frequency interface point — the classic hard clash between a routed line and a beam, girder, or joist. Published clash-detection research also identifies structural-versus-MEP as the most common discipline-pairing overall, ahead of any other combination measured.
Why do fire-rated penetration conflicts get missed so often?
Because they aren't physical clashes. The penetrating pipe or conduit fits through the wall or floor geometrically — the conflict is that the rated assembly's firestop detail wasn't coordinated against the actual number and type of penetrations shown crossing it on the MEP sheets. That kind of documentation gap doesn't show up in a 3D clash report and often isn't caught until special inspection.
Can rooftop equipment support conflicts really be caught before the roof is built?
Yes, if the mechanical equipment schedule (weights, locations, curb dimensions) is checked against the structural roof framing plan before the set is issued. The reason this interface point fails as often as it does isn't that the conflict is hard to see — it's that the two sheets are frequently finalized on different timelines, and nobody cross-checks them against each other until submittals or, worse, installation.
Is a hanger and support conflict really a design error, or is it unavoidable?
It's usually not unavoidable — it's a coordination gap. Joist manufacturers publish clear limits on point loads and attachment locations, and an MEP system routed and sized with those limits in mind from the start avoids the conflict entirely. The problem is that the structural drawings and the final MEP hanger loads are often not checked against each other until the joist submittal comes back, which is much later in the process than a document-level review would catch it.
Does this ranking apply the same way to every project type?
The relative order shifts with the project. A high-rise or multifamily building with extensive fire-rated corridor and shaft assemblies will see fire-rated penetration conflicts more often; a data center or manufacturing facility with heavy rooftop mechanical loads will see equipment support conflicts more often. Duct-through-framing conflicts show up at high frequency across nearly every project type, which is why it holds the top spot regardless of asset class.