What does an MEP clash detection service include?
Running a clash test is easy. Navisworks will happily report several thousand clashes on a single floor of a services-dense building. The work that matters is everything that happens after the test: deciding which clashes are real, grouping them into problems a person can solve, proposing a resolution that respects the engineering, and tracking each one to a decision. A clash detection service that stops at the report has handed you a list, not a coordinated design.
Our design-stage clash detection service for M&E consultants covers:
- An audit of incoming models: origins, shared coordinates, levels, system classifications and model health.
- Federation in Navisworks Manage of the mechanical, electrical, public health and fire models with the current architectural and structural models.
- A clash matrix and tolerances agreed with you, run on a set cycle.
- Triage, grouping and prioritisation of results.
- Resolution proposals for every issue, with an owner, a status and a target date.
- Remodelling of the services in our scope to resolve agreed issues.
- Combined services drawings, coordination sections and a builder's work opening schedule.
If you are deciding which tool should do what, our article on Revit vs Navisworks for MEP clash detection explains when each is the right choice.
What is the difference between hard, soft and clearance clashes?
Hard clashes are physical intersections: a duct through a beam, a drainage pipe through a cable tray. They are the easiest to find and, at design stage, often the easiest to fix.
Clearance (or soft) clashes are breaches of space that must stay free even though nothing physically touches: insulation thickness, maintenance access in front of a distribution board, withdrawal space for a coil or a pump, access to valves and fire dampers, or the zone a sprinkler needs to discharge properly. These cause the most expensive surprises on site, because they only show up when someone tries to install, commission or maintain the equipment.
Workflow clashes are conflicts of sequence or responsibility, such as a riser that has to be installed before the slab it passes through is poured, or an opening that the structural engineer has not been told about. Clash software does not find these; experienced coordinators do. Our team's background is MEPF site work going back to 2009, which is why we test for access and installability, not only for geometry.
How is a clash matrix and its tolerances set up?
A clash matrix sets out which model pairs are tested against each other, at what tolerance, and in what order of priority. A sensible design-stage matrix usually starts with services against structure, because the structure is the least negotiable, then services against architecture, then services against each other, with the largest and least flexible systems (gravity drainage, main ductwork, busbar) taking priority over the most flexible (small-bore pipework, final circuits).
Tolerances are set per test. A hard test against structure might use zero tolerance, while a test between small services might ignore minor touches that will be resolved during installation. Clearance tests use modelled access and maintenance zones attached to equipment. We agree the matrix and tolerances with you at the start and record them in the clash report, so the results can be compared from one cycle to the next.
Why do raw clash counts mislead?
One badly placed duct run can create hundreds of clashes with every hanger, tray and pipe it crosses. Reporting all of them as separate issues buries the engineer in noise and hides the single decision that would clear them. Equally, a falling clash count does not prove the design is coordinated, because a test with the wrong tolerance or a missing model will also produce a low number.
We group clashes by cause and location, so that each group represents one problem with one resolution, and we discard duplicates and false positives with a reason recorded. What you receive is a short list of real issues, ranked by how much redesign each one could cause if left unresolved. The cost of letting a single issue reach site is set out in the cost of one clash.
What goes into a useful clash report?
Each issue in our report carries:
- An ID, level, grid reference and zone, with a saved viewpoint.
- The disciplines and elements involved.
- A short description of the problem in plain engineering language.
- A proposed resolution, for example re-route, re-level, re-size or request an opening, and the trade-off it involves.
- An owner, a status (open, proposed, agreed, resolved) and a target date.
Issues can be exchanged in BCF so they open at the right viewpoint in Revit, Navisworks or your design review tool, or raised as issues in Autodesk Construction Cloud if that is how your project team works. In coordination reviews we walk your engineers through the open items and leave with decisions, not red dots on a screen.
How is design-stage clash detection different from construction stage?
| Design stage (RIBA 3–4) | Construction stage (RIBA 5) | |
|---|---|---|
| Who runs it | Consultant, or a coordination partner on its behalf | Main contractor and M&E subcontractors |
| Goal | Prove the services fit in the allocated zones with access | Resolve installation detail before fabrication |
| Model detail | LOD 300–350; generic or selected plant | LOD 400; fabrication fittings, supports, hangers |
| Typical fixes | Re-zoning, riser and plant room resizing, structural openings | Local re-routes, offsets, support changes |
| Cost of change | Remodelling time | Redesign, re-fabrication, programme delay |
| Main output | Coordinated model, combined services drawings, builder's work schedule | Installation and shop drawings |
LOD values are typical and should be set in the project BEP.
The earlier a spatial problem is found, the less it costs to fix. For UK higher-risk buildings this is now a regulatory point as well: Gateway 2 expects a complete, fully coordinated technical design before construction, with later changes going through formal change control (PowerOn). Uncoordinated design that reaches site turns into rework, which we have analysed in MEP rework costs and what happens when you don't coordinate.
What are combined services drawings and builder's work openings?
Combined services drawings (CSDs) show all building services on one drawing, at a scale where the relationship between them can be read: plans of ceiling voids and plant rooms, with sections through the tightest zones showing levels, sizes and clearances. At design stage they are how a consultant demonstrates coordination to the architect, the client's team and later the contractor, and in many UK and Irish projects they are a named deliverable.
Builder's work in connection (BWIC) covers the openings, sleeves, plinths and supports that other trades must provide for the services. We generate opening locations and sizes from the coordinated model and issue them as a schedule and marked-up drawings, so the structural engineer and architect can include them before their own drawings are frozen. Late openings through post-tensioned slabs or fire-rated cores are one of the costliest coordination failures; see when BIM coordination fails.
What do we need from you to start?
Current discipline models in Revit (or IFC), the latest architectural and structural models, your BEP or office standards, the stage and issue date, and any agreed service zones. If the models are incomplete we report the gaps on day one. We work in your Autodesk Construction Cloud or BIM 360 hub where you prefer, and data handling is described on our trust and security page.
For whole-building design-stage coordination, see building services BIM coordination; for our general coordination service, see MEP BIM coordination; and for plant-dense projects, see data centre MEP BIM coordination. Offshore clash work often fails by "treating engineering as drafting" (MVN); our coordinators read the engineering before they move a pipe.
How does the fixed-price pilot work?
The best test of a clash detection partner is a real zone of your project. The pilot is a paid, fixed-price package on one floor or one plant room.
- One floor or one plant roomyour models, your template
- About 10 working daysfrom complete inputs to coordinated model
- Fixed quote in 48 hoursagreed before any work starts
You receive the federated model, a triaged clash report with proposed resolutions, the coordinated services in your template and a combined services drawing for the zone. Compare it with your own process before committing to more.
Request a pilot quoteFrequently asked questions
What is MEP clash detection?
MEP clash detection is the process of combining building services models with the architectural and structural models in software such as Navisworks to find physical intersections and breaches of required clearance, so they can be resolved before construction.
What is the difference between a hard clash and a soft clash?
A hard clash is a physical intersection between two elements. A soft or clearance clash is an intrusion into space that must stay free, such as insulation, maintenance access or equipment withdrawal space, even when nothing physically touches.
Do you only report clashes, or resolve them too?
We do both. Every issue gets a proposed resolution, an owner and a status, and we remodel the services in our scope once your engineers agree the resolution.
What are combined services drawings?
Combined services drawings show all building services together on plans and sections of ceiling voids, risers and plant rooms, so that levels, sizes and clearances can be checked and agreed by the design team and the contractor.
Can you deliver clash issues in BCF or Autodesk Construction Cloud?
Yes. Issues can be exported in BCF with saved viewpoints, or raised directly as issues in your Autodesk Construction Cloud or BIM 360 project.
How long does clash detection take for one floor?
A single floor of a commercial building usually takes 5 to 10 working days for full clash detection and resolution, depending on the number of systems and the quality of incoming models.
Sources
- PowerOn – Gateway 2 requirements for M&E professionals explained, accessed October 2026.
- MVN Services – Why offshore MEP design outsourcing fails, accessed October 2026.