Todoist subtasks: break a deliverable into independently owned steps

SOURCE-BASED ANALYSIS · NO HANDS-ON RATING

Use a parent for an outcome

Todoist lets you create, assign and schedule subtasks. Its documentation notes that a parent and a subtask both scheduled for today can appear at the same indentation level in Today. Therefore a flattened daily list should not be the only explanation of how the work fits together.

Example: deliver an interview article

Suppose a small editorial team needs one approved interview article. Use the parent task for that outcome, with subtasks for preparing questions, recording consent, drafting and editorial review. Give each step an observable result. A subtask called Work on interview is difficult to verify; Questions approved is a clearer checkpoint.

Separate steps when they need different owners or different working dates. Keep incidental notes inside the relevant task rather than turning every sentence into another obligation. The purpose of nesting is to explain a relationship, not to maximize the number of boxes to tick.

Write a completion contract

1. Describe what makes the parent deliverable accepted.
2. Identify the steps that can be completed independently.
3. Put an owner and an intended work date on each step that needs them.
4. Ask the final reviewer which evidence they need before accepting the parent.
5. Inspect both the parent task view and the daily view to make sure the next action is understandable.

Test the view the worker actually uses

In a rehearsal, ask a colleague to find the review subtask from their normal daily queue. Can they identify the source draft and the acceptance criteria without asking who created it? If not, add a meaningful description or link and use a clearer title. Nesting alone is not context.

Do not infer dependency enforcement from visual order. If the reviewer must wait for a draft, make that operational rule explicit and choose a suitable workflow for enforcing it. This guide does not claim that parent-child placement automatically blocks later work.

Review before closing the outcome

Check unfinished steps, missing evidence and the final deliverable before marking the parent done. A manually completed checklist can still contain an unusable output. The review should answer whether the promised article exists and was accepted, not only whether preparation activities occurred.

Use a separate project when the supposed subtask becomes a sustained workstream with its own audience and many outcomes. Keep a subtask when it remains a bounded piece of the parent's deliverable. That decision keeps daily execution readable without hiding complex work several levels down.

For the complete learning path, visit the Todoist practical guide hub.