This video is the final assignment for the basic Verify module training. The written guide below walks through creating a new project, adding a document with smart fields, defining a simple scope requirement for exterior walls, and using the Verify module to check whether the model actually contains the required information properties.

Define a requirement, connect a model, and verify the result

This assignment brings together everything covered in the Docs, Scope, and Verify modules. You will create a new project, add a document from the library, define a simple scope requirement with information properties, connect it to a 3D model using a model rule, and check whether the model contains what was asked for. The entire workflow demonstrates how ISO 19650 verification works in practice: define the requirement, connect the deliverable, and see instantly whether the information is actually there.

The project starts at the account home in Plannerly, where you create a new project and select a document from the library. The document loads with smart fields already populated, so you don’t need to fill in project details across every section manually. In the Scope module, you add a retaining wall element from the library, rename it to “exterior walls” to match the model content, and assign it to a cost estimation milestone. Then you define three simple information requirements: width, length, and area. No units, no groups, no complex rules – just three properties that need to have a value.

In the Verify module, you connect the model to the task. Because you renamed the scope item to “exterior walls” and the model contains elements with the type name “exterior walls”, the existing model rule automatically matches them. The rule connects 12 wall elements to the task, and Verify immediately evaluates whether the required properties are present. The initial result shows 67% completion with all elements marked red – a clear signal that something is wrong. In this case, the property name “length” was misspelled in the scope setup, so the check could not find a matching property in the model.

This is an important lesson: verification results are only as good as the requirement setup. Going back to Scope and correcting the spelling instantly changes the result to 100% completion with all elements green. Once verified, you mark the task as complete, move it to the completed column on the Kanban board, and share the model so the manager is notified that it is ready for review. The colour coding across the 3D view shows exactly which elements passed and what percentage of the overall milestone is complete, making the status visual and immediate rather than buried in a report.

Assignment steps

1. Create a new project – Start from the account home and create a fresh project for this exercise.
2. Add a document from the library – Click once to add a document template; smart fields populate project details automatically across the Docs module.
3. Add a scope item – Open the Scope module library, search for a retaining wall, and add it to your project.
4. Rename and configure – Rename the item to “exterior walls” and assign it to a cost estimation milestone.
5. Define information requirements – Create three simple properties: width, length, and area, each requiring any value.
6. Open the Verify module – Navigate to Verify and use the demo model (or your own) that contains exterior wall elements.
7. Check the model rule connection – Confirm that the model rule matches “exterior walls” in the task name to the type name property in the model, linking the elements automatically.
8. Review the verification result – Check the completion percentage and identify any elements marked red that do not meet the requirements.
9. Fix the setup – If the result shows incomplete, go back to Scope and correct any property names that were misspelled or misconfigured.
10. Re-verify and complete – Return to Verify, confirm 100% completion, mark the task as complete, and share the model for manager review.

What you’ll learn

• End-to-end workflow – How Docs, Scope, and Verify work together to define, deliver, and check project requirements in a single platform.
• Model rule matching – How naming a scope item to match model content allows automatic element-to-task connection without manual linking.
• Property checking – How Verify evaluates whether required information properties are present and calculates a completion percentage.
• Troubleshooting setup errors – How incorrect property names in Scope cause verification failures, and how fixing them instantly updates results.
• Colour-coded verification – How red and green colour coding on model elements makes pass/fail status visually obvious in the 3D viewer.

Common questions

Explore further

• Linking models for auto-checking – Detailed guide to model rules and task rules for automated element-to-task connection.
• Why a parameter is not linking or checking – Troubleshooting guide for when verification rules do not produce expected results.
• Simplifying BIM model checking automation – Overview of how automated checking reduces manual effort across project delivery.
• Creating and structuring scope – Help collection for building accurate scope that verification can check against.
• BIM Boot Camp – Free course covering BIM management fundamentals and ISO 19650 workflows.