A Common Data Environment (CDE) is the single, shared digital space where all project information is stored, managed, and exchanged by everyone on a construction project. It replaces the chaos of emails, shared drives, and USB sticks with a structured, auditable workflow. ISO 19650 mandates a CDE for BIM projects — but even without a formal BIM mandate, setting one up transforms how a team collaborates.
Why a CDE Matters
Without a CDE, teams end up with multiple versions of the same drawing circulating at once, no clear record of who approved what, and contractors building from superseded information. The CDE solves this by creating a single source of truth — one place where the current, approved version of every document and model lives, and where the history of every change is preserved.
The Four Information States
ISO 19650 defines four states that any piece of information moves through in a CDE:
Work in Progress (WIP): The author is still working on it. Only the author and their immediate team can see it. No one else should be acting on WIP information.
Shared: The information has been checked internally and is now available for other project team members to review, coordinate against, or comment on. It is not yet approved for construction use.
Published: The information has been formally approved by the appointing party (client or their representative) and is authorised for its intended purpose — whether that is design coordination, procurement, or construction.
Archived: The information is no longer current but is retained for record purposes. This includes superseded revisions and as-built documentation.
Naming Conventions and Metadata
A CDE only works if information is findable. That means a consistent file naming convention applied to every document, drawing, and model. ISO 19650 recommends a structured naming format covering project, originator, volume/system, level/location, type, role, and revision. A typical drawing name under this convention looks like: PROJ-ORIG-ZZ-00-DR-A-0001. Every organisation adapts this slightly, but the principle — that the file name tells you everything about the file without opening it — is universal.
Choosing a CDE Platform
There are purpose-built CDE platforms (Autodesk Construction Cloud, Aconex, Asite, Trimble Connect, BIMcollab) and many teams adapt general document management tools (SharePoint, Dropbox) with manual folder structures. Purpose-built platforms are worth the cost on projects with more than three or four active parties — they enforce the workflow states, track approvals automatically, and produce the audit trail that ISO 19650 requires. Adapted general tools work for smaller teams but require discipline to maintain.
Setting One Up: The Practical Steps
Start by defining your folder structure to mirror the four states. Agree a naming convention with all parties before any files are created — changing it mid-project is painful. Set access permissions so WIP folders are private to each originator. Define the approval workflow: who reviews, who approves, and what the turnaround time is. Document all of this in the BIM Execution Plan so every new team member has a reference from day one.
Conclusion
A well-run CDE is not a software problem — it is a process problem that software supports. The platform matters less than the discipline of using it correctly. Get the naming convention right, enforce the four states, and the CDE becomes the backbone of a project that runs on current, trusted information instead of guesswork.