This video explains the collaborative production of information stage in ISO 19650, covering how teams produce, check, review, authorise, and deliver project information. The written guide below covers the full workflow from mobilizing resources and testing workflows through to task team quality assurance, information model review, lead appointed party authorisation, and appointing party acceptance.

Why collaborative production of information is where planning becomes delivery

After the assessment, tender, and appointment stages have been completed, the project moves into the stage that matters most: actually producing and delivering information. The collaborative production of information is where all the planning documented in the BIM Execution Plan, the responsibility matrix, and the Master Information Delivery Plan (MIDP) gets put into action. This stage is not just about creating information. It is about doing it accurately, managing it efficiently, checking that it meets quality standards, approving it systematically, and delivering it in compliance with the Exchange Information Requirements (EIR) and ISO 19650 standards.

The process begins with mobilization. First, resources are confirmed — the right people with the right skills, tools, and technology must be available and ready to deliver. The lead appointed party checks resource availability while appointed parties align their capacity to meet project requirements. Next, information technology is mobilized by setting up and testing the tools and platforms needed for delivery. This includes configuring the common data environment (CDE), validating workflows, and ensuring all systems are ready for collaboration. Finally, the agreed methods and procedures for producing, sharing, and validating information are communicated and tested, confirming everything aligns with the project standards and EIR before work begins. These three mobilization steps ensure that teams start confidently, knowing the project infrastructure is ready.

Once mobilization is complete, the iterative cycle of producing, checking, and approving information begins. Task teams first check that they have access to all relevant reference information and shared resources within the CDE. If anything is missing, they must inform the lead appointed party immediately and assess the impact on their delivery plan. Information is then generated according to each team’s Task Information Delivery Plan, with deliverables coordinated spatially against other models to ensure seamless integration. Every piece of information then goes through a quality assurance check where the task team reviews it for accuracy, completeness, and alignment with the EIR. If the quality is sufficient, it moves forward; if not, it is rejected and sent back for revision. The task team then reviews their own information containers against the EIR and the level of information need before approving them for sharing. This entire cycle — generate, check, review, approve — is repeated for every deliverable throughout the project lifecycle.

The final phase is information model delivery. Task teams submit their information model to the lead appointed party for authorisation within the CDE. The lead appointed party reviews the model against the MIDP deliverables, the EIR, and the acceptance criteria. If approved, teams are instructed to publish the information. If rejected, the model is rejected as a whole — partial acceptance is not permitted because it could lead to coordination issues later. The authorised model is then submitted to the appointing party for final acceptance. The appointing party conducts a detailed review and either accepts the model as a published deliverable within the CDE or rejects it for further updates. Again, partial acceptance is not allowed. Using Kanban boards and task tracking to manage this workflow makes it far easier to see which deliverables are proposed, approved, completed, or need attention, while 3D model checking tools allow teams to verify deliverables against requirements visually rather than through manual spreadsheet-based processes.

How collaborative production of information works step by step

1. Mobilize resources – Confirm that all team members have the right skills and availability, that technology platforms are configured and tested, and that agreed methods and procedures have been communicated to all parties.
2. Check reference information and shared resources – Before producing any deliverables, verify that all relevant reference information is available in the CDE. If anything is missing, inform the lead appointed party and assess the impact on the delivery plan.
3. Generate information – Produce deliverables according to the Task Information Delivery Plan, coordinating with existing shared information and spatially coordinating models to ensure alignment across disciplines.
4. Perform quality assurance checks – Review each deliverable for accuracy, completeness, and alignment with the EIR. Use the Verify module to check models against requirements automatically, with results highlighted visually rather than tracked manually.
5. Review and approve for sharing – Task teams review their own information containers against the EIR and level of information need, then assign suitability and approve for sharing. If unsuccessful, record why and note required amendments.
6. Conduct information model review – The delivery team reviews the information model as a whole to ensure all information remains coordinated, aligned with requirements, and meets acceptance criteria. This is a continuous and iterative process.
7. Submit for lead appointed party authorisation – Share the information model with the lead appointed party within the CDE for review against the MIDP, EIR, and acceptance criteria. Models are authorised or rejected as a whole.
8. Submit for appointing party acceptance – Once authorised, submit the model to the appointing party for final review and acceptance. Accepted models are marked as published deliverables within the CDE.

What you’ll learn

• What collaborative production of information means – How this stage moves the project from planning into actual delivery, with teams producing, checking, reviewing, and approving information in a structured and repeatable cycle.
• Mobilization before delivery – Why confirming resources, testing technology, and verifying methods before work begins prevents the slow, chaotic project startups that undermine delivery quality.
• Quality assurance as an iterative process – How the generate-check-review-approve cycle repeats for every deliverable throughout the project, ensuring accuracy and compliance at every step.
• Information model review and coordination – Why continuous review of the information model as a whole ensures that all deliverables remain coordinated and aligned with the appointing party’s requirements.
• Authorisation and acceptance rules – Why models must be accepted or rejected as a whole, not partially, to prevent coordination issues and maintain the integrity of the information model.
• Visual delivery management – How Kanban boards, task tracking, and 3D verification workflows replace manual spreadsheet-based checking with visual, automated, and more effective compliance management.

Common questions

Explore further

• Information verification, project tracking, compliance, and lessons learned – The full expert course lesson covering verification and compliance across the project lifecycle.
• BIM model quality and the Verify module – How automated model checking and visual verification simplify quality assurance workflows.
• EIR, PIR, and BEP documents with Plannerly – How the complete set of information requirement and delivery documents connects across the project lifecycle.
• ISO 19650 concepts and workflows – The full help centre collection covering how each component of ISO 19650 works together in practice.