Common Data Environments in Practice: A Guide for Australian AEC Teams

A common data environment (CDE) is the controlled project record that tells your AEC team what is current, what can be used, and who approved it.

That control matters when approvals sit in email, models stay on discipline servers, and contracts live in separate cloud drives.

The files may all be accessible, but the team can still issue the wrong revision or lose the history behind a decision.

If you lead project delivery, BIM, or operations, the business case is practical: Reduce avoidable rework, find information faster and preserve evidence when a client, tender panel or commercial reviewer asks how the project was controlled. Start with what a CDE actually controls.

In this guide, we explain what a CDE controls, how it works under ISO 19650, and what Australian AEC teams should consider when selecting and implementing.

What Is a Common Data Environment (CDE)?

A common data environment is an agreed workflow and information environment for collecting, managing, sharing, and retaining project or asset information.

Rather than simply providing a central place to store files, a CDE controls how information moves through a project.

It helps teams identify which information is being developed, what has been shared for coordination, what has been authorised for use, and what should be retained as part of the project record.

This creates a more consistent way for architects, engineers, contractors and other project stakeholders to work with project information.

The ISO 19650-1 framework covers the exchange, recording, versioning and organisation of information across the built asset lifecycle. In practical terms, a CDE brings three elements together:

Element	What It Controls	Practical Question It Answers
CDE workflow	Identification, checking, review, authorisation, sharing and archiving	What can this information be used for?
CDE solution	The document, model, workflow and reporting technology	Where does the controlled process run?
Project record	Models, drawings, specifications, RFIs, submittals, approvals and asset data	Which information is current and traceable?

For reference, the UK BIM Framework’s official CDE guidance confirms that one project workflow may span several connected solutions.

The single source of truth is therefore the governed record, not necessarily one database or one software vendor.

How a CDE Works: The Four States of Information

A CDE works by moving each information container through four controlled states: Work in Progress, Shared, Published and Archived.

Here, an information container means a model, drawing, document, or dataset managed as one unit. 

Its assigned state tells project participants whether the information may be developed, coordinated, relied on or retained as a record.

In practice, the state communicates permitted use and approval status, rather than simply indicating where a file is stored.

The distinctions become easier to see once the four states are matched with their permitted actions and levels of reliance:

Information State	What Happens	What the Team Can Rely on
Work in Progress (WIP)	The originating task team develops and checks its information.	Other teams should not use it for coordination, approval or construction.
Shared	Checked information is released to authorised recipients for a stated purpose, such as coordination or review.	Recipients may use it only for that purpose. Shared does not mean approved for construction.
Published	Information has passed the required authorisation and acceptance gates.	The approved audience may rely on it for its authorised project or asset use.
Archived	The CDE retains previous states, revisions and transaction history.	The project can reconstruct what changed, when it changed and what was issued.

Each state has a defined purpose. In this case, across all four states, three controls keep the workflow reliable in day-to-day project delivery:

• Movement is controlled: information can return from Shared to WIP for revision before it is shared again.
• Metadata carries meaning: the identifier, status, revision, and classification show what the container is and how it may be used.
• History is retained: the archive preserves the path from early work to the current project record.

CDE vs BIM (and vs a Shared Drive): Clearing Up the Confusion

For AEC projects, BIM, a CDE, and shared file storage often work alongside each other, but they are not the same thing. Understanding the difference is important when deciding how project information should be created, coordinated, reviewed, and controlled.

A CDE governs project information, BIM creates and uses structured asset information, and a shared drive mainly stores files. 

The distinction matters because these three can exist within the same project but serve different purposes.

A BIM workflow may generate models and structured data, while the CDE controls how that information is checked, shared, approved, and retained.

A shared drive may store project files, but without the appropriate controls, it does not necessarily provide the workflow or traceability needed to manage project information reliably.

The table below shows how CDE, BIM, and a shared drive differ.

Key Area	CDE	BIM	Shared Drive or Generic Cloud Storage
Primary job	Controls review, approval, exchange and retention	Produces and uses model-based information	Stores and shares files
Information state	Applies WIP, Shared, Published and Archived states	Produces information that can pass through those states	May show file versions without proving suitability or approval
Traceability	Records revisions, transmittals, reviews and approvals	Depends on the surrounding management process	Often limited to file history and user activity
Project role	Holds the governed project record	Supports design, coordination, delivery and operation	May remain one disconnected repository among several

For Australian AEC teams, the point of difference affects how model‑based work is coordinated and what a storage platform must do to support controlled project information:

• BIM management coordinates the people, standards, roles and tools around model-based delivery.
• A CDE gives that work a controlled route between teams.
• A shared drive can form part of a CDE only when it enforces required metadata and permissions and supports workflow states, approval gates and audit history.

In short, folder access and automatic versioning alone are not enough.

The CDE Under ISO 19650 in Australia

Under Australia’s AS ISO 19650 standards, the CDE provides the controlled workflow for organising, exchanging, versioning and recording project information.

Standards Australia adopted ISO 19650’s concepts and principles as AS ISO 19650.1:2019 and its delivery-phase requirements as AS ISO 19650.2:2019.

These controls can also strengthen an Australian AEC firm’s tender response.

Let’s say your client asks for ISO 19650-aligned information management, your bid team can show how revisions, approvals and exchanges will be governed from mobilisation.

To make that commitment credible, define the following controls before delivery starts:

Control Area	What the project should define	Practical business value
Ownership and authority	Who provides the CDE and who can review, authorise or accept information	Shows the client who is accountable before delivery starts
Identification and metadata	Naming, status, revision and classification rules	Reduces ambiguous submissions and makes deliverables easier to check
State transitions	The gates between WIP, Shared, Published and Archived	Stops preliminary work being treated as approved information
Access and audit history	Permissions, onboarding, offboarding and retained transaction records	Supports secure collaboration and provides evidence if a decision is challenged

