What Is CDE? Common Data Environment Explained for BIM & Construction

A Common Data Environment (CDE) is a single, managed digital space where all project information — models, drawings, documents, and data — is stored, shared, reviewed, and approved by all project participants throughout the lifecycle of a construction or BIM project.

Rather than a simple folder on a server, a CDE is a structured information management system with defined workflows, access controls, version history, and approval processes that ensure every team member is working from the correct, current information.

What Does CDE Stand For?

CDE stands for Common Data Environment.

The term was formalized within the BIM and construction industry to describe a controlled, centralized information repository for AEC projects. It appears prominently in ISO 19650, the international standard for managing information over the whole life cycle of a built asset.

Within a CDE, project information is not limited to drawings or models alone. It encompasses:

BIM models and federated models
Drawings and technical documents
Specifications and schedules
Contracts and correspondence
Point cloud data and survey information
Reports, submittals, and RFIs
Operation and maintenance data

The word common is important. It means the environment is shared across all disciplines and project participants — architects, engineers, contractors, clients, and facility managers — within a single governed space, rather than fragmented across individual inboxes or disconnected drives.

What Is a Common Data Environment?

At its simplest, a CDE is the project’s single source of truth for information.

When an architect updates a floor plan, that revision is uploaded to the CDE. The structural engineer, MEP consultant, and contractor all access the same updated drawing from the same place. No one is working from an emailed attachment from three weeks ago.

For AEC professionals, a more technical explanation: a CDE is an information management platform — or a defined set of processes operating on an existing platform — that applies structured workflows, metadata standards, naming conventions, status codes, revision control, and access permissions to all project information containers.

A CDE is not simply a cloud storage folder.

Storing project files in an unstructured cloud folder without naming conventions, version control, approval workflows, or defined permissions is not a CDE. The defining characteristic of a CDE is the management of information, not just the storage of it.

Why Is CDE Important in BIM?

BIM projects generate large volumes of information across multiple disciplines, revisions, and project stages. Without a controlled environment, that information becomes unreliable — teams work from different versions, clash detection is compromised, approvals are missed, and handover documentation is incomplete.

A properly implemented CDE supports:

Collaboration — All disciplines access the same information from the same location
Version control — Only the current approved version is active; previous versions are retained but clearly superseded
Coordination — MEP, structural, and architectural models are shared for clash detection against consistent, current data
Design review and approval — Formal review workflows ensure information is checked before it is published for construction use
Information security — Role-based permissions mean each participant can access only what they are authorized to see
Project traceability — Every action — upload, comment, approval, rejection — is logged with a timestamp and user record
Reduced duplication — One master information source eliminates the parallel file copies that cause errors
Better information management — Metadata, status codes, and structured naming make information retrievable and auditable throughout the project

How Does a CDE Work?

A CDE organizes project information through defined information states. ISO 19650 describes these states conceptually, though different platforms implement them with slightly different labels and workflows.

The four commonly referenced information states are:

WIP → Shared → Published (Documentation) → Archived

Work in Progress (WIP)

Information in WIP is being actively created or edited by the responsible team. It is not yet ready for others to rely on. Each team member or discipline typically has a private WIP space where work is prepared before it is shared with the wider project team.

Shared

Once information is ready for review, coordination, or comment by other project participants, it moves to the Shared state. At this point, other teams can see and use the information — for example, a structural engineer can reference an architect’s shared model for coordination — but the information has not yet been formally approved.

Published (Documentation)

Information that has completed the review and approval process moves to the Published state. Published information is authorized for its intended use — for example, for construction or procurement. This is the authoritative version that teams rely on for formal decisions and contract deliverables.

Archived

Superseded or historical versions of information are retained in the Archive. This ensures that a full audit trail of the project’s information history is maintained — important for contract disputes, as-built records, and future reference.

It is worth noting that ISO 19650 defines these states as a framework rather than prescribing specific software workflows. Platform implementations vary, and some platforms use different terminology while following the same underlying logic.

CDE Workflow in BIM Projects

Here is a practical example of how information moves through a CDE on a multi-discipline building project:

