BIM Coordination Explained: Workflow, Responsibilities, Deliverables and Common Project Problems
BIM coordination is the process of combining architecture, structure and MEP models, finding conflicts, assigning owners, and issuing coordinated deliverables. This guide explains the workflow, roles and the problems that derail projects.
BIM coordination is the organised process of combining discipline models, finding spatial and information conflicts, assigning owners, and publishing a set that construction can trust more than a pile of uncoordinated 2D drawings. It is a management process that uses software, not a software process that replaces management. Architecture, structure and Mechanical, Electrical and Plumbing (MEP) can each be internally tidy and still be mutually impossible. Coordination is how a project discovers that before a ceiling is closed.
Coordination has three layers. Spatial coordination asks whether objects occupy the same space or violate a clearance. Information coordination asks whether names, levels, grid codes, system types and parameters match the BEP. Process coordination asks whether the right people look at the right issues on a cycle that matches the design programme. A team that only runs Navisworks once a month is doing a clash export, not coordination.
Federation is the technical act of bringing models into one review environment: Navisworks, Solibri, an IFC viewer, or a Revit host with links. A federated model is not automatically a coordinated model. It is the table on which coordination happens. If links sit on the wrong origin, the federation is fiction. Shared coordinates and a published origin are therefore coordination prerequisites, not advanced topics.
Coordination is also not “making everything fit by moving MEP.” Structure may need an opening. Architecture may need a ceiling change. A plant selection may be too large for the room the architect drew. The coordinator’s job is to make those choices explicit. A modeller’s job is to implement the choice that was instructed.
Roles and responsibilities
The BIM coordinator (sometimes called BIM manager on smaller jobs) owns the process: BEP maintenance, federation, clash tests, issue log, meeting agenda, and publish register. They may not author every discipline model. On a small job one person wears both hats; on a large job they should not.
Discipline leads own the correctness of their model against their drawings and specifications. The architectural lead decides wall types and ceiling heights. The structural lead decides member sizes and opening rules. The MEP lead decides system routes after a clash option is chosen. Outsourcing a discipline model does not outsource that lead’s duty unless the contract says so — and even then, statutory responsibility may not be transferable.
The client or project manager owns freeze dates and the authority to accept residual risk. If nobody can accept a residual clash, the log never closes. If freeze dates slip silently, the coordinator becomes a historian of last week’s geometry.
A specialist hired through BIMProSG should have a named role in the responsibility matrix. “Help with BIM” is not a role. “Run weekly federation and issue the clash log for zones A and B” is a role.
The weekly (or fortnightly) workflow
A durable workflow looks like this:
Discipline authors update models to a cut-off.
Files are named and placed per the BEP.
Coordinator federates and validates origins, levels and completeness.
Clash tests run against the agreed matrix and tolerances.
Results are grouped, duplicates removed, and issues assigned.
A meeting reviews new critical issues and overdue items, not the entire raw list.
Authors revise.
A published federated set is issued with a changelog.
Tools: Revit for authoring, Navisworks Manage or similar for clash and timeline views, BCF (BIM Collaboration Format) or an issue tracker for assignments, IFC when native files cannot be the common language. Spreadsheets still appear because many teams live in Excel; if you use Excel, lock the issue IDs.
The cut-off is sacred. A modeller who uploads a new plant room during the meeting invalidates the report. Write the cut-off in the BEP and in the marketplace milestone.
Clash matrix, tolerances and grouping
A clash matrix is a table of whose geometry is tested against whose, at what tolerance, and at which project stage. Architecture versus structure may be a hard clash of 15 mm. Duct versus beam may be 0 mm hard clash plus a separate clearance test. Pipe insulation versus cable tray may use a small tolerance so that grazing insulation is not treated like a 300 mm penetration. There is no universal tolerance; there is a documented one.
Grouping turns noise into work. Fifty clashes along one duct run through one beam line is one issue: “Level 4 grid C duct versus transfer beam — opening or reroute.” A coordinator who delivers 50 rows is transferring their unpaid sorting onto the meeting. When you hire, ask to see a grouped log.
Soft clashes need a definition: access zones, maintenance, code working space, and insulation. If you cannot define them, do not run them and then argue about the result. 4D clashes need a programme; without it they are theatre.
Deliverables of coordination
Typical deliverables:
Federated file (NWD/NWC or IFC federation) with a version date
Clash matrix and test settings
Issue log with ID, location, screenshot or viewpoint, owner, status, due date
Meeting minutes that record decisions, not only attendance
Residual clash list signed or accepted by the lead consultant
Publish register of model versions used in the federation
Optional: BCF files for issue exchange
Drawings are not automatically coordination deliverables, but a coordinated model that never appears on a drawing is only half useful. Shop drawings should be cut from the coordinated state; see BIM shop drawings.
Common project problems
Unshared coordinates. Models miss each other by a building length or by 200 mm. Always validate a known grid intersection in 3D at the start of every federation.
Architecture not room-bounding, structure not using real members, MEP as solids. Clash detection then reports junk or misses systems. Coordination cannot repair authoring category errors; it can only reject the file.
Too late. First clash run a week before tender. The correct first run is as soon as typical geometry exists: one floor, one plant room.
No owner for leftover clashes. The log becomes a museum. Residual risk must be accepted or funded as a design change.
Infinite revision without freeze. Coordination becomes a subscription to chaos. Use a revision rule in the commercial brief; see BIM costs.
Coordinator also being the only MEP modeller. Self-review fails under deadline. A second pair of eyes on a sample zone is cheap.
Issue tracker nobody opens. If the team lives in WhatsApp, the log will die. Pick a tool the leads will actually use, even if it is a well-kept spreadsheet.
IFC round-trip surprises. Geometry or parameters drop. If IFC is the federation language, test a sample early, especially for Singapore CORENET X related exports.
Point clouds used as decoration. Scan context without a modelling rule does not coordinate future work. See Scan to BIM.
Information coordination: names, levels and the boring failures
Spatial clashes get screenshots. Information failures get silence until a schedule or an IFC export breaks. Level names that differ by a trailing space, grids named 1 versus 01, rooms that do not match door numbers, and worksets that dump all MEP into “Workset1” are coordination defects. The coordinator should run a checklist on every drop: level list, grid list, file name, version, and a sample parameter (for example, every duct has a system type). This is unglamorous and more valuable than a new 3D viewpoint style.
ISO 19650 language — containers, information requirements, exchange events — maps onto this if the project uses it. If the project does not, still keep a publish register. Outsourcing does not remove the need for a register; the specialist can maintain it as a deliverable. A marketplace milestone that says “federation plus register” is easier to approve than “coordination vibes.”
Status on elements (for information, for coordination, for construction) should not be a colour that only one person understands. If you use Revit worksharing user names as a status system, you will regret it when a freelancer’s user name is the only clue that a riser is on hold.
Zone strategies for large buildings
Do not federate a 40-storey tower as a single weekly clash of everything. Split by floor bands, by podiums versus typical, by plant levels, by basement. Each zone can have a different maturity. Basement drainage may be ahead of typical-floor lighting. A coordinator who insists on one global percentage complete is usually hiding zone truth.
Grid-based zones help meetings. “Today we close Level 12, grids A–D” is a sentence a trade lead can prepare for. “Today we look at clashes” is not. When you post a project, name the first zone. Specialists can price a zone. They cannot honestly price an unnamed tower.
Handover between zones needs a rule for risers that pass through all of them. Vertical systems are the seams. Assign a vertical-systems owner so that Level 12 coordination cannot “solve” a clash by moving a stack that Level 3 already built.
Coordination on design jobs versus construction jobs
Design coordination proves that a scheme can exist. Construction coordination proves that the selected equipment, the shop drawings, and the install sequence can exist. The second is denser. Hangers, seismic bracing where required, and prefabrication spools appear. The same coordinator skill applies; the matrix and LOD change. Do not reuse a design clash matrix unchanged for installation models.
Trade-to-trade coordination among Mechanical, Electrical and Plumbing contractors needs a lead — often the main contractor’s BIM lead or the mechanical contractor if that is the local convention. Write it. In a vacuum, every trade will assume another trade will move.
The issue lifecycle: new, open, in review, closed, residual
An issue that cannot change state is a comment, not an issue. Define states. New means detected since last run. Open means assigned. In review means a proposed fix exists in a model that is not yet federated. Closed means the next clash run did not find it — not merely that someone said they fixed it. Residual means accepted for construction with a method (site measure, opening, ceiling change). Closed-without-retest is how clashes return on site.
Screenshots must include a grid, a level, and a scale clue. A cropped duct in a black void is not locatable. Navisworks viewpoints should be saved with the issue ID. If you use BCF, the viewpoint travels. If you use a slide deck, the IDs will drift unless someone is pedantic. Pedantry is the job.
Duplicates across weeks need a stable location key. Coordinators who reopen the same beam-duct hit with a new ID every Friday destroy trust. A good specialist will match issues to previous IDs. Ask for that behaviour in the brief.
How to outsource coordination
Outsource the process with access to the models, not a request to “coordinate” from PDFs alone. The specialist needs native or IFC files, the BEP, and authority to reject a bad drop. Milestone one should be: validate origins, propose a clash matrix, run a sample zone, deliver a grouped log. Milestone two: full current set. Milestone three: a cycle of updates.
If you also outsource modelling, consider a different person for coordination on anything larger than a house. On BIMProSG, you can award two packages. Protected payments let you fund the sample zone before you fund the building.
A coordinator hired as “extra modeller capacity” will be pulled into authoring and will stop grouping issues. Keep the commercial line visible: hours spent modelling are modelling; hours spent federating and running the matrix are coordination. If you need both, buy both. If you only buy one, accept the gap.
Ask applicants to describe a failed coordination cycle they have seen — not a fake case study with invented savings, just the failure pattern. Useful answers sound like: “architecture issued a ceiling after MEP had modelled, and nobody owned the freeze.” Useless answers sound like: “we always achieve zero clashes.” Zero clashes on a live design is usually a sign of tests that were too narrow, geometry that was too crude, or a log that was edited for comfort.
Meeting design: make the hour count
A coordination meeting is not a cinema screening of every clash viewpoint. Send the log 24 hours before. Mark the ten issues that need a decision in the room. Time-box each. Record the decision in the log during the meeting. Do not reopen closed issues without a change in geometry. If a lead does not attend, their default is to accept the proposed resolution or to freeze their model — pick one rule and write it.
Remote meetings need shared viewpoints. Navisworks viewpoints or BCF viewpoints beat “look at my screen” chaos. A specialist who can run that smoothly is worth more than a specialist who only exports a 200-page PDF.
Quality checklist for a coordination package
BEP exists and names coordinates, naming, and the clash matrix
Federation origin checked against a known grid
Tests match the matrix; tolerances recorded
Issues grouped; IDs stable across weeks
Owners and due dates present
Residual list exists
Changelog of incoming models
Sample viewpoint accuracy (the screenshot matches the clash)
Coordinator load: how much building one person can actually federate
A coordinator who is also modelling three disciplines is not coordinating; they are drowning with a job title. As a buyer, estimate load by number of incoming files, number of tests, number of meetings, and number of open grouped issues — not by GFA. A dense plant-heavy laboratory can be more coordination than a large simple warehouse. If the specialist says they need a deputy for issue grouping, that may be cheaper than a missed freeze.
Handover between coordinators needs the same artefacts as a modelling handover: matrix, test settings, issue ID scheme, origin note, and the last federated file. Changing coordinator without those artefacts resets the log to zero and destroys trust.
Client reporting that does not become a second job
A one-page weekly: incoming file versions, origin check pass/fail, open critical grouped issues, residuals added, freeze dates. That is enough for a project manager. A twenty-page illustrated novel every Friday is a coordination tax. If a client demands the novel, price it as a reporting extra. Do not steal the hours from grouping.
Dashboards with a single “coordination percent” are almost always gamed. Prefer counts of open grouped issues by zone. Prefer honesty about skipped tests.
Multi-contract and novation
When a design team hands a model to a contractor, the coordinator’s authority may change. The BEP should say who runs the matrix after award. Design residuals must be listed or they will be rediscovered as if they were new contractor clashes. A freelancer supporting the contractor should receive that residual list as an input. Without it, they will be blamed for design-era problems and the log will fill with duplicates.
Software versions and the federation computer
Navisworks versions, Revit versions, and IFC viewers must be named. A coordinator on a newer version than the authors will create files the authors cannot open for viewpoint review. Hardware must open the federated set in a meeting. If it cannot, region the federation. “It works on my machine” is not a deliverable.
CTA: hire a coordinator with a matrix, not a slogan
Is a BIM manager the same as a BIM coordinator? On small jobs the titles merge. On large jobs a manager owns information standards and a coordinator runs spatial cycles. Ask what they will actually do this month.
Can we coordinate only in Revit without Navisworks? For small link sets, sometimes. For multi-trade clash tests, a dedicated review tool is usually clearer. The method matters more than the logo.
How many clashes is “too many”? Raw counts are a weak KPI. A grouped list of open critical issues is the number that matters.
Who pays for redesign after a clash? The commercial contract, not the software. The log should still record the technical choice.
Do we need BCF? Useful when many tools are in play. Not mandatory if one tracker is actually used.
When should Scan to BIM enter coordination? When existing conditions constrain the new work. Register the cloud to the same coordinates.
How does this relate to 4D? Only after 3D coordination is meaningful. Linking an uncoordinated model to a programme produces a coordinated-looking video of a bad design.
Sources and reference notes
buildingSMART’s BCF standard describes issue exchange. Autodesk Navisworks documentation describes clash tests and viewpoints. ISO 19650 describes information management roles that projects may map to a coordinator. BIMForum and AIA LOD documents inform how much geometry can be trusted at a stage. Singapore digital submission processes are separate; see official CORENET X material. This article does not invent statutory coordination duties.
Image brief
A simple swimlane of author, coordinator, meeting, publish. A second image: one grouped clash viewpoint with a beam and a duct, labelled with an issue ID. Avoid heatmaps with invented “coordination scores.”