BIM Coordination: 7 Powerful Steps for Smoother Projects

BIM coordination is the managed process of getting every discipline’s model to work as one buildable whole. It runs in seven steps: set the rules in a BIM Execution Plan, take in and audit each discipline’s model, federate them in a shared coordinate environment, run clash detection, resolve conflicts in a structured coordination meeting, update and re-test, then sign off and hand over a coordinated model. Steps four to six repeat on a weekly cycle until the model is constructable. Clash detection is one step inside that process, not a substitute for it — and on projects in Abu Dhabi and Dubai, coordination quality is now a submission requirement rather than an internal quality measure.

What Is BIM Coordination?

BIM coordination is the process of bringing the architectural, structural, mechanical, electrical, plumbing and fire protection models together into a single federated model, finding where they conflict, and managing those conflicts through to resolution — with named owners, agreed decisions and a documented record.

The word that matters is managed. Coordination is not a piece of software and it is not a report. It is a cycle of intake, testing, decision and re-issue that runs on a fixed rhythm from design development through to the point where the model is constructable and signed off.

Done well, it replaces the default alternative: discovering the same conflicts on site, in front of a foreman, with two trades already fabricated to different assumptions.

Coordination vs Clash Detection

These two get used interchangeably, and the confusion causes real damage — because a team that runs a clash report and calls it coordination has done a fraction of the work and believes it has finished.

A worked example makes the difference concrete. Clash detection reports that a duct passes through a beam. Coordination decides whether the duct reroutes or the beam gets a penetration, who is responsible for the change, whether the reroute still clears the ceiling height, whether the new route conflicts with anything else, and whether the result can actually be installed in sequence.

The blunt version: a model with fewer clashes is not the same as a coordinated project. If someone says the project has been coordinated but all that happened was a clash report, half the work is missing.

This guide covers the full coordination scope. For the technical step in detail — the three clash types, the discipline test matrix, tolerance settings and false-positive control — see our dedicated guide to BIM clash detection.

The Seven-Step Coordination Process

Each step has an exit criterion. Moving to the next step without meeting it is where coordination programmes lose weeks.

Steps 4 to 6 are the cycle. On an active project they repeat weekly, and the health of the project is visible in how the numbers move between cycles rather than in any single report.

Model Intake: The Quality Audit Checklist

The most under-documented step in the whole process, and the one with the highest return. A bad intake audit early wastes entire clash cycles later, because the team spends the week resolving issues caused by a model that should never have been accepted.

Run this on every model, every submission:

1. Shared origin and coordinate system match the project base point defined in the BEP.
2. Units and project north are correct and consistent with the other disciplines.
3. File naming follows the agreed convention, with the correct status code.
4. Level names and elevations match the agreed level datum schedule exactly — not approximately.
5. Grid matches the structural grid in name and position.
6. Level of development matches what the milestone requires for the elements concerned.
7. Systems and elements are correctly classified and named, so tests can target real system pairs.
8. Worksets or model organisation follow the agreed structure.
9. No unplaced, duplicated or orphaned elements, and no leftover elements from linked or copied files.
10. Model file size and performance are within workable limits; a model that will not open is not a submission.
11. Warnings and errors reviewed, with anything significant reported rather than ignored.
12. Export test passed — where an IFC or other exchange format is required, the export produces correct geometry and classification.

Federation and Shared Coordinates

Federation is combining the discipline models into one environment for testing and review, without merging them — each model stays owned and edited by its own team.

Three things decide whether federation works:

• A single agreed origin. Every discipline model positioned against the same project base point and survey point. A misaligned origin is the single most common cause of a first federation where everything clashes with everything.
• A consistent level and grid structure so that “Level 3” means the same elevation in every model and grid line C is in the same place.
• A defined federation strategy in the BEP: which models federate together, at what frequency, and who owns the federated file.

Where the project’s information is managed — the status codes, the submission day, the revision control — is the common data environment, and the rules governing all of it belong in the BIM Execution Plan.

The Coordination Meeting: An Actual Agenda

Every guide says “hold weekly coordination meetings”. Almost none of them say what happens in one. Here is a workable structure.

Who attends

The BIM coordinator chairs. Each discipline sends someone who can make a decision, not someone who will take it back to the office. The contractor’s site or installation representative attends where the project is in construction, because buildability questions get answered in the room instead of becoming another cycle. The project manager attends to escalate what cannot be decided.

The agenda

What gets recorded

Every decision, with the issue reference, the decision taken, the named owner, the due date, and any consequential impact on another discipline. Recorded in the CDE against the issue — not in meeting minutes that live in an inbox.

Movement Hierarchy and Ownership Rules

When two systems want the same space, one moves. Deciding which one in the room, every time, is what turns a coordination meeting into a negotiation. Setting the hierarchy in the BEP is what turns it back into a process.

Alongside the hierarchy, three ownership rules prevent the most common stalls:

• Every issue has one named owner, not a discipline. A discipline cannot be chased; a person can.
• The owner is whoever must change their model, determined by the hierarchy — not whoever raised the issue.
• Escalation has a deadline. An issue that cannot be resolved in two cycles goes to the project manager automatically, rather than remaining open indefinitely because nobody wants to raise it.

For the full discipline-by-discipline routing logic, see our guide to MEP plans in construction.

The Weekly Cycle and When to Stop

The cycle has a fixed shape: models submitted on the agreed day, tests run, results classified and circulated, meeting held, decisions recorded, models updated, repeat.

