Common Mistakes When Tracking Your Own Hourly Pay

If you invoice by the hour, or work part-time shifts where pay depends on logged time, the accuracy of your own record is not a minor detail — it is your actual income. And the uncomfortable truth is that most people's mental estimate of hours worked is wrong in one consistent direction: too low.

The planning fallacy works backwards too

Most people have heard of the planning fallacy — the well-documented tendency to underestimate how long a task will take before you start it. Less discussed is that the same bias shows up afterwards: people also underestimate how long a task actually took, once it is done and memory has to reconstruct it rather than a clock having measured it in real time.

Memory rounds down because it remembers the task, not the clock. You recall "I worked on the report this afternoon," which becomes a vague block of a few hours, quietly losing the fifteen minutes you spent finding a reference, the phone call that interrupted you, and the twenty minutes after dinner when you went back to fix one paragraph. None of those pieces feel like "working on the report" in memory, even though every one of them was billable time.

The small tasks that never make it into the count

Beyond the general underestimate, there is a specific category of work that freelancers and part-time workers routinely leave out entirely, not because they forget it happened, but because it does not feel like "real" work at the moment it happens.

• Replying to a client's message at 9pm, which takes four minutes but happens outside any block you think of as "working hours."
• Preparing before a session starts — reading a brief, gathering files, mentally reviewing what the client asked for.
• Small revisions requested after the main work was delivered, which often get done "real quick" and never logged at all.
• Admin around the job itself: invoicing, scheduling, the email thread negotiating scope, none of which feels like the actual craft but all of which is time spent because of the job.

Individually these look trivial. Across a month, they routinely add up to several unbilled hours — often enough to matter, rarely enough that any single instance felt worth writing down at the time.

Why a simple log beats a better memory

The instinct is to try to remember better, or to reconstruct the week more carefully at invoicing time. Both approaches fight against how memory actually works, rather than working around it. A log recorded at the moment of doing the work sidesteps the whole problem: there is nothing to reconstruct, because nothing needs remembering.

It does not need to be complicated

The failure mode with time tracking is usually over-engineering it — a spreadsheet with categories, tags, and client codes that feels like its own small job to maintain, and gets abandoned within two weeks. A log only needs two things to be useful: a start time and an end time, captured close to when they actually happened. Everything else is optional detail you can add later if you want it.

Capture it near the moment, not at the end of the day

The four-minute reply at 9pm is the piece most likely to get lost if you wait until bedtime to write down the day. A reminder or a habit of logging as you go — even a rough note you clean up later — catches the fragments that end-of-day reconstruction reliably misses.

The negotiation benefit nobody mentions

Accurate logs are usually framed as a billing tool, but their second use is easy to overlook: they are evidence for you, later, about what a job actually costs in time. When a client asks for a quote on similar work next time, "I think it took about eight hours" is a guess. A log that shows it actually took eleven, split across three separate sessions with two rounds of revisions, is a number you can defend and price around.

1. Before quoting similar work again, check what the last job actually took — not what you remember it taking.
2. If revisions consistently add hours you did not originally quote for, that is a pattern worth pricing into the next quote, not absorbing again.
3. A log across several jobs shows you which type of work is quietly underpriced relative to the time it takes, which memory alone will not reveal.

None of this requires new software or a formal process. It requires catching the moment you start and the moment you stop, consistently enough that the record is more trustworthy than your recollection of the week.