1. Help Articles Index
  2. Training + Certification
  3. ISO 19650 Specialist (Education Assignment)
Image

ISO 19650 Specialist (Education Assignment)

Hands-on ISO 19650 training

Learn ISO 19650 by doing the full workflow, step by step.

Build confidence with practical exercises inside Plannerly. You’ll move from Owner goals to clear requirements, then into delivery planning, verification, and handover acceptance.
This is practical implementation, not just theory.
Start Assignment 1 See the 4-part workflow
Less theory

Complete each activity yourself with clear, guided steps.

Real roles

Work through the same information management roles used in practice.

Practical outcomes

See how structured information reduces rework and improves delivery confidence.

Roles you will experience

Appointing Party (client/owner)
Defines the goals and what information is required.
Lead Appointed Party + Appointed Parties
Plans delivery, assigns responsibilities, coordinates outputs, and supports verification.

How you are expected to think

You are encouraged to think like an information manager, not a document author. 

Every decision you make should answer one simple question:

What decision does this information support?

If you cannot answer that, the requirement is probably noise.

 Orientation - Start Here 
 How the Assignment Is Structured 


Assignment 1 - Define EIR
Clarify what information is needed, by whom, and for what decisions.

Assignment 2 - BEP + MIDP
Translate requirements into a coordinated delivery plan with roles, timing, and outputs.

Assignment 3 - Model Verification
Verify that what was delivered matches what was agreed.

Assignment 4 - Handover + Acceptance
Confirm information is fit for purpose and formally accepted.

Why this matters: The fastest way to fail ISO 19650 is to treat it like a document-writing exercise. The fastest way to succeed is to treat it like a connected workflow where every requirement links to delivery, verification, and acceptance.
 Set Up Your Plannerly Workspace 
1. Sign in to Plannerly
If your university provides access, sign in using your university Plannerly account. 
If not, create a free account at app.plannerly.com 
2. Create a new Project and add "Contract Template" document
  • Go to your Projects workspace and click New Project. Give your project a suitable name. Once the project is created, review the project settings and add key details such as the project ID, location, and other basic information you consider appropriate. This project will be used to complete all tasks in this assignment.

  • From the Plannerly Library → "ISO 19650 Example Templates - English", add the Contract Example (for ISO 19650 Specialist) to your project’s Docs module.

3. Work individually or as a group
If you’re working individually
You will complete every step in this assignment on your own.
If you’re working as a group
Your instructor may create the shared project and add your team members to it. Later, divide the steps across your team and assign tasks to the right people inside the Contract Example document. Each person is responsible for completing their assigned steps and contributing to the final submission.

 Free Resources and Support 
Free Certified Training Courses
 https://plannerly.com/training/ 
Help During the Assignment
If students get stuck, use the in-app chat. Our team can help with setup, navigation, and workflow questions.
 Professor/Teacher/Educator Guide - How to run this Assignment  professor guide education setup  
Option A - Students work individually

Best for solo assessment and quick setup. Each student can complete all four assignments inside a free Plannerly account.

  • Students sign up for free Plannerly account
  • Start the assignment in their own free workspace
  • Complete Assignments 1-4 in order
  • Export deliverables to File Manager
  • Submit exports and/or a short screen recording
Option B - Students work in teams (recommended)

Best for collaboration and role clarity. Typical teams are 3-5 students. Teams of 4 map neatly to the four tasks.

  • 4-person team: one student per
  • 5-6 person team: pair up on heavier tasks
  • Final handover should look consistent and complete

Setting up the Education Workspace

Team projects require an Education account so you can create workspaces, projects, and invite students.

Step 1 - Join the university program
 https://plannerly.com/partner/ 
Step 2 - Book a setup call
 https://plannerly.com/meeting/ 
Practical setup tip: Create one shared workspace per class, and either one project per team or one project per student.

How to Run the Assignment

Assignment 1
Define clear information requirements (what + why).
Assignment 2
Turn requirements into BEP + MIDP delivery plan.
Assignment 3
Verify models against agreed requirements.
Assignment 4
Owner review, archive, sign-off, lessons learned.
Student Submission Requirements
  • Exports saved in File Manager
  • Verification evidence (screenshots or reports)
  • Updated task statuses
  • Final sign-off document with reflection
 ISO 19650 Workflow Assignments 
 Assignment 1 - Define EIR  OIR PIR AIR EIR  

