Course Content
Level 1 Information Manager – Basics

This video shows how to use Quick Assign to define BIM scope requirements efficiently across multiple items and milestones. The written guide below explains how the Quick Assign menu works, how teams use it in scope meetings, and how Delete Mode helps remove requirements that are no longer needed.

Define scope requirements in clicks instead of hours

When you have dozens or hundreds of scope items that each need requirements defined across multiple milestones, clicking into every single task individually takes far too long. The Quick Assign tool in Plannerly’s Scope module solves this by letting you define scope requirements, coordination needs, team responsibility, and status in just a few clicks per item. What would normally take hours of manual entry can be completed in a fraction of the time.

Quick Assign works from a panel on the right side of the Scope module. You open the menu, choose the scope level required, define the coordination needs, select the responsible team, and set a status. Four clicks and the full requirement is defined for that item at that milestone. Then you move on to the next item and do the same. This speed matters because teams that define scope well tend to do it in focused, dedicated meetings where stakeholders go through each set of requirements together. Quick Assign makes those meetings productive rather than tedious.

The workflow is designed around the questions teams should be asking at each information exchange. For a specific purpose – whether that is 3D coordination, cost estimation, or an asset model – do we require geometry? Do we require information? Do we require documentation? And who is responsible for delivering each aspect? Each milestone and each exchange will have a different set of answers, and Quick Assign lets you capture those answers rapidly as information containers without losing the flow of the conversation.

Quick Assign also includes Delete Mode for cleaning up scope that is no longer required. If a review meeting determines that certain requirements are unnecessary, you can switch to Delete Mode and remove them just as quickly as you added them. This keeps the scope accurate and prevents the buildup of requirements that nobody actually needs, which is one of the main causes of waste on ISO 19650 projects. The combination of fast creation and fast removal means your scope stays lean and purposeful throughout the project.

How to use Quick Assign for scope definition

  1. Open the Quick Assign menu – Click the Quick Assign panel on the right side of the Scope interface to access the rapid assignment controls.
  2. Set the scope level – Choose the scope required for the item, defining the level of detail or coordination needed at that milestone.
  3. Define coordination needs – Specify exactly how coordinated the deliverable needs to be for its intended purpose.
  4. Assign a team – Select which team is responsible for delivering this requirement.
  5. Set a status – Choose the current status (such as proposed, agreed, or in progress) to reflect where this requirement sits in the review process.
  6. Move to the next item – Click on the next scope item and repeat the process. Each assignment takes just a few clicks.
  7. Use Delete Mode to clean up – Switch to Delete Mode to quickly remove any requirements that are no longer needed after a scope review.

What you’ll learn

  • Quick Assign workflow – How to define scope requirements, coordination, responsibility, and status in just four clicks per item.
  • Purpose-driven questions – How to ask the right questions at each information exchange: do we need geometry, information, or documentation, and who delivers it?
  • Scope meeting efficiency – How teams use Quick Assign in dedicated meetings to define requirements collaboratively without losing momentum.
  • Delete Mode – How to rapidly remove requirements that are not needed, keeping scope lean and preventing unnecessary work.
  • Information containers – How Quick Assign builds structured containers of requirements tied to specific milestones and deliverables.

Common questions

When should teams use Quick Assign versus defining requirements individually?

Quick Assign is ideal when you need to define requirements across many items in a single session, such as during a scope review or proposal meeting. For individual tasks that need more detailed configuration, like adding specific information requirements, checklists, or attachments, you would open the task directly. Most teams use Quick Assign first to set the broad structure, then go back and add detail where needed.

Can I change requirements after using Quick Assign?

Yes. Quick Assign sets the initial values, but everything can be edited afterwards. You can open any task to adjust geometry, coordination, team assignments, status, or any other property. Quick Assign is about speed of initial definition, not locking things down.

How does Delete Mode work?

Delete Mode reverses the Quick Assign workflow. Instead of adding requirements when you click, it removes them. This is useful after a scope review where the team agrees that certain items are not needed at certain milestones. You can clean up the scope just as fast as you built it, keeping the scope accurate without manual task-by-task deletion.

How does Quick Assign support ISO 19650 scope meetings?

ISO 19650 requires that information requirements are defined for each exchange. Quick Assign lets teams work through those exchanges systematically in a meeting, asking the right questions (geometry, information, documentation, responsibility) and recording the answers in real time. This produces a structured set of requirements that can be agreed and then followed through delivery.

Explore further

0% Complete

Pin It on Pinterest