What to Do When You Forgot to Start the Timer

Quick answer

Forgot to start the timer? Here's the short version: reconstruct the block from anything with a real timestamp — calendar, sent messages, file saves, commits — round conservatively, log the entry as an estimate rather than a precise figure, then fix the trigger that made you forget in the first place. It's not a crisis. It happens to nearly every freelancer who tracks time, and the fix takes minutes.

An unlogged block isn't just one missing invoice line. Left alone, it quietly drags down your real effective hourly rate for the whole year, because the work still happened — it just never got counted. The four steps below get it counted honestly.

Why this happens

You're most likely to forget the timer at exactly the moment you're most absorbed in the work. You sat down mid-thought, jumped straight into a call, or picked up where you left off yesterday without anything that felt like a "beginning." Deep, focused work doesn't announce itself with a natural pause — that's precisely when the timer gets skipped.

This is different from logging everything from memory at the end of the day, which is a chronic habit that erodes accuracy every single day. What you're dealing with here is a one-off miss. It deserves a one-off fix, not a reason to abandon tracking altogether.

Still worth taking seriously, though. James Clear's framework for calculating your real hourly value shows why: divide take-home pay by every hour actually worked, not just billable hours, and plenty of freelancers find their real rate sits well below their quoted one. Every block that goes unlogged because the timer wasn't running is part of that gap. It happened — it's just not in the math.

Step-by-step: reconstructing the block honestly

Pull from timestamped sources first, memory last. In order of trust: calendar events, sent emails or messages, file-save or commit timestamps, then app or browser history. Anything with a timestamp you didn't create after the fact beats a guess. Freelancers on Indie Hackers describe two versions of this: blocking time on the calendar ahead of a work session and adjusting the event afterward to match reality, or running short intervals and tallying them as you go so a single missed start doesn't wipe out the whole session.

Round conservatively. When the artifacts give you a range instead of an exact number, round down — or to your standard invoice increment. See how billing increments affect the final number. Rounding down on an estimate costs you a few minutes now. Rounding up on a guess costs you a client's trust the moment they check.

Write the estimate down immediately. Log it as soon as you've reconstructed it — not "later today." Later is exactly how the next gap starts. Stripe's guidance on hourly invoicing is blunt about this: a line item that just says "3 hours" invites questions, while one that says "3 hours (estimated) — client call plus follow-up revisions" doesn't, because it's upfront about being an estimate and specific about the work behind it.

Common problems and fixes

You genuinely can't find an artifact for part of the block. Log only what you can actually support, and note the gap rather than padding it to a round number. A shorter, honest entry holds up. An inflated one doesn't.

A client questions the entry. This is where reconstruction pays off, even a rough one. Time-tracking records are the strongest evidence in an amount dispute — not because they're perfect, but because they show what you worked on and roughly when. That turns a disagreement about a number into a five-minute conversation instead of a standoff.

It keeps happening. A forgotten timer once is a fluke. A forgotten timer every week looks a lot like the small tasks freelancers forget to bill for — untracked work that's real but invisible. If reconstruction is turning into a weekly ritual, the fix isn't a better reconstruction process. It's removing the step you keep skipping.

Doing this with Pomlo

The real fix for a forgotten timer is making "start" stop being a separate step you have to remember. Pomlo's focus sessions turn starting the timer into starting the work itself — open a session the same way you'd open your editor or join a call, and the tracking just happens as a side effect instead of a prerequisite.

When a gap does slip through, Pomlo's reports show it clearly against the rest of your week, so a reconstructed block isn't buried in a spreadsheet — you can see exactly where it sits next to everything else you tracked normally. And because projects and clients are built in, a reconstructed entry lands on the right invoice automatically instead of needing to be sorted out later.

Pomlo is free to try on the App Store and Google Play — a simple way to make sure the next session doesn't need reconstructing at all.

Frequently Asked Questions

Is it okay to estimate hours instead of tracking them exactly?

Yes, as long as the entry is clearly flagged as an estimate rather than presented as a precisely logged block. Clients and your own records both hold up better when an estimate is honest about being an estimate.

What's the most reliable source for reconstructing lost time?

Anything with a real timestamp you didn't create after the fact: calendar events, sent emails or messages, file save times, and commit history beat memory every time, because memory compresses and drops small gaps.

Should I round up or down when I'm not sure?

Round down, or to the nearest standard increment your invoice already uses. Rounding down on an estimate costs you a little now; rounding up on a guess costs you a client's trust if they ever check.

How do I stop this from happening again?

Pair a timer with a trigger you already do at the start of every work session — opening your editor, joining a call, sitting down at your desk — so starting the timer stops being a separate step you can forget.

Conclusion

A forgotten timer is fixable in the moment and preventable going forward. Reconstruct the block from timestamped artifacts before relying on memory, round conservatively, flag the entry as an estimate, and log it right away. Then spend five minutes on the habit that caused the miss — that's the part that actually stops this from happening every week. If missed timers are turning into a pattern rather than a one-off, read about the hidden cost of reconstructing your whole day from memory. The fix there is different, but it starts from the same problem.