Why to Use This Approach
Users typically don’t need a full copy of another project, only key parts.
It helps reusing certain tasks, phases, or deliverables across multiple projects.
It helps keep your active project lean and avoid duplicating unnecessary items.
It supports maintaining relationships (such as dependencies or assignments) in your current project while bringing in new content.
Step-by-Step: Bringing in Content from Another Project
Here’s how to bring content from another project into your current project:
Open your current (target) project, i.e., the one you will continue working in.
Locate your Templaters library both in the Docs and Scope module in the top left corner
You’ll be presented with a list of your existing projects. Choose the source project from which you want to bring content.
Once selected, you’ll see a list of items within that source project, such as Document sections in the Docs module and list of tasks in the Scope module - in the Scope module, you can also define what additional information you want to import, eg.: information requirements, task assignments, document requirements, checklists, etc...
Select only the items you want to import and ADD them to your actual project, or drag them to a specific place in your document/scope
The selected items will now appear in your current project. They are added as new items, not overwriting content in your actual project
Review the imported items in your project: reorganize if needed (move to different phase, reassign, adjust dates).
Key Differences from “Duplicate Project”
Scope: You only bring particular items, not the whole project.
Project identity: use SmartFields to quickly fill the documents with project specific information and create a project specific agreement from a generic template efficiently
Source project remains untouched: The source project is not duplicated, and its items are not altered.
More control: You pick exactly what you want, rather than getting a full copy you then have to prune.