BIM Coordination Best Practices

BIM coordination is where the theoretical value of building information modeling becomes real project delivery. A well-coordinated federated model catches conflicts before construction, compresses the RFI cycle and keeps the project programme intact. A poorly run coordination process, even on a technically capable BIM project, produces the same problems as a 2D drawing-based coordination approach: conflicts discovered late, expensive variations and strained consultant relationships.

The difference between the two outcomes is almost entirely process, not software. Here are the practices that consistently separate effective BIM coordination from the kind that exists only on paper.

Establish a shared coordinate system from day one

Every discipline model must be set up on the same survey point and project base point before any work begins. This sounds obvious but is violated regularly — especially when models are started before a formal pre-design coordination meeting. A model whose origin is at a different location than the others will not federate correctly, and realigning it after weeks of production is a costly exercise. Mandate a single coordinate setup file issued by the architect, to which every consultant's model is linked before they begin modelling.

Define the model ownership matrix

Every building element in a federated model should have one and only one owner — the discipline responsible for modelling it and for maintaining it through revisions. Walls owned by architecture, slabs owned by structure, ductwork owned by MEP. When ownership is ambiguous, elements get modelled twice or not at all, and revision coordination breaks down because nobody knows which model is authoritative. A model ownership matrix, agreed before design development begins, prevents these problems entirely.

Set clash detection rules that match your project stage

Running every possible clash against every element produces thousands of false positives that make the report meaningless and the meeting unproductive. Effective clash detection is selective: at schematic design, check major discipline routing conflicts only. At design development, add hard clashes between structure and MEP. At construction documents, add soft clashes for clearance and maintenance access. The rules evolve with the project, and the person managing the Navisworks or BIM 360 model needs to understand why each rule is set, not just how to run it.

Assign every clash a status and an owner immediately

A clash report is not useful if the clashes are unassigned. Every issue from a clash detection run should be assigned within 48 hours of the review meeting to the discipline responsible for resolving it, with a target resolution date. Using the issue tracking in BIM 360 or an equivalent platform to track status from open through in-progress to resolved means that the next coordination review begins with confirmed closures rather than a repeat of last week's unresolved list.

Run coordination meetings on the model, not the report

Reading through a PDF clash report in a meeting is a remarkably inefficient way to coordinate. Every participant should be looking at the federated model in Navisworks or BIM 360 during the meeting, navigating to each issue in three dimensions and making resolution decisions based on what they can see. Discipline leads who attend coordination meetings without the ability to navigate the model add no value; they need to either develop that capability or delegate to someone who has it.

Issue resolved models on a fixed cycle

Coordination only works if models are current. A coordination review conducted against a model that is several weeks old produces resolutions that do not reflect actual design development and creates a second round of clashes when updated models are issued. Establish a fixed model update cycle — weekly or fortnightly during active coordination phases — and enforce it contractually if necessary. Disciplines that consistently issue outdated models delay the project for everyone else.

The standard that separates good coordination from nominal coordination

Effective BIM coordination produces a documented clash-free federated model before construction starts. Nominal BIM coordination produces a series of meetings with a shrinking clash count that still has unresolved items when the contractor begins work. The difference is enforceability: a process with clear ownership, fixed cycles, tracked issues and contractual model submission requirements produces the first outcome. A process that depends on voluntary compliance by consultants who are managing their own time pressures tends to produce the second.