.png)
Subtasks & checklists
Bluprint gives you two ways to break a task into smaller pieces. They look similar but solve different problems, and picking the right one keeps your project tidy.
The quick rule
Which should I use?
Use a subtask when a step needs its own owner, status, priority, or description. Use a checklist for small, simple to-dos that just need ticking off.
Subtasks
A subtask is a smaller unit of work that lives inside a parent task and behaves much like a task in its own right. Each subtask has its own:
- Title and description
- Status
- Priority — Low, Medium, or High
Reach for subtasks when the work is layered or collaborative — when different people own different parts, or when a step is substantial enough to track its own progress and discussion.
Checklists
A checklist is a lightweight list of items you tick off inside a task. There are no separate assignees, statuses, or dates — just items and a checkbox. It's the right tool for a simple, repeatable set of steps (a "definition of done", a pre-launch list, a QA pass) where the overhead of subtasks would be overkill.
Side by side
| Subtask | Checklist item | |
|---|---|---|
| Own status | Yes | No (just done / not done) |
| Own priority | Yes (Low/Medium/High) | No |
| Own description | Yes | No |
| Best for | Layered or shared work | Simple, repeatable steps |
Next
Last updated: 2026-05-31