What is a Subtask?
Subtask
A subtask is a smaller piece of work nested inside a parent task, used when one task is too big for one person to own and finish in a single sitting.
A subtask is a smaller unit of work nested inside a parent task. It exists because a single task is too coarse a unit for anything with more than one owner, more than one approval step, or more than a day of work. Instead of one card labeled "Launch new landing page" sitting untouched in one column for two weeks, the work splits into pieces small enough to assign, time, and check off on their own.
A subtask is not a separate project, and it's not a smaller version of a Work Breakdown Structure. A WBS decomposes an entire project into phases and work packages before any work starts. A subtask decomposes one task, inside an existing card, usually created once work reveals its own shape.
For agencies running Kanban boards, subtasks keep a single card honest. A designer's card "Homepage design" can carry three subtasks, wireframe, visual design, client revisions, each with its own assignee and timer, while the parent card still shows one deadline and one person accountable for the whole thing.
Subtask vs Task: The Real Difference
A task is a unit of work with a deadline that shows up on a board or a list. A subtask is a task that lives inside another task, created to represent a portion of the parent's scope rather than sitting on the board by itself.
Two things separate a subtask from a small standalone task. First, it inherits the parent's project and client context automatically, there's no separate card to file under the right client. Second, its completion rolls up into the parent's progress, so the parent card shows what fraction of the work is done without anyone updating a status by hand.
When to Break a Task into Subtasks
A task is a candidate for subtasks when any of the following is true.
- It needs more than one person to finish (a designer draws it, a copywriter writes for it)
- The work spans more than a day, so progress needs to be visible mid-task, not only at the end
- It has a review or approval gate inside it (draft, then client feedback, then final)
- Two people would otherwise log time on the same card with no way to see who did what
- It has 5 or more discrete steps that a checklist would hide rather than clarify
How Deep Should Subtask Nesting Go
One level of subtasks covers nearly every real case. A second level, a subtask of a subtask, usually signals the parent card should have been its own task from the start, or the whole thing should have been a small project with its own board.
Teams that let subtasks nest three or four levels deep end up with a card nobody can read at a glance, and a progress percentage that means less the deeper it goes. If a subtask itself needs breaking down, that's a sign the estimate on the parent task was wrong, not a reason to add another layer of nesting.
Subtasks vs a Work Breakdown Structure
A Work Breakdown Structure decomposes an entire project into phases and work packages before a single task exists on a board. A subtask decomposes one task after it already exists, usually as the person doing the work discovers its real shape.
| Question | Work Breakdown Structure | Subtask |
|---|---|---|
| Scope | The whole project | One task |
| Built when | Before work starts, during planning | As work reveals its shape, often mid-task |
| Built by | Project manager or lead | Whoever owns the task |
| Lives where | A planning document or the project's phase structure | Nested inside a single card on the board |
How Subtask Completion Rolls Up to the Parent
The parent task's progress is calculated from the subtasks under it: closed subtasks divided by total subtasks. A task called "Client onboarding" with four subtasks, contract signed, kickoff call scheduled, workspace created, welcome email sent, shows 25% as each one closes, reaching 100% once all four are done.
The parent stays open until every subtask closes, or an admin closes it explicitly ahead of the subtasks. That override should require a deliberate action, not happen by accident, since it's the one place progress can quietly disagree with reality.
A Worked Example: Splitting a Website Launch Task
A parent task, "Launch new landing page", is due Friday. On its own it's one card with one owner and no way to see who's behind. Split into subtasks, the same work looks like this:
| Subtask | Owner | Estimated time |
|---|---|---|
| Write page copy | Copywriter | 3h |
| Design hero image | Designer | 2h |
| Build page in CMS | Developer | 4h |
| QA on desktop and mobile | Developer | 1h |
| Client approval | Account manager | N/A |
Subtasks in Melororium
Melororium's Tasks module nests subtasks under any card, each with its own assignee, due date and timer, visible across Kanban, list and calendar views. Bulk mode lets admins move or close subtasks in batches instead of one at a time.
Time logged on a subtask rolls into the parent task's total and into Work Reports automatically, so an invoice reflects who did what without a separate breakdown. Starter plan is $29/mo for 4 users, subtasks are included in every plan.
In Melororium
Manage subtasks in Melororium
Common mistakes with subtask
What teams get wrong most often, and what to do instead.
- 1
Nesting subtasks inside subtasks
Adding a subtask to a subtask instead of stopping at one level. A card three layers deep is harder to read than the two-week task it was meant to simplify.
- 2
No owner per subtask
Listing subtasks with no individual assignee, so the parent task's single owner ends up doing, or chasing, every piece anyway.
- 3
Splitting a task that should be its own project
Turning a two-week engagement into 15 subtasks on one card instead of giving it its own board. At that size the card stops fitting on a Kanban column and starts hiding real project risk.
- 4
Closing the parent before the subtasks are done
Marking the parent task complete while two subtasks are still open, because the visible checklist looked close enough. The rollup exists to catch exactly this gap.
Frequently asked questions
What's the difference between a subtask and a checklist item?
A checklist item is a line inside a task description with no owner, no timer and no independent status. A subtask is a full task in its own right, nested under a parent, with its own assignee, due date and time log. Use a checklist for simple steps one person handles alone; use subtasks when different people own different pieces.
How many subtasks should a task have?
Most tasks that need subtasks at all need somewhere between 2 and 6. Fewer than that and a checklist would do the job. More than roughly 8 usually means the card should be its own task or project instead.
Can a subtask have a deadline earlier than the parent task?
Yes, and it should when subtasks have a real sequence. A subtask deadline earlier than the parent's is normal; the parent's due date is the final constraint everything else has to fit inside.
Does time logged on a subtask count toward the parent task's total?
Yes. In Melororium, hours logged on any subtask roll up into the parent task and into Work Reports, so a project's total tracked time stays accurate without manual addition.
Should every task have subtasks?
No. Most tasks that take a few hours and have one owner don't need them. Subtasks earn their place on tasks with more than one owner, a review step inside them, or more than a day of work.
