This video shows how to define detailed information containers inside the Scope module. The written guide below explains how to set geometry, reliability, descriptions, checklists, attachments, information requirements, and team assignments so every deliverable has clear acceptance criteria.

Define what good looks like for every project deliverable

One of the most common problems on BIM projects is receiving a model that doesn’t actually serve the purpose it was intended for. When requirements are vague, teams interpret them differently. The result is duplicated effort, overlapping models, and wasted time sorting out who was supposed to deliver what. The Scope module in Plannerly solves this by letting you define information containers that spell out exactly what is required, who is responsible, when it is needed, and what the acceptance criteria are.

An information container is a structured package of requirements attached to a specific task at a specific milestone. Inside each container, you define the geometric requirements and how reliable that geometry needs to be. You can configure these using Level of Information Need, level of detail, level of development, or whichever framework your project follows – all of these can be selected in project settings. Beyond geometry, each container holds a description explaining the purpose, a checklist of items the team must complete, attachments such as specifications or reference documents, and detailed information requirements like concrete compression strength or material thickness.

The checklist feature is especially practical for teams that need to define acceptance criteria clearly. You can type items individually or paste a full list in one go – Plannerly creates one checklist item per line, so preparing your criteria in a text editor and pasting them in takes seconds. Attachments work the same way: drag and drop a specification PDF or reference drawing, and it becomes part of that task’s container. These attachments are also visible in the File Manager, connecting the scope to the wider project data environment.

Once a container is fully defined, you assign it to specific teams and team members. Every change, assignment, and update is tracked in the activity history, creating a golden thread of who did what and when. This audit trail matters for ISO 19650 workflows because it supports accountability and traceability throughout delivery. And this approach is not limited to model elements. You can define the same level of detail for drawing packages, reports, and any other type of deliverable. When you define containers this way, every task on the project has a clear, agreed set of requirements that teams can work towards and be measured against.

How to define an information container in the Scope module

1. Select a task – Click on a task in your scope to open its container and start defining the detailed requirements for that deliverable.
2. Set geometry and reliability – Define the geometric representation required and the reliability level, choosing the appropriate framework (LOIN, LOD, or LODev) in project settings.
3. Add a description – Type a clear explanation of the task’s purpose so the team understands not just what to deliver, but why it matters.
4. Define checklist items – Add acceptance criteria one by one, or paste a prepared list to create multiple items at once (one per line).
5. Attach specifications – Drag and drop reference documents, specifications, or drawings directly onto the task to give the team everything they need in one place.
6. Set information requirements – Define the specific properties required, such as material type or compression strength, using standardized property names where possible.
7. Assign teams and members – Allocate the task to the responsible team and team members so ownership is clear from the start.
8. Review the activity history – Check the golden thread of tracked activities to confirm all requirements have been set and assignments are in place.

What you’ll learn

• Information containers – How to build structured packages of requirements that define geometry, reliability, descriptions, checklists, attachments, and properties for each task.
• Acceptance criteria – How checklists and information requirements give teams a clear standard to deliver against and measure completion.
• Bulk checklist entry – How to paste a prepared list of checklist items to define acceptance criteria quickly rather than typing each one individually.
• Attachments and specifications – How dragging reference documents into a task connects them to both the scope and the File Manager.
• Activity tracking – How the golden thread of history records every change, supporting accountability and traceability under ISO 19650.

Common questions

Explore further

• Defining information tasks and containers – Companion lesson on building task containers inside the Scope module.
• How to create a master information delivery plan (MIDP) – Step-by-step guide to building delivery plans from your defined containers.
• Level of Information Need (LOIN) explained – Guide to the ISO 19650 framework for defining information requirements at each project stage.
• 5 reasons to use BIM checklists – Why structured checklists improve project quality and team alignment.
• BIM Boot Camp – Free course covering BIM management fundamentals and ISO 19650 workflows.