What we do
Tools
Industries
Department
How we workLet's talk →
Home/Asana/Asana Template
Asana

Asana Template: Where to Find One, and How to Save Your Own

Asana has two kinds of template. A project template sets up a whole project: sections, tasks, fields, rules and who does what. A task template sets up one repeat task with its subtasks. You can start from Asana's gallery or save a project you've already run as your own template.

Asana templates, fast

Use one: create a new project and choose Use template, then pick from your team's library or Asana's gallery. Asana lists more than 80 ready-made ones.

+ Create Project Use template

Save your own: open the dropdown next to the project's name and choose Save as template. On some views it's under More.

Task template: open a task's three-dot menu and convert it to a template, or add one from the project's Customize menu.

Which kind of Asana template fits the work

The work you repeat Use Watch for
A whole project with a start and an end: an event, a launch, a client onboarding A project template, with due dates set relative to the start date. If dates aren't relative, every task lands on the dates of the project you saved from.
One task that recurs inside a project: a weekly report, a new-hire setup A task template with its subtasks and fields. It belongs to that project. Other projects need it added there, or built into their project template.
A process that runs differently per person or team A project template with roles instead of named people. Assign each role when you create the project, or tasks start unassigned.
Something you do once or twice a year Duplicate last year's project. Clear out last year's comments and completed tasks first. A template is only worth it once you repeat it.

Save a project as an Asana template

  1. 1

    Clean up a project you already ran

    Keep the sections, tasks, custom fields and rules that every run needs. Remove client names, one-off tasks and anything already done.

  2. 2

    Save it as a template

    Open the dropdown next to the project name and choose Save as template. Pick the team it belongs to so it shows in that team's library.

  3. 3

    Set dates relative to the start

    In the template, set each due date as a number of days from the project's start or due date. Asana can skip weekends when it works them out.

    Watch for: this is the step people skip. Without it, a project created next month still has last month's dates.

  4. 4

    Replace people with roles

    Assign tasks to roles such as Designer or Account lead. When someone uses the template, Asana asks who fills each role, so the work still reaches the right person after the team changes.

  5. 5

    Preview it, then use it

    Preview the template, create a test project from it, and check the dates, assignees and rules before the team relies on it.

Keeping 30 projects in step with one template

Templates are good at day one. The trouble comes when your process changes and a few dozen projects are already running. Asana won't push the change into them, so someone opens each one and adds the new tasks by hand, or the old process quietly carries on.

n-frames writes the script that does it: it finds every project made from that template, adds the missing sections and tasks with the right relative dates, and leaves finished work alone. We also start projects from your template through Asana's API when the work arrives elsewhere, a signed order or a new hire in your HR system, with the start date and roles set. For the rules inside a project, see Asana automation, and for linking Asana to other systems, Asana integrations.

What Asana templates do and don't change later

Editing the template leaves existing projects alone

How you'll know: You added a compliance step to the template, but every project started before today still lacks it.

Fix: Asana applies template changes to future projects only. Add the step to live projects yourself, or script it for many projects at once.

Rules fire the moment the project is created

How you'll know: Tasks move or people get notified before anyone has looked at the new project.

Fix: Rules saved in a template run when the template is used. Check them on a test project before the team starts using it.

Too many near-identical templates

How you'll know: "Onboarding", "Onboarding v2" and "Onboarding (Sam)" all sit in the library.

Fix: Keep one per process, duplicate it only for a real variation, and limit who can edit it. The creator sets edit access.

Questions people ask

How do I create a custom template in Asana?

Build the project (or task) the way every future one should start, then choose Save as template from the dropdown next to the project's name. For a single task, convert it from the task's three-dot menu. Saving your own templates depends on your plan.

Can I create a task template for a recurring deliverable?

Yes. A task template recreates the same subtasks and fields each time, for a weekly report or a client checklist, and can set due dates relative to when the task is created.

Does Asana have an SOP or event-planning template?

Asana's gallery has event-planning, event-schedule and run-of-show templates, and Asana publishes an SOP template guide. Each gallery template opens with sections and fields set up for that kind of work.

Can admins require a specific template for new projects?

We couldn't find an Asana setting that forces every new project to start from one template. Teams usually keep one approved template in the team library and limit who can edit it. Where it must be guaranteed, projects are created from the template automatically instead of by hand.

Can I create an Asana project from a template through the API?

Yes. Asana's API has an instantiate-project call for project templates. It runs as a background job and takes the new project's name, team, dates and who fills each role. There's also a call to save an existing project as a template.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.