Course Content
Level 1 Information Manager – Basics

This video introduces the Verify module and how it combines a 3D viewer with a Kanban board for model checking. The written guide below explains how Verify connects model review, task management, and quality assurance into a single workspace for checking BIM deliverables against your original requirements.

Check models, track tasks, and verify quality in one connected space

Model checking is usually treated as a separate activity from task management. Teams open a model viewer to inspect geometry, then switch to a spreadsheet or task board to update status, then send emails to flag issues. The Verify module in Plannerly brings all of this together by combining a 3D model viewer with a Kanban board in the same workspace. You can review model elements, check information requirements, update task status, and manage the whole process without switching between tools.

The critical insight behind Verify is that checking whether model elements exist is not enough. A model might contain all the right geometry, but if the required information properties are missing, the deliverable is incomplete. Verify checks both. When you review an element like a ceiling, you can see whether it has the required material type, and the model is colour-coded based on status so you can instantly identify which elements meet the requirements and which do not. This visual feedback makes it far quicker to assess the state of a model than reading through a spreadsheet of pass/fail results.

For teams delivering models, Verify supports a self-quality check workflow. Before submitting work for formal review, the delivery team can connect their model, run checks against the original scope requirements, and see exactly where things are incomplete. This means issues are caught and fixed before the information manager or lead appointed party sees them, which reduces the back-and-forth that slows down every project. The Kanban board within Verify lets teams drag task cards through status columns, so tracking which elements are complete, in progress, or need attention becomes a visual, collaborative activity rather than a manual reporting exercise.

This approach directly reduces the time spent on task management and issue resolution. When teams can see at a glance whether a model deliverable meets the requirements that were originally defined in Scope, the whole verification process becomes faster and more reliable. The connection between what was required and what was delivered is maintained throughout, which is exactly what ISO 19650 workflows are designed to achieve.

How the Verify module works

  1. Open the Verify module – Navigate to Verify to access the combined 3D viewer and Kanban board workspace.
  2. Connect a model – Link a 3D model so its elements can be reviewed against the scope requirements you defined earlier.
  3. Review model elements – Use the 3D viewer to inspect geometry and see colour-coded status indicators showing which elements meet requirements and which do not.
  4. Check information properties – Go beyond geometry to verify that required information properties (like material type) are present and correct on each element.
  5. Use the Kanban board – Drag task cards through status columns to track which deliverables are complete, in progress, or outstanding.
  6. Run self-quality checks – Delivery teams use Verify to check their own work against scope requirements before submitting for formal review.
  7. Identify and resolve issues – Use the visual feedback to pinpoint exactly which elements need attention, reducing the time spent on issue management.

What you’ll learn

  • Combined workspace – How Verify merges a 3D model viewer with a Kanban board so model checking and task management happen in the same place.
  • Beyond geometry checking – Why verifying that information properties are present and complete matters as much as checking that model elements exist.
  • Colour-coded status – How visual colour coding on model elements makes it instantly clear which parts of a deliverable meet requirements and which do not.
  • Self-quality workflow – How delivery teams can check their own models against scope requirements before submitting for formal review.
  • Streamlined issue management – How connected model checking reduces the time spent managing tasks and resolving issues later in the workflow.

Common questions

What is the difference between Verify and a standard model viewer?

A standard model viewer shows you geometry. Verify goes further by connecting the model to your scope requirements, so you can check not just whether elements exist but whether they carry the correct information properties. It also includes a Kanban board for task status tracking, making it a complete checking and management tool rather than just a viewer.

How does self-quality checking work?

Delivery teams connect their model to Verify and run checks against the requirements defined in Scope. The colour-coded results show them exactly where information is missing or incomplete, so they can fix issues before submitting for formal review. This reduces rework and means the information manager spends less time on basic checking and more time on coordination.

Does Verify only work with 3D models?

The 3D viewer is a core feature, but the Kanban board and task tracking work for any type of deliverable. If your scope includes drawing packages, reports, or other non-model outputs, those tasks can still be managed and tracked through the Verify module’s task management features alongside model checking.

How does Verify connect back to the requirements defined in Scope?

The information containers you define in Scope – including geometry, information requirements, checklists, and specifications – are what Verify checks against. When you link a model for auto-checking, elements are matched to scope requirements, and the colour-coded results show whether each requirement has been met. This creates a direct line from definition to verification.

Explore further

0% Complete

Pin It on Pinterest