Time Management

What to Track (and What to Stop Tracking) as a Freelancer

Time tracking for freelancers is supposed to make the week legible. Too often it becomes a second job: logging the three-minute Slack glance, the walk to the kettle, the “quick look” at a Figma file you are not billing. You end the day with a timesheet that is precise, exhausting, and still hard to invoice.

The usual essay says tracking prevents burnout because you can see overload. That can be true. The quieter failure mode is the opposite: you treat every minute as a moral test. The tracker starts to feel like a boss you hired to watch you. Then you abandon it, and Friday becomes archaeology.

Why over-logging feels responsible — and still fails

Freelancers over-track for decent reasons. You were burned by a fixed-price overrun. You want a “real hourly rate,” not a sticker rate. You read that micro-work adds up. All of that is real. None of it requires a line item for washing a mug.

Over-logging has a cost the spreadsheet never shows:

• Context-switch tax. Starting and stopping a timer for every ping trains you to interrupt deep work so the clock stays “honest.”
• Invoice noise. A client’s AP person does not want 14 lines of “Slack / email / thinking.” They want Discovery, Implementation, Revisions R1, Meetings.
• Shame loops. If the only ethical day is 100% captured, every gap feels like theft — including lunch. That is how time tracking starts to feel like surveillance even when nobody is watching.

Capturing micro-work can be profitable when the micro-work is actually client work: a 12-minute production hotfix, a revision pass, a billing question you answered in writing. The failure is treating life as a billable unit. For the case where small client tasks really do vanish, we already covered when small tasks add up. This post is the other half: what to stop feeding the clock.

What is worth a task on the timesheet?

Use a test you can run at 4 p.m. without a philosophy course:

1. Would a non-technical client recognize this name? Homepage mockups, workshop facilitation, brand revisions R2 — yes. “Misc,” “admin-ish,” “stuff” — no.
2. Would you defend the duration in an email? If you would immediately discount it to avoid a fight, either the task is wrong or you should not bill it.
3. Is this a different job than the parent task? Meetings are not Implementation. Code review is not feature work. Sales calls are not the retainer. Split them or you poison estimates vs actuals.

A practical catalog for a software consultant looks like Discovery, Architecture, Implementation, Code review / QA, Meetings, Support, Internal / admin / sales. A designer’s catalog is closer to audit, wireframes, UI, prototyping, Revisions R1–R3, handoff, meetings. You do not need all of them on every engagement. You need enough structure that Friday’s report is readable.

Billable vs non-billable is a separate axis. Unpaid overhead still deserves a named task on an internal client or an “Internal” project so you can see it. Pretending it was Homepage mockups is how you lie to your future quotes. The longer version of that split is how to track billable vs non-billable time.

What you can stop tracking this week

Give yourself a deny list. Not forever — for this month, while you rebuild the habit.

• Sub-five-minute glances that are not a real interruption of billable work. If rounding is on, those glances were never going to be the story anyway.
• Personal admin dressed as “context.” Banking, gym, a family call. Your utilization rate does not improve because you named it.
• Duplicate clocks. A Pomodoro session, a calendar block, and a billable timer for the same hour. Pick the billable clock for money. Let the others be focus tools.
• Tasks you already closed. If a revision round is done, stop feeding it. Lock or close the task so you cannot “just add a few more minutes” onto a phase the client already approved.
• Notes pretending to be time. A link, a screenshot, a “waiting on feedback” sentence belongs in a note. It is not 18 billable minutes unless you actually spent 18 minutes.

If you are burning out because the tracker never lets you be off the clock, that is a different problem than “I cannot see my hours.” We wrote about using time tracking to prevent burnout when the issue is overload. Here the issue is ritual. Rituals can be thinned.

Where a simple tracker helps — including MinuteShark

If you want the software to match the deny list above, look for a client → project → task model, a way to lock or close work that should not receive more time, and rounding that does not destroy the original minutes. MinuteShark is built for that independent workflow: timers and manual History entries on tasks, optional 6 / 15 / 30-minute (or custom) rounding up, reports you can actually read, invoices generated from the same report plus a cost profile.

MinuteShark AI can log forgotten time in plain English, but nothing is written until you confirm a proposal card. That matters if your old habit was to “just dump the afternoon” into one blob. The assistant should not guess you into a more granular diary than you meant to keep. For the rounding conversation with clients, the time rounding guide is the short version.

Start on Starter if you only need a few clients. Standard is $5/user/month if you need unlimited clients, projects, and subtasks. The point is not more fields. The point is a clock you will still use in November because it never asked you to narrate the kettle.