Subtasks
What Subtasks Are
A subtask is a smaller task nested inside a parent task. It breaks a large or complex task into individually trackable steps. The parent task “Launch Q3 marketing campaign” might have subtasks like “Write email copy,” “Design landing page,” “Set up tracking pixels,” and “Schedule social posts.” Each subtask can have its own assignee, due date, and status.
Subtasks serve two purposes. First, they make large tasks manageable by converting a vague commitment into concrete steps. Second, they distribute work across a team by allowing different people to own different pieces of a parent task.
When to Use Subtasks
Use subtasks when a task meets any of these criteria.
Multiple steps that could be done by different people. “Prepare the quarterly report” becomes subtasks assigned to finance (pull data), marketing (write narrative), and design (format the deck).
The task takes more than 2 hours. Breaking it into 30 to 60 minute subtasks creates natural checkpoints and makes progress visible before the parent task is fully complete.
You need to track completion of individual steps. If knowing that 3 of 5 steps are done matters to you or your team, subtasks provide that granularity. A simple checklist inside the task description does not show up in dashboards, filters, or reports.
Do not use subtasks for tasks that are genuinely atomic. “Send the invoice” does not need subtasks. Over decomposing creates administrative overhead that slows you down instead of speeding you up.
How Deep Should Subtasks Go
One level of nesting (parent task → subtasks) covers 90% of use cases. Two levels (parent → subtask → sub subtask) are occasionally useful for complex projects but should be rare. Three or more levels signal that your task is actually a project and should be restructured as a project with its own task list.
ClickUp supports unlimited nesting depth. Asana supports one level of subtasks with the ability to view subtask subtasks. Todoist supports sub subtasks but keeps the interface flat. Trello uses checklists instead of true subtasks, which means checklist items cannot have their own assignees, due dates, or comments.
Subtasks vs. Checklists
Subtasks are full tasks: they have their own assignees, due dates, statuses, comments, and attachments. They appear in filters, reports, and dashboards. Checklists are lightweight lists of items inside a task description with checkboxes. They do not appear in reports, cannot be assigned to different people, and do not have independent due dates.
Use checklists for personal step by step reminders within a task you own entirely. Use subtasks when steps need individual ownership, deadlines, or visibility in team reports.
Commonly Confused With
| Term | Key Difference |
|---|---|
| Checklist | Checklists are lightweight checkbox items inside a task. Subtasks are full tasks with their own assignees, due dates, statuses, and comments. Subtasks appear in reports and dashboards; checklist items do not. |
| Task Dependencies → | Dependencies define the sequence between tasks (Task B cannot start until Task A is done). Subtasks define the structure of a single task broken into parts. Dependencies are about order; subtasks are about decomposition. |