Featuresquad and up

Task Templates

A reusable task tree with descriptions, tags, assignees, and subtasks up to three levels. Stamp it into any project, under any parent task.

By ToDidIt Product TeamUpdated 6 September 2026

What does a task template hold?

Task titles, descriptions, tags, assignees, and nested subtasks up to three levels deep. The standard multi-step things your team does over and over: a client onboarding, a release checklist, a new-hire setup.

How do I use one?

Drop a task template into an existing project, into your project-less tasks, or underneath another task as its subtree. It goes where you point it rather than forcing a new project.

The one rule is depth. Tasks nest three levels deep and no further, so a template that is itself two levels deep cannot be dropped under a task that is already a subtask. You get told rather than getting a quietly flattened tree.

One saved Task Template, a three step release checklist, with arrows to three destinations. First, into a project, where its tasks are added to the bottom of that project's list. Second, into the Inbox of the workspace you are in, when you pick no project. Third, underneath an existing task, where its tasks arrive as that task's subtasks. A note under the third destination records the limit: nothing may end up more than three levels deep, so a two level template cannot be dropped under a task that is already a subtask, and ToDidIt refuses rather than flattening it. — One template, three destinations. You point, it lands there.

Turning a checklist you keep retyping into a template

The onboarding steps, the release checks, the things you do every time.

Mark step 1 complete: Select the tasks that make up the checklist.
Select the tasks that make up the checklist.
Shift click takes a range. Subtasks come along with their parents, so selecting the parent is enough.
Open All Tasks
Mark step 2 complete: Save the selection as a task template.
Save the selection as a task template.
Give it a name and, if it needs one, a description. What gets stored is a snapshot of those tasks and their structure, taken there and then.
Mark step 3 complete: Stamp it wherever you need it next time.
Stamp it wherever you need it next time.
Into a project, into Inbox, or underneath an existing task as its subtasks. That last one is the useful one: a standard checklist can be dropped under any task that needs it.

How do I make one?

Save a selection of existing tasks as a template, or write one from scratch in a blank editor. A project template has a project to snapshot; a task template is just a tree of titles, so it does not need a source.