Toodledo’s subtasks are flat — one level of parent/child, no grandchildren. People sometimes complain about this. They are wrong. Flat subtasks are not a limitation; they are a discipline that prevents project bloat.
Use Case 1: Launch Checklists
Parent: “Launch May product update.” Subtasks: write release notes, draft email, schedule social posts, update help docs, brief support team, smoke test in staging. Each subtask is a real, executable action. The parent holds the project context. Done = parent complete.
Use Case 2: Client Onboarding
Parent: “Onboard Acme Corp.” Subtasks: send contract, schedule kickoff, set up shared drive, intro to account team, send first invoice, schedule 30-day check-in. Repeatable structure for every new client. Copy the template, change the name.
Use Case 3: Weekly Content Production
Parent: “Publish blog post — week of May 18.” Subtasks: research keywords, draft outline, write first draft, edit, schedule on CMS, write social copy, send newsletter mention. Each Friday, complete the parent and create a new one for next week.
The Discipline Flat Subtasks Enforce
Nested trees encourage bloat — sub-projects within sub-projects within sub-projects. Flat subtasks force you to ask: “Is this actually a separate project, or is it just a step?” That question alone makes your task system simpler and more honest. Subtask docs show the full behavior.
Try Toodledo free → toodledo.com/subscribe
Read the docs → toodledo.com/info/index.php
Join the conversation → toodledo.com/forums