A well‑established BIM management plan can turn these controls into project rules people can follow. Let the client brief, contract and project information standard determine the detail.

Also, do not copy another country’s national annex without first checking the Australian project requirements.

Benefits of a CDE for AEC Project Delivery

The main benefit of a CDE is more controlled project delivery. It reduces version errors, search time, and data silos while strengthening accountability and access control.

The value comes from matching each common project problem with a control that governs how information is issued, used, and traced:

Project Problem	What CDE Control	The Outcome
Outdated drawings or models	Current revisions and controlled publishing	Less risk of coordination or site work using superseded information
Information spread across systems	One governed record connecting files, reviews and approvals	Less time spent reconciling email, servers and cloud folders
No clear decision history	Review, approval, transmittal and revision records	Stronger evidence for change discussions, delay reviews or disputes
Slow document searches	Consistent identifiers, metadata and workflow status	Staff can find the current item and see its review status faster
Broad external access	Permissions by role, organisation or package	Consultants get the access they need without opening the wider project record

A CDE gives your team a faster way to spot exceptions, confirm the current revision and trace the decision behind a change.

These benefits become particularly important on large or complex projects, where information needs to move between multiple disciplines, systems and stakeholders without losing its context or history.

The Infrastructure NSW case study on Sydney Metro City shows how this works in a technically complex project environment.

Sydney Metro’s digital engineering team used a CDE to connect Building Information Modelling (BIM), Geographic Information System (GIS) data and project data building blocks on a common platform.

This allowed information to be shared and used across multiple systems rather than remaining isolated within individual team tools.

Infrastructure NSW reports that the approach improved information exchange, reduced errors and sped up decision-making.

It also helped the project team identify design and construction issues earlier, before construction commenced.

Technically, that outcome depended on connecting the relevant systems through clear data standards, defined information requirements and a controlled CDE workflow.

Choosing and Setting Up a CDE: Software and What to Consider

Choose and set up a CDE in three stages: Define the workflow, assess the software against it, then configure, pilot and govern the selected platform.

This sequence prevents product features from setting your project rules, which will answer three practical questions:

• What should the workflow control?
• Whether the software can support it?
• Whether the set-up will work under live delivery conditions?

Define the Workflow Before Selecting Software

You need to define the information workflow before comparing software, which is why always start with a structured BIM implementation process. 

The main idea is to map a representative handoff from authoring through checking, coordination, approval and issue. That path should define:

• The information and deliverables required
• The purpose of each WIP, Shared, Published and Archived transition
• Naming, status, revision and classification metadata
• Review, approval and access responsibilities
• Retention, handover and export requirements.

Assess software against project delivery risks

Assess CDE software against the project handoffs and risks it must manage, not brand familiarity.

Shortlist BIM consulting software options against the controls that matter in day-to-day delivery:

Key Area	What to Verify
Workflow and approvals	Can the platform apply the four states and configurable review gates?
Metadata and search	Can it enforce identifiers and filter by status, revision, discipline or package?
Revision and audit history	Can users see superseded information, transmittals, comments and approvals?
Access and identity	Can permissions be controlled by user, role and organisation, with suitable sign-in and offboarding controls?
AEC information exchange	Can models, drawings and data move between project tools without losing the source record or required metadata?
Resilience and exit	Do backup, recovery, retention, data location and bulk export meet the client and contract requirements?

Then, test the shortlist with the people who will use it. If site staff cannot find the current drawing or reviewers bypass the approval route, the platform is not enforcing the project controls you need.

Configure, pilot and govern the CDE

Before the project leans on the CDE, run one full information path to make sure everything works the way it should:

• Configure the baseline: Set naming conventions, metadata, permissions, review routes and the first approved record. Get the foundations right before anyone starts uploading.
• Run a representative exchange: Push a model, drawing or submittal through checking, review, approval and issue.
• Train by role: Show authors, reviewers, project leads and admins only the tasks they’re responsible for. No clutter, no guesswork.
• Govern the live environment: Keep an eye on overdue reviews, access changes, workflow exceptions and closeout exports. Step in early before small issues turn into rework.

Show Clients How Your CDE Will Work

Your CDE should give a client an explicit answer before the project starts: Which drawing is current, who can approve a change, and where to find the decision later.

If a tender asks for ISO 19650-aligned information management, your team needs more than a platform name.

You need a practical workflow that shows how information will move between designers, reviewers and the site team.

Based on our experience, your project documentation should clearly define:

• Review and approval routes: who checks and authorises information at each stage.
• Information states: when information is WIP, Shared, Published or Archived.
• Issue tracking: how coordination issues are assigned, reviewed and closed.
• Access controls: who can view, edit, approve or issue information.
• Project records: how revisions, decisions and approvals are retained for future reference.

Where a client scores information management during procurement, this gives your bid team something concrete to show: how your team will control information from day one, rather than simply naming the CDE platform you intend to use.

How Interscale Can Support Your CDE and BIM Workflows

Setting up the technology is only part of implementing a reliable CDE. AEC teams also need practical workflows, coordination processes, and standards that people can follow during live project delivery.

As a BIM services provider in Australia, Interscale can support AEC teams with:

• BIM coordination to establish structured review and coordination workflows
• BIM implementation to align digital processes with project requirements
• BIM management to define standards, roles and information workflows
• AEC software and technology support to help teams adopt and manage the tools behind their workflows

If you are preparing for a new project or tender and need to define how your CDE and BIM workflows will operate, talk to Interscale about your requirements.

FAQ