Time Tracking for Freelancers: A Practical One-Week Review

Suppose you estimated a job at twelve hours, spent sixteen, and still cannot explain where the extra afternoon went. That is a useful reason to track time. A timer alone will not fix the estimate, but a short record of the work can show what to change in your next quote.

Try the following routine for one working week. You need a timer or spreadsheet, your calendar, and a few minutes to check each day's entries.

Separate client work, business work and breaks

Start with three categories. Add detail only when it helps you make a decision:

• Client work: delivery, research, project meetings, revisions and client communication. Record the project and task, including work covered by a fixed fee. Whether those hours can be billed separately depends on your agreement.
• Running your business: proposals, bookkeeping, marketing, maintaining your tools and your own training. These hours consume capacity even when there is no client to invoice.
• Breaks and time away: pause the work timer. If you want to understand your day's schedule, record breaks separately without adding them to project hours.

Do not label every client-related minute billable or every internal minute wasted. A proposal may win next month's work. A revision may belong to a project but be included in an existing price.

Write entries that explain the work

“Website, three hours” gives you little to use later. Record the date, start and end, project, task and a short description of the result. For example:

• 09:00–10:10, North Studio, landing page: built the mobile navigation and checked the menu at three screen widths; 70 minutes of project work.
• 10:10–10:25, internal, bookkeeping: matched supplier invoices to bank transactions; 15 minutes of business work.
• 10:35–11:05, North Studio, review: discussed the first layout and recorded the requested changes; 30 minutes of project work.

The ten-minute gap is a break, not missing billable work. Stop the previous timer when switching tasks so the same period is not counted twice. If you forget an entry, reconstruct it that day from your calendar or work notes and mark it as an estimate.

In TimeBill, the live timer and manual-entry guide explains how to record and correct these sessions. For decimal entry, 1 hour 45 minutes is 1.75 hours, not 1.45; a decimal time converter handles the conversion. Keep actual recorded time separate from any rounding agreed for billing.

Run a one-week experiment

1. Monday: choose one question. For example, “Are revisions using the time I allowed for implementation?” Break the current project into a few tasks, estimate each, and reserve calendar space for meetings and internal work before promising delivery dates.
2. Tuesday: record a normal day. Start and stop at task changes. Add a description when stopping. Spend five minutes before finishing to correct forgotten timers and fill obvious gaps. Do not reorganize the whole day yet.
3. Wednesday: check the forecast. Compare time spent with work still remaining. If a task has consumed its estimate but is unfinished, revise the forecast and discuss the scope before doing more work that may not be covered.
4. Thursday: change one thing. If repeated messages split your work, agree two reply windows with the client and an exception for urgent issues. If routine administration dominates, batch it or prepare a reusable template. Keep recording.
5. Friday: review for fifteen minutes. Total project and internal hours, compare estimates with actuals, and write one specific change for next week. Keep any uncertainty visible instead of turning guesses into precise totals.

There is evidence for reviewing progress, though not for a particular timer app. Harkin and colleagues' meta-analysis of 138 randomized studies found that interventions encouraging progress monitoring improved goal attainment on average. The research covered varied goals, not specifically freelance billing, so it does not establish a guaranteed productivity gain from tracking hours.

Check the budget before the project finishes

Suppose a fixed-fee project pays €1,200 excluding VAT. You allowed twelve delivery hours, equivalent to €100 of revenue per planned project hour. By Wednesday, eight hours are recorded and you estimate another eight to finish. The forecast is now sixteen hours, so the expected revenue per project hour is €75.

That is a four-hour overrun against the estimate, not automatically four extra hours you can charge. Check its cause: additional client requests, an underestimated task, or correcting your own mistake. The response may be a revised scope and fee agreed with the client, a later deadline, or a better estimate next time. Record the reason while it is still clear.

Keep your hourly figures distinct

Consider a separate example: you complete and bill twenty hours at €60 per hour, generating €1,200 excluding VAT. You also spend ten hours running the business during the same period.

Your contract rate is €60. Your billable share of working time is 20 ÷ 30, approximately 67%. Your revenue per total working hour is €1,200 ÷ 30, or €40. That last figure includes the internal hours in its denominator.

None of these figures is take-home pay or profit. Costs and taxes have not been deducted, and invoiced revenue is not the same as money already received. Match revenue and hours to the same work period; payments arriving for old invoices will distort a weekly comparison. For fixed-fee work, include all hours spent delivering that fee, not just the ones you expected to need.

Make room for breaks without promising a magic interval

Try a manageable block of focused work followed by a break. Twenty-five minutes can be a starting point, not a rule you must obey during every task. A Pomodoro timer is useful if having a clear stopping point helps you begin. Adjust the interval when it repeatedly interrupts useful work.

A 2022 meta-analysis of micro-breaks found that participants felt slightly more energetic and less fatigued on average, but overall performance did not improve significantly. Breaks can be worthwhile without turning into a promise of more output. Keep them separate from email, which is still work, and leave some unallocated space for overruns and unexpected requests.

After the first week, keep the smallest useful routine: record task changes, check entries before finishing, and review one estimate each Friday. The result you want is a decision you can explain, such as allowing two hours for review in the next quote, rather than a calendar with every minute filled.