The question nobody answers is when coordination is finished. Total clash count is a poor measure — a model with fifty clashes might be nearly coordinated or barely modelled. Four indicators say more:

Coordination is converging when closure rate is high and new issues per cycle is falling. If total count drops but new issues stay high, the project is trading one set of conflicts for another rather than closing them.

What Gulf Authorities Require

This is where regional practice diverges most sharply from international guidance, and it changes the status of coordination entirely.

Abu Dhabi

Abu Dhabi Municipality publishes CAD and BIM submission requirements covering naming conventions, coordinate systems and file formats, with compliance requirements referencing ISO 19650. Separately, a model quality document addresses naming standards, model coordination and clash detection protocols, intended to standardise the quality and health of submitted models.

Read that again, because the implication is significant: model coordination and clash detection are named in a submission requirement. Coordination in Abu Dhabi is not an internal quality measure a contractor may choose to invest in. It is part of what determines whether the deliverable is accepted.

Dubai

Dubai Municipality has required the use of BIM on defined categories of project since 2013, expanded by a further circular in 2015. A circular issued in October 2023 introduced BIM model submission for new building permits with IFC as the format, taking effect from the start of 2024, and the authority has publicly aligned with open standards including ISO 19650, IFC, IDS and BCF.

When the model is the submission, federation discipline and export quality become permit issues. A model that coordinates perfectly in its authoring tool but exports to IFC with broken geometry or missing classification will fail regardless of how well it was coordinated internally.

Saudi Arabia

BIM requirements in the Kingdom are predominantly driven by client and programme, with large developers and giga-project programmes specifying BIM deliverables, information requirements and BIM Execution Plans contractually. The Saudi Building Code governs the technical content of what is designed and submitted.

The plenum problem

There is also a physical reason coordination takes longer here. Buildings in Saudi Arabia and the UAE carry cooling loads that temperate-climate buildings do not, which means larger ducts, larger chilled water pipework and more terminal units competing for the same ceiling void as containment, sprinkler mains and drainage falls. Coordination programmes built on temperate-climate benchmarks under-allocate time to the plenum.

Coordinating Across Distributed Teams

A practical reality on most Gulf projects: the design team, the coordination team and the contractor are frequently in different countries. That is not a problem in itself, but it changes how the cycle has to be designed.

Working weeks do not align

Saudi Arabia works a Sunday to Thursday week. The UAE moved federal working to a Monday to Friday pattern in 2022, with private sector practice varying. Teams supporting from Europe, South Asia or North America work different weeks again. The overlap between any two of these can be as few as three or four common working days.

The implication is direct: a coordination cycle designed around a five-day week will not fit. Set the model submission day and the meeting day against the days all parties actually share, and publish them in the BEP so nobody negotiates them weekly.

Design the cycle for asynchronous work

• Circulate classified issues before the meeting, not during it. Attendees in a different time zone need to arrive prepared, not be walked through a report live.
• Record decisions in the CDE, not in the meeting. A decision that exists only in a conversation is invisible to the team that was asleep.
• Use BCF issues rather than screenshots. An issue that opens directly on the problem in the recipient’s authoring tool removes an entire round of clarification.
• Give every issue an unambiguous owner by name. Ambiguity that a co-located team resolves by walking across the office costs a distributed team a full cycle.

Sign-off and the Coordinated Model as a Deliverable

Coordination ends with a deliverable, not with a feeling that the model looks clean.

A defensible close includes:

• The federated coordinated model at the agreed revision, issued from the CDE with status applied.
• The closing clash report, showing what was tested, with what tolerances, and the disposition of every result including dismissals and their reasons.
• The issue log, showing every issue raised, its owner, its resolution and its closure date.
• Outstanding items, explicitly listed rather than quietly omitted, with an agreed position on each.
• Written sign-off from the parties named in the BEP.

The documentation produced downstream — construction drawings, shop drawings, penetration drawings, schedules — should be generated from the coordinated model rather than maintained separately, so drawings and model cannot diverge.

Who Pays for Coordination?

A question that surfaces on every project and appears in almost no guide.

The general position is that resolving conflicts arising from a party’s own design or modelling work sits within that party’s scope — coordination is what each discipline is appointed to participate in, not an extra. The difficulty is that conflicts rarely present that cleanly.

• Ordinary coordination between disciplines during design development is normally absorbed within scope. This is the job.
• Conflicts introduced by a design change may form part of that change rather than ordinary coordination, and should be raised at the time rather than absorbed silently.
• A design that cannot physically be built as issued — insufficient ceiling void being the classic case — is a design matter, not a coordination one, and belongs escalated as such rather than resolved quietly by the contractor’s coordinator.
• Repeated failures to meet the intake standard generate real cost for the coordination team, and a BEP that defines the intake gate gives that cost a documented basis.

Seven Coordination Failures

Frequently Asked Questions

Conclusion

Coordination is a process, and processes fail at their weakest step. On most projects that step is intake — a model accepted when it should have been returned, costing a full cycle of results nobody can use. On others it is the meeting, used to discover issues instead of decide them. On others it is the record, kept in minutes instead of the CDE, so that by month six nobody can prove what was agreed.

In Saudi Arabia and the UAE there are two further reasons to run it properly. Coordination and model quality now appear in authority submission requirements rather than only in internal quality plans. And the ceiling void in an air-conditioned Gulf tower carries more service volume in the same depth than almost anywhere else, so the coordination effort a temperate-climate benchmark predicts will not be enough. Set the rules before modelling starts, hold the intake gate, and close the phase with a signed record rather than a clean-looking model.