Define the EIR - set the rules for information delivery.

A structured information workflow starts with the Owner. In this task, you’ll translate the Owner’s strategic goal into clear, practical Exchange Information Requirements (EIR) - the document/resource that shapes what information is delivered, when it is delivered, and why it matters. For training purposes, this assignment uses a simplified and condensed version of ISO 19650 workflows. It represents a streamlined approach to real-world practice, focusing on how information requirements are defined, planned and verified. On live projects, these requirements may be distributed across multiple documents such as OIR, PIR, AIR, EIR, BEP, appointments and protocols. For education and clarity, this assignment brings those elements together into a manageable, structured workflow.

 Your role - Appointing Party   Output - EIR Doc + structured Information Requirements in Scope 

Owner’s strategic goal

Goal statement
“Capture the information required for long-term maintenance and operation of the building, ensuring all assets, systems, and spatial data are accurate and complete.”
Your job - turn this goal into clear requirements the delivery team can actually follow.

What you will do

1.1 Create the EIR in Docs (using the provided template)
Work through the pre-filled EIR document in the Contract Document and complete the required sections by following the instructions provided.
1.2 Structure the requirements in Scope
As part of the EIR task, confirm and structure the Information Requirements in Scope so they are clearly assigned for the Operation milestone.
1.3 Prepare the EIR final deliverables
Set tender-relevant EIR sections to Shared, then export and upload the Invitation to Tender package.
 Step 1.1 - Access and complete the EIR document  Docs EIR  

Required checklist

  • Review the pre-filled EIR sections and understand the Owner’s information needs
  • Complete all highlighted SmartFields in this EIR template
  • Ensure your responses focus on operational needs, not delivery methods
  • Follow any inline guidance provided within each section

Accessing the pre-filled EIR document

Plannerly Templates → "ISO 19650 Example Templates - English" → "Contract Example" → Add

Accessing the pre-filled EIR document - screenshot 1Accessing the pre-filled EIR document - screenshot 2

Once located, the EIR document will guide you through the task. 

Follow the instructions in each section and complete the highlighted Smart Fields.

Why this matters: If the EIR is unclear, delivery becomes guesswork and verification becomes opinion. Completing the EIR properly makes later steps faster and more objective.
  Step 1.2 - Define the information requirements in Scope  Scope Import   

Required checklist

  • Create discipline folders in Scope: Architecture, Mechanical, Electrical
  • Add tasks under each folder: Interior Walls, Air Terminals, Mechanical Equipment, Lighting Fixtures, Cable Tray with Fittings
  • Rename Milestone 1 to Operation
  • Download and Import the CSV:  Download Asset Information Requirements (AIR) Template
  • Assign the correct information requirements in the Operation column for each task (use the reference image)

Create discipline folders

Your completed EIR document (from Step 1.1) explains Owner's goals and maintainable assets. 

Now you will define these as structured requirements in the Scope so the project team can clearly see who delivers what - and so the requirements can be contracted as part of a tender package. 

Add three Folders: Architecture, Mechanical, Electrical.

Create discipline folders

Add tasks under each folder

Add asset Task Rows under each discipline folder to represent the maintainable assets identified in the EIR.

Add tasks under each folder

  • Architecture - Interior Walls
  • Mechanical - Air Terminals, Mechanical Equipment
  • Electrical - Lighting Fixtures, Cable Tray with Fittings

Each row represents an asset that will require structured information at handover. 

Ensure each task is placed under the appropriate discipline folder (see 3 below):

Tasks created

Rename Milestone 1

Rename Milestone 1 to Operation.

Rename Milestone 1 to Operation

Import the CSV

Click Information at the bottom and import the CSV file to load the information requirements.

Import the CSV

Assign requirements

Assign the relevant information requirements to each task in the Operation column.

For each task, select the information required to support the operation and maintenance of that asset.

Assign the following:

  • Interior Walls - AcousticRating, Material
  • Air Terminals - Flow, Level, Static Pressure Drop, System Classification
  • Mechanical Equipment - Water Flow, Water Pressure Drop
  • Lighting Fixtures - Electrical Data, Manufacturer
  • Cable Tray with Fittings - Length, Manufacturer

Each task should show only the information requirements that are relevant to that asset at the operational stage.

Assigned requirements reference

Assigned requirements example

Finalise the EIR document

Add images to tasks using AI: If you want to add images to your tasks, click the AI (robot) icon on the task row to generate an image for that specific row. This step is optional. Free Plannerly accounts have limits on AI generations.

