This video shows how to define visual BIM requirements inside the Scope module. The written guide below explains how to use library elements, custom images, and geometric representations to make project requirements clearer and easier for your team to understand.
Replace bland spreadsheet rows with visual scope requirements
When geometric requirements live in a spreadsheet, they are just text in a cell. A row that says “concrete stair flight – LOD 300” tells you something, but it doesn’t show you anything. Teams end up interpreting those requirements differently, and misunderstandings only surface once modelling is underway. The Scope module in Plannerly takes a different approach by letting you define requirements visually, so everyone on the project can see exactly what needs to be delivered, when, and at what level of geometric detail.
The visual element library gives you a searchable collection of pre-built objects. Open the library, select it from the dropdown, and either browse or search for specific elements like stairs, walls, or structural members. When you find what you need, drag it directly into your scope. Each element comes with images that represent different levels of geometric detail, so your scope grid shows a visual progression of what is expected at each milestone. At an early stage you might require 2D geometry, then 3D at a later milestone, and more detailed representation further along. The visual difference between those stages is immediately obvious in the grid.
If the library doesn’t have the exact image you need, you can upload your own. Edit any element, drag in an image from a web search, and Plannerly isolates the object by removing the background automatically. This means you can represent any deliverable visually, whether it’s a model element, a report, a drawing package, or any other type of project output. The isolated background keeps your scope clean and consistent, making the grid easy to scan at a glance.
This visual approach matters for ISO 19650 requirements management because it connects scope directly to understanding. When a team member opens the scope and sees an image of a concrete stair flight at a particular level of detail, there is no ambiguity about what is expected. As you build your scope, the key discipline is making sure every visual representation has a clear customer and purpose. If nobody needs that level of detail at that milestone, it shouldn’t be there. This selective approach prevents teams from over-modelling and keeps the scope focused on what actually drives project value.
How to define visual requirements in the Scope module
- Open the element library – Click the library panel and select the element library from the dropdown to access the pre-built collection of visual objects.
- Search for elements – Use the search function to find specific objects like stairs, columns, or facades rather than browsing the full library.
- Drag elements into scope – Click or drag visual elements directly from the library into your scope structure to add them as requirements.
- Upload custom images – Edit any element and drag in your own reference image; Plannerly removes the background automatically to keep the visual clean.
- Review geometric progression – Check that each element shows the correct visual representation at each milestone, from simple 2D through to detailed 3D geometry.
- Assign milestones in the grid – Click cells in the task grid to define when each visual requirement is needed during delivery.
- Validate each requirement has a customer – Confirm that every geometric representation at every milestone has a clear purpose and recipient to avoid unnecessary scope.
What you’ll learn
- Visual element library – How to search, browse, and drag pre-built visual elements into your scope to represent geometric requirements clearly.
- Custom image upload – How to add your own reference images with automatic background removal for a clean, consistent scope view.
- Geometric progression – How different visual representations at different milestones communicate changing levels of detail over time.
- Requirement validation – Why every visual requirement should have a clear customer and purpose, preventing unnecessary modelling effort.
- Team understanding – How visual scope requirements reduce misinterpretation and get everyone aligned on what needs to be delivered.
Common questions
Can I use my own images instead of the library elements?
Yes. Edit any element in your scope, drag in an image, and Plannerly automatically removes the background to isolate the object. This works with any image source, so you can represent custom deliverables, project-specific components, or any requirement that isn’t covered by the built-in library.
How do visual elements show different levels of detail across milestones?
Each element can have multiple visual representations that correspond to different levels of geometric detail. In the scope grid, these appear at different milestones, so you might see a simple 2D representation at an early stage, a basic 3D model at mid-stage, and a fully detailed version at a later milestone. This makes LOD requirements immediately visible rather than buried in text.
Does this work for non-geometric deliverables like reports?
Yes. Visual scope is not limited to model elements. You can represent any type of deliverable, including reports, drawing packages, schedules, and other project outputs. Each can have its own image and milestone assignments in the grid, so your full set of project requirements is visible in one place.
Why does it matter that each requirement has a customer?
Defining a customer for each requirement prevents scope creep and over-modelling. If nobody needs a detailed 3D representation of a particular element at a particular milestone, including it wastes the team’s effort and adds unnecessary complexity. Linking every requirement to a clear purpose keeps the scope focused on real project needs.
Explore further
- Understanding the Scope user interface – Overview of the Scope module layout, including the library panel and visual grid.
- Custom levels of development – How to define your own LOD scales to match your project’s geometric requirements.
- Defining your classification structure – Companion lesson on organising scope elements within a classification hierarchy.
- The root of BIM problems: poor information requirements – Why clear, visual requirements prevent the most common delivery failures.
- BIM Boot Camp – Free course covering BIM management fundamentals and ISO 19650 workflows.