If you've ever walked onto a job site and found a ductwork run clashing with a structural beam, or a sprinkler line running straight through a ceiling grid that was already installed, you already know why coordination matters. BIM coordination is the process of bringing together the 3D models from every discipline — architecture, structure, mechanical, electrical, plumbing, and fire protection — into one combined federated model, and then systematically checking that model for clashes, spatial conflicts, and constructability issues before anything gets built.

In practical terms, coordination means your architect's model, your structural engineer's model, and your MEP contractor's model all get overlaid in a tool like Navisworks. From there, a coordinator runs clash detection to flag every point where a duct hits a beam, a pipe crosses a cable tray, or equipment doesn't have enough clearance for maintenance access. Each clash gets reviewed, assigned to the right discipline, and resolved in the model — not on-site, not after fabrication, not after the concrete has already been poured.

Why does this matter so much on real projects? Because rework is expensive and slow. A clash caught in the model costs a few minutes to fix. The same clash caught on-site after ductwork is hung and pipework is installed can mean days of delay, wasted material, and a very uncomfortable conversation with the client. Coordination shifts that cost from the construction phase, where it's expensive, back to the design phase, where it's cheap.

What actually happens during a coordination process

A typical coordination cycle looks like this:

1. Each discipline delivers their model at an agreed Level of Development (LOD), usually LOD 300 or 350 for coordination purposes.
2. Models are federated into a single combined model.
3. Clash detection rules are set up — hard clashes (physical overlap), soft clashes (clearance violations), and workflow clashes (sequencing conflicts).
4. Clash reports are generated and distributed to the relevant discipline leads.
5. A coordination meeting is held, usually weekly, where the design team walks through open clashes and agrees on resolutions.
6. Models are updated, re-federated, and re-checked until the clash count trends to zero for that milestone.

This cycle repeats at every major design stage — schematic design, design development, and construction documentation — with the level of detail and the strictness of clash rules increasing each time.

Where coordination fits into ISO 19650

If your project follows ISO 19650, coordination isn't a one-off task tacked onto the end of design — it's built into the Common Data Environment (CDE) workflow itself. Models move through the WIP, Shared, Published, and Archive states, and coordination happens formally at the "Shared" stage, where disciplines review each other's work before anything is signed off. This is worth reading up on directly from buildingSMART International if you want the full standard: https://www.buildingsmart.org/standards/bsi-standards/iso-19650/

The benefits, in plain terms

• Fewer surprises on-site. Most clashes that would normally show up during construction get caught and resolved during design.
• Lower rework costs. Fixing a duct routing issue in Revit takes minutes; fixing it after installation takes days and materials.
• Better coordination between subcontractors. Everyone is working off the same federated model, so there's no ambiguity about who owns what space.
• Faster approvals. Clash-free models move through client and consultant review much faster than models still full of unresolved conflicts.
• Accurate documentation. Coordinated models produce coordinated drawings, so what's on paper actually matches what gets built.
• Better use of ceiling and shaft space. Coordination isn't just about avoiding clashes — it's about routing services efficiently in tight risers, bulkheads, and plant rooms.

Where BIM365 fits in

At BIM365, MEP coordination is a core part of what we do for architecture and engineering firms across Australia, the US, UK, and the Gulf. We take mechanical, electrical, plumbing, and fire protection models through structured clash detection cycles in Navisworks, produce clean clash reports mapped to each discipline, and hand back resolved, coordinated models your team can build from with confidence. If you're weighing up whether to bring coordination in-house or outsource it, our MEP 3D Revit modelling service page walks through how the process works end to end: https://bim365.in/services/mep-bim-modelling and our clash detection service page covers the specifics of how we structure clash reports and turnaround: https://bim365.in/services/clash-detection

We've also written more on related topics if you want to go deeper — our piece on scan-to-BIM workflows (https://bim365.in/blog/scan-to-bim) is a natural companion read if your coordination work involves existing buildings, and our ISO 19650 breakdown (https://bim365.in/blog/iso-19650-explained) is useful if you're setting up a CDE workflow for the first time.

What software is used for BIM coordination?
Navisworks is the industry standard for federating models and running clash detection, though Solibri and BIM Collab are also used depending on the project and region. Individual discipline models are usually authored in Revit, then brought into the coordination platform for checking.

What's the difference between clash detection and coordination?
Clash detection is one step within coordination — it's the automated process of finding overlaps between models. Coordination is the broader process that includes clash detection, but also covers meetings, resolution tracking, sequencing checks, and re-issuing updated models until the design is genuinely buildable.

At what stage of a project should coordination start?
As early as possible — ideally from design development onward, once disciplines have models detailed enough to check meaningfully (typically LOD 300). Starting too late means major structural or layout changes become far more disruptive to fix.

Who is responsible for running coordination on a project?
This varies by contract, but it's commonly led by a BIM Manager, BIM Coordinator, or an outsourced BIM coordination provider, working with input from every discipline lead. On design-build or IPD projects it's sometimes led by the contractor.

How often should coordination meetings happen?
Weekly is standard on active projects, though this can shift to fortnightly during quieter design phases or ramp up to twice-weekly as construction documentation deadlines approach.

Can coordination be outsourced?
Yes — many architecture and engineering firms outsource MEP coordination to specialist BIM providers rather than building an in-house team, particularly for projects with tight deadlines or fluctuating workload. This is exactly the kind of work BIM365 handles for firms across Australia, the US, UK, and the Gulf.

Getting coordination right is less about the software and more about discipline — sticking to the review cycle, resolving clashes properly instead of just closing them out, and keeping every model at the LOD the project actually needs at each stage. Firms that treat coordination as a scheduled, recurring process (not a one-time check before issue) consistently ship projects with fewer site delays and cleaner as-built documentation.

If MEP coordination is eating into your team's bandwidth, or you're finding clashes later than you'd like, it might be worth having a conversation about how outsourced coordination could fit into your workflow: https://bim365.in/contact