The information requirements for each asset have now been defined and structured in Scope.

Complete the remaining sections in this template to finalise the EIR, as this document will form part of the tender/contract information.

Want to learn more about defining information requirements?

https://plannerly.com/courses/expert/lesson/creating-the-detailed-responsibility-matrix/

Why this matters: When requirements live in a structured scope, they can be assigned, tracked, and verified. This is what turns "requirements" into real delivery accountability.
  Step 1.3 - Prepare the EIR final deliverables  Docs File Manager Tender Export   

Required checklist

  • Set all tender-relevant EIR sections to Shared.
  • Export and upload the Invitation to Tender document in the File Manager.

Prepare the EIR for export

All Appointed Parties shall read, understand and agree to the requirements of the EIR as it is cascaded down through the whole project supply chain.

Before exporting the Invitation to Tender document, review the EIR structure and confirm which sections are to be included in the tender package.

Update the status of all relevant sections from In Progress to Shared. 

When exporting the Tender document, we can use the Section Status to filter only the Shared/Published content to be included in the PDF.

Prepare the EIR for export (share relevant sections)Prepare the EIR for export (share relevant sections) 2

Create Invitation to Tender Document

Export your completed EIR + AIR Scope as a single PDF document.

Create Invitation to Tender Document

Why this matters: Deliverables are where requirements become contractual reality. Sharing the right sections and exporting the right evidence is what makes the process auditable and repeatable.
 Assignment 2 - BEP + MIDP  BEP MIDP TIDP  

Turn requirements into a delivery plan the team can follow.

You are now stepping into the role of the Lead Appointed Party. In this task, you’ll translate the Owner’s EIR into a coordinated plan that makes delivery clear - what gets delivered, who delivers it, and when. You’ll also set up Work Packages so models can be verified against the agreed requirements later. The BIM Execution Plan (BEP) explains how the project will deliver information, while the Master Information Delivery Plan (MIDP) defines who delivers what, and when. On real projects, these plans often fail because they are written in isolation or simply copied from previous jobs. Here, you will build them directly from the EIR you already created - so they are connected, realistic, and verifiable. Requirements without a delivery plan are just empty promises. The BEP and MIDP are where intent becomes commitment - linking what’s needed to who delivers it, when, and how it will be verified. These steps build directly on Assignment 1. If your EIR is unclear or incomplete, you will feel it immediately here.

 Your role - Lead Appointed Party + Appointed Party   Output - BEP + MIDP + Work Packages linked to demo models 

What you will do

2.1 Create the BEP
Define how the team will collaborate and deliver information.
2.2 Set up the MIDP
Organise deliverables by milestone - including document placeholders.

2.3 Create Work Packages
Group tasks and link the correct demo models for verification.
 Step 2.1 - Complete the BEP in Docs  Docs BEP  

What the BEP is really for

A BIM Execution Plan (BEP) is not a “BIM document” you write because someone asked for it. It is the team’s operating manual for how information will be produced, checked, shared, and accepted on this project.

In ISO 19650 terms, the BEP sits between the requirements (what the Appointing Party needs) and the delivery plan (what the delivery team will produce and when). If the EIR is the “what and why”, the BEP is the “how”.

Think of the BEP as the answer to three questions:
  • Who is doing what (roles, responsibilities, approvals)?
  • How will information be created, named, shared, reviewed, and signed off?
  • How will we prove the deliverables meet the EIR (verification and acceptance)?

This assignment makes it easier than a real project - the structure is already in place, the template content is already aligned to ISO 19650, and you only need to complete the SmartFields to capture the important decisions. The key skill you are practicing is not typing - it is choosing clear, workable processes that match the EIR.

Required checklist

  • Project information management roles and responsibilities.
  • Model and information delivery processes.
  • Coordination, review, and approval workflows.
  • Common Data Environment usage.

Completing the BEP

Access the pre-filled BIM Execution Plan (BEP) template provided in the Contract Documents. This document already contains guidance and structure aligned with ISO 19650.

Completing the BEP in Docs

How to complete it in this assignment
  • Complete the highlighted SmartFields and follow the guidance embedded in each section.
  • Keep the BEP aligned to the EIR - do not add processes that are not required by the EIR.
  • Write processes so a real project team could follow them (clear owners, clear steps, clear outputs).
  • If you are unsure, choose the simplest process that still protects quality (clarity beats complexity).

