How to prepare your firm for ISO 19650 — a 5-stage roadmap

The most common question we get from BIM Managers and technical directors is: "Where do we start?". The right answer is not "pick a platform" — it is "understand where you are now and where you want to be in 6 months". Here is the roadmap that has worked across dozens of implementations.

Stage 1 — Objective diagnosis (week 1-2)

Before any technical decision, run an objective assessment of your starting point. The 5 dimensions evaluated are: information management, common data environment, BIM processes, compliance / audit and organisational culture. The result is a 75-point score and your maturity level (Initial / Repeatable / Defined / Managed / Optimised).

Stage 2 — Define the framework (week 3-4)

Based on the score, define the foundational documents:

• EIR — Exchange Information Requirements clear per project type
• BEP template — reusable BIM Execution Plan adapted to your firm
• Naming convention — per ISO 19650-2, with codes relevant to your disciplines
• Roles matrix — who can do what in the CDE, mapped to the 4 ISO roles

Stage 3 — Pilot on a real project (month 2-3)

Do not roll the transformation across all projects at once. Pick a medium project (not the smallest, not the biggest) and apply the full ISO 19650 framework there. That is where you discover where your framework breaks in real conditions — and refine before generalising.

Stage 4 — Standardisation and scaling (month 4-6)

After the pilot, you have the real framework (not the theoretical one). Now you scale:

• Apply the refined framework to 2-3 new projects simultaneously
• Train on real cases from the pilot, not generic slides
• Establish a review cadence — weekly in the first months, monthly after stabilisation
• Track KPIs: document search time, % rework, audit trail completeness

Stage 5 — Operationalisation and continuous improvement (month 7+)

At this point, ISO 19650 is no longer a special project — it is your default mode of working. You focus on continuous improvement:

• Automating compliance reporting for tenders
• Integration with specialised tools (Revit, AutoCAD, existing FM systems)
• Extension to AIM (Asset Information Model) for OPEX phases

Classic mistakes to avoid

• Buying the platform before knowing the framework — risk of using it at 30%
• Writing the BEP as a formality — the tender committee sees it immediately
• Postponing training "for when we have time" — adoption fails
• Not measuring — without KPIs you cannot demonstrate ROI or course-correct