How to Run a One-Week Time Audit (and What It'll Reveal)

Most freelancers and indie hackers have a rough sense of where their week goes — and that sense is usually wrong. A one-week time audit replaces the guess with two real numbers: how many hours you actually worked, and what your time was really worth once every hour, billable and not, gets counted.

Quick answer

Log every hour for seven days as it happens, without editing or judging it yet. At the end of the week, categorize each block — billable client work, admin, focus time, meetings, breaks — then calculate your real effective hourly rate. Most organizations manage capital with strict discipline but leave time completely unmanaged, and freelancers have the same blind spot at a smaller scale: you probably budget invoices more carefully than you budget your own week. The audit fixes that by turning "I'm busy" into two comparable numbers — the week you assumed you had, and the week you actually had.

Step-by-step

Log every hour for 7 days, as it happens

The rule that makes or breaks a time audit: log in the moment, not from memory at the end of the day. Cal Newport's version of a time audit treats this as two separate steps — first map your actual fixed schedule, then separately estimate how many hours each commitment really demands. Applied to a work week, that means logging client work, admin, breaks, and context-switching as they happen, not just the parts that feel like "real work."

Categorize each block after the week is done

Once the week is logged, sort every block into a small set of categories: billable client work, non-billable admin, focus/deep work, meetings, and breaks. This is the step where patterns you'd never have guessed become visible — a week that felt like "mostly client work" often turns out to be a third admin.

Calculate your real effective hourly rate

Divide what you actually earned that week by the total hours you worked — not just the hours you billed. That's the calculation James Clear uses to find your real hourly value: once you know the number in dollars and cents, you can compare it to your stated rate instead of guessing at the gap. Two freelancers can bill the same $2,000 a month and land at wildly different effective rates once every hour worked gets counted — one study of freelance economics found the gap runs as wide as $166/hr versus $36/hr for identical monthly revenue. This is also where you'll start to see which clients and projects are quietly your most profitable work, and which ones just feel busy.

Compare the week you had against the week you assumed

Put the categorized log next to what you expected going in. The gap between the two — not the raw hours — is the useful output of a time audit.

Common problems and fixes

The most common thing a one-week audit turns up is non-billable time quietly eating the week. Lose just 4-5 hours a week to meetings, admin, and revisions, and it compounds to roughly 200-250 hours a year — at a $50/hr rate, that's about $12,500 in annual profit that never shows up on an invoice. The fix isn't to eliminate admin entirely — it's tracking your non-billable time deliberately, so you can see how much of it there actually is and decide what's worth batching, delegating, or cutting.

Right behind that is Parkinson's Law at work: low-value tasks tend to expand to fill whatever time is available, regardless of how complex they actually are. Without a log, that expansion is invisible — you just feel busier than the work justifies. With a categorized week in front of you, it's obvious which tasks ballooned, and you can cap or batch them going into the next week.

Doing this with Pomlo

A time audit is only as good as how honestly the week gets logged, and that's exactly where most manual attempts fall apart — a spreadsheet started with good intentions on Monday and abandoned by Wednesday. Pomlo's one-tap start/stop makes in-the-moment logging realistic instead of a chore, and its reports turn a week of raw entries into the categorized breakdown an audit needs, without any manual spreadsheet work afterward. Projects and clients let you see your effective rate per client instead of one blended number, and focus sessions separate real deep work from the admin sitting next to it in your calendar — useful once you've mapped out your peak working hours and want your log to reflect them accurately.

Run your first one-week audit with Pomlo, free on the App Store and Google Play.

Frequently Asked Questions

How long should a time audit take?

One full week is enough to see a real pattern — long enough to include a normal mix of client work, admin, and at least one slow day, but short enough that you'll actually finish it. Repeating it every quarter catches drift as your workload changes.

Do I need special software to run a time audit?

No — a notebook or spreadsheet works. The only requirement is logging every block of time as it happens, not reconstructing it from memory at the end of the day. A lightweight tracker just removes the friction of that in-the-moment logging.

What if I forget to log an hour or two?

Estimate it as closely as you can and move on — a time audit doesn't need to be perfectly precise to be useful. Even a week that's 90% logged will surface the big patterns: where your billable hours actually go and what's quietly eating non-billable time.

What's the difference between a time audit and just tracking time?

Tracking time is the raw log. A time audit is what you do with it afterward — categorizing every block, calculating your real effective hourly rate, and comparing what you expected against what actually happened that week.

Conclusion

A week of honest logging turns a vague sense of "I'm busy" into two concrete numbers: how many hours you actually worked, and what those hours were really worth. Run it again next quarter — your client mix and workload will have shifted, and the audit is what catches the drift before it costs you a real chunk of billable time.