Accurate, Trade-Ready MEP Coordination Using
Revit and Navisworks, From Design Review to
Construction Release
Most site delays and rework claims trace back to a single point: MEP systems that were never properly coordinated before construction began. When ductwork, conduit runs, and pipework are designed in separate models and not brought together until site, clashes turn into cutting, re-routing, and re-ordering on a live construction programme with every trade watching. MEP BIM Coordination using Autodesk Revit and Navisworks eliminates this by resolving every conflict in the digital model first. Each trade knows exactly where their systems go, what clearances they have, and where sleeve openings are located before the first component is ordered or installed. At Bimacme, we manage coordination from model intake through to signed construction release. Every zone is cleared, every clash is logged and resolved, and the handover model reflects what can actually be built.
Clash Discovered on Site.
Identified and resolved in the model weeks before installation
Trades waiting on RFI responses
Coordination meetings resolve design conflicts before they reach the site team
Rework delays affecting the programme
Construction release issued only when the zone is fully clash-free
Our coordination scope covers every trade discipline from individual model build-out through to federated model assembly, clash testing, and construction release.
We link all trade models architectural, structural, and MEP into a single coordinated Revit and Navisworks environment aligned to a common coordinate system and agreed naming protocol.
Systematic clash testing across all discipline pairs using project-defined tolerances. Hard clashes, clearance conflicts, and access route obstructions are all tested and tracked to resolution.
Every identified clash is logged, assigned to the responsible trade, and tracked through each coordination round. No issue is closed without model confirmation and trade sign-off.
Sleeve locations and structural penetrations are coordinated and documented before structural work begins, eliminating the need for reactive core drilling or blocked openings on site.
When coordination surfaces a design conflict or an under-specified area, we raise a structured RFI with model references and markup, ready for the design team to respond.
Coordinated zones are issued for construction with a full package: signed-off federated model, coordination drawings, clash resolution log, and a zone-by-zone construction release record.
Our coordination workflow follows a fixed sequence on every project. Each step has a clear output that feeds directly into the next, so there are no handoff gaps and no coordination rounds that have to be repeated because earlier steps were skipped.
We receive Revit files, IFC exports, or CAD drawings from all trades. Each file is reviewed for coordinate alignment, naming conventions, and BEP compliance before coordination begins.
We run targeted clash tests between each discipline pair using project-specific tolerances, not software defaults. Hard clashes, soft clearance clashes, and workflow conflicts are all tested separately.
Each trade receives a clear, itemised clash report showing location, affected disciplines, severity, and a recommended resolution path. Reports are issued in a format your team can act on immediately.
We facilitate structured weekly coordination meetings with trade representatives. Each session works through the active clash matrix, confirms resolutions, and updates model responsibilities.
Updated trade models are re-federated and re-tested after each round. Resolved clashes are closed with confirmation from the responsible trade before moving to the next zone.
Each coordinated zone is formally signed off by the project lead and trade contractors. Construction release documentation is issued with the cleared model and a full clash resolution log.
LOD Level | What Is Modelled | Stage of Use | Primary Purpose |
LOD 200 | Approximate routing, system zones, placeholder equipment | Concept / RIBA Stage 2 | Spatial planning and system feasibility checks |
LOD 300 | Exact geometry, confirmed pipe and duct routing, connection points | Design Development / RIBA Stage 3 | Design-stage clash detection between disciplines |
LOD 350 | Support structures, hanger positions, sleeve openings, service zones | Pre-Construction / RIBA Stage 4 | Construction-level trade coordination and site release |
LOD 400 | Fabrication data, manufacturer specifications, spool geometry | Construction / Fabrication | Shop drawings, prefabrication, and subcontractor coordination |
LOD 500 | Verified as-installed positions and field-measured geometry | Post-Construction / RIBA Stage 6 | Handover model for FM, O&M, and asset management |
We have delivered coordinated MEP models across commercial, residential, healthcare, education, and infrastructure projects in the UK and internationally
Technical Depth Our team includes Revit MEP modellers, BIM coordinators, and MEP engineers working together on every project. We do not outsource coordination checking or run generic Navisworks tolerances every project gets a coordination protocol built to its specific geometry, programme, and trade mix.
Process Discipline We run coordination to a fixed process with documented outputs at each stage. You always know what has been checked, what has been resolved, and what is outstanding. Our clash matrices are live documents, not snapshots they update through every coordination round until the zone is signed off.
We understand that coordination has a schedule consequence. Our weekly meeting cadence, structured RFI process, and zone-by-zone construction release approach are designed to keep your programme moving rather than creating a coordination bottleneck between design and site.
Tell us about your project and we will come back with a coordination scope and timeline within 48 hours.
MEP BIM Coordination is the process of assembling individual mechanical, electrical, plumbing, and fire protection models into a single federated environment, running systematic clash detection, and resolving all conflicts before construction begins. It ensures every system has a defined, unobstructed path through the building.
MEP BIM Coordination should ideally begin at RIBA Stage 4, once design intent is confirmed and trade contractors are on board. Starting too early produces clash reports that quickly become outdated, while starting too late risks carrying unresolved conflicts into site.
We work in Autodesk Revit for trade modelling and federated model assembly, and Navisworks Manage for clash detection and coordination reporting. For project collaboration and model sharing, we support Autodesk Construction Cloud and BIM 360. We adapt to project-specific BIM Execution Plan requirements.
LOD 300 confirms geometry and routing for design-phase checking. LOD 350 adds support structures, hanger positions, and sleeve locations the details trades need on site. LOD 350 is the minimum standard for construction release.
Every identified clash is logged in a structured clash matrix with its location, the disciplines involved, severity classification, and the assigned trade responsible for resolution. Clashes are tracked through each coordination round. A clash is not closed until the updated model confirms the resolution and the responsible trade has signed off.
Yes. When coordination has stalled or was not set up at the start of a project, we step in by first documenting what has already been installed through as-built drawings or a site survey then coordinating the remaining scope against verified existing conditions. This is a common engagement for phased projects and renovation works.
At project completion you receive a coordinated federated model, a final clash-free Navisworks file, zone-by-zone coordination drawings, a sleeve and penetration schedule, a full clash resolution log, and a signed construction release document for each coordinated zone.
Fixing a clash in the model costs far less than cutting and re-routing installed systems on site. Unresolved coordination also drives up RFI volumes, slowing the design team and delaying downstream trades.
