BIM coordination exists to find problems on screen instead of on site. When ducts, pipes, cable trays and structure all compete for the same ceiling void, a coordinated model is the cheapest place to resolve it. This guide explains what good coordination looks like, so you can judge a partner and set expectations with your team.
What BIM coordination is
Coordination brings the architectural, structural and MEP models together into one federated model, checks them against each other, and resolves conflicts before drawings are issued. It is a process, not a single clash report: models are updated, re-checked and signed off in cycles until each zone is clear.
Level of development (LOD), in plain terms
| LOD | What the model shows | Typical use |
|---|---|---|
| 200 | Approximate size, shape and location | Design development, early coordination |
| 300 | Specific size, shape and location | Construction documents, design coordination |
| 350 | Adds interfaces and connections to other systems | Trade coordination |
| 400 | Fabrication-level detail | Shop drawings, fabrication and installation |
Agree the LOD for each discipline and stage in the BIM execution plan. Many disputes come from one party modelling at LOD 300 while another expects LOD 400.
The three kinds of clash
- Hard clashes. Two elements occupy the same space, such as a duct running through a beam.
- Soft (clearance) clashes. Elements do not touch but break a required clearance, such as access space around equipment or insulation thickness.
- Workflow (4D) clashes. Sequencing conflicts, where elements cannot be installed in the planned order.
Good clash tests are set up by discipline pair and by zone, with tolerances agreed in advance, so the report shows real problems instead of thousands of duplicates.
A typical coordination workflow
- BIM execution plan. Roles, LOD, file naming, coordinates and exchange schedule, aligned with ISO 19650 where the project requires it.
- Model set-up. Shared coordinates, levels and grids, and agreed Revit templates and families.
- Federation. Discipline models combined in Navisworks or a cloud platform such as Autodesk Construction Cloud.
- Clash runs. Tests by discipline pair and zone, with results grouped and assigned.
- Issue tracking. Each issue logged with a screenshot, location, owner and due date, often exchanged as BCF.
- Coordination meetings. Weekly reviews to agree fixes and priorities.
- Sign-off. Zones signed off as clash-free before drawings are issued.
Deliverables to ask for
- Federated, coordinated models by discipline
- Clash reports with grouped, assigned issues and status
- Coordinated plans, sections and services drawings produced from the model
- Builders’ work and penetration drawings
- Quantity takeoffs from the model, where needed
- Rendered stills or walkthroughs for client and marketing use
Choosing a BIM partner
Ask to see a real clash report and an issue log from a past project. Check that the team works in your Revit version and templates, can join your coordination meetings in your time zone, and has a clear QA step before models are shared. A short pilot on one floor or zone is the fastest way to see how they work.
A clash found in the model costs minutes. The same clash found on site costs days.
Proworks provides architectural and MEP BIM, clash detection and rendering from one coordinated team. Talk to us about a BIM project.