SOURCE-BASED ANALYSIS · NO HANDS-ON RATING
Treat a copy as a draft
Todoist documents that project duplication copies active tasks and sections but excludes reminders, comments, completed tasks and archived sections. Sharing settings are not copied; the duplicate starts private. Review both included content and omissions before treating a duplicated project as a ready client workspace.
Example: repeat a website handover
Assume an agency has a reusable checklist from one website launch. The next client needs similar steps, but different dates, contacts and deliverables. A copied task called Approve homepage can be useful. A copied description pointing to the previous client's private material is not.
Build a reset sheet with three columns: reusable process, client-specific value and required new value. Put review steps in the first column and names, URLs, dates and file locations in the second. Leave the final column empty until the new project owner supplies them.
Inspect before inviting collaborators
- Duplicate into a clearly named preparation project.
- Read every active task title and description for old client details.
- Replace dates with an approved schedule instead of shifting them blindly.
- Recreate reminders only after their purpose and recipient are confirmed.
- Review the finished content and intended audience before sharing.
This checklist is a proposed procedure. It does not imply that invitations have been sent or that a copy has been created in an account.
Resolve missing instructions
If the original process relies on comments, decide where the reusable instruction belongs. For example, a standing approval criterion should be written into the template description, while a one-off conversation should remain with the original client record. Do not compensate for missing comments by copying an entire private discussion into a new project.
Check the copy's first and last tasks together. If the first task lacks the required inputs or the final task does not define acceptance, the middle of the checklist can be perfectly organized and still fail to deliver a usable handover.
Approve a reusable baseline
Once the new project is accepted, keep a separate neutral baseline for future work. Name the owner of that baseline and the trigger for revising it. Copying the most recent client project each time encourages accidental accumulation of specific details.
Use duplication when the active process is genuinely similar. Start a fresh structure when the scope or audience changes substantially. A few reusable tasks are helpful; inheriting a whole workflow merely because it is convenient can create more review work than it saves.
For the complete learning path, visit the Todoist practical guide hub.
Sources and verification
Official documentation checked on 2026-10-29. Worked examples are hypothetical planning exercises, not measured product benchmarks.