Construction Management

ISO 19650 and SharePoint: Making Your Project Data Room Compliant

ISO 19650 is becoming a baseline requirement in construction and infrastructure contracts. Many organizations already have Microsoft 365 and SharePoint in place—often underutilized for project document control. The question: can SharePoint serve as a fully ISO 19650-compliant Common Data Environment (CDE)?

Yes—but only with the right controls, workflows, and governance layered on top. Native SharePoint provides foundational capabilities but lacks the discipline ISO 19650 demands.

What is ISO 19650?

ISO 19650 is the international standard (originating from the UK’s PAS/BS 1192 lineage) for information management using BIM across the lifecycle of a built asset. It covers how information is exchanged, approved, stored, and retrieved, and defines the Common Data Environment (CDE)—the single agreed source of truth for all project information.

Leveraging SharePoint as a Common Data Environment (CDE) for Large Construction Projects

A Common Data Environment (CDE) centralizes project documents, drawings, models, and coordination data in a single accessible location. For organizations using Microsoft 365, SharePoint provides the underlying infrastructure: document libraries, metadata, version control, and permissions.

This guide covers the technical implementation of SharePoint as a CDE for construction projects.

SharePoint capabilities relevant to CDE

Data storage and organization

SharePoint document libraries support:

  • Folder hierarchies for organizing by discipline, zone, or work package
  • Metadata columns for classification (document type, status, revision, originator)
  • Content types for applying consistent metadata schemas across libraries
  • Views for filtering and sorting based on metadata values

Version control

  • Automatic version history with configurable major/minor versioning
  • Check-in/check-out to prevent concurrent editing conflicts
  • Version comments and restore capability

Permissions and access

  • Site-level, library-level, folder-level, and item-level permissions
  • SharePoint groups for role-based access (e.g., design team, contractor, client)
  • External sharing with configurable link expiration and password protection
  • Conditional access policies through Azure AD

Integration with Microsoft 365

  • Teams: Channels linked to SharePoint folders for collaboration context
  • Power BI: Reports and dashboards connected to SharePoint lists and libraries
  • Power Automate: Workflow automation for notifications, approvals, metadata updates
  • Outlook: Email alerts and document sharing

Example CDE folder structure

A typical SharePoint CDE for construction might use this hierarchy: