Help Center
DocsProject Templates
Save a repeatable set of project tasks once and stamp it onto new delivery projects
A project template is a saved set of tasks for delivery work you run the same way each time: an onboarding, an implementation, a standard engagement. When you start a project from a template, the template's tasks are copied onto the new project so the delivery team begins with the checklist already in place instead of a blank slate. A template can include tasks marked as milestones, so the key dates come along too.
Create a template
Give the template a name and add the tasks it should seed, marking any that represent milestones. The template is saved to your organization so anyone who starts a project from it gets the same starting checklist.
Edit its task list
Rename a template or change the tasks it seeds at any time. Edits apply to future projects created from the template. Projects you already created from it are not touched.
Delete a template
Remove a template you no longer use. Deleting it does not affect any project that was already created from it: those projects keep their tasks.
A project copies a template's tasks by value at creation time.
Starting a project from a template stamps a copy of the template's tasks onto the project. From that point the project is independent: it does not stay linked to the template, and it does not track the template's later edits. Change a template and only new projects pick up the change. Delete a template and existing projects keep everything they were seeded with. This makes templates safe to evolve without worrying about disturbing delivery already in flight.
The most common way to use a template is when you turn a won deal into a delivery project. In the Start delivery flow you can pick a template and an optional project name; the new project is created linked to the deal and company, with the template's tasks already seeded. See From Won Deal to Delivery Project for the full handoff.
Automations can seed a project from a template too. The Create project from template automation action lets a flow spin up a project with its starter tasks when a trigger fires, so a repeatable delivery kickoff can run without anyone clicking through it.