MEP Coordination and Fire Compliance: Where Clashes Become Code Violations
· 4 min read · By Verify AI
Clash detection tools are very good at finding objects that occupy the same space. They are much less useful at telling you which of the thousands of results matter for fire safety. A duct passing through a partition is a normal coordination item. The same duct passing through a fire-rated wall without a damper is a code violation. The geometry is the same, and the consequences are not.
This article covers the interfaces where MEP coordination and fire compliance meet, so you can prioritise them.
Hard clashes vs compliance-critical interfaces
A hard clash is two objects overlapping. A compliance-critical interface is a place where a service crosses or sits next to a fire-safety element and the code says something specific about it. Many of the second kind are not clashes at all, because the objects do not overlap. They are simply missing something: a damper, a seal, a clearance or a separation.
That is why a clash report cannot double as a fire-compliance review.
The interfaces to check
| Interface | Why it matters | What to verify |
|---|---|---|
| Duct through a fire-rated wall or floor | Fire and smoke can spread along the duct | A fire damper of the right rating at the crossing, accessible for maintenance |
| Pipe or cable through a rated element | The opening weakens the rating | Fire-stopping shown or specified at every penetration |
| Service shafts | Shafts act as chimneys between floors | Shaft enclosure rating, and separation of electrical risers from wet services |
| Sprinkler pipework and heads | Obstructions block spray patterns | Clearance from ducts, beams, lights and other services |
| Stair and lift-lobby pressurization | Smoke must be kept out of escape routes | Supply ducts, fans and relief paths shown and consistent with the enclosure |
| Basement smoke extraction | Smoke must be removed and replaced with fresh air | Extraction and make-up air routes, plus fan redundancy where required |
| Electrical panels and switchgear | Safe access is required during an emergency | Clear working space in front of panels, and no wet services above them |
| Emergency power feeders | Life-safety loads must keep running | Feeders routed so one fire does not cut both supply and backup |
Three patterns that cause repeat comments
Dampers that are drawn in one model and missing in another
Ducts are usually modelled by the mechanical team and walls by the architect. The rating lives on the wall, and the damper lives on the duct, so neither model shows the gap. Checking the two together is the only way to see it.
Shafts shared by incompatible services
Space in a core is tight, and it is tempting to run electrical and plumbing risers in the same shaft. Codes often require them to be separated or enclosed differently, and the conflict only shows up when the shaft is read as a fire compartment rather than as empty space.
Clearances lost late in design
Panels, hydrants and valves are placed early and then squeezed by later changes. A clearance that was fine at the design stage can be gone by the time drawings are issued.
A coordination workflow that catches these
- Agree which model owns each rating and each device. Ratings on walls, dampers on ducts, and so on.
- Coordinate against fire-safety elements, not only against each other. Include the rated walls, shafts and stair enclosures as their own reference layer.
- Run compliance checks alongside clash detection, before design freeze rather than after.
- Track the results per interface. A list of open dampers, seals and clearances is a better working document than a list of clash IDs.
- Re-run after every significant model update. Fixing one interface often affects another.
The related guide on checking an IFC model for code compliance explains how to make sure the model carries the ratings and object types these checks rely on.
Where Verify AI fits
Verify AI reads the fire, electrical, HVAC and plumbing systems from a coordinated model together and checks the interfaces above as compliance rules, rather than only reporting overlaps. That means the review lands on the missing damper or the shared shaft directly. See the solutions by discipline, or contact us to see it on a coordinated model of your own.