Common Data Environment for Owners: CDE Guide

Common Data Environment For Owners — Definition

A common data environment for owners is a shared, governed digital space where the project and asset information an owner needs is created, checked, approved, stored and accessed according to agreed information requirements and workflows. It combines a digital environment with an information-management process, rather than being only a software product or file repository.

BS EN ISO 19650-1:2018 defines a CDE as a “shared digital space for collecting, managing and disseminating information for all project team members” throughout the asset lifecycle. The UK BIM Framework describes it as the single source of information for a project, used to collect, manage and disseminate relevant approved documents. Its purpose is to reduce the risk of teams using incorrect or outdated information.

For an owner, that means the CDE is governed around the information required to make decisions, administer contracts, control delivery and operate the completed asset. Employer’s Information Requirements and Organisational Information Requirements specify what information is needed, when it is needed and in what format. During operations, Asset Information Requirements support the development of an Asset Information Model under ISO 19650-3.

A CDE is therefore not simply “where the files are”. It defines how information moves from work in progress to shared, published and archived states; who can review or approve it; what metadata identifies it; and which version can be relied upon for a particular decision or activity. A CDE may use more than one technology, but those technologies should behave as one logical information environment under ISO 19650 guidance.

Why Does Common Data Environment For Owners Matter for Document Controllers & Project Coordinators?

Document controllers and project coordinators often carry the operational burden of an owner’s information regime. They maintain registers, issue transmittals, check revisions, route approvals, respond to retrieval requests and preserve the evidence trail. A project may contain thousands of documents, with control needed over versions, permissions, approvals and audit records, according to ACDCC resources and case interviews from 2019–2023.

The problem is not just document volume. In the FMI and PlanGrid report Construction Disconnected (2018), construction professionals were reported to spend 35% of their time on non-productive activities, including looking for project data and correcting mistakes. The same research attributed 52% of rework to poor project data and miscommunication, with a reported US construction cost of $31.3 billion in 2018. Autodesk and FMI reported in Harnessing the Data Advantage in Construction (2019) that more than 25% of project data was recreated because teams could not find existing information.

These findings do not establish a universal saving from adopting a CDE. They do show why information retrieval, revision control and communication are owner-side controls rather than administrative details. If a site team uses a superseded drawing, or a reviewer cannot establish which response was approved, the owner may face rework, delay evidence gaps or a more difficult claims process.

A governed CDE gives the document controller a defined operating model:

• Information has a state and suitability for use, rather than only a folder location.
• Revisions, approvals and transmittals are connected to an auditable record.
• Access rights distinguish visibility and authority from information status.
• RFIs, submittals, drawings, specifications and site records can be related to the information they concern.
• Handover information can be assembled progressively instead of reconstructed at practical completion.

For project coordinators, the practical question is often: how does a CDE help with RFIs and submittals? It creates a controlled route from submission to review, response, approval and closure, with the relevant drawing, specification or contract reference attached to the record. The exact workflow remains a project decision, but the principle is that the transaction and its source information should remain connected.

The owner also needs to preserve information beyond a single construction package or contractor portal. ISO 19650-3’s operational-phase approach recognises that design intent, as-built conditions, warranties, operation and maintenance manuals and future refurbishment information may need to remain linked over the asset lifecycle. A CDE designed only for today’s document exchange can leave tomorrow’s facilities team with fragmented records.

Key Components / How It Works

1. Information requirements define the outcome

The owner should begin with the information required for governance and delivery, not with a folder structure. OIR, EIR, project information requirements and AIR describe the information to be produced, its timing, its format and its intended use. This gives the project team a basis for deciding what must be submitted, reviewed, published and retained.

For example, an owner may require approved design information for construction, evidence supporting a variation, inspection records for quality assurance and an organised set of operation and maintenance documents for handover. Each requirement should identify the accountable role, required milestone and acceptance conditions.

2. Information states control suitability for use

ISO 19650-aligned workflows commonly distinguish work in progress, shared, published and archived information. WIP is under development and should not be relied upon by others. Shared information is made available for coordination. Published information is suitable for an authorised construction or operational use. Archived information is retained as a record.

These states are not the same as permissions. A document can be visible to a role without being suitable for construction use. The CDE should represent state through metadata and workflow so that downstream users do not take quantities, instructions or decisions from WIP information.

3. Metadata and naming make information retrievable

File names, classification, revision identifiers, document types, suitability codes and other metadata provide the structure needed for search and reporting. Projects may use classification systems such as Uniclass, OmniClass or ISO 12006, subject to the information standard agreed for that project.

Naming rules are not cosmetic. Inconsistent naming and incomplete metadata make retrieval unreliable, particularly when people search across drawings, specifications, RFIs, submittals and correspondence. The owner’s information standard should define the minimum fields required before information can move to the next state.

4. Workflows connect people to decisions

