Subtasks vs Checklists

A task can be broken down in two ways. A subtask is another task, with its own status, sitting under a parent. A checklist is a list of lines on the parent task. Each line can be ticked, and a line can name a person, but the line is not a task. Picking the wrong one makes the board noisy or hides work that needed an owner and a date.

Use a subtask when the step is real work

Create a subtask when the step needs any of these:

• Its own status, such as In progress while the parent stays In review
• Its own start or due date
• Its own place on a board, calendar, or schedule
• An assignee in the same way any other task has an assignee

A subtask is a task with a parent. It is not a lighter object. It follows the same status groups as other tasks: Not started, In progress, Done, or Closed, under whatever names the project uses. How to set up task statuses covers that list. The subtask uses it. The checklist does not.

Example: "Launch the help center" is the parent. "Import the old articles" needs a due date and a status, because it can slip on its own. That is a subtask. You will look for it on the board without opening the parent.

Use a checklist when the parent stays the unit

Create a checklist when the steps are how you finish one task, and you do not want each step to be a card.

A checklist item has a title and a done tick. It can also have an assignee. It does not have a status, a start date, a due date, or a time entry. You cannot put a checklist item on the Gantt chart. You cannot block another task with a checklist line.

Example: "Publish the September newsletter" stays one task. The checklist is: subject line, hero image, three links, test send. Those lines are not projects of their own. The newsletter task moves to Done when the work is finished. The ticks are how the owner sees what is left.

Assigning a checklist item is for that kind of split. The designer can be assigned the hero image line while the parent task stays with the editor. The designer does not get a separate card, a separate status, or a separate due date. If the image actually needs those, it should have been a subtask.

A direct comparison

	Subtask	Checklist item
What it is	A task with a parent	A line on a task
Status	Yes	No, only ticked or not
Dates	Yes	No
Assignee	Yes, as a task assignee	Yes, optional on the line
Shows on the board by itself	Yes	No
Can block another task	Yes, it is a task	No
Time tracked on it	Yes, it is a task	No

If you need the left column, do not imitate it with a checklist. If you only need a tick, do not create a subtask and then wonder why the board doubled in size.

A launch week, chosen badly and chosen well

Badly. The parent is "Ship version 1.4." Twenty checklist lines include "migrate the database," which takes two days and has its own risk. The line cannot be In progress on the board. The only status anyone can see is the parent, which stays In progress for a week and tells nobody that the migration is the part that slipped.

Better. "Migrate the database" is a subtask with a due date and an owner. The checklist on the parent is the short punch list: tag the release, update the notes, tell support. The board shows the migration. The parent shows the punch list.

The reverse mistake is also common. "Write the release notes" is split into subtasks for every paragraph. The board fills with cards that have no dates and no reason to exist apart from the notes. Those paragraphs were a checklist.

Rules you can apply without a meeting

1. If the step can be late while the parent is still "on time," it needs its own due date, so it is a subtask.
2. If two people will work at the same time and you need both statuses, use subtasks.
3. If one person will tick lines while they do a single task, use a checklist.
4. If you want to name a helper on a line without giving that line a life of its own, assign the checklist item.
5. If you want the helper's work on the calendar, it is a subtask, because a checklist item has no date.

Do not use either tool as a comment. A note belongs in the description or a comment. A checklist is for steps you will mark done.

What stays on the parent

The parent remains the task people mention in conversation. Subtasks do not replace it. Close or finish the parent when the outcome is done, not when every checklist line is ticked, unless your team has agreed the ticks are the definition of done. Say that in the task, so "done" is not an argument.

Checklist assignees do not change the parent's assignee. The parent can still name the person accountable for the whole task. The line names who ticks that line.

Converting the wrong choice

You will guess wrong sometimes. The repair is ordinary.

A checklist line that grew a life: create a subtask with the same name, assign the person, give it the date you have been keeping in your head, and delete or tick the old line so the work is not in two places. Do this as soon as someone asks for the status of the line. That question means it is a task.

A subtask that never earned a date or a status change: fold it back into a checklist on the parent, assign the line if a person still ticks it, and close the extra card. Do this when the board is mostly empty-looking children of one parent. The parent was the task all along.

Avoid a hybrid that keeps both forever. A subtask plus a checklist line with the same title will be updated in one place. Pick the object that matches the rules above and remove the other.

Parents with many subtasks still need a status of their own. Agree what moves the parent to Done: all subtasks Done, or the outcome accepted even if a punch-list checklist remains. Write that in the parent description once. Do not encode it as a new status name such as "subtasks done," which is how status lists become a second breakdown.

Checklist progress is the ticks, nothing more. There is no percent complete to report, and no email when the last line is ticked. Open the task. If you needed a number on a dashboard, you do not have that dashboard. Count the open lines yourself or turn the heavy lines into subtasks you can filter.

Conclusion

Subtasks are tasks. Use them when a step needs status, dates, or its own place on a view. Checklists are ticks on the parent. Use them when the parent is still the thing you track, and assign a checklist item only when a person should tick that line without a card of their own. The project tools, including both, are on /pms.