BIM Coordination: A Practical Guide for AEC Teams

BIM coordination is the process of aligning models from different disciplines—architecture, structure, MEP, civil—so that a building can actually be built without surprises. Done well, it catches clashes before they hit the field. Done poorly, it becomes a weekly meeting where everyone argues about whose duct is in whose beam.

This guide covers what BIM coordination actually involves, how the workflow runs in practice, common tools, and the mistakes that sink coordination efforts on real projects.

What BIM Coordination Actually Means

BIM coordination is not the same as BIM modeling. Modeling is building the 3D representation of a discipline's scope. Coordination is the cross-discipline process of:

Aggregating models from multiple trades into a shared federated model
Running clash detection between systems (structural steel vs. ductwork, piping vs. cable tray, etc.)
Resolving conflicts through discussion and model updates
Tracking issues to closure with accountability assigned to specific teams
Validating that the coordinated model matches design intent and constructability requirements

The goal isn't a pretty federated model. It's a buildable set of documents and models that reduce RFIs, rework, and field conflicts.

Why Coordination Fails Without a Process

Throwing models into a viewer and generating a clash report is not coordination. That's clash detection, which is one small piece of the puzzle. Real coordination requires:

Agreed-upon standards before modeling starts (origin points, units, LOD/LOI expectations)
A defined coordination cadence (weekly clash reviews, milestone coordination freezes)
Clear ownership of each clash or issue
A closed-loop tracking system so resolved issues don't reappear in the next model upload

Skip any of these and you get clash reports with thousands of entries, half of which are false positives from unaligned coordinate systems, and no one knows who's responsible for fixing what.

The Standard BIM Coordination Workflow

1. Establish the BIM Execution Plan (BEP)

Before any coordination begins, the project needs a BIM Execution Plan that defines:

Model origin and shared coordinates
File naming conventions
Level of Development (LOD) requirements per phase
Software platforms and file formats for exchange
Coordination meeting frequency and issue resolution SLAs
Roles: who's the BIM coordinator, who's the discipline model owner

Without this document, every discipline models to their own assumptions, and you'll spend the first coordination cycle just fixing coordinate misalignment instead of resolving actual clashes.

2. Model Aggregation

Each discipline exports or links their native model (Revit, Civil 3D, Tekla, etc.) into a common coordination environment. This is typically done through:

Direct federation in Revit (linked models)
Neutral format aggregation using formats like IFC, NWC, or NWD
Cloud-based model aggregation platforms that ingest multiple formats

Federation should happen on a fixed schedule—weekly is common—so every team knows when their model needs to be current.

3. Clash Detection

Clash detection tools compare geometry across linked models and flag intersections. There are generally three clash types worth distinguishing:

Hard clashes: physical geometry actually intersects (a pipe running through a beam)
Soft clashes (clearance clashes): objects violate a required clearance zone (insulation, access space, maintenance clearance)
Workflow/4D clashes: no geometric overlap, but sequencing conflicts (a wall scheduled to close before ductwork installation in that cavity is complete)

Most teams only chase hard clashes initially, then get burned in the field by clearance violations that never showed up as geometric intersections.

4. Issue Tracking and Resolution

Every clash needs to become a tracked issue with:

A responsible party
A due date
A resolution status
A link back to the model elements involved

Tools like BIM 360/Autodesk Construction Cloud, Navisworks, Solibri, and BIMcollab handle this differently—verify current issue-tracking features in each platform's documentation since these evolve across releases.

5. Model Update and Re-Coordination

Once a discipline resolves an issue in their native model, they re-export or re-link into the federated model, and the cycle repeats. This is where discipline matters: teams that update inconsistently create false confidence—everyone thinks a clash is resolved when the fix never made it into the coordinated set.

Clash Detection Tools: A Comparison

| Tool | Primary Use | Strength | Limitation | |---|---|---|---| | Navisworks | Clash detection, 4D simulation | Deep Revit/AutoCAD integration, mature clash rule sets | Desktop-based, less collaborative by default | | Solibri | Model checking, rule-based validation | Strong on QA/QC and standards compliance, not just geometry | Steeper learning curve for rule authoring | | BIMcollab | Issue tracking, BCF-based collaboration | Vendor-neutral issue exchange via BCF | Relies on other tools for actual clash geometry detection | | Autodesk Construction Cloud / BIM 360 | Cloud coordination, issue management | Centralized, accessible from field and office | Feature sets and naming change across releases—check current documentation |

