Digital coordination on construction projects

An adoption figure does not describe a working project

NBS surveyed 559 design and construction professionals for its 2025 report. In its November 27 account of the findings, roughly seven in ten respondents used BIM, a proportion broadly stable over several years. Fewer described BIM simply as three-dimensional models with data. More associated it with structured information management and the ISO 19650 standards.

That is evidence about professional use and understanding, rather than a measured improvement in project delivery. NBS supplies construction information products, and its survey is an industry respondent sample. It does not establish that seven in ten projects worldwide use effective coordination, or that BIM caused a particular reduction in cost.

For a contractor, the more revealing questions concern particular work packages. Can the installation team identify the approved revision? Can the designer explain why an issue was closed? Can the client find the product information required to maintain the completed asset? These are observable tests of coordination that a software adoption percentage cannot answer.

A company can use sophisticated models while still relying on disconnected email decisions. It can also manage a modest project well with a relatively simple toolset. The difference is whether responsibilities and information exchanges fit the work.

Start with the information needed for a decision

An illustrative ceiling-services package shows the problem. Mechanical, electrical and structural teams each produce competent designs. When combined, the models reveal a duct intersecting a beam. The obvious response is to move the duct, but the project still needs to check headroom, access for maintenance, fire separation, installation order and the effect on procurement.

A useful coordination record therefore includes more than a coloured collision marker. It identifies the location, affected systems, responsible decision-maker, proposed resolution and deadline. It also records whether the solution has been accepted and incorporated into the information issued for construction. Closing the software issue before those actions occur creates a misleading picture of progress.

Teams should distinguish between an issue resolved in principle and a change released for use. A subcontractor may be able to price the former but should not assume it is authorised construction information. The required distinction needs to survive model exports, drawing production and the transfer to a site tablet.

This approach makes the first digital investment a definition exercise. Decide which decisions need supporting information, who supplies it, who checks it and when it becomes usable. The appropriate level of model detail follows from those requirements.

A common data environment is also a workflow

The UK BIM Framework's earlier Guidance Part C explains a common data environment as a combination of processes and technical solutions. It distinguishes work in progress, shared information and published information, with an archive supporting the history of transactions. It also recognises that different organisations may use different systems within a project workflow.

The practical implication is that a shared folder alone does not settle an information's permitted use. Revision and status information need to remain understandable when files move between systems. A document can be the newest version and still be unsuitable for construction because it remains under review.

Consider another illustrative situation: an engineer downloads a drawing before travelling to a site with unreliable connectivity. A revised drawing is issued later that morning. The process needs a way to identify the superseded copy and communicate the change. Cloud access does not automatically solve the last step when the worker is offline.

A project can test this before mobilisation. Send a small sample of models, drawings, approvals and asset records through the actual tools used by each organisation. Check identifiers, revision histories, permissions and the recipient's understanding. A successful file transfer is useful evidence, but a recipient using the correct information for the correct purpose is the stronger result.

Safety information gives coordination a longer life

ISO 19650-6, published in January 2025, addresses the collaborative classification, sharing and delivery of health and safety information across project and asset life cycles. Its public scope also makes clear that the principles can apply where BIM is not used. The significance is the continuity of structured information, rather than a requirement to represent every risk as geometry.

An earlier HSE white paper illustrates how models can support construction planning and communication through industry case studies. These examples offer plausible mechanisms for improvement, including making a sequence or maintenance task easier to understand. They are not a controlled estimate of an accident reduction that every project can expect.

For a building owner, an unresolved access issue can outlive the construction contract. A valve that appears accessible in a model may become difficult to reach after other equipment is installed. Coordination should therefore include people who understand operation and maintenance, with a way to retain the relevant decisions at handover.

The same principle applies to uncertainty. A model assembled from incomplete surveys should not visually imply that hidden conditions are known. Record assumptions and verification needs so that later users can distinguish surveyed information from a design expectation. Visual clarity should help expose uncertainty rather than conceal it.

Measure the work that information changes

The 2021 CDBB study on the value of information management combined literature and organisational case studies to examine potential benefits. It linked better information to organisational productivity and wider outcomes while recognising limits in the evidence. It remains useful background for framing benefits, rather than a current guarantee of a return on a particular implementation.

A project-level assessment can be more specific. Track the time from an issue being raised to an approved resolution, the number of installations affected by superseded information, and the hours spent recreating data that another organisation already holds. Separate genuine improvements from changes in project size, complexity or reporting discipline.

Clash counts alone are especially ambiguous. A higher count may mean better detection, a more detailed model, poor coordination or a deliberately wider search. A lower count may mean fewer problems, or simply fewer checks. Pair the count with severity, closure evidence and the point at which the issue was discovered.

Costs also need a full boundary. Information management takes staff time, training, checking and maintenance. Those costs can be worthwhile, but they do not disappear because the software is already licensed. Measure benefits against the actual earlier process, including any useful practices it already contained.

Handover is an acceptance test

The final test is whether the receiving organisation can use what the project delivers. A facilities team may need a searchable equipment register, reliable locations, maintenance information and a clear record of substitutions. A large model containing poorly identified objects may be less useful than a smaller, accurate dataset aligned with its systems.

Agree that acceptance test early enough to influence procurement and installation records. Ask the owner to retrieve information for a sample asset during delivery, not only at completion. If the search fails, the project still has time to improve the process while suppliers and installers are available.

Digital coordination is progressing when information remains dependable as it crosses organisational boundaries. The convincing evidence is a decision made earlier, an installation completed from the correct revision, or an operator receiving usable records. Those outcomes make the model valuable to the project and explain why information management deserves attention beyond the design office.