“Which one’s the latest?” “Who has that file?” The further a project goes, the messier version control and file whereabouts get. The idea that prevents this is the CDE (Common Data Environment).
- A CDE is a single place to manage and share a project's information
- It makes clear "which is the latest, which is approved" so everyone sees the same thing
- Information moves through states: Work in Progress → Shared → Published → Archive
- ISO 19650 frames the CDE within international information management
Why a CDE is needed
In BIM, many parties — design, construction, MEP — exchange models, drawings and documents constantly. Run that through email attachments and personal folders and you quickly hit:
- Nobody’s sure which version is current (work continues on an old one)
- The same file scattered across multiple places
- No distinction between “approved” and “still under review”
- No trace of who updated what, and when
A CDE solves this by consolidating everything into one trusted home — creating a single source of truth.
Information status states
The crux of a CDE isn’t just storage; it’s separating information by state. ISO 19650 organises this roughly as:
Work in Progress
Being edited within a team. Not shared externally yet.
Shared
Shared for cross-discipline review and coordination. Open to checks and comments.
Published
Approved and fixed as a formal deliverable.
Archive
A record of past versions, kept so the history can be traced.
With these states, everyone can tell “shared but not yet approved” at a glance, preventing rework on stale or unconfirmed versions.
Relationship to ISO 19650
A CDE isn’t the name of a single tool; it’s an information-management mechanism. Its international framework is ISO 19650, which structures everything from the client’s requirements to the handover of deliverables. Within it, the CDE is positioned as the central machinery for circulating information. The same framework defines the client’s requirements (the EIR) and the delivery team’s response to them — the BEP (BIM Execution Plan).
How a small team can start
You don’t need a heavyweight platform to adopt the CDE mindset.
- Pick one home: enforce “the latest exists only here.”
- Express version and status in names: make WIP / Shared / Published obvious at a glance.
- Share by link: don’t duplicate-and-distribute files; point people at the same place. A model like Bimly’s share links, where recipients always see the same model, is ideal.
Even just reaching “everyone can instantly say where the latest version is” cuts the chaos dramatically.
Summary
- A CDE is a single place to manage and share project information.
- The crux is separating information into WIP → Shared → Published → Archive.
- ISO 19650 frames the CDE internationally.
- The goal isn’t buying a tool but a practice where latest, status and history are clear.
Ending the information lost-and-found is a fast route to feeling BIM’s benefits. Start small, with a single home.