Verify current feature sets and platform names directly with each vendor, since cloud products in this space get renamed and re-scoped often.

LOD, LOI, and Why They Matter for Coordination

Coordination only works if models are built to a consistent level of detail. A structural model at LOD 200 (generalized systems) can't be meaningfully clash-checked against an MEP model at LOD 400 (fabrication-level detail)—the geometry granularity doesn't match, and you'll either miss real clashes or drown in false ones.

Practical guidance:

Align LOD expectations per discipline per project phase, not just once for the whole project
Fabrication-level coordination (LOD 400) should happen close to construction, not at schematic design
Document LOD requirements in the BEP and audit models against them before each coordination cycle—don't just trust that everyone complied

Common Coordination Problems (and Fixes)

Problem: Coordinate System Misalignment

Models come in offset or rotated because disciplines set up their own project base points. Fix this at the BEP stage by mandating a shared coordinate system tied to survey control, and verify it before the first federation, not after clash detection returns 4,000 false positives.

Problem: Clash Report Overload

Running a single clash test across every discipline pair produces reports too large to act on. Instead, run targeted clash tests: structure vs. MEP, MEP vs. MEP, architecture vs. structure. Filter by zone or level to keep review sessions manageable.

Problem: Issues Resolved in One Model, Not Reflected in Others

A duct gets moved, but the ceiling model isn't updated to reflect the new access panel location. This happens when coordination is treated as clash-fixing rather than design coordination. Every geometry change should trigger a check of adjacent systems, not just the flagged clash.

Problem: Coordination Meetings Without Model Updates

Teams review the same clash report meeting after meeting because no one actually updated their model between sessions. Enforce a hard cutoff: models not updated by the deadline get flagged, and unresolved clashes carry consequences (schedule impact, RFI generation).

Problem: No Distinction Between Design Coordination and Field Coordination

Design-phase coordination focuses on system routing and major conflicts. Field/construction coordination needs fabrication-level accuracy—actual duct gauge, real fitting geometry, actual hanger locations. Trying to do field-level coordination during design development wastes effort on details that will change anyway.

4D and 5D Coordination

Beyond spatial clash detection, mature coordination programs incorporate:

4D (schedule): linking model elements to construction sequence to catch scheduling conflicts, like structural steel installation conflicting with concrete curing zones
5D (cost): tying coordinated models to cost estimates so design changes during coordination show real cost impact immediately

These require more setup than basic clash detection and are usually reserved for larger or more complex projects where the coordination overhead pays off. Confirm what your specific software stack supports for 4D/5D workflows in current documentation, since capabilities vary significantly by platform and version.

Roles in a Coordination Program

BIM Coordinator: manages the federation process, runs clash detection, facilitates meetings, tracks issues
Discipline Model Owners: responsible for their model's accuracy and timely updates
BIM Manager/VDC Manager: oversees standards, BEP compliance, and escalates unresolved conflicts
General Contractor's VDC team: often owns the overall coordination process on design-build or CM-at-risk projects, aggregating subcontractor models

On smaller projects, one person may wear several of these hats. On larger ones, unclear role boundaries are a common source of coordination breakdowns—someone needs explicit authority to say "this issue isn't resolved, resubmit."

Practical Checklist for Starting Coordination on a New Project

Confirm shared coordinate system and verify it across all disciplines before first federation
Define LOD/LOI requirements per phase in the BEP
Set a fixed weekly (or biweekly) coordination cadence
Choose a clash detection and issue-tracking toolchain everyone can access
Run a baseline clash test early, even on incomplete models, to catch coordinate and scale errors immediately
Assign clear ownership for every open issue with due dates
Require model updates before each coordination session, not during it
Escalate unresolved clashes past their due date to project leadership

Final Note

BIM coordination succeeds or fails based on process discipline, not software sophistication. The best clash detection tool won't fix a project where teams don't update models on schedule or where no one owns issue resolution. Set the process up front, hold teams accountable to it, and treat the federated model as a living coordination tool rather than a report generated for a meeting.

Software features, supported file formats, and cloud platform capabilities referenced above change across releases—always check current vendor documentation before finalizing your coordination toolchain for a project.