Most teams think ISO 19650 is “extra paperwork.”

It’s not.

It exists because without standardised information management:

• Everyone uses different naming systems
• Files go missing
• Models get corrupted
• Information becomes unreliable
• Clients lose trust
• And coordination becomes chaos

ISO 19650 stops these problems before they start.

It matters because it:

• Reduces rework
• Improves collaboration
• Streamlines approvals
• Creates predictable delivery
• Makes your work auditable
• And saves a project from drowning in its own data

On large projects, it’s non-negotiable.

On small projects, it’s a performance hack.

ISO 19650 doesn’t ask you to do everything — just the right things.

It focuses on:

• How information is created
• How information is named
• How information is approved
• How information is shared
• How information moves from WIP → Shared → Published → Archive

That’s it.

Everything else is supporting detail.

The Core Ideas:

• Deliverables must be predictable
• Responsibility must be clear
• Information must be trackable
• The CDE must operate logically
• Naming must be universal across the team

Master these five concepts and you’ve mastered most of ISO 19650.

The Common Data Environment (CDE) is the backbone.

WIP (Work in Progress)

• Draft work
• Team-specific
• Not visible to other disciplines
• No approvals needed

Shared

• Information that is coordinated
• Ready for others to reference
• Requires discipline-level checking

Published

• Finalised deliverables
• Issued to client or contractor
• Must be locked

Archive

• Everything frozen at milestones
• Full audit trail
• No edits allowed

A messy CDE = a messy project.

A clean one = smooth coordination, fewer RFIs, fewer arguments.

The BIM Execution Plan (BEP) is where ISO 19650 becomes practical.

Your BEP should clearly define:

• Who does what
• When information is exchanged
• Naming conventions
• Model responsibilities
• File formats
• Approval workflows
• Level of Information Need
• CDE responsibilities
• Coordination process

A good BEP eliminates:

• scope confusion
• duplicated work
• team disagreements
• model ownership disputes

The BEP is where your project stops depending on “tribal knowledge.”

To implement ISO 19650 smoothly, you need the right templates:

• Naming convention table
• CDE folder structure
• BEP (pre-contract & post-contract)
• MIDP (Master Information Delivery Plan)
• TIDP (Task Information Delivery Plan)
• Model responsibility matrix
• Approval workflow diagram
• Incoming/outgoing information tracker

You can customise, scale, and automate all of this with:

• Notion
• Google Workspace
• SharePoint
• Asite
• Revizto
• N8N automations
• Dynamo scripts

Templates = consistency.

Consistency = ISO compliance.

Get the ISO 19650 Setup Package

Full naming system, CDE structure, BEP alignment, templates, training & automation.

A simple 2-page breakdown of ISO 19650 you can share with your team.

..........................................................

..........................................................