In digital construction, the most expensive clashes are not always geometric. Sometimes they happen between roles.
Imagine the poster for an unnecessarily dramatic blockbuster. On one side, the Project Manager: deadlines, budget, contracts, risk, client expectations. On the other, the BIM Manager: information strategy, digital workflows, model quality, coordination rules. Two people who should be looking at the same project — and who, in some organisations, somehow end up behaving as if they were defending different universes.
The BIM Manager often occupies a strange position. They may be central to digital transformation, define workflows, organise information and protect consistency across disciplines, yet still sit at the edge of strategic decisions. Called when something goes wrong. Asked to fix the process. Less often invited to shape the decision that created the problem in the first place.
The Project Manager, meanwhile, is usually much closer to the formal centre of gravity: client, programme, procurement, cost, risk and delivery. They understand how decisions travel through contracts and people. But in a digital project, control of delivery increasingly depends on control of information. A programme can be perfectly managed on paper and still fail if the information needed to build arrives late, ambiguously or in the wrong form.
And here is the first correction to my own title: the day-to-day counterpart of the Project Manager is often not the BIM Manager at all. It is the BIM Coordinator.
The BIM Manager sets the information strategy. The BIM Coordinator translates that strategy into project action: federating models, resolving coordination issues, reviewing information, talking to disciplines, tracing decisions. That puts the Coordinator surprisingly close to project management. Both roles are concerned with objectives, dependencies, timing and consequences — they simply approach them from different sides.
This is where the relationship can become difficult. The PM may see BIM as an additional layer of process: more meetings, more requirements, more things that apparently need to happen before anybody can build. The BIM Coordinator may see the PM as someone who wants results without understanding the information needed to produce them. One manages time and money. The other manages data and coordination. When they stop talking, both lose visibility.
The future has very little space for that separation. Project Managers need enough information literacy to understand that data quality affects delivery. BIM Coordinators need enough business literacy to explain why information management matters in terms that the project can act on. Knowing Revit or running clash detection is not enough. Neither is knowing a programme and a cost report if the information behind them cannot be trusted.
A useful place to meet is the Information Delivery Plan. Instead of treating the IDP as a purely BIM document, look at it through the lens of effort, payment and cash flow. If a model delivery is linked to a commercial milestone, why should the PM and BIM Coordinator analyse those two flows separately? Put them on the same table and the conversation changes immediately.
Suppose, for example, that automated drawing production can save days of repetitive work — but only if the drawing list is available early enough. For the BIM team, that list is an input. For the PM, producing it earlier may look like bringing a cost forward. Once the BIM Coordinator can quantify the downstream saving, however, it becomes a project decision rather than a software request.
The same applies to clash detection. A clash is not valuable because it appears in a report. It becomes valuable when resolving it early prevents a more expensive consequence later. A duct crossing a beam is not just a red marker in a federated model: it can become redesign, rework, delay, wasted material and site disruption. If the BIM team can translate coordination into avoided cost or avoided risk, the PM suddenly has a reason to care about the quality of the clash process — not just the number of issues closed.
This is also why I am increasingly uncomfortable with treating the BIM Coordinator as a purely operational technician. Coordinators plan, negotiate, prioritise, review, train and mediate. In many organisations those are management behaviours, even when the job title and career framework have not caught up yet.
So who gets the keys to the Batmobile? I am still not going to say who is Batman and who is Robin. But I do think somebody needs to define the rules of the road. Governance matters: who decides, who advises, who approves, who owns the consequences. In a mature organisation, that relationship should be designed rather than improvised project by project.
Will the Project Manager of the future also become a BIM Coordinator? Will BIM Coordinators grow into broader project-management roles? Probably, in some organisations. In others, the roles will remain distinct but become much more tightly connected. The title matters less than the ability to make time, cost, information and technical judgement part of the same decision-making system.
The most interesting future is not a victory of BIM over project management, or vice versa. It is the moment when both stop defending their own dashboards and start reading the same project.
Maybe the sequel is not a battle at all. Maybe it is a crossover.