When you finish, you should be able to point to the BEP and say: “This is how we will deliver the information that matters, in a way that can be checked and accepted.”

Why this matters: The BEP is where requirements turn into coordinated action. Preparing it properly ensures responsibilities are clear, dependencies are visible, and the Appointment Document reflects how the team will actually deliver.
 Step 2.2 - Build the MIDP in Scope  Scope MIDP  

What the MIDP really is

The Master Information Delivery Plan (MIDP) organises what will be delivered, by whom, and when.

If the EIR defines what information is required, and the BEP defines how the team will work, the MIDP defines when each information container will actually be delivered and who is responsible for it.

The MIDP turns scope into schedule:
  • Tasks created in Scope become delivery commitments.
  • Each task is assigned to an owner.
  • Milestones define when deliverables are due.
  • Dependencies define the logical sequence of work.

In this assignment, you will import a structured example MIDP from the Plannerly Library to speed things up. Your job is then to adjust it so it reflects a realistic and logical delivery sequence.

Required checklist

  • Import the Example Project Scope MIDP from the Plannerly Templates Library.
  • Reorder milestones so Pre-Construction appears before Operation.
  • Assign owners and confirm delivery dates.
  • Add one document placeholder: Site Plan.pdf to the Drawing Package.
  • Add or review task dependencies in Timeline view.
Add the MIDP Template

Import the MIDP from the Plannerly Library:

Scope > Library > Plannerly Templates > Example Project Scope > Master Information Delivery Plan > Add

1 - Select the Example Project Scope
2 - Click Add for the MIDP

The dashed blue outline in the image below shows the imported content:

Reorder milestones
1 - Click the milestone header to open the "Edit Information Delivery Milestones" modal.
2 - Drag Pre-Construction above Operation to re-order. This ensures the delivery sequence reflects how a real project progresses.
Complete document placeholders

A document placeholder represents a required deliverable that has not yet been created.

It allows you to assign responsibility, define naming expectations, connect it to a task, and schedule it - before the file exists.

Why this is powerful:
  • The requirement becomes trackable.
  • An owner is clearly assigned.
  • Delivery dates are visible.
  • Verification can be linked later.

This is a major upgrade from maintaining a checklist in Excel that must be manually reconciled against folders and emails. Here, the requirement lives inside the delivery plan itself.

In the Drawing Package task, add one additional non-geometric document placeholder: Site Plan.pdf

Add task dependencies in Timeline view

The imported MIDP already includes several dependencies. Now complete the sequence.

  • Switch to Timeline view.
  • Review existing dependencies.
  • Adjust milestone dates if required.
  • Drag from the end node of one task to the start of another to create dependencies.

Example: Link Visualization → Drawing Package.

1 - in the image shows switching to Timeline view.
2 - shows adjusting dates.
3 - shows linking tasks by dragging between nodes.

That’s it - your MIDP is set up. Next, you’ll create Work Packages and link models so the team is ready for verification.
Why this matters: If no one owns a requirement, it won’t be delivered. The MIDP turns coordination into accountability by making delivery visible, measurable, and time-bound.
 Step 2.3 - Create Work Packages, assign models, and export your deliverables  Scope Verify File Manager  

What Work Packages do

Work Packages group related deliverables and connect your Scope tasks to real models in Verify. This is what prepares the team to check whether the model meets the agreed information requirements.

Before you create Work Packages

Make sure every task is assigned to a delivery team. The imported MIDP is already assigned to Architect and Contractor teams. For the tasks you created in Assignment 1, assign each task to the appropriate team (Architect or Contractor).



Required checklist
  • Create a Work Package filtered to Architect team named Architecture WP.
  • Create a Work Package filtered to Contractor team named MEP WP.
  • Assign demo models: Architecture WP → Plannerly-Arc.rvt, MEP WP → Plannerly-MEPF.rvt.
Create two Work Packages
  1. In All Scope, add a new Work Package filtered to the Architect team and name it Architecture WP.
  2. Add a second Work Package filtered to the Contractor team and name it MEP WP.

Save each work package.





Assign models to Work Packages

Assign the correct model to each Work Package:

  • Architecture WP → Assign Plannerly-Arc.rvt (demo model)
  • MEP WP → Assign Plannerly-MEPF.rvt (demo model)

