Using templates

Start projects from a proven structure — your own templates, the curated gallery, or one generated from a description of your process.

A template is a project structure without the project: phases, the tasks inside them, and the gate criteria that end each phase. It is how a methodology stops being something one experienced person carries around in their head.

Where templates come from

There are three ways to get one.

Templates in the sidebar lists everything your team has built. These are yours to edit, duplicate and delete.

Most teams end up with a small number — one per genuinely different kind of project, not one per project.

Using a template

Pick it at step two of the project wizard. The new project gets:

  • every phase, in order, with the first started,
  • every task, unassigned and not started, with the template's priorities, estimates and required skills,
  • every gate criterion, all incomplete.

Deadlines are not copied — templates carry effort estimates, not dates, because a date only means something relative to a real start.

If the project has a description, cadence. rewrites each task's title and description to fit it. The structure is untouched; only the wording becomes specific.

A project created from a template is independent of it from that moment on. Editing the template later does not change projects already created from it, and editing a project never affects the template.

This is deliberate. A live project should not change shape because someone tidied a template, and a template should not accumulate one project's exceptions.

Plan limits

The free plan includes up to 2 templates. Pro and Enterprise are unlimited. See plans and limits.

Reading templates over the API

GET /templates returns every template with its phases and tasks, which is the straightforward way to mirror your methodology into another system. See the API reference.

Was this page helpful?

Search the docs

Find a page or a section by name.