This video recaps the complete ISO 19650 workflow from assessment and need through to closeout, showing how every stage connects. The written guide below walks through each phase of the standard, explains how documents, scope planning, and verification workflows fit together in practice, and covers how built-in checklists and reusable templates help teams simplify compliance and carry improvements forward into every future project.
How the full ISO 19650 workflow connects from start to finish
ISO 19650 can feel complex when each stage is studied in isolation, but the standard is designed as a connected workflow where each phase builds on the one before it. Understanding the full picture — how ISO 19650 concepts and workflows link together — is what gives teams the confidence to apply the standard in practice rather than treating it as a theoretical exercise. This recap brings together every stage covered across the expert course and shows how the key documents, roles, plans, and processes create a single coherent delivery framework.
The workflow begins at the assessment and need stage, where the appointing party defines what information they need and why. The Organizational Information Requirements (OIR) capture what the organisation needs to support its strategic objectives, and the Project Information Requirements (PIR) translate those objectives into the specific information needed to make decisions on the project. These requirements set the foundation for everything that follows. Without clear OIR and PIR, the entire downstream process is built on assumptions rather than defined needs.
From there, the appointing party develops the Exchange Information Requirements (EIR) and issues them as part of the invitation to tender. The EIR defines exactly what information is expected, at what level of detail, in what format, and by when. Prospective teams respond with a tender package that includes a pre-appointment BIM Execution Plan, a mobilization plan, and a risk register. These documents demonstrate that the team has the capability, resources, and processes to deliver what is being asked for. The tender response stage is where teams prove they can meet the project’s needs before any contract is signed.
Once the lead appointed party is selected, the appointment stage formalises the delivery arrangements. The pre-appointment BEP evolves into the post-appointment BIM Execution Plan, which becomes the definitive execution document for the project. The Master Information Delivery Plan (MIDP) is created to track which information needs to be delivered, by whom, and by when. The responsibility matrix assigns clear accountability for every deliverable. Together, these documents create the roadmap that guides the entire delivery phase, ensuring that nothing is missed and every team member is aligned with their obligations.
The mobilization and collaborative production phase is where teams begin producing information according to the agreed plans. Task statuses are tracked against the MIDP and responsibility matrix, and the CDE manages the flow of information through work in progress, shared, published, and archived states. This is where automation makes the biggest practical difference. Rather than manually cross-checking models against the EIR across multiple screens and spreadsheets, the Verify module connects models directly to tasks and information requirements. Each task shows a completeness percentage, elements change colour as they are statused, and teams can filter by discipline, milestone, or status to see exactly where things stand. Models are only moved to published status once their tasks have been verified, ensuring that no information is released for use until it has been properly checked.
The closeout stage captures lessons learned — what went well, what gaps were found, and what should be done differently next time. When tasks arise during delivery that were not originally scoped, they are recorded and reviewed as a team. These unscoped tasks and any updated requirements are incorporated into reusable templates, so the next project starts from a stronger foundation. Plannerly flags when a template has been updated since it was last used, allowing teams to incorporate improvements into their current work without manually tracking what changed. This creates a continuous feedback loop between project delivery and organisational learning.
The ISO 19650 stages at a glance
- Assessment and need – The appointing party defines the OIR and PIR to establish what information is needed, why, and for what decisions.
- Invitation to tender – The appointing party develops the EIR and issues it to prospective teams, defining the information expected in terms of content, format, level of detail, and delivery milestones.
- Tender response – The lead appointed party responds with a pre-appointment BEP, mobilization plan, and risk register demonstrating their capability and approach to meeting the requirements.
- Appointment – Contracts are finalised. The pre-appointment BEP evolves into the post-appointment BEP. The MIDP and responsibility matrix are created to define who delivers what and by when.
- Mobilization and collaborative production – Teams mobilize resources, produce information according to the agreed plans, and track progress against the MIDP using task statuses and CDE workflows.
- Information delivery and verification – Deliverables are validated against the EIR using the Verify module. Models are checked automatically, completeness is evaluated, and information is only published once verified.
- Closeout and lessons learned – Teams review what worked, capture unscoped tasks and missed requirements, update templates with lessons learned, and feed improvements back into future projects.
What you’ll learn
- The complete ISO 19650 workflow – How every stage from assessment and need through to closeout connects into a single coherent delivery framework, with each phase building on the outputs of the one before it.
- How key documents fit together – Why the OIR, PIR, EIR, BEP, MIDP, and responsibility matrix are not isolated documents but interconnected components that create a traceable chain from organisational objectives to individual deliverables.
- ISO 19650 compliance checklists – How built-in checklists guide teams through each stage of the workflow with predefined tasks, ensuring that nothing is missed and that compliance is managed step by step rather than checked retrospectively.
- The three-module workflow – How the Docs module for creating project documents, the Scope module for defining requirements and delivery plans, and the Verify module for checking models against requirements work together as an integrated compliance workflow.
- Automated verification in practice – How connecting models to tasks and requirements replaces the frustrating process of manual cross-checking across multiple screens, giving teams clear visibility of completeness and compliance.
- Continuous improvement through templates – How capturing lessons learned, updating templates, and using Plannerly’s update flagging system ensures that every project benefits from the insights of previous delivery experience.
Common questions
How do all the ISO 19650 documents connect?
The workflow follows a clear chain. The OIR defines what the organisation needs. The PIR translates that into project-level decisions. The EIR specifies exactly what information must be delivered. The BEP describes how the team will meet those requirements. The MIDP schedules every deliverable against milestones and owners. The responsibility matrix assigns accountability for each task. Each document builds on the previous one, creating a traceable link from organisational objectives all the way down to individual model elements and data deliverables.
How do the Docs, Scope, and Verify modules work together?
The Docs module is where you create and manage project documents like the BEP, EIR, and information protocol using templates that can be customised for each project. The Scope module is where you define the responsibility matrix, create the MIDP, set information requirements, and assign them to milestones and teams. The Verify module connects models to those requirements and checks deliverables automatically. Together, they create a single workflow from defining what is needed, through planning who delivers it, to verifying that it has been delivered correctly.
What are ISO 19650 compliance checklists?
Plannerly includes built-in ISO 19650 compliance checklists that break each stage of the workflow into predefined tasks. These guide teams through actions like appointing information managers, verifying deliverables, and archiving the project information model. Each checklist item can be assigned, tracked, and statused, giving teams full visibility of what has been completed and what still needs attention.
Why should lessons learned be captured throughout the project?
Waiting until the end of the project to capture lessons means that the team has already moved on and critical insights are lost. By capturing lessons at each milestone, teams identify recurring challenges and missed requirements while they are still fresh. These insights can be incorporated into updated templates immediately, so improvements are available for both the current project and future ones. This creates a continuous improvement cycle rather than a one-off retrospective exercise.
Explore further
- ISO 19650 expert course summary – The full expert course recap lesson bringing together the complete ISO 19650 workflow.
- Full BIM workflow — ISO 19650 made simple – A practical overview of how the complete BIM workflow can reduce admin effort by up to 80%.
- ISO 19650 training – The full range of free BIM and ISO 19650 training courses available on Plannerly.
- ISO 19650 concepts and workflows – The full help centre collection covering how each component of ISO 19650 works together in practice.