Note
The Plannerly Arc and MEPF demo models are already available in your free Plannerly account’s Verify module - no upload needed. Work Packages connect Scope tasks to the models used for verification.

Before moving on, confirm that the BEP and MIDP are aligned, complete, and ready to be agreed.

Agreement baseline check

  • BEP completed and reviewed.
  • MIDP fully populated with owners and dates.
  • No orphan requirements.
  • Plans ready to be shared with the delivery team.
Why this matters: Agreement at this stage prevents disputes later. A shared baseline is what allows verification to be objective in the next assignment.

Final deliverable checklist

  • The BEP is completed and reflects the EIR and project delivery approach.
  • The MIDP is imported, milestones are ordered clearly, and Site Plan.pdf is added as a document placeholder.
  • Architecture WP and MEP WP exist and are linked to their correct demo models.
  • You exported your completed BEP document - including the MIDP with timeline - in File Manager.
Export BEP + MIDP timeline to File Manager

Export your completed BEP document, including the MIDP with Timeline in File Manager as a single document.

How to Video - To be Uploaded
That’s it - your delivery plan is ready. Next, you’ll move into verification and check what passes, what fails, and what changed.
 Assignment 3 - Model Verification  IDS Verification Information Requirements  

Deliver with confidence - verify what you’ve promised.

This task is about trust. You’ll prove that what was agreed and contracted in the EIR, BEP, and MIDP is exactly what’s being delivered - before anything reaches the client. This is where the workflow becomes objective - the plan becomes the test. On real projects, verification often turns into opinion because requirements are vague or scattered. Here, you are using a structured set of requirements and a defined delivery plan - so checking compliance becomes repeatable and explainable.

 Your role - Appointed Party + Lead Appointed Party   Output - Verified models, approved documents, structured handover 

What you will do

3.1 Verify the models
Check the assigned demo models against the defined information requirements.
3.2 Organise deliverables
Structure deliverables and complete the required document upload.
3.3 Handover deliverables
Export the final, verified handover package.
 Step 3.1 - Quality assurance (verify the models)  Baseline Verify Models Sync  

Before issuing anything externally, Appointed Parties must confirm that the model content matches the agreed scope and information requirements. This is your internal safety net.

Confirm you have a clear baseline:

  • The EIR is complete and shared where required.
  • The BEP + MIDP are complete and agreed (baseline).
  • Your Scope tasks and information requirements are structured for the milestone you are verifying.

Tip: If you are missing clarity here, fix it now. Verification should confirm decisions - not create new ones.

Required Checklist
  • Verify the Architecture Work Package
  • Verify the MEP Work Package
  • Review the verification results and Export IDS
Verify Work packages

In the Verify module, open Model Viewer, continue with the demo model, and in All Scope select Architecture WP

Set the Model Rule to Name = Name, then review the verification results. 

Repeat the same steps for MEP WP, confirming the rule Name = Name and reviewing the results for compliance.

IDS Export

Exporting an IDS creates a machine-readable specification of the information requirements you have defined. This allows requirements to be reused, shared and supports openBIM workflows. 

  • Export the IDS Specification file for the verified scope 
  • Save the exported IDS file for use in model checking and information exchange

Why this matters: Verification only works when everyone agrees on the baseline. If "what good looks like" is unclear, every issue becomes a debate instead of a decision. Connection is what turns "I think it’s right" into "we can demonstrate it’s right."
 Step 3.2 - Run verification checks against the requirements  Checks Requirements  

Module - Verify

Follow the step-by-step lab instructions to run checks against the information requirements you structured in Scope.

  • Select the correct milestone / exchange (based on your MIDP).
  • Run the automated checks for required properties, units, and rules.
  • Review pass/fail results and identify gaps that must be corrected.

Running checks

Run checks - screenshot 1

Run checks - screenshot 2

Why this matters: This is where structured requirements pay off. When checks are linked to agreed rules, issues become actionable - not personal - and fixes become faster.
 Step 3.3 - Final deliverables for Assignment 3  Report Evidence  

Step 3.3 final deliverables

Follow the lab instructions to capture your verification outcome and prepare evidence for review.

Required checklist

  • Verification checks run for the correct milestone / exchange.
  • Results reviewed and issues identified.
  • Evidence captured (screenshots / exports as instructed in the lab).
  • Ready to move into Assignment 4 - Handover + Acceptance.

Reference screenshot

Verification deliverables - screenshot 1