The architect creates and develops the architectural BIM model in their WIP space.
When ready for coordination, the architect publishes the model to the Shared area with the appropriate status code and metadata.
The structural engineer references the shared architectural model and develops the structural model in their own WIP space.
The structural model is shared for coordination once ready.
The MEP engineer does the same — working in WIP, then sharing the MEPF model.
The BIM Coordinator federates the models, runs clash detection, and raises issues through the CDE’s issue management system.
Discipline leads respond to clashes, update their models, and re-share revised versions.
Once coordination is resolved, information is submitted for formal review and moves through the approval workflow.
Approved information is Published — available for the contractor to use for construction.
Previous versions are moved to Archive, preserving the revision history.

This workflow ensures that at every point, each participant knows the status of any piece of information and whether it is authorized for their intended use.

Key Features of a CDE

Feature	What It Does	Why It Matters
Version control	Tracks every revision of a file with timestamps	Prevents teams from using outdated information
Revision management	Manages formal revision sequences	Maintains a clear history of document evolution
Access permissions	Controls who can view, upload, or approve information	Protects sensitive information and maintains accountability
Approval workflows	Routes information through defined review and authorization steps	Ensures only checked information is released for use
Document management	Organizes and stores all project documents	Provides structured access to the complete information set
Model sharing	Allows BIM models to be shared for coordination and review	Enables multi-discipline collaboration and clash detection
Metadata	Attaches structured attributes to information containers	Makes information searchable, filterable, and auditable
Audit trails	Records all actions with user and timestamp data	Supports accountability and dispute resolution
Issue tracking	Manages clash reports, RFIs, and design queries	Keeps coordination and problem resolution organized
Notifications	Alerts relevant parties when action is required	Keeps workflows moving without manual chasing
Search and filtering	Allows retrieval of information by metadata, status, or keyword	Reduces time spent locating current documents
File naming standards	Enforces consistent naming conventions	Ensures information is identifiable without opening files
Status management	Assigns and tracks information status codes	Communicates the suitability of information for its intended use
Transmittals / information exchange	Formally records the issue of information to other parties	Provides a contractual record of what was issued, when, and to whom

CDE vs Traditional File Sharing

Many project teams operate with informal file sharing that creates serious information management risks. Here is how a structured CDE compares:

Capability	Email & Attachments	Network Drive / Shared Folder	Cloud Folder (unstructured)	CDE
Single source of truth	✗	Partial	Partial	✓
Version control	✗	✗	Limited	✓
Access permissions by role	✗	Basic	Basic	✓
Approval workflows	✗	✗	✗	✓
Audit trail	✗	✗	Limited	✓
Status/revision tracking	✗	✗	✗	✓
Metadata and search	✗	✗	Limited	✓
Issue management	✗	✗	✗	✓
Transmittal records	✗	✗	✗	✓
BIM model coordination	✗	✗	✗	✓

It is worth clarifying: some cloud platforms — when configured with defined naming conventions, folder structures, permissions, and workflows — can support CDE-like functions for simpler projects. The distinction lies in the degree of information management maturity, not simply whether files are stored online.

For complex BIM projects, purpose-built CDE platforms provide the structured workflows, model viewing, and metadata management that generic file storage cannot reliably replicate.

CDE vs Document Management System

A Document Management System (DMS) focuses primarily on the storage, retrieval, and version control of documents. Many DMS platforms provide approval workflows and access controls and serve this function well.

A CDE extends beyond document management to encompass the full project information environment — including BIM models, federated model coordination, spatial data, issue management, and information state workflows that align with standards such as ISO 19650.

In practice, the terms sometimes overlap. Some document management platforms have evolved into platforms that support CDE-level workflows. Others remain focused on document-centric functions.

The key distinction is that a CDE is designed around the full information lifecycle of a built asset, while a DMS is primarily organized around the management of individual documents. For BIM-intensive projects, the additional capabilities of a purpose-built CDE are generally significant.

CDE and ISO 19650

ISO 19650 is the international standard for managing information over the whole life cycle of a built asset using BIM. It is closely associated with CDE workflows but is itself a standard, not a software platform.

ISO 19650 defines requirements for:

Information management across the project lifecycle
Information containers — named and structured units of information (models, drawings, documents)
Naming conventions — systematic metadata embedded in file names
Status and revision information — codes that communicate the suitability of information for use
Permissions and access control
Review and approval processes
Information states — the WIP, Shared, Published, and Archived framework described earlier

The standard specifies what should be managed and how information should move through defined states. The CDE is the environment — whether a specific platform or a defined set of processes — within which those requirements are implemented.

ISO 19650 also refers to the Employer’s Information Requirements (EIR) and the BIM Execution Plan (BEP), which define the project’s specific information management requirements and how the project team will meet them. Both of these are closely related to how the CDE is configured and used on a given project.

For teams working on projects where ISO 19650 compliance is required — particularly UK public-sector projects and international clients with BIM mandates — the CDE configuration is a direct expression of the standard’s requirements.

Common Data Environment in Construction

A CDE is relevant at every stage of a construction project, not only during design.

Design Stage — Architects and engineers develop and share models and drawings. The CDE manages revisions, coordinates between disciplines, and maintains the review and approval process.

Coordination Stage — The BIM coordinator and discipline leads use the CDE to share federated models, run clash detection, raise and resolve issues, and track coordination progress.

Procurement Stage — Tender drawings, specifications, and bills of quantities are issued formally through the CDE with transmittal records confirming what was issued to whom and when.

Construction Stage — The contractor and subcontractors access construction-issue drawings and models. RFIs, submittals, and site instructions are managed through the CDE’s issue and correspondence workflows.

Handover Stage — Operation and maintenance documentation, as-built models, warranties, and handover records are compiled and delivered to the client through the CDE, ensuring a complete and auditable information package.

Operations Stage — Asset information from the CDE can be transferred to facilities management systems, supporting the ongoing operation and maintenance of the completed building.

Benefits of Using a CDE

One controlled information source — All participants work from the same data, reducing the risk of decisions made on outdated files
Better collaboration — Disciplines share information in a structured, transparent environment
Fewer outdated files in circulation — Status codes and version control make it clear which information is current
Improved traceability — Every revision, approval, and transmittal is recorded with a full audit trail
Faster information retrieval — Structured metadata and search functions reduce time spent locating documents
Better coordination — Current models are available for clash detection against consistent, controlled data
Improved project transparency — Owners and project managers can monitor information progress in real time
Reduced duplication — A single repository eliminates parallel file copies
More controlled approvals — Formal workflows ensure information is reviewed before it is used for critical decisions
Better handover information — Structured, auditable information from the CDE forms a reliable basis for the building’s operational record

Common CDE Platforms

Several platforms are widely used to support CDE and project information management workflows in AEC projects. The right platform depends on project size, team preferences, contract requirements, and the level of BIM maturity involved.

Autodesk Construction Cloud (ACC) / Autodesk Docs is widely used across commercial, infrastructure, and large residential projects. It supports model coordination, document management, issue tracking, and approval workflows, and integrates with Revit and other Autodesk tools.

Bentley ProjectWise is commonly used on large infrastructure, engineering, and civil projects. It provides strong support for ISO 19650 workflows and handles complex, multi-discipline information environments.

Trimble Connect supports BIM collaboration, model viewing, and project coordination, and is often used with Tekla and other Trimble products. It suits structural and construction-focused workflows.

Asite provides cloud-based CDE, document management, and collaboration tools with a focus on ISO 19650 alignment, commonly used on UK public-sector and infrastructure projects.

Viewpoint offers construction-focused project management and document control with CDE-supporting features, often used by main contractors.

Dalux provides mobile-first BIM and document management tools with strong on-site use cases, supporting both design coordination and construction information access.

This is not an exhaustive list, and no single platform is universally best. Platform selection should be based on project requirements, client standards, existing software ecosystems, and team capability.

How to Implement a CDE on a BIM Project

