The underlying misunderstanding
Almost everyone starting in this role believes the job is finding clashes. It is what they do in month one, what they are asked about in the interview, and what the tool puts in front of them. But finding clashes is what the machine does in twenty minutes.
The hard part comes afterwards, and it is an odd mixture of technical judgement and management: deciding which ones matter, knowing whose problem each one is, getting that person to solve it before the material is bought, and leaving a record that it was solved.
A BIM coordinator has no authority. They have visibility. Confusing the two is the mistake that ruins a new coordinator.
A coordinator who moves the duct «because it fitted there» has done three bad things at once: modified somebody else’s work without permission, left the model different from the approved design, and become the person who answers for it if that fix fails on site. The correct way is slower and it is the only one that holds: issue the problem, assign it to the element’s owner, and verify that they resolved it.
Coordinator, modeller and BIM manager
The three titles get used as if they were interchangeable, and they are not. The clean way to separate them is not by tooling or seniority, but by what each one decides.
| Role | What they decide | They work on | Typical failure |
|---|---|---|---|
| BIM modeller | How an element of their discipline is represented | One model — their own | Good-looking geometry with no information: nothing can be queried |
| BIM coordinator | Which problem is a priority and whose it is | Several federated models, in one zone and one phase | Huge lists with no owner, and decisions nobody ever made |
| BIM manager | How the whole team will work, and under what rules | The project or the whole company | An execution plan nobody reads and nobody follows |
Put shortly: the modeller answers «is my part done right?», the coordinator answers «does everyone’s work fit together, and in time?», and the manager answers «are we working the way we agreed?». On small teams one person wears all three hats — but it is worth knowing which one you have on at any moment.
Where the craft came from
This is not trivia. Almost everything that looks arbitrary today — IFC, level of development 350, the execution plan, the weekly meeting — was invented to solve a specific problem that can be told as a story.
The light table
Coordination with transparent overlays: ductwork on one sheet, piping on another, electrical on a third, and a light underneath. The craft already existed. What changed later was the medium, not the work.
Describing the building instead of drawing it
Chuck Eastman publishes the complete idea of what we now call BIM: a single description from which every view derives, updating itself when something changes. Computers were thirty years behind.
The term VDC is born at Stanford
Out of the CIFE centre comes Virtual Design and Construction, with a thesis most of the industry forgot: it is not the 3D model. It is three things at once — product (what gets built), organization (who builds it) and process (how and when).
The Boeing 777 is pre-assembled digitally
The first commercial aircraft assembled entirely in the computer, with no physical mock-up. That is literally where clash detection comes from: it was pre-assembly, not audit.
IFC, because nothing talked to anything
A group of companies founds the alliance that produces the open exchange format. The problem was no longer modelling: it was that no program understood another, and every project paid for that translation twice.
Clash detection becomes a job title
Detection stops being something a modeller does with spare time and gets its own line on the org chart. Two schools appear in parallel: checking geometry and checking rules. It is worth knowing both.
The rules get written down
The UK publishes the standard for the common data environment and the information states. BCF appears, letting an issue travel between programs. And the first level-of-development specification is published, with a new rung — 350 — created specifically for coordination.
From recommendation to contract requirement
The UK makes it mandatory on public work, and two years later those standards go international. That is where the contractual vocabulary in any serious tender comes from: appointing and appointed parties, information requirements, execution plan.
The documents that govern the work
A coordinator does not work «on judgement». They work against agreed documents. These are the ones that show up on any serious project, and what each one prevents.
| Document | What it fixes | What it prevents |
|---|---|---|
| Execution plan (BEP) |
What the model is for, who delivers what, in which format and when | Discovering in week twenty that nobody was going to model the supports |
| Common data environment (CDE) |
Where each file lives and in what state: work in progress, shared, published, archived | Coordinating against somebody’s draft left in a folder |
| Authorship matrix | Who authors each element, by system and by phase | Two disciplines modelling the same thing — or neither modelling it |
| Clash matrix | Which disciplines are tested against which, and at what tolerance per pair | Three thousand false positives and a team that stops opening reports |
| Level of development (LOD) |
How far each element can be trusted, one by one | Coordinating a model that has no supports or connections yet |
| Shared origin | The common point and zero level for every model | The most expensive and most stupid error: models a metre apart |
| Coordination calendar |
Which zone closes each week, and when it freezes | Coordinating the whole building at once and never closing anything |
How the work should be measured
The metric almost everyone uses — number of clashes found — measures noise, and it rewards the opposite of what you want: a coordinator who lowers the tolerance finds more and looks busier.
- Decisions closed on time, not problems opened. One problem with an owner and a date is worth more than fifty without.
- Zones released to fabrication that do not reopen. Closing a zone and having it stay closed is the proof that coordination actually happened.
- How many problems die inside the discipline that created them. If most escalate to the lead or the designer, something upstream is wrong.
- Rework on site attributable to coordination. It is the only indicator the person paying cares about.
Frequently asked questions
What is the difference between a BIM coordinator and a BIM manager?
The coordinator works across federated models within a project and decides which problem is a priority and whose it is. The manager works across the project or the whole company and decides how the team will work: the standards, the execution plan, the formats and the rules. One resolves the day to day; the other sets the frame it is resolved in.
Does a BIM coordinator model?
They may model, but they must not modify other disciplines’ elements. The job is to federate, detect, classify, assign and verify. The moment they start moving somebody else’s work, the model stops matching the approved design and the liability shifts onto them.
What do you need to become a BIM coordinator?
Less software than people assume and more craft than gets taught. You need to understand how things get built — why gravity drainage does not negotiate, what is fabricated in the shop and what on site — to read a federated model, and to run a meeting where several disciplines each have to give something up. The tool takes weeks to learn. The rest does not.
What is a BEP or BIM execution plan?
The document that states how the team will work before work starts: what the model is for, who delivers what, in which format, at what level of development and on what dates. Its original idea — deciding what the model is for before building it — is simple, and almost nobody follows it in that order.
What does it mean that the coordinator «has no authority»?
That they can see the problem and name it, but cannot resolve it alone or compel anybody. The element’s author resolves it; if something else has to move, the discipline lead decides; if it is a design conflict, the designer decides; and if it changes cost, the owner decides. The coordinator’s power is that all of that gets written down with a date.