Beyond the Checkbox: 5 Better Ways to Track Task Progress
A checkbox can't show partial progress. Here are 5 better ways to track task progress — percent, counts, sub-tasks, stages, and notes — and when each fits.
Quick answer
A binary checkbox hides real progress on multi-step work. Track it five ways instead: percent complete for fuzzy work, counts (7 of 12) for repetitive items, checklists for sequenced sub-tasks, stages (To do → Doing → Done) for pipelines, and timestamped notes for open-ended efforts. Match the model to the task, not the other way around.
The checkbox is the most honest UI in productivity software, and also the most misleading. It tells you a task is done or not done — and nothing in between. But most real work lives in the middle: the chapter that's 60% drafted, the move where 7 of 12 boxes are packed, the launch that's cleared design but not engineering. A blank checkbox makes all of that look like zero. That's demoralizing, and worse, it's wrong.
There are at least five better ways to represent progress, and each fits a different shape of work. Below is each model, a concrete example, and the apps that do it well — plus an honest note about overhead, because in most tools you have to pick the model by hand.
1. Percent complete
A single number from 0 to 100. It's the right call when work is continuous and hard to chop into discrete units — writing, designing, research, anything where "how far along are you?" has a fuzzy but real answer.
Example: "Write Q3 report." You can't checklist your way through prose cleanly, but you know when you're roughly a third in. Set it to 30%, bump it as you go. The bar gives you (and anyone watching) a felt sense of momentum.
The catch: percent is subjective. "50% done" often means "50% of the time has passed," which is not the same thing — the last 10% of a document can take as long as the first 90%. Use it as a morale gauge, not a forecast.
Where you'll find it: project tools lean on this. Notion lets you build a progress property or a rollup that computes percent from sub-items. Asana and similar work-management tools show percent at the project level.
Build a percent property, a rollup, or a formula that aggregates sub-tasks — Notion will track progress however you model it. The caveat is that you design the system, and a database that flexible is easy to over-engineer until maintaining it becomes the task.
2. Count / units (7 of 12)
When a task is really a pile of identical small things, a count beats a checkbox. "Read 30 pages," "send 12 invoices," "do 50 reps" — you want to see 7 of 12, not a box that stays empty until the very end.
Example: a daily habit like "Drink 8 glasses of water." A single checkbox is all-or-nothing; a counter lets you tap up to 5 by mid-afternoon and feel the partial win. Same logic for "Apply to 10 jobs this week" — the number moving is the reward.
Counts shine for anything repetitive or measurable, which is why habit trackers live and die on them.
Its habit tracker handles numeric goals well — set a target count, log progress through the day, and watch the streak build. The honest caveat: the habit module and the task list feel like two adjacent apps, so a counted habit doesn't always sit naturally next to your regular to-dos.
3. Checklist / sub-tasks
When a task has a fixed set of named steps, break it into a checklist. Each item is its own small checkbox, and the parent shows how many are done. This is the most concrete progress model, because the steps are explicit — you're never guessing what "60%" means.
Example: "Onboard new hire" becomes: order laptop, create accounts, schedule intro calls, share the handbook, assign a buddy. Five clear wins instead of one vague obligation. Checklists are also the antidote to procrastination on big, blurry tasks — see how to break big tasks into bites you'll actually finish for the full method.
The trade-off is up-front effort: someone has to write the steps. For genuinely novel work that's worth it; for routine work, save it as a template.
Things lets every to-do hold a checklist of sub-items, wrapped in one of the most refined interfaces on iOS and Mac. The caveats: it's Apple-only and a one-time purchase per platform, and its checklists are deliberately lightweight — no due dates on individual sub-items.
Todoist supports real sub-tasks with their own dates, priorities, and assignees, and the parent shows a progress count as you finish them. It's cross-platform and fast. The caveat: deeply nested projects can get visually busy, and the most useful views sit behind the paid tier.
4. Stages / pipeline (Kanban)
Some work doesn't progress on a single line — it moves through states. To do → Doing → Done is the minimum; real pipelines add stages like Backlog, Blocked, In review, Shipped. A card moving across columns is progress you can see across a whole project at a glance.
Example: a content calendar where each article is a card that travels Idea → Drafting → Editing → Scheduled → Published. You instantly see what's stuck in editing and what's ready to ship — information a flat list of checkboxes can't show.
Stages are the right model when work flows through hand-offs or waiting states, and when seeing the whole board matters more than any single item.
Trello is the most approachable Kanban tool there is — drag cards between columns and the board is your progress view. The caveat: it's board-first, so it's less suited to a personal daily list, and power features (automation, multiple views) push you toward paid plans.
5. Free notes / journal with timestamps
Sometimes progress isn't a number or a stage — it's a story. Open-ended work (research, debugging, a slow negotiation, a creative project) advances in ways no bar can capture. A running log of timestamped notes — "tried X, hit a wall," "called the vendor, waiting on quote" — is the only honest record.
Example: debugging a flaky issue. There's no percent and no clean checklist; what helps next week is the trail of what you already ruled out. A timestamped journal on the task turns scattered effort into a paper trail you can pick back up cold.
This model pairs naturally with the others: a task can sit in the "Doing" stage and carry a note log. Tools built for thinking — Notion, Obsidian — are strong here, and any to-do app with a comment or notes field does the job for a single task.
The overhead nobody mentions
Here's the honest part: in almost every app, you have to choose the model and set it up. You decide a task gets a checklist, you create the columns, you add the percent field. That's fine for a project you'll live in for weeks. It's friction for the dozens of small things you capture daily — and that friction is exactly why people default to the lonely checkbox even when it doesn't fit.
This is where AI-assisted tools are starting to help. Watermelon Todo, for instance, looks at what you capture and auto-picks the progress type that fits — a multi-step task gets a checklist, a repetitive one gets a count, an open-ended one keeps a timestamped history — so you're not configuring a tracking system before you've even started the work. It's one approach among several worth weighing; the broader landscape is covered in the best AI to-do list apps.
Which model fits which task
| Progress type | Example | Apps that do it well |
|---|---|---|
| Percent complete | "Write Q3 report" — 30% drafted | Notion, Asana |
| Count / units | "Pack 12 boxes" — 7 of 12 | TickTick, Todoist |
| Checklist / sub-tasks | "Onboard new hire" — 5 named steps | Things 3, Todoist |
| Stages / pipeline | Article: Idea → Drafting → Published | Trello, Notion |
| Notes / journal | Debugging log with timestamps | Notion, Obsidian, Watermelon Todo |
How to choose, fast
You don't need a flowchart. Ask one question: what does "making progress" actually look like on this task?
- If it's a fuzzy push toward a finish line → percent.
- If it's many of the same small thing → count.
- If it's a fixed set of named steps → checklist.
- If it flows through states or hand-offs → stages.
- If it's open-ended and you'll need the history → notes.
Then keep it light. The point of tracking progress is to feel momentum and know where to pick back up — not to build a second job maintaining the tracker. Fold the model you chose into your daily planning routine so reviewing progress takes thirty seconds, not thirty minutes.
Key takeaways
- A binary checkbox hides real progress on anything multi-step — use it only for genuinely atomic tasks.
- Five better models: percent (fuzzy work), counts (repetitive items), checklists (named steps), stages (pipelines), and timestamped notes (open-ended work).
- Match the model to the task: ask what "making progress" looks like, then pick the lightest fit.
- The hidden cost is setup — most apps make you choose and configure the model yourself; AI-assisted tools can auto-pick it.
- Models combine: a project can run stages at the top, checklists inside, and a note log on the hard parts.
Try Watermelon Todo
Capture tasks by voice, let on-device AI shape them, and track real progress. Free on iPhone.
Frequently asked questions
Why isn't a simple checkbox enough for tracking tasks?
A checkbox is binary — done or not done — so it shows nothing for work in progress. For multi-step tasks, long projects, or partial effort, an empty box looks like zero progress even when you're most of the way there, which is both demoralizing and inaccurate.
What's the difference between a checklist and stages (Kanban)?
A checklist breaks one task into a fixed set of named sub-steps you complete in order. Stages move a whole task through states like To do → Doing → Done across a board. Use checklists for the steps inside a task; use stages to see where many tasks sit in a workflow.
Which progress model is best for habits?
Counts. Habits are usually repetitive and measurable — 8 glasses of water, 30 pages, 50 reps — so a counter that shows 7 of 12 captures partial progress through the day far better than an all-or-nothing checkbox. Habit-focused apps like TickTick are built around numeric goals.
Can one task use more than one progress model?
Yes, and complex work usually should. A project can sit in a 'Doing' stage, hold a checklist of sub-steps inside, and carry a timestamped note log on the tricky parts. The models layer rather than compete — pick whichever fits each level of the work.
Do I have to set up the progress type myself?
In most apps, yes — you choose and configure the model (add a checklist, create columns, build a percent field). That setup is the main friction. Some AI-assisted to-do apps, like Watermelon Todo, look at what you capture and auto-pick a fitting progress type so you skip the configuration step.
Written by the Watermelon Todo team. We make an AI to-do app for iOS — but every guide here is meant to help you work better, whatever tools you choose. We link to other apps on their merits, not for commission.