Common Data Environment vs SharePoint: what's right for your practice?

"Do we need a proper CDE?" is one of the most common questions we get from growing architecture and project management practices – usually prompted by a client or contractor asking about ISO 19650 compliance. The honest answer is: it depends on your projects, not on what's fashionable.

What a Common Data Environment actually needs to do

Whatever platform you use, a CDE needs to support the core information management workflow behind ISO 19650:

• Clear work‑in‑progress, shared, published and archive states for documents.
• Consistent naming conventions and metadata across the project team.
• Controlled access for different organisations working on the same project.
• An audit trail of who approved and issued what, and when.

When SharePoint is genuinely enough

For many small and mid‑sized practices, particularly on projects where you're the lead consultant or working with a smaller number of familiar collaborators, a well‑structured SharePoint site can cover the above requirements perfectly well. The key word is "well‑structured" – most of the SharePoint sites we review were never actually set up with ISO 19650 states, naming conventions or permissions in mind, which is where the frustration usually comes from.

Done properly, SharePoint gives you:

• No additional licensing cost, since it's already part of Microsoft 365.
• Familiar tools for your team, reducing training time.
• Reasonable version history and approval workflows via Power Automate.

When a dedicated CDE platform earns its cost

Specialist platforms tend to make more sense when:

• You're working on larger, multi‑disciplinary projects with many external parties.
• Clients or main contractors mandate a specific platform for the project.
• You need native BIM model viewing, clash detection or issue tracking alongside documents.
• Formal, contract‑level information exchange and sign‑off is a routine requirement.

In these cases, the extra licence cost is usually justified by the time saved managing large, multi‑party document exchanges and model coordination.

A practical way to decide

Rather than choosing a platform first, we usually recommend mapping your actual project types and typical collaborator numbers, then matching the platform to that – rather than buying a specialist CDE "just in case" for every project, or forcing every project into SharePoint regardless of scale.

Many practices end up running a hybrid approach: a well‑structured SharePoint environment as the default, with a dedicated CDE brought in for the specific projects that need it.