Why this matters: Evidence is what makes verification useful. If you can’t show what you checked and what passed or failed, acceptance in the next step becomes subjective again.
 Assignment 4 - Handover + Acceptance  AIM Handover Acceptance  

Final acceptance - hand over information that can actually be trusted.

This is the moment the Owner cares about most. You are now acting as the Appointing Party (Owner). Your job is to confirm the handover is usable, organised, and aligned with the requirements - and to capture what should improve next time. You will package the verified outputs into a structured handover and confirm acceptance against what was agreed. The goal is not “a folder of files” - it is information that is complete, consistent, and usable for operations. Because you verified delivery in Assignment 3, acceptance here becomes a decision - not a debate.

 Your role - Appointing Party + Lead Appointed Party   Output - Accepted handover package + export evidence 

What you will do

4.1 Review the AIM
Confirm operational deliverables are present and organised - then archive non-operational items.
4.2 Confirm acceptance
Check that everything meets the agreed EIR and is fit for operational use.
4.3 Capture lessons learned and sign-off
Create a simple sign-off document including lessons learned, and complete e-signature workflow.
4.4 Final deliverables package
Export the final handover package and capture submission evidence.
 Step 4.1 - Review the acceptance criteria  Criteria Baseline  

Modules - Docs + Scope + Verify + File Manager

Before you package anything, confirm what “acceptable” means for the Owner.

  • Revisit the EIR and identify handover-related requirements (format, completeness, naming, and structure).
  • Confirm the relevant milestone / exchange in the MIDP for handover.
  • Review the verification outcomes from Assignment 3 and ensure issues are resolved or clearly documented.

Tip: Acceptance should be measured against requirements - not against how confident someone feels today.

Reference screenshots

Review acceptance criteria - screenshot 1

Review acceptance criteria - screenshot 2

Why this matters: Acceptance only works when criteria are clear. If the baseline is vague, handover turns into negotiation instead of confirmation.
 Step 4.2 - Organise the handover deliverables  Deliverables File Manager  

Module - File Manager

Follow the instructions in the Information Management Lab for “Assignment 4 - Handover + Acceptance” to organise the final deliverables.

  • Create or confirm the handover folder structure.
  • Upload or link the required verified documents and models.
  • Ensure naming and status reflect “handover-ready” (not draft).

If you’re not sure what belongs in the handover set, check the EIR and MIDP - that’s the agreed shopping list.

Organising deliverables

Organise handover deliverables - screenshot 1

Organise handover deliverables - screenshot 2

Why this matters: A handover is only useful if it’s findable and consistent. Structure is what turns a pile of files into usable operational information.
 Step 4.3 - Confirm acceptance and record the outcome  Acceptance Record  

Modules - Docs + Verify

Now you will confirm the final set is acceptable against the agreed requirements.

  • Check that required deliverables are present and correctly named.
  • Confirm verification issues from Assignment 3 are closed, accepted, or documented.
  • Record the acceptance decision (and any conditions) as instructed in the lab.

If something is missing, don’t “make it pass.” Record it. Good information management is honest before it is optimistic.

Acceptance evidence

Confirm acceptance - screenshot 1

Confirm acceptance - screenshot 2

Why this matters: Acceptance is where trust becomes official. When it’s recorded against clear criteria, disputes fade and accountability becomes simple.
 Step 4.4 - Final deliverables for Assignment 4  Export Handover  

Step 4.4 final deliverables

Follow the lab instructions to export the final handover package and capture your submission evidence.

Required checklist

  • Handover deliverables organised and complete.
  • Acceptance outcome recorded.
  • Final export created (package / report as instructed).
  • Submission evidence captured (screenshots / exports).

Reference screenshot

Final handover export - screenshot 1

Nice work. You have now completed the full chain: requirements → planning → verification → handover acceptance.

Next up is reflection - what worked, what broke, and what you would change on a real project.

Why this matters: Information only has value if it can be trusted and accepted. Structured handover confirms the work is complete - and makes the information usable beyond the project team.
 Assessment 
 Reflection + Bonus Credit   Reflection Learning    

Lessons learned (reflection)

On real projects, lessons learned are captured to improve the next delivery. For this assignment, use the questions below to reflect briefly on how Plannerly supported ISO 19650 delivery - from defining requirements to final handover.

 Your role - Appointing Party (Owner) + Lead Appointed Party 
