This video is a hands-on assignment that brings together the Docs and Scope modules. The written guide below walks through creating a new project, reusing a BIM Execution Plan and scope milestone from a previous project, and exporting everything together as a combined PDF.
Reuse previous project content to set up new projects faster
Every new project does not need to start from a blank page. Teams that have already defined documents and scope on a previous project can reuse that work to get a new project up and running in minutes. This assignment puts that into practice by walking through the full workflow: creating a new project, pulling in an existing BIM Execution Plan from a previous project, selectively importing a scope milestone, and combining both into a single PDF export.
The process starts at the account home in Plannerly, where you create a new project and reference an existing one as a starting point. For documents, you select the BIM Execution Plan from the previous project. For scope, you choose a specific milestone rather than bringing in everything. In this example, you import just the 3D coordination milestone along with the structural concrete scope. This selective approach means you only carry across what is relevant to the new project, rather than duplicating an entire scope and cleaning it up afterwards.
When scope content is imported this way, the project teams, information requirements, and attachments all carry across into the new project. Task statuses are not copied, which makes sense because the new project’s tasks haven’t started yet. The attachments that were linked to tasks in the original project are available in File Manager, so specifications and reference documents travel with the scope automatically.
The final step is creating a combined PDF that includes both the document and the scope information. You select a cover page, add a document index, choose the BIM Execution Plan, include the scope grid and details, give the export a name, and generate it. The result is a single PDF with bookmarks that make it easy to navigate between sections. This is exactly the kind of output that teams share at project kickoffs or include in ISO 19650 delivery packages, where documents and scope need to be presented together as a coherent set of project requirements.
Assignment steps
- Create a new project – Go to the account home and start a new project, referencing the previous project (Skyline Residences) as your source.
- Import a BIM Execution Plan – Select the BEP from the previous project to bring it into your new project’s Docs module.
- Import a scope milestone – Open the Scope module library, choose the previous project, and selectively import just the 3D coordination milestone with the structural concrete scope.
- Review imported content – Check that project teams, information requirements, and attachments have carried across. Confirm that task statuses are blank (ready for the new project).
- Create a combined PDF export – Go to PDF export, select a cover page, add a document index, choose the BEP and scope grid with details, name the document, and hit create.
- Review the final PDF – Open the generated document and check that all sections are present with bookmarks for easy navigation between the BEP and scope content.
What you’ll learn
- Project reuse workflow – How to create a new project that references previous work instead of starting from scratch every time.
- Selective scope import – How to bring in only the milestones and scope items relevant to the new project, keeping your requirements lean and accurate.
- Content that travels – How teams, requirements, and attachments carry across from one project to another while task statuses reset for the new project.
- Combined PDF export – How to merge documents and scope into a single bookmarked PDF that is easy to navigate and share.
- Docs and Scope integration – How the two modules work together to produce a complete set of project documentation from a single platform.
Common questions
Can I import from multiple previous projects into the same new project?
Yes. You can reference different previous projects for documents and scope separately, or bring in content from several projects. The library and template system lets you combine content from any available source to build up your new project exactly as needed.
Why are task statuses not copied across?
Task statuses reflect the progress of a specific project. When you import scope into a new project, the tasks start fresh because no work has been done on them yet. The structure, requirements, teams, and attachments carry across, but each new project tracks its own progress independently.
What is included in the combined PDF export?
You choose exactly what goes into the export. Options include a cover page, document index, any documents from the Docs module, and the scope grid with varying levels of detail. The final PDF includes bookmarks for each section, making it easy to navigate. The PDF export and eSignatures guide covers the full set of export options.
What comes after this assignment?
With Docs and Scope covered, the next stage moves into the Verify module, where you connect 3D models and deliverables and start comparing them against the scope requirements you have defined. This is where the detailed information containers you built become the basis for automated checking.
Explore further
- How to use content from another project – Detailed guide to referencing previous projects when setting up new ones.
- How to schedule your scope – Guide to timeline and scheduling features that complement the scope you have imported.
- Model checking introduction – Preview of the Verify module that follows this assignment in the course.
- Creating and structuring scope – Help collection covering all aspects of building scope in the Scope module.
- BIM Boot Camp – Free course covering BIM management fundamentals and ISO 19650 workflows.