A common data environment (CDE) is the agreed single source of information for a project, used to collect, manage, and share every information container among all project parties. The term is defined in ISO 19650-1, the international standard for managing information on built-asset projects. A CDE is a working arrangement supported by software, rather than a product in itself.
The idea
Multi-party projects fail informationally in a predictable way: each organization keeps its own copies, versions drift, and decisions get made on superseded information. The CDE concept answers this with one agreed environment where each piece of information exists once, with a known status, and every party works from it. ISO 19650-1:2018 defines the CDE as the agreed source of information for the project, and pairs the term with a workflow that governs how information moves through it.
The CDE workflow: states
ISO 19650 describes information moving through defined states, each with different visibility and reliance rules:
- Work in progress. Being developed by one task team; not to be relied on by others.
- Shared. Checked and made visible to other teams for coordination; usable for their own development but not yet authorized for delivery.
- Published. Authorized for use, for example issued for construction.
- Archive. The record of everything that passed through, including superseded versions, kept for audit.
The state transitions carry approval gates. This is the substance of the standard: the value is not the shared folder, it is the agreed rules about what each party may rely on at each state.
CDE vs EDMS, and what one runs on
An EDMS is a software category; a CDE is the project arrangement ISO 19650 defines. In practice a project's CDE is implemented on one or more platforms: a construction collaboration platform, an EDMS, or a combination (a "CDE ecosystem") when different information types live in different tools. UK-influenced projects, where ISO 19650 adoption is furthest along, commonly name the CDE and its platform in the appointment documents.
The boundary problem practitioners hit: much of a project's real information, email decisions, meeting outcomes, field observations, never enters the CDE, because the workflow was designed around models and documents. Information management plans increasingly have to say where that material lives.
Related terms
- EDMS: the software category CDEs are often built on.
- Document control: the operational discipline inside a CDE.
- PIM: project information management, the wider discipline including the information a document-centric CDE misses.
- Transmittal: the issue record; CDE state changes serve a similar audit function.
Frequently asked questions
What does CDE stand for in construction? Common data environment: the agreed single source of project information defined in ISO 19650-1, through which all project parties collect, manage, and share information.
Is a CDE a piece of software? No. The CDE is the agreed arrangement; software platforms implement it. ISO 19650 deliberately defines the CDE as a workflow and source of information, not a product, and one project may implement its CDE across several connected platforms.
Is a CDE required? Where ISO 19650 is invoked contractually, common on UK public projects and increasingly elsewhere, an appointing party can require a CDE. Outside those contexts it is good practice rather than an obligation.
What is the difference between a CDE and SharePoint or an EDMS? The platform provides storage, versions, and permissions. A CDE adds the ISO 19650 arrangement on top: agreed information states (work in progress, shared, published, archive), approval gates between them, and rules about what each party may rely on.
What is ISO 19650? The international standard series for managing information over the life cycle of built assets, developed from the UK BIM standards. Part 1 sets concepts and principles, including the CDE; Part 2 covers the delivery phase of assets.
Markdown version of this entry, for AI assistants and agents.