⚠️
Important - answers entered here will NOT be saved
The answer fields below are provided for reflection and printing only. Anything you type here will not be saved when the page is refreshed or closed.

If you want to keep a copy of your responses, please:
  • Print this section (or save it as a PDF), or
  • Take screenshots of your completed answers, or
  • Complete the Lessons Learned section in the provided template, which is designed for submission.
1. Defining the right information

At what stage did the required information become clear, and how did Scope help you structure it?

Guidance: Think Docs templates, Smart Fields, and how Scope influenced clarity.
2. Turning requirements into a plan

How did the MIDP structure (tasks, milestones, dependencies) change your understanding of delivery over time?

Guidance: Compare reading requirements vs seeing them sequenced.
3. Responsibility and coordination

Which part of the process helped clarify who delivers what?

Guidance: Think folders, work packages, ownership, and reduced ambiguity.
4. Verification before handover

How did the Verify module support quality before handover?

Guidance: Early issue detection, confidence, and objective checks.
5. Handover readiness

What made the final handover feel usable, not just complete?

Guidance: Think structure, naming, filtering, and day-one FM needs.
6. Carry this forward

If you were starting another project tomorrow, what would you keep exactly the same and why?

Guidance: Keep it simple and practical.
Note
Keep responses short. There are no right or wrong answers. The goal is to reflect on the workflow and how it supported ISO 19650 delivery.
 Evaluation Criteria - Grading Guide  grading guide assessment  

Evaluation criteria

Use this as your grading guide. Aim for the highest band by completing the “Distinction” checklist for each task.
 Distinction = 70%+ 
 70%+ Distinction   60-69% Merit   50-59% Pass   Below 50% Fail 
Assignment 1
Define Information Requirements
AIRs / OIR / PIR templates + mapping + rules
70%+ Distinction
  • Clear, accurate EIRs using relevant templates (OIR, PIR, AIR)
  • Tasks mapped with correct verification rules
  • Correct classification applied where needed
60-69% Merit
  • Mostly correct EIRs with minor errors
  • Task mapping present (may miss small elements)
50-59% Pass
  • EIRs included but inconsistent template use
  • Some gaps in rules or task assignment
Below 50% Fail
  • Incomplete or incorrect EIRs
  • Missing verification rules
  • Unclear task assignment
Assignment 2
BEP + MIDP + Work Package Setup
Responsibilities + milestones + model links
70%+ Distinction
  • Tailored BEP & MIDP
  • Clear responsibilities, milestones, and dependencies
  • Work packages linked to correct models
60-69% Merit
  • BEP and MIDP present
  • Most tasks assigned
  • Model linkages may lack detail
50-59% Pass
  • Basic BEP/MIDP submitted
  • Incomplete or not well-aligned
  • Models assigned with gaps
Below 50% Fail
  • BEP or MIDP missing or unclear
  • Work packages not created or not linked
Assignment 3
Model Verification and Handover Packaging
Verification + statuses + folder structure + report
70%+ Distinction
  • Verification run correctly and issues resolved
  • Relevant tasks marked complete
  • Placeholder file added properly
  • Structured folders created with proper naming conventions
  • All required files included + verification report included
60-69% Merit
  • Verification completed (small issues missed)
  • Task status mostly updated
  • Folder structure mostly correct
  • Minor naming issues or missing report
50-59% Pass
  • Basic model check completed
  • Task status not fully updated
  • Placeholder file may be missing
  • Folder exists but lacks structure / naming conventions
  • Report may be incomplete
Below 50% Fail
  • Verification not performed correctly
  • Status updates and placeholder absent
  • No clear handover structure / missing files
  • Non-compliance with standards
Assignment 4
Final Acceptance
Archive + sign-off + lessons learned
70%+ Distinction
  • Thorough review completed
  • Archive folder used correctly
  • Sign-off document complete with lessons learned
60-69% Merit
  • Final review evident
  • Archive present
  • Sign-off may lack reflection or signature
50-59% Pass
  • Final review basic
  • No archive or missing sign-off
Below 50% Fail
  • No evidence of final acceptance or review process
Bonus
Optional - added value
Extra effort + clarity + insight
70%+ Distinction
  • Insightful reflection, strong presentation, or added value
  • Examples: creative structure, extra detail, clearer organisation
60-69% Merit
  • Some extra effort shown
50-59% Pass
  • Minor enhancements
Below 50% Fail
  • No attempt for bonus work
IMAGE

We run on SmartLeanBIM®