09. How Many CDEs Does One Project Have?
Multiple CDEs on one project is the ordinary condition of major infrastructure delivery. A Common Data Environment (CDE) belongs to the organisation that licences it, and a large project involves many organisations with their own document control obligations, so the project carries as many environments as it has parties. The count is a property of the contract structure.
Most information delivery plans name two or three environments. Walking through where each deliverable physically sits at any given moment usually produces a longer list, including systems that were never written down anywhere.
This article covers:
What counts as a CDE on a project
Why the count is higher than most teams assume
Where the environments come from
Why the number grows rather than shrinks
What the count costs
What to do about multiple CDEs on one project
What counts as a CDE on a project?
A CDE is the managed environment holding the controlled copy of a party's project information, with revision control, review and approval workflow, and an audit trail. On that definition the client's mandated platform counts, and so does each contractor's enterprise environment and each consultant's document control system.
Anything holding working copies of deliverables also has to be counted, whether or not it was set up to be a CDE. A network file share holding calculation sheets and marked up PDFs forms part of the project record in practice. So does a site stood up in the first month of delivery to hold material that fits nowhere else.
Counting only the platforms named in the information delivery plan understates both the size of the estate and the effort involved in moving content around it.
Why the count is higher than most teams assume
Deloitte and Autodesk, in "State of Digital Adoption" (2025), found that construction businesses across Asia Pacific use a median of 11 separate data environments, and that streamlining them could save 10.5 hours a week.
Two things push the real number above the assumed one. Environments introduced for a single package or a single delivery phase are rarely recorded centrally, so they never reach the register. Environments belonging to other parties are counted by those parties, so nobody holds a total.
The result is that the count is knowable but unknown. Establishing it is usually a half day of asking each party where its deliverables live before they are issued.
Where the environments come from
The sources are consistent across large projects:
The client's mandated platform, named in the contract, holding the record the owner will eventually inherit.
The design joint venture's platform, chosen because both partners already hold licences for it.
Each tier one contractor's enterprise environment, tied to that business's own systems and internal audit position.
Specialist consultants' platforms, often certified as part of their own quality management systems.
The surveyor's system, built around point clouds and setout data that other platforms handle poorly.
A network file share that predates the project and still holds live working files.
A site holding whatever fits nowhere else, which grows into a dependency during delivery.
Why the number grows over the life of a project
Work is contracted in packages, and each package brings a party with an established licence estate, an information security position and internal processes already audited against a particular platform. Asking that party to work somewhere else means asking it to run two systems, retrain its people and accept risk its insurers have not priced. That cost ends up in its tender price.
Events during delivery add environments. Packages get added, contractors get replaced, a partner is novated, an operator joins for commissioning. Almost nothing removes an environment. Retiring one means moving its history somewhere else with the version lineage intact, and that is a project in its own right.
Mandating a single platform does not reduce the count either. Under ISO 19650 at BIM Stage 2, the most commonly implemented level, multiple CDE solutions are permitted on a single project, and a single unified collaborative CDE belongs to Stage 3. Where a contract names one platform, parties with certified internal systems commonly populate the mandated environment from the one they actually work in.
What the count costs
Duplicate storage is the visible cost and the smallest one. The same model sits in four environments and somebody pays a subscription for each.
Reconciliation hours are larger and harder to see, because they are spread across many people doing small amounts of manual work: downloading, renaming, re-keying metadata, re-uploading and checking. Construction professionals spend 35 per cent of their working time on non-productive activity, including 5.5 hours a week searching for project data and 4.7 hours resolving conflicts, on PlanGrid and FMI's 2018 "Construction Disconnected" findings. Large public sector projects routinely require in excess of a hundred individual metadata fields per document, and re-keying at that depth across several platforms occupies whole roles.
Version ambiguity turns that effort into rework. Where the same drawing exists in five places and only one is current, somebody eventually builds from the wrong one. Bad data caused 14 per cent of all rework globally in 2020, worth US$88.69 billion, on Autodesk and FMI Corporation's 2021 survey of more than 3,900 construction professionals.
Dispute exposure follows the ambiguity. An argument about what was issued, when, and to whom has to be answered from several audit trails that were never designed to agree with each other. The Arcadis Global Construction Disputes Report puts the average construction dispute value at US$52.6 million globally, with sums in dispute trending towards 32.3 per cent of project CAPEX.
What to do about multiple CDEs on one project
Reducing the count means renegotiating with every party that holds a platform, and it rarely succeeds. Connecting the environments is a technical decision a project can take without renegotiating anything, and it leaves each party on the platform its own business runs.
When files, folder structure, version history, metadata and workflow state move automatically between platforms, the number of environments becomes an administrative fact rather than a daily cost. Document controllers spend their time on register accuracy and transmittal discipline instead of transfers. Reviewers open the platform they already use and find current content in it. The client's assured record fills from the environments where the work is actually done.
The field level mapping between schemas that do not agree is the practical heart of the work, and it is covered in ISO 19650 metadata compliance across multiple CDEs. The options for making the connection, from native connectors to general automation tools to purpose-built platforms, are compared in our CDE integration comparison guide. Where an environment is genuinely being retired instead of connected, that is a migration, and Migration or Sync? Knowing Which One Your Project Actually Needs sets out which applies.
Challenges organisations face when running multiple CDEs on one project
No agreed total. Each party counts its own environments and no single register lists them all, so the estate is never sized properly at the point when it could still be planned for.
Metadata schemas that disagree. Status, suitability and discipline are modelled differently on every platform, and each transfer between them is a translation somebody has to perform.
Unclear authority. Where two environments hold the same document, the project has to state which one is authoritative for which content type, and that decision is often left unmade.
Environments outside the delivery plan. Network shares and ad hoc sites hold real deliverables and receive none of the governance applied to the named platforms.
No plan for handover. Each environment holds part of the record the owner will inherit, and assembling it at project close is rarely priced into anyone's contract.
How many CDEs does a typical infrastructure project have?
More than the delivery plan records. Deloitte and Autodesk found that construction businesses across Asia Pacific use a median of 11 separate data environments. On a major project the count usually includes the client platform, the joint venture platform, each tier one contractor's environment, specialist and consultant systems, a surveyor's system, and the legacy shares and ad hoc sites that appear on no register.
Is having multiple CDEs on one project a compliance problem?
No. ISO 19650 at BIM Stage 2 permits multiple CDE solutions on a single project, and Stage 2 is where most delivery sits. The obligation concerns the state of the information, its revision, suitability and approval status, rather than the number of platforms holding it. The risk lies in losing that state as content crosses a platform boundary.
Can we mandate a single CDE for everyone on a project?
You can write it into the contract, and it will be priced. Parties with certified internal systems will either quote to run two environments or run the mandated one as a copy of their real one. A second environment exists in both cases, so a mandate tends to move the cost onto somebody else.
CDE Sync™ keeps content, metadata, version history and workflow state aligned across 21 supported vendor integrations without moving any party off its own platform. Counting the environments on your project is the first step, and connecting them is the second. Book a demo or get in touch with your count.