You open your task list and see “Finish the client project”. The deadline is close. You have time to work on it now. But what do you actually start with? You open the brief, skim your notes and try to remember where you left off.
That is where task management with subtasks helps: you split one deliverable into smaller actions, each with a clear result. Next time you open the list, “Check the source data” gives you somewhere to begin.
The point is not to make your task list more detailed. The point is to make it easy to restart without thinking from zero.
Project, task and subtask: what is the difference?
Where does the work belong? What do you owe the client? What can you do next? Give each level one job.
| Level | What it describes | Example |
|---|---|---|
| Project | The client engagement or area of work | Customer research for Northstar |
| Task | A deliverable or outcome within that project | Prepare the findings report |
| Subtask | An action that moves that deliverable forward | Group interview notes by theme |
“Email the meeting agenda” can stay one task. A research report needs several steps. Keep the hierarchy as small as the work allows.
Give each action a home under the deliverable it helps finish. Unrelated work gets its own task.
Start with one deliverable and define what finished means
Take the Northstar report. You have the interview notes and the brief, but “write the report” still feels too big to start. Give yourself a finish line first.
The parent task is Prepare the findings report. Its finish condition is: “The client has received a reviewed report with three recommendations and links to the supporting data.”
That sentence tells you when to stop. You could spend another afternoon researching a side question or polishing the client's presentation template. But does the agreed report need it? A clear finish condition gives you a reason to move on.
Write the next few actions beneath it:
| Subtask | Finish condition |
|---|---|
| Check the source files | Required files open and missing inputs are listed |
| Group findings by theme | Each finding has a category and a source reference |
| Draft three recommendations | Each recommendation explains the issue and proposed action |
| Check the report against the brief | Required sections are present and factual gaps are flagged |
| Send the reviewed report | The agreed version and supporting links reach the client |
Make each subtask easy to start
Write a subtask for the version of you who comes back tomorrow with half the context missing. “Research” makes you work out the plan again. “Compare the three shortlisted providers” tells you where to put your attention. Start with a verb and name the result.
Useful examples across freelance work include:
- Development: reproduce the checkout error, fix the failing condition, check the affected flow.
- Writing: outline the article, draft the introduction, verify the quoted sources.
- Translation: translate the first section, check terminology, proofread the final document.
- Administrative support: collect the missing files, reconcile the contact list, send the handover summary.
- Design: sketch two layout options, refine the selected direction, prepare the agreed file formats.
A subtask can take several focus sessions. Split it when the starting point is unclear or it contains separate outcomes. The goal isn't to create a perfect task breakdown. It's to make the next 25 minutes obvious.
Choose one next step instead of scheduling every row
Put dates on commitments you intend to keep. The delivery deadline belongs on the parent task. Add a subtask date for a Tuesday interview or a draft needed before a review call. Leave the other steps flexible.
The list records your order; you decide what can move. If you are waiting for source files, name that blocker and choose another step.
Suppose you allow one 25-minute session to check files and two to draft recommendations. That gives you 75 minutes of focused work to plan around, plus breaks and messages. Adjust the estimate as you learn what the work needs.
For more on this distinction, see how to estimate client work in Pomodoros.
How to use subtasks in Pomiq
You put Prepare the findings report in your Northstar project and add the five steps from the example above. On desktop, hover over or focus the parent card to reveal + Add sub-task. On your phone, use the plus beside the title. The subtasks inherit the project, so you can stay with the work you are breaking down.
You have checked the files and grouped the findings. Now you choose Draft three recommendations and press Play on that subtask. For this session, you have one clear job: turn the findings into recommendations the client can act on. Your recorded focus time stays attached to that action.
Then another client needs your attention. Before switching projects, make the next action concrete. “Check the figures in section two” is much easier to return to than “Continue the report.”
When all three recommendations are ready, you mark the subtask complete. The timer records the time you spent; you decide whether the result is ready. Expand the subtask group to see what remains, then review the full report before completing the parent task. Completing every subtask does not automatically finish the parent, and checking the parent completes its subtasks too.
That is the workflow I want Pomiq to support: you can see the next action, focus on it, and leave yourself a clear way back.
For the wider project and reporting workflow, see Pomiq for freelancers.
Keep progress, time and waiting separate
You check off three of five subtasks. Good: three results are ready. But writing the report may take an afternoon and sending it five minutes. The count tells you which steps are done, not the effort remaining.
Use recorded focus time to see where your attention went. Read the report total directly; adding parent totals and child rows together would count the same work twice.
Waiting deserves a place in the plan. Put the blocked parent task on hold and set Follow up on for the day you will check back. Its subtasks inherit that hold, so keep independent work in a separate task.
When that date arrives, check the reply and decide what comes next. Meanwhile, give your attention to work you can move forward. See planning across multiple freelance projects.
Avoid turning the breakdown into more work
Your task list should earn the attention you give it. If you spend more time rearranging tiny steps than doing them, combine a few. “Open the document” usually does not need its own row. Keep it if that small prompt helps you get started; otherwise, move straight to the work.
Keep one copy of each action so you know where to update it. When the client changes the scope, change the affected steps and your estimate too.
A useful plan can change. Give yourself permission to revise it.
Common questions about subtasks
Are subtasks the same as checklist items?
Both describe smaller steps. Use a Pomiq subtask when you want to start a focus session on that action and track its completion. A checklist in Notes stays text.
How many subtasks should a task have?
Start with three clear actions. Add more when the work calls for them. Stop splitting when the extra rows give you nothing useful to decide or track.
Should every subtask have a due date?
No. Keep the client deadline on the parent. Date individual steps when another person or piece of work depends on their timing.
Can this approach work outside creative freelancing?
Yes. A report, a software fix or a translated document all need a finish condition and a next action. Use the same approach in your own field.
Try it on one active task
Pick the task you keep scrolling past. Write one sentence that says what finished looks like. Add three actions you can actually start, then choose the first one. You can work out the rest as you learn more.