How to track your work hours honestly

Ask a freelancer how long a project took and you will get a genuinely believed wrong answer. Time-use research keeps finding the same pattern: people reconstructing their day from memory drop the fragments — the twenty-minute revision, the client call, the email thread that ate half an hour — because none of them felt like "working on the project." Reconstructed timesheets systematically shrink, and every shrunk hour of client work is money quietly donated. This article is about tracking time in a way you'll actually sustain, and what to do with the numbers.

Memory is a terrible timesheet

The failure has a shape. Long, focused blocks survive in memory: the Tuesday you spent all afternoon on the design gets remembered as an afternoon. What vanishes is the fragmented work — and modern work is mostly fragments. Five short client interactions across a week feel, in retrospect, like "a few emails," and get billed as nothing. The result isn't random error, it's biased error: reconstruction almost always under-counts, which is why the fix is recording, not remembering. Start the clock when you start, stop it when you stop, and the argument with memory never happens.

What underbilling actually costs

Run the arithmetic once and it stops being abstract. Miss five billable hours a week — one fragmented hour a day, entirely typical — at $50 an hour, and reconstruction is costing around $1,000 a month. Even at half that rate and half that leakage, it's a holiday a year. The habit that fixes it costs two clicks per work session.

A tracking method you'll keep

Tracking systems die of friction, so remove all of it:

• Two clicks, no ceremony. Name the project, start, stop. Our time tracker is built to be exactly this and nothing more — and it suggests your previous project names so totals don't fracture across "Acme site" and "acme website".
• Track at the project level, not the task level. "Acme redesign" is sustainable; "adjusting header padding" is a diary you'll abandon by Thursday.
• Stop the clock when you stop working. Honest 25-minute entries are the whole point — a timer left running through lunch produces numbers you'll rightly distrust and then stop using.
• Forgot to stop it? Nothing is lost. The tracker stores only the start time while running, so it survives a closed tab — stop it when you notice and delete the overrun entry if it's wrong.

A weekly review closes the loop: every Friday, glance at the totals, export the CSV, done. That rhythm — track as you go, review weekly — takes about two months to become automatic, and then it runs itself.

Billable versus honest hours

Track everything a client causes, then decide what to bill. Those are two different operations, and collapsing them is how the admin disappears. The call, the revision round, the invoice you wrote, the files you prepared — clients cause all of it, and it belongs in the client's total whether or not your contract lets you bill each minute. Even when a project is fixed-price, the tracked total is what tells you whether the fixed price was right — the difference between your quote and your log is next quote's correction.

From log to invoice

At billing time the log becomes line items. The clean route: total the hours per project for the period, put them into the invoice generator as quantity, your hourly rate as the unit price, and keep the CSV export with your records as backup for the numbers. An invoice line that says "Design revisions — 6.5 h @ $60" backed by dated entries is also the end of most "this seems high" conversations — itemised, dated hours read as evidence, not estimate.

What the log teaches you

After a month, the totals start answering questions you didn't ask:

• Your real hourly rate. Fixed-price project income ÷ tracked hours. This number is frequently a shock, and it is the single most useful input to your next quote.
• Where the week actually goes. The client you'd have named as "small" is often a quarter of your hours — under-priced attention, made visible.
• What to fix first. If admin is eating six hours a week, that's the argument for templates and automation, with a number attached.

None of this requires software more complicated than a start button, a stop button and a CSV. It requires the two clicks, every session, until they're reflex.