This video walks through creating BIM scope requirements from scratch inside the Scope module. The written guide below covers the full workflow, from opening the library to selectively importing milestones, folders, tasks, and information requirements for your project.
Build precise project scope without copying old spreadsheets
Most teams start a new project by copying the last one’s Excel scope file, then spending hours deleting rows, checking what still applies, and hoping nothing irrelevant slipped through. That process creates waste. Requirements left over from a previous project cause confusion, trigger unnecessary work, and introduce risk that only surfaces once delivery is underway.
The Scope module in Plannerly replaces that copy-and-clean approach with a selective import workflow. Instead of starting with everything and removing what you don’t need, you start with a blank scope and pull in only the milestones, folders, tasks, and requirements that actually apply. The result is a scope that’s accurate from day one, with no leftover items creating noise for your team.
The key to this workflow is the library panel on the left side of the Scope module. It gives you three sources to draw from: raw content (a curated library of elements, items, and task types), your previous projects, and a collection of ready-made templates. When you find the content you need, a single click brings it into your project. You choose what comes along with it: teams, information requirements, checklist items, attachments, notes, and even the dependencies between tasks so your timeline reflects the correct delivery sequence from the start.
This matters for ISO 19650 workflows because scope definition directly affects everything downstream. When you selectively import project setup requirements and then add discipline-specific scope (structural, architectural, or MEP), each task arrives with its full set of information requirements already defined. The element linking rules that come with imported content also prepare your project for the Verify workflow, where model elements are automatically connected to scope requirements for checking. The more precise your scope is at the start, the less rework your team faces later.
How to create scope requirements from a blank project
- Start with a blank scope – Remove or skip any default content so you are working from a clean starting point with no inherited requirements.
- Open the library panel – Click the library on the left side of the Scope interface to access your import sources.
- Choose your source – Select from raw content, previous projects, or templates using the dropdown at the top of the library panel.
- Configure import settings – Click import settings to choose which elements travel with your scope: teams, information requirements, checklists, attachments, notes, dependencies, and element linking rules.
- Import project setup requirements – Click once on the project setup folder to bring in foundational requirements that apply across all disciplines.
- Add discipline-specific scope – Select the structural, architectural, or other discipline folders you need, each bringing their tasks and information requirements.
- Review your scope – Confirm that only the milestones, tasks, and requirements relevant to your project have been imported.
- Begin collaboration – With a precise scope in place, create contracts or invite team members to start working inside the project.
What you’ll learn
- Selective importing – How to bring in only the milestones, folders, and tasks your project actually needs instead of inheriting an entire previous scope.
- Library sources – How to use raw content, previous projects, and templates as starting points for new project scope.
- Import configuration – How to control what travels with each import, including teams, information requirements, checklists, and dependencies.
- Element linking rules – How imported linking rules prepare your scope for automatic model verification later in delivery.
- Faster project setup – How starting selective produces a cleaner, more accurate scope in less time than copying and cleaning a spreadsheet.
Common questions
Can I import from multiple sources into the same project?
Yes. You can pull in content from raw library items, previous projects, and templates in any combination. Each import adds to your existing scope, so you can build up your project requirements from several sources in a single session.
What happens to dependencies when I import scope?
If you enable the dependencies option in import settings, the task relationships come across with the imported content. This means your timeline will reflect the correct delivery sequence from the moment you import, without needing to manually rebuild the waterfall.
How is this different from duplicating a project?
Duplicating a project copies everything, leaving you to remove what doesn’t apply. The library import approach is the opposite: you start with nothing and add only what you need. This produces a more accurate scope with less cleanup, and avoids the risk of leftover requirements causing confusion during delivery.
Do information requirements come through with imported tasks?
Yes, as long as you enable the information requirements option in import settings. Each task arrives with its full set of requirements already attached, so you don’t need to redefine your information requirements manually after importing.
Explore further
- Importing scope from a template or another project – Step-by-step guide to the library import workflow in the Scope module.
- Centralize BEP information and avoid duplicating efforts across Excel – Why moving away from spreadsheet-based scope reduces duplication and risk.
- Creating and structuring scope – Help collection covering all aspects of building scope in the Scope module.
- BIM Boot Camp – Free course covering the fundamentals of BIM management and ISO 19650 workflows.
- How to build BIM requirements – Blog post on defining clear, structured requirements for your projects.