Common data environment (CDE): ISO 19650 states and transition workflow (2026)

A common data environment (CDE) is the agreed source of information for a project or asset, used to collect, manage and disseminate information containers through a managed process. ISO 19650 describes four information states (Work in progress, Shared, Published, and Archive) with checks and authorisations governing the moves between them. The ISO text is paywalled; for exact clause numbers see ISO 19650-1 and ISO 19650-2 (clause 5.1.7 of Part 2 deals with establishing the project’s CDE).

CDE numbers at a glance

An information container is ISO 19650’s term for a named persistent set of information retrievable from a file, system or application storage hierarchy, such as a model, a document, a drawing or a schedule. It is the unit that the CDE manages.

What is a common data environment under ISO 19650?

A CDE combines a technology platform with a process: states for information containers, the checks that move a container between states, and defined responsibilities. A platform alone does not satisfy ISO 19650; the process is what ISO 19650 specifies. ISO 19650 is platform-neutral and does not name products. Who provides and configures the CDE is set in the appointment documents; for the ISO wording, see ISO 19650-2.

What are the four ISO 19650 information states?

An information state describes the status of a container in the CDE. The four states are Work in progress, Shared, Published, and Archive.

WIP protects in-progress work from premature use by other teams. Shared enables coordination across disciplines. Published marks information authorised for use, for example in construction or as part of the asset information model. Archive keeps the traceable record.

What does each state transition require?

A state transition is the move of a container from one state to the next. Each move is tied to a check, review or authorisation by an accountable party; the project’s information production procedures define who performs it.

WIP to Shared follows the task team’s check that the container meets the project’s information standards (such as naming and classification) and is fit for the stated purpose of sharing. The appointing party is not normally involved at this step.

Shared to Published requires authorisation. Under ISO 19650-2 the lead appointed party reviews and authorises the information model (clause 5.7.2), and the appointing party then reviews and accepts it (clause 5.7.4). Skipping this step means work proceeded on information that was never formally authorised.

Into Archive records the information at the end of a stage or phase so the project keeps a traceable history. The records feed handover to the next phase, including operation.

What distinguishes a CDE from a shared drive?

A shared drive stores files. A CDE implementation controls how containers move between states and keeps a record of it. A folder named “WIP” is not a WIP state unless the process behind it is enforced. ISO 19650 does not list the technical features a platform must have; the ones below are common practice, not clauses of the standard:

• Container states and transitions: workflow enforced by the platform, not by folder naming
• Version control: every revision retrievable, with history per container
• Audit trail: who accessed, changed and approved each container, with timestamps
• Metadata: container identification, revision and status fields as the project’s information standard defines them
• Access control: role-based, aligned with the project’s security requirements (ISO 19650-5 where it applies)
• Support for issue tracking: for example BCF-based issue management between teams

Which CDE platforms do architects use?

ISO 19650 does not certify or recommend platforms. Commonly used products on BIM projects include Asite, Aconex, Autodesk Construction Cloud, Bentley ProjectWise, Trimble Connect and Procore. BIMcollab (BCF issue management) and Solibri (model checking) are often used beside a CDE rather than as the container store. Check each vendor’s documentation for how it implements the four states. Select the platform that enforces the transitions the project’s EIR requires.

What are the most common CDE mistakes on ISO 19650 projects?

Four mistakes appear often.

1. Calling a file share the CDE. A folder named “WIP” has no enforced states, transitions or audit trail unless the platform and process add them.

2. Treating CDE selection as only a platform problem. Define the process first, then select the platform that supports it.

3. Opening WIP to everyone. The WIP state exists for the originating task team’s own iteration. Keep access to that team.

4. Skipping the authorisation step before Published. Information used for construction should have passed the authorisation the appointment documents require. Skipping it creates traceability gaps at handover.

Frequently asked questions

What is the difference between WIP, Shared, and Published states in ISO 19650?

WIP is the originating team’s working information. Shared is checked and available to other delivery teams for coordination. Published is authorised for its intended use, such as construction or asset operation. Each move is tied to a check or authorisation.

Who sets up the common data environment on an ISO 19650 project?

ISO 19650-2 includes establishing the project’s CDE in its delivery-phase process (clause 5.1.7). Which party provides and configures the platform is set in the appointment documents, and the delivery team’s BEP records how the team uses it.

Does ISO 19650 require a specific CDE platform?

No. ISO 19650 is platform-neutral. Any solution that supports the states, the transitions, and the records the project requires can serve.

What is an information container under ISO 19650?

A named, persistent set of information, such as a model, document, drawing or schedule, that the CDE manages as one unit. The project’s information standard defines which metadata each container carries.