Time Management
Why Checking Off a To-Do Is Not Closing the Task
Time tracking for freelancers falls apart when a checkbox and a closed task mean the same thing. They do not. One is a plan for today. The other is a lock on the timesheet.
You finish the homepage mockups you promised yourself this morning. You strike the line through. It feels like done. Then the client pings at 4:40 with a crop, a caption, and “quick look?” You cannot start a timer on a task you already buried. Or worse: you can, because the checkbox only hid the row in your personal list, and now Friday’s invoice has a surprise sixth hour on a task you told yourself was closed last Tuesday.
The split that keeps billing honest: a to-do is a focus list. Checking it off means “I am done with this for now.” Closing a task means “do not log more time here.” Mix those up and you either lock yourself out of real follow-up or you keep a graveyard of tasks that still accept hours.
Why freelancers treat every checkbox like a contract
Employee tools train the habit. Done in Jira means the ticket left your column. Done in a personal notes app means you want the dopamine. Neither is a billing event.
Freelance work is messier. A task named “Homepage mockups” can be honestly finished for the day and still be the right place to put tomorrow’s revision. A phase named “Discovery” can be done as a plan item and still need a locked boundary so you stop leaking strategy time into implementation. If your tracker only has one “done,” you will pick the wrong one under pressure.
Three situations where the mix-up shows up:
- Same task, second sitting. You planned two hours. You used 90 minutes. Checking the to-do should not prevent the remaining 30 tomorrow.
- Revision after “done.” The client’s “quick look” is still Homepage mockups. If you closed the task, you will invent a sibling named “Homepage mockups 2” and your report will lie about the phase.
- A phase that should stay shut. Discovery is over. You sold implementation. If the discovery task still accepts time, scope creep hides inside a friendly old name.
A to-do list is a filter, not a second project tree
The useful to-do list for a consultant is not a pile of naked sentences. It is a short view of tasks that already live under a client and a project. “Write the deck” with no client is a sticky note. “Write the deck” under Northwind / Q3 workshop is something you can invoice.
That is why a personal list should select existing work, not invent a parallel universe of chores. You can have “This week” and “Waiting on client” as lists. You should not have a third hierarchy that never appears on a report.
Two different finishes
- Checked off on the list. You are done planning around that row today. The task stays open. You can start a timer on it again. The line is a focus signal, not a lock.
- Task closed (or locked). Further tracking should stop. Use this when the phase is actually over, the deliverable shipped, or you do not want “just five more minutes” leaking into a finished bucket.
If your tool only offers one of those, you will either over-lock (and then duplicate tasks) or under-lock (and then argue with your own report).
When should you actually close a task?
Close when the billing story is finished, not when you feel tired of the row.
Good close moments:
- A named revision round is delivered and you want R2 to be a new task, not more hours on R1.
- A discovery or audit phase is accepted and implementation should not hide inside it.
- A support bucket for the month is invoiced and next month needs a clean start.
Bad close moments:
- You hit your Pomodoro target. That is a focus clock, not a project state.
- You want the list to look empty before lunch. Empty lists are a mood. Closed tasks are a policy.
- The client went quiet. Quiet is not shipped. Leave the task open and take it off today’s list.
If you need a daily picture of what is in motion without locking anything, a dashboard with a short list plus today’s history is enough. The daily dashboard post is about that picture — not about pretending a checkbox is an invoice line.
How to keep the list from becoming a second timesheet
People who hate tools still need a plan for Tuesday. The trap is building a plan that cannot start a timer.
- Only list work that already has a client and a project. If it is not billable and not a named overhead task, it should not crowd the list that drives your day.
- Start the timer from the list. If you have to leave the list, open the project tree, and hunt, you will skip tracking for “just this one.”
- Check off without closing. End-of-day review is for History, not for mass-closing every row you touched.
- Close on purpose, once a week. When a phase is actually over, lock it so Friday you cannot “fix” the report by adding time to a finished name.
That last habit is the one that protects estimates versus actuals. If Implementation stays open forever, every meeting and every Slack look lands there, and you will swear the build “took twice as long.”
Where MinuteShark puts the split
In MinuteShark, to-do lists live on the dashboard as a widget. You add tasks that already exist under a project. You can hit Play from the widget. Marking a row done crosses it off the list. It does not close the task, so you can still log time later. Closing or locking a task is a separate action — that is the one that prevents further tracking.
The notes widget is private. The to-do widget is a plan. History is what actually happened today. None of those three should silently rewrite the other. The dashboard widgets guide is the short version of that layout.
If you would rather speak the close than hunt for it, MinuteShark AI can propose closing or opening a task. Nothing writes until you confirm the card. It does not close a project from a to-do checkbox, and it does not treat “done on my list” as “lock this forever.”
Setup still starts the same way: client, then project, then task, then track. The getting started guide is enough if you do not have that tree yet. The list comes after the tree, not instead of it.