ISO 19650

Approvals Connector vs Approvals Kit vs ISO 19650 Governance

Microsoft Approvals and the Approvals Kit orchestrate decisions (approve/reject). They do not provide ISO 19650 governance primitives: information states, release gates, naming/metadata enforcement, or repeatable project blueprints. A policy-driven ISO layer treats approvals as one step inside a gated state transition—not the governance engine itself.

The terminology problem

In Microsoft 365 environments, “approval” conflates two distinct concepts: a workflow task (approve/reject an item) and a release authorization (transition information into a contractually binding state). Treating Power Automate approval flows as ISO 19650 publication governance produces fragile implementations, incomplete audit trails, and operational complexity at scale.

ISO 19650 on SharePoint: Why a Policy-Driven App Beats Power Automate-Only

ISO 19650 on SharePoint: Why a Policy-Driven App Beats a “Power Automate-Only” Approach

Many construction and infrastructure organizations want an ISO 19650–aligned Common Data Environment (CDE) while keeping data inside Microsoft 365. SharePoint provides the underlying document management platform, and Power Automate is often used to stitch processes together. In practice, however, an ISO 19650 CDE requires more than automation steps: it requires governance, repeatability, enforceable rules, and predictable user experience at scale.

ISO 19650 App for SharePoint

ISO 19650 compliance for SharePoint

Your data stays in M365. Your rules get enforced.

Data stays in your M365 tenant Policy-JSON configuration Partner-ready blueprints

Product Introduction

SharePoint stores documents. It doesn't enforce ISO 19650.

The Problem

Large construction projects need ISO-19650 compliant CDE processes on their existing M365 tenant. But ISO rules (naming, status/revision, approvals) are not enforced — leading to inconsistency and compliance risks.

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.