Define project information requirements — Establish what information needs to be produced, by whom, at what stage, and in what format. This is often captured in the Employer’s Information Requirements (EIR) and the BIM Execution Plan.
Establish information standards — Agree on the naming conventions, status codes, revision sequences, and metadata attributes that will be used on the project.
Define the information structure — Design the folder and container structure within the CDE to reflect the project’s discipline breakdown, information types, and stages.
Define roles and permissions — Determine who can upload, view, comment, approve, and archive information. Assign permissions accordingly.
Define review and approval workflows — Map out the formal review process for each information type, including who is responsible for review and sign-off.
Establish revision and status procedures — Define how revisions will be managed and which status codes apply at each information state.
Configure the platform — Set up the chosen CDE platform to reflect the agreed standards, structure, permissions, and workflows.
Train project participants — Ensure that all team members understand the CDE workflows, naming conventions, and their specific responsibilities. Poor training is the most common cause of CDE failures.
Issue the BIM Execution Plan — Document and distribute the agreed information management approach so all participants have a common reference.
Monitor and improve — Audit the CDE regularly during the project to identify naming inconsistencies, permission issues, or workflow bottlenecks, and address them promptly.

CDE Best Practices

Enforce consistent naming conventions from day one — Naming inconsistencies compound over time and become very difficult to resolve mid-project
Define permissions carefully — Overly broad permissions create security risks; overly restricted permissions create workflow bottlenecks
Assign clear responsibilities — Every information container should have a clearly identified owner responsible for its management
Control revisions formally — Informal updates outside the CDE workflow undermine the entire system
Avoid duplicate information — If a file exists in the CDE, it should not also exist in email threads or personal drives
Audit the CDE regularly — Periodic reviews catch naming errors, permission drift, and orphaned files before they cause problems
Define approval workflows explicitly — Vague review processes result in information being used before it is authorized
Manage information security — Sensitive commercial, contractual, or design information should be visible only to parties with a legitimate need
Apply project-wide standards — All disciplines and subcontractors should use the same naming, status, and metadata conventions
Train all users, not just BIM managers — The CDE is only as effective as its least-trained regular user

Common CDE Challenges — and How to Address Them

Poor user adoption is the single most common CDE problem. Teams revert to email and shared drives because they are familiar. Solution: Mandate CDE use contractually and provide structured onboarding for all participants, not just technical leads.

Inconsistent naming undermines searchability and version control. Solution: Publish a project-specific naming convention guide and enforce it from the first upload.

Incorrect permissions either expose sensitive information or prevent legitimate users from accessing what they need. Solution: Map permissions carefully during setup and review them whenever team membership changes.

Duplicate information — the same file in multiple locations with different revision levels — is a sign that the CDE is being bypassed. Solution: Make CDE use the path of least resistance by training teams effectively and removing alternative file sharing habits.

Poor folder structures make information hard to find and encourage workarounds. Solution: Design the structure before the project begins, based on how information will be used, not how it is created.

Lack of training leads to incorrect status codes, missing metadata, and workflow errors. Solution: Training should be project-specific, not generic platform training alone.

Platform fragmentation — where different project participants use different platforms — forces information to be manually transferred and breaks the CDE concept. Solution: Agree on a single CDE platform contractually at project outset.

Incorrect status or revision usage confuses information suitability. Solution: Provide a concise status code reference sheet specific to the project.

Unclear responsibilities mean that no one knows who should approve what. Solution: A RACI matrix or responsibility matrix in the BIM Execution Plan resolves this.

Excessive notifications cause notification fatigue and missed actions. Solution: Configure notifications thoughtfully — alert the right people for the right actions, not everyone for everything.

CDE Example: A Commercial Office Building Project

Consider a six-storey commercial office project with an architect, structural engineer, MEP engineer, BIM coordinator, and main contractor.

Stage 1 — Design Development
The architect develops the architectural Revit model in their WIP space. When the floor plans and building envelope reach a coordination-ready state, the model is uploaded to the Shared area with status code S2 (suitable for coordination) and the correct metadata — discipline, project number, revision, date.

Stage 2 — Coordination
The structural engineer references the shared architectural model and develops the structural model, sharing it when ready. The MEP engineer does the same with the MEPF model. The BIM coordinator downloads all three models, federates them in Navisworks, and runs clash detection. Clashes are raised as issues within the CDE, assigned to the relevant discipline lead with a resolution deadline.

Stage 3 — Issue Resolution
The MEP engineer resolves the ductwork clashes and re-uploads the updated model. The BIM coordinator confirms clash resolution and closes the issues.

Stage 4 — Review and Approval
The coordinated models and associated drawings are submitted for client review through the CDE’s approval workflow. The client’s representative reviews, annotates, and formally approves or returns with comments. Comments are tracked and addressed.

Stage 5 — Construction Issue
Approved information is moved to Published status — suitable for construction — and the contractor is notified. A formal transmittal is generated, recording exactly what was issued and when.

Stage 6 — Archive
Previous revisions of all information are moved to Archive, maintaining a complete revision history for contractual reference.

When the project completes, the full CDE — models, drawings, approvals, RFIs, submittals, and correspondence — forms the basis of the handover information package, which can be transferred to the client’s facilities management system.

CDE vs BIM

BIM and CDE are related but distinct concepts that work together rather than compete.

BIM	CDE
A process for creating and managing digital information about a built asset	The environment in which that information is stored, shared, and managed
Focuses on model creation, coordination, and information production	Focuses on information management, version control, and access governance
Produces models, drawings, data, and documentation	Provides the controlled space through which that information is exchanged
A methodology applied by project participants	A platform or defined set of processes applied to the project information environment
Can exist without a formal CDE (though with greater risk)	Is designed specifically to support BIM information management at scale

Put simply: BIM produces the information. The CDE manages it.

Frequently Asked Questions

1. What is CDE in BIM?
In BIM, a CDE (Common Data Environment) is a centralized, managed information environment where all project models, drawings, documents, and data are stored, shared, reviewed, and approved. It provides the controlled infrastructure through which BIM information is exchanged between architects, engineers, contractors, and clients across the project lifecycle.

2. What does CDE stand for?
CDE stands for Common Data Environment. The term is used in BIM and construction information management to describe a single, structured space where all project participants access and contribute to the same controlled set of project information.

3. Why is CDE important in construction?
A CDE ensures that all project participants are working from the same, current information. It reduces errors from outdated files, provides an audit trail, supports formal approval workflows, and improves coordination between disciplines — all of which are critical to the successful delivery of complex construction projects.

4. Is CDE required for BIM?
A CDE is not always legally mandatory, but it is strongly recommended — and increasingly required — for projects following ISO 19650 or public-sector BIM mandates. For Level 2 BIM and beyond, a CDE is considered a fundamental component of sound information management practice.

5. What is the difference between CDE and BIM?
BIM is a process and methodology for creating and managing digital building information. A CDE is the environment — a platform or structured set of processes — in which that information is stored, shared, reviewed, and controlled. BIM produces the information; the CDE manages it.

6. What are the four CDE states?
The four commonly referenced information states in a CDE are: Work in Progress (WIP) — information being actively developed; Shared — information ready for coordination or review by others; Published (Documentation) — approved information authorized for its intended use; and Archived — superseded or historical information retained for reference.

7. Is CDE a software?
A CDE can be implemented through dedicated software platforms — such as Autodesk Construction Cloud, Bentley ProjectWise, or Asite — but it is fundamentally a concept and a set of information management processes. The software is the tool; the workflows, standards, and governance are what make it a true CDE.

8. What is CDE according to ISO 19650?
ISO 19650 defines a CDE as an agreed-upon source of information for any given project or asset, used to collect, manage, and disseminate each information container through a managed process. It describes information states (WIP, Shared, Published, Archived) and the governance framework for managing project information containers consistently.

9. What information is stored in a CDE?
A CDE can store BIM models, architectural and engineering drawings, specifications, schedules, reports, submittals, RFIs, meeting minutes, contracts, point cloud data, operation and maintenance documentation, and any other project information that needs to be managed, shared, and controlled across the project team.

10. What are examples of CDE platforms?
Widely used CDE platforms include Autodesk Construction Cloud (Autodesk Docs), Bentley ProjectWise, Trimble Connect, Asite, Viewpoint, and Dalux. The choice of platform depends on project size, team preferences, client requirements, and the level of BIM integration required.

11. Who uses a CDE?
A CDE is used by all project participants who produce, review, or rely on project information — including architects, structural engineers, MEP engineers, BIM coordinators, contractors, subcontractors, project managers, clients, and facilities managers.

12. How does CDE improve BIM collaboration?
A CDE improves BIM collaboration by providing a single, controlled information source that all disciplines access consistently. It eliminates version confusion, enables formal coordination workflows, provides an audit trail of all actions, and ensures that information is reviewed and approved before it is used for critical decisions — reducing errors and improving overall project communication