MEP Coordination Problems: Why Systems Clash During Construction

A clash-free screenshot does not guarantee an installable building. Mechanical, electrical and plumbing systems occupy physical space, need maintenance access and rely on support, firestopping and structural interfaces. Coordination problems appear when the shared model does not represent those requirements or when resolved issues fail to reach the construction documents.
Coordinate more than the equipment outline
Include duct insulation, pipe insulation, cable tray access, valve operation space and equipment removal paths at the level required for the project stage. A pump can fit inside a plant room while its motor cannot be withdrawn for maintenance. Distinguish a physical clash from a clearance or access conflict.
Gravity drainage needs slope and connection levels, not merely a clear centreline. Cable containment needs bend radii and pulling access. Fire protection and ventilation arrangements must retain their functional coverage after routing changes.
Establish a shared spatial and revision basis
Agree coordinates, levels, units, model origin and reference revisions before combining disciplines. A displaced model can generate hundreds of false clashes. Missing or stale links can hide genuine conflicts that appear only when fabrication drawings arrive.
Define which model owns openings, sleeves, supports and builders' work. Include the relevant structural and architectural constraints. A route through a beam cannot be accepted just because the MEP model has been moved clear of another service.
Prioritise by consequence and installation sequence
Group duplicate clashes and review the ones that control layout: major risers, plant access, large ducts, drainage falls and structural crossings. Then resolve local interfaces. Autodesk's model-coordination workflow supports clash grouping and issue assignment; software detection still needs an engineer to decide the acceptable resolution.
Sequence matters. A route may fit in the final geometry but be impossible to install after another trade closes the access. Coordinate lifting paths, prefabricated module sizes and the space needed for jointing or welding.
Make every change an owned engineering decision
Each issue should identify the location, affected revisions, responsible designer, agreed resolution and due date. The person moving a service must understand the consequence for pressure drop, drainage, electrical separation, support loading and maintenance.
For example, lowering a duct may solve a beam clash while reducing headroom or forcing a drainage diversion. Review the combined consequence, update calculations when required and re-run the affected clash checks. Closing an issue should reference the revised deliverable, not only a meeting comment.
Release coordinated construction information
Issue coordinated layouts and sections with penetration schedules, support interfaces and equipment access requirements. Check that fabrication and shop drawings retain the agreed constraints. Field changes should enter the revision and as-built process.
A preconstruction review should ask whether the models are aligned, critical clearances are represented, unresolved issues are visible and each trade has an approved installation basis. Fluxiss can support MEP design review with the architectural and structural inputs needed to make those answers concrete.
Frequently Asked Questions
No. It helps detect and communicate conflicts; designers must agree changes that preserve system performance and construction requirements.
Technical references & further reading
Practical engineering explainers connecting analysis methods, design inputs and project decisions.
Related articles.
Let's Build Something Great Together.
Partner with Fluxiss for engineering that holds up - under pressure, under load, under scrutiny.

