A Common Data Environment is the agreed place a project keeps its information containers, and the rules for how those containers move. It is a workflow with permissions. It is not a logo on a login screen.
What it is for
Delivery teams need one current copy of a drawing, model or schedule, a record of who changed it, and a way to say whether other people may rely on it. Without that, coordination happens in inboxes. Federation then mixes a Friday file with a Tuesday file and calls the clash real.
The container needs a stable name — the file-naming guide — and a state that says who may use it. Those states are WIP, Shared, Published and Archive. A platform that stores files but does not enforce that move is a drive with a new label.
What it is not
- Not the authoring tool. The model is still built in the discipline application.
- Not automatic quality. A CDE will store a bad file if someone has permission to upload it.
- Not a promise of ISO 19650 compliance. Buying a platform does not appoint an information manager.
- Not a design approval. A number checked on this site can be stored in WIP. Storing it does not publish it.
Who decides the rules
The appointing party sets the information requirements. The appointing party also sets the project’s information standard: naming, states, who may share, and what “accepted” means before something is Published. The lead appointed party confirms it or proposes additions in the BIM execution plan. Task teams produce the containers. If those roles are not named, the CDE is whoever has the admin password.
A worked distinction
A structural model uploaded for the Monday coordination meeting is Shared: other task teams may look at it and raise clashes. It is not Published unless the appointing party’s process says that purpose has been accepted. Printing that Shared model and issuing it to site as the construction issue is the failure mode this site keeps pointing at.
Read the state guide next: WIP, Shared, Published, Archive.
How containers move
| From | To | What has to happen |
|---|---|---|
| Work in progress | Shared | The task team checks and approves the container for a stated suitability. |
| Shared | Work in progress | A new revision is developed after comments; the shared version stays visible. |
| Shared | Published | The lead appointed party authorises it and the appointing party accepts it. |
| Published | Archive | Superseded or completed information is kept as a record. |
Each step is a decision by someone with the authority to make it, recorded in the CDE. A file copied into a different folder has not changed state unless that decision was made and recorded. See CDE states for each state in detail.
Questions
Is SharePoint a CDE?
A document management system can host a CDE, but the system alone is not one. The CDE is the system plus the agreed process: states, naming, metadata, permissions and who approves each move. A shared drive with no agreed process is a file store, whatever the software.
Does every project need a dedicated CDE product?
No. ISO 19650 does not name software. A small project can run a workable CDE on general tools if the states, metadata and approvals are defined and followed. Larger projects usually choose a product that records the workflow automatically.
Who sets up the CDE?
The appointing party is responsible for establishing the CDE for the project, although it may appoint someone to provide and run it. The information standard and production methods say how it is used.
What should be agreed before the first upload?
The naming convention, the metadata fields, the suitability and revision codes, the folder or container structure, who may approve each move and what the acceptance checks are. Testing these with a few dummy containers during mobilisation saves rework later.
Metadata a container usually carries
| Field | Example |
|---|---|
| Name | PRJ-ABC-ZZ-01-DR-S-0001 |
| Title | Level 01 general arrangement |
| Revision | P02 |
| Suitability | For coordination |
| State | Shared |
The name stays the same across revisions; the other fields change as the container moves.
What goes wrong most often in a new CDE?
Permissions and states drift apart. A folder named “Shared” that every team can edit is not the Shared state, because the shared version can be overwritten without a record. Another common problem is approving moves by email outside the system, so the CDE no longer shows who decided what. Both are fixed by testing the workflow during mobilisation: create a dummy container, move it through each state, and check that the record shows who approved each step and when. If the test needs a workaround, the process or the configuration needs changing before real information arrives. Revisit the test when the team or the software changes.
Does a CDE replace a document register?
It usually contains one, generated from the container metadata.
Related: ISO 19650 in plain English · Information requirements · File-name checker · Glossary
Sources
- BS EN ISO 19650-1:2018 and BS EN ISO 19650-2:2018, with the UK National Annex revised in 2021
- UK BIM Framework guidance
Last checked 14 October 2026. Official requirements stay in ISO 19650 and the UK BIM Framework. This is original guidance. Not a design sign-off.