Asana task templates provide a reusable starting structure for work inside a project. Use one when a deliverable repeats but each request needs its own brief, owner and acceptance checks.
Table of Contents
Choose a task template or a project template
A project template recreates a larger project structure. Its dates can be relative to the new project’s start or due date, with before-and-after offsets and an option to skip weekends. Choose that approach when each client engagement needs a separate coordinated project. Project templates and dates.
Illustrative example: a small studio produces client case studies inside its delivery project. Each request needs a brief, interview material, a draft and approval. A task template can make that individual deliverable consistent. An entire campaign with several deliverables and shared milestones may deserve a project template instead.
Create a clean reusable task
Task templates are available on Starter, Advanced, Enterprise and Enterprise+, plus specified legacy paid tiers. In a project, use Customize → Add template, or convert an existing task through its three-dot menu. Set the owner, instructions, dates, subtasks and handovers; save with Done. Use Add new or a section’s + menu to create a task from the template. Task template instructions.
Write the common method using placeholders for the client, brief and approval contact. Keep the final acceptance condition explicit: for the studio, it might be “approved text and design delivered to the agreed folder”. Remove the last client’s answers and files before making an existing task reusable. A filled-in example can accidentally become someone else’s instructions.
Treat relative dates as a starting schedule
Task templates support relative due dates or a date range instead of one fixed calendar deadline. Inspect the generated task’s actual dates before adopting the offset for a live request. Relative date controls.
For the studio, a request received today is not automatically ready for production today. The interview may still be unconfirmed. Agree the real deadline after checking the brief and reviewer availability, then inspect each generated subtask date. Our Asana recurring tasks guide addresses work that should repeat on a schedule; a reusable task structure and recurrence solve different needs.
Give subtasks their own meaningful responsibilities
Subtasks have their own task fields, but do not inherit the parent’s assignee. Completing the parent does not complete its subtasks. Subtasks also do not automatically inherit the parent’s project membership; add one to the project when it needs to appear in that project’s list or calendar. Subtask behaviour.
For the case study, useful steps might be Confirm brief, Collect approved material, Prepare draft, Review claims and Deliver approved files. Assign a person when the work changes hands. Keep a simple instruction in the parent task for checking all required steps before completing the deliverable. Avoid a deep nesting scheme that hides who is waiting for whom.
Use dependencies for genuine handovers
A dependency marks a task as blocking or blocked by another task. From the task details, add a dependency and select the predecessor. Completing the first task notifies the next task’s assignee that they can begin. The list view separates Blocked by and Blocking fields. Dependency setup.
Make the draft wait for the approved source material when that is a real prerequisite. After creating a sample from the template, inspect every link: it should describe the current job rather than an unrelated old client task. A dependency indicates order; the team must still explain what acceptable input looks like and decide how to handle missing material.
Keep the fields useful and consistent
Custom fields add structured data such as priority or stage. Local fields belong to one project or portfolio; global fields come from the organization’s reusable field library. Choose the field intended for the project rather than creating another similarly named status every time. Custom field types and scope.
For the studio, a small set of agreed stages can help identify Ready for drafting and Waiting for approval. Document who changes each value. Our Asana custom fields guide covers the broader setup; the template should use that structure consistently.
Check access with the people doing the work
Project access is contextual. Someone with access to a project can access its tasks and messages. Asana distinguishes projects private to their members from projects shared with the organization; those settings are separate from read-only links. Review the project’s actual privacy setting before placing client material in it. Project privacy and permissions.
Create a harmless sample and ask a colleague to find it with their normal access. Check the task owner, dates, fields, attachments and dependency targets, then inspect every subtask. Ask them to explain what they need to start and what proves the work is finished. Nominate someone to maintain the template after difficult jobs reveal unclear prompts. Reusable instructions are useful when they reflect the method the team actually follows.
Sources reviewed 11 October 2026 against official Asana documentation. Examples and rehearsal checks are illustrative recommendations, not reported product tests.
