Most project teams do not struggle because they lack information. They struggle because the information is scattered. Drawings sit in one place, models in another, comments in email and approvals in someone’s inbox. A Common Data Environment (CDE) is designed to bring all of those elements into a single, controlled space.
Choosing CDE software takes careful evaluation because the label is used loosely. Some products are little more than shared storage with a new name. The features below help you tell a genuine CDE from a basic file folder.
What a CDE Is Meant to Do
A CDE is the single source of truth for a project’s information. Under the ISO 19650 approach to managing information with BIM, information moves through defined stages:
- Work in progress: Content being developed by one team, not yet shared.
- Shared: Content checked and made available for coordination.
- Published: Content approved for use, such as for construction.
- Archive: A permanent record of what was issued and when.
Good CDE software makes these stages clear and controls who can move information between them.
Core Features to Compare
Status and workflow: Documents should carry a visible status and follow defined approval steps.
Naming and metadata: The system should support project naming rules and tags so files can be found and sorted.
- Version history: Every revision is kept, with a clear current version highlighted.
- Access control: Permissions by role, team, and project stage.
- Audit trail: A complete record of who did what and when.
Handling Models and Large Files
- Support for BIM and CAD files, including large federated models.
- Reliable sync so remote teams are not waiting for files to open.
- Viewing in the browser, so reviewers do not need expensive authoring software.
- Clear links between models, drawings, and related documents.
Collaboration Features
- Comments and markups attached to the right file and revision.
- Issue tracking with owners, due dates, and status.
- Notifications when something relevant to you changes.
- Simple ways to invite external partners and consultants.
Security and Compliance
Many projects involve sensitive designs or client data, so check for:
- Encryption in storage and transit.
- Multi-factor authentication and single sign-on options.
- Clear rules for data location and retention.
- Controlled, time-limited access for outside parties.
Integration
A CDE does not work alone. Look at how well it connects with:
- Design and modelling tools your teams already use.
- Project management and document control systems.
- Identity systems used by your organisation.
- Export options for handover and long-term records.
You can learn more about how a CDE fits within a broader document environment in this Egnyte guide to CDE software, which explains the concept and what to expect from it.
Questions to Ask Before You Buy
- Can the workflow follow our contract and information requirements?
- How does the system handle a project that changes scope halfway?
- What happens to the data when the project ends?
- Can we limit what each partner sees to their own scope?
- How easy is it for a new team member to start using it?
Rolling It Out Well
- Agree on naming rules, folder structure, and responsibilities before the first upload.
- Set out in writing who can approve a move between stages.
- Run a short onboarding session for every new partner.
- Review how the CDE is being used at set points during the project.
Common Mistakes
- Treating the CDE as simple storage and ignoring the workflow.
- Allowing partners to keep sharing files by email.
- Leaving permissions open to save time at setup.
- Skipping the project information plan that explains how the CDE will be used.
The Takeaway
A CDE is only as good as the discipline around it, but software can make that discipline easier. Compare how each product handles status, versions, access, and audit, test it with a real project, and choose the one that makes the right behaviour the easy behaviour.
