Ask ten people on a project what a BIM coordinator does and you’ll get ten different answers — “the model person,” “the clash-detection guy,” “the one who runs Navisworks.” All of those are partly true and none of them is the job. The real job is quieter and more important: making sure the building goes together in the field the way it goes together on screen, before anyone pours concrete or hangs a duct.
I run live BIM coordination today, so this is the job as I actually do it — not a textbook definition. I’ve spent 10+ years in construction and virtual design and construction, about four of them on-site in the field and the rest on the office and VDC side. That mix matters here, because half of this role is technical and half of it is knowing which conflicts will actually stop the field. Here’s what the work really is.
First, what BIM coordination actually is
BIM coordination is the process of combining every discipline’s 3D model — structure, architecture, mechanical, electrical, plumbing, fire protection — into one federated model, then finding and resolving the places where those trades physically conflict before the work reaches the field. The deliverable isn’t a pretty model. It’s a building that can actually be built as drawn, with the expensive surprises caught while they’re still a line edit on a screen instead of a change order on a jobsite.
A BIM coordinator is the person who owns that process. Not the person who models a single trade — that’s a trade modeler — and not, strictly, the person who sets the company’s overall BIM standards across many projects — that’s closer to a BIM manager. The coordinator sits in the middle of a live project and makes the trades’ models agree with each other. On most jobs, that’s a weekly rhythm that runs for months. Here’s what each week actually involves.
1. Federating the models
Every trade builds its own model, on its own schedule, in its own software. The first job is pulling all of them into one combined (“federated”) model so conflicts become visible. That sounds mechanical, but it isn’t — models arrive late, in the wrong coordinates, at the wrong level of detail, or modeling something that’s already changed in the field. Part of the coordinator’s job is simply keeping the inputs honest: chasing the trade that’s two weeks behind, flagging the model that’s clearly stale, and making sure everyone is coordinating against the same reality. A federated model built on bad inputs produces confident, useless answers.
2. Running the clash cycle — and knowing which clashes matter
This is the part people picture: clash detection. The software compares the trades and flags every place two objects occupy the same space. On a real project that’s hundreds or thousands of “clashes” — and the single most important skill is knowing which ones are real.
Software finds every overlap. Experience tells you which ones will actually stop the field.
A lot of flagged clashes don’t matter — a hanger passing near a pipe, two objects modeled to touch that the trades resolve in the field without a thought. Others are genuinely critical: a duct routed straight through a beam, a main that leaves no clearance to service a valve, a chase too tight for a trade to physically get a tool into. A coordinator who has only worked inside the software treats every overlap as equal and buries the team in a report no one can act on. The years I spent in the field taught me to sort the majors from the molehills fast — to push the structural and concrete conflicts to the front, because those are the ones that hold up construction, and to let the trades absorb the noise that was never going to matter. That triage is the difference between a clash report and a usable plan of attack.
3. Driving trades to sign-off
Finding a conflict is the easy half. The hard half is getting it closed. Each conflict gets assigned to the responsible trade with a clear ask, then it has to actually get resolved — re-routed, re-modeled, re-checked — and the area signed off as clean before the field gets there.
This is where coordination is really a people job. An open conflict isn’t a paperwork problem; it’s construction that can’t proceed, and every day it sits costs the schedule. So when a trade is sitting on a conflict, someone has to stay on it — politely the first time, firmly after that — until it’s closed and the area is signed off. A coordinator who just emails a report and waits isn’t coordinating; they’re documenting. Driving the trades is the job.
4. Managing RFIs and model updates
Coordination doesn’t happen in a vacuum. Conflicts surface questions the model can’t answer on its own — a routing that needs the engineer’s call, a dimension that doesn’t close, a detail that’s genuinely ambiguous. Those become RFIs (requests for information), and the coordinator manages them so the answer flows back into the model. As the design evolves and the field reports as-built conditions, the coordinator keeps the federated model current so it stays the single source of truth — not a snapshot that drifted out of date in month two.
5. Reporting it so the whole team can see it
The last piece is visibility, and it’s the one that quietly decides how fast everything else moves. On the work I run, every conflict lives in the model environment, where the whole project team — GC, trades, and design — can open the model and the live issue log in a browser anytime. Nothing is hidden in a black box.
On top of that, I produce an AI-leveraged weekly coordination report: I distill the meeting and the clash data into one document any project manager can read at a glance, and it tracks overdue conflicts so trades stay accountable. “AI-leveraged” means technology does the heavy lifting on assembling and formatting the report quickly and consistently, while I stay in control of every call and review every deliverable before it goes out. It is never auto-generated and shipped blind. The point is simple: you should never have to guess where coordination stands.
BIM coordinator, BIM manager, trade modeler — what’s the difference?
These titles get used interchangeably, and they shouldn’t be:
- A trade modeler builds one discipline’s model — the mechanical model, the plumbing model.
- A BIM coordinator federates all the trades, runs the clash cycle, and drives the project to a coordinated, signed-off model. Project-level, week to week.
- A BIM manager typically sets standards, templates, and workflows across many projects — company-level, not the day-to-day on one job.
On a lot of projects — especially with a lean partner like me — the coordinator wears more than one of these hats. The line that matters for a GC is this: the coordinator is the person accountable for your model being buildable, on your schedule.
A bit more on how I approach this comes from having been on the building side of these jobs, not just the screen side. And if you’re weighing an outside coordinator against an offshore production shop, this read on US-based vs. offshore BIM coordination walks through the trade-offs. The full scope of what I run lives on the BIM coordination service page.
Frequently asked questions
What does a BIM coordinator do, in one sentence?
They combine every trade's 3D model into one, find and resolve the places those trades physically conflict, and drive the project to a coordinated model the field can build from — before the expensive surprises reach the jobsite.
What's the difference between a BIM coordinator and a BIM manager?
A coordinator works at the project level — federating models, running clash cycles, and driving trades to sign-off week to week on a specific job. A BIM manager usually works at the company level, setting the standards and workflows that projects follow. On a lean engagement, one person often covers both.
Do I need a BIM coordinator if my trades already model their own work?
Usually yes. Trades modeling their own scope is exactly why you need coordination — each model is correct on its own and conflicts only show up when you combine them. The coordinator is the neutral party who federates all of them, finds the conflicts no single trade can see, and gets them resolved.
What software does a BIM coordinator use?
The federation and clash-detection tools are industry-standard, and the specific tool matters less than how it's used. The skill isn't running the software — it's knowing which of the conflicts it flags will actually stop the field, and driving those to resolution. That judgment comes from the field, not the manual.
Can a BIM coordinator work alongside our in-house team?
Yes. I run coordination as a dedicated partner whether you have an internal VDC group or none at all — clash detection, trade sign-offs, RFI management, model updates, and the weekly deliverables. The BIM coordination service page lays out the full scope, and if you're weighing an outside coordinator against an offshore production shop, the US-based vs. offshore BIM coordination read walks through the trade-offs.