A CDE should route information to the role responsible for checking, reviewing or approving it. That may include the design manager, consultant, contractor, owner’s engineer, quantity surveyor, project manager or owner representative. The workflow should record the action, date, status and response, while preserving the submitted revision.

An RFI workflow might link the question to a drawing revision and specification clause, assign it to the responsible reviewer, record the response and publish the outcome for authorised use. A submittal workflow might capture the product or material, supplier, specification reference, review status, comments and resubmissions. A change-control workflow can preserve the relationship between the instruction, cost assessment, schedule effect and approved record.

5. Permissions and audit trails protect the record

Role-based access controls determine who can view, create, edit, share or approve information. This matters when external vendors, consultants and contractors contribute to the owner’s project record. An audit trail should show who changed what and when, supporting governance and later reconstruction of events.

That evidentiary function is relevant to claims and disputes. Arcadis’ Global Construction Disputes Report 2024 and HKA’s CRUX Insight series (2019–2024) identify conflicting drawing versions and unclear communication records among issues associated with construction disputes. A CDE does not eliminate disputes or prove causation, but a governed record can make the project’s information history easier to examine.

6. The CDE continues into handover

For an owner, practical completion is not the end of information management. A progressive approach links approved design information, as-built records, warranties, O&M manuals, commissioning evidence and other required asset information as the project develops. ISO 19650-3 provides the operational-phase context for this continuity and the development of an Asset Information Model.

Common Data Environment For Owners vs Related Terms

The term CDE is used both in the strict ISO sense and as a broader label for cloud platforms that centralise construction information. The distinctions below help owners assess whether an environment is governed as a CDE, rather than relying on the product label.

How is a CDE different from a shared drive in practical terms? A shared drive answers “where can I place this file?” A governed CDE also answers “what is this information, which revision is it, who may rely on it, what review has occurred, and what record should be retained?”

Real-World Example / Use Case Walkthrough

Consider a generic private developer delivering a major mixed-use project through several consultants and trade contractors. At the start, drawings and specifications are exchanged through email, shared drives and specialist tools. An RFI register is maintained in a spreadsheet. Submittals arrive as attachments, while the document controller separately updates a transmittal log. Different teams keep local copies of drawings.

The immediate difficulty is not that information is absent. It is that the owner cannot reliably determine which version is current, whether a response was formally issued or which record supports a later change. A project coordinator spends time checking inboxes and registers rather than resolving exceptions. At handover, the team must search across drives and contractor submissions for warranties, manuals and as-built information.

The owner then defines an ISO 19650-aligned information standard. It sets the required naming and metadata fields, the WIP-to-shared-to-published route, approval responsibilities, access rights, retention expectations and handover requirements. The CDE becomes the agreed logical environment, even where connected technologies remain in use.

For an RFI, the document controller records the question against the relevant drawing revision and specification reference. The workflow routes it to the responsible reviewer, records comments and preserves the response. Once approved for use, the response and associated information move to the appropriate published state. A dashboard can then show open RFIs, overdue reviews, response dates and affected work packages.

For a submittal, the record includes the supplier or contractor submission, product information, specification reference, review status, comments and resubmissions. The owner’s team can distinguish a submitted item from an accepted item and retain the decision trail. The process does not guarantee that every review is timely; it makes the status and accountability visible.

At handover, the owner does not begin with a blank request for “all documents”. Required asset information has been identified earlier, checked as it is produced and linked to the relevant project records. Missing or non-conforming information can be reported before the final closeout period.

What should a document controller measure in this scenario? Start with on-time information delivery, completeness against the EIR or AIR, naming and metadata conformance, revisions caused by incorrect information, RFI and submittal cycle time, document-related nonconformances and retrieval time. Do not apply an industry-wide target without evidence: the research identifies no globally comparable benchmark for average RFI cycle time or a universal CDE performance threshold.

How Zepth Approaches This

Zepth approaches the CDE as a common data layer for project and asset information rather than only a document repository. In Zepth Core for documents, RFIs and submittals, project teams can organise these workflows alongside quality, safety, site operations, project controls and risk management. Zepth AI supports document classification, retrieval and review across the connected information environment; it can review submittals and RFIs against drawings and specifications with a confidence score, draft RFI responses with cited references and surface risks for human review.

That distinction matters for governance. AI can help identify and connect information, but a human remains responsible for signing off consequential actions. The quality of any AI result also depends on the underlying information discipline: reliable revisions, metadata, permissions and approved states. In that sense, the CDE is both the owner’s information-control framework and the foundation on which AI-assisted project work can be evaluated.

Owners should assess any platform against their own EIR, AIR, approval matrix, information standard, contractual obligations and handover requirements. The relevant question is not whether a product uses the CDE label; it is whether the configured environment gives the owner a traceable, usable record across delivery and operations.

FAQ

A practical next step is to map the owner’s information requirements to the workflows, roles, states and evidence needed on each project. To discuss how that framework can be applied, schedule a walkthrough.