Time Management

How to Log Forgotten Time Without Rewriting Yesterday

Forgotten time tracking is not a moral failure. It is what happens when the work and the app are in different rooms. You finished the workshop, walked the client to the elevator, answered a Slack from the next retainer, and remembered the timer on the train. Reconstructing the afternoon from memory is how honest people accidentally invent a timesheet.

The job is narrower than “catch up.” You need a way to log forgotten time that keeps the original duration honest, attaches the hours to the right client and task, and does not require you to narrate the whole day in fifteen-minute fan fiction. Stopping a timer you left running is a different leak — we have written about losing billable time when you forget to stop. This is the other direction: you never started, and now you have to write the hours down without lying to Friday-you.

Why reconstruction creates worse data than a blank

Consultants hate empty History more than they hate a slightly late entry. Empty feels unprofessional. So they sit down at 9:40 p.m. and paint yesterday in rounded blocks that look like a calendar: 9–11 Homepage, 11–12 standup, 1–4 “website.” That document is prettier than the truth and less useful. You cannot see scope creep. You cannot see whether the workshop ate the afternoon. You cannot tell a non-technical client what happened without a glossary you just invented.

A calendar is still not a timesheet. Meetings you attended are not automatically billable, and the gap between two events is not “deep work on the open task.” If you only remember that you were in the client’s office from 2 to 3:30, log 1.5 hours on the workshop task — not 6 hours of “onsite” because the commute felt like part of the job unless the contract says it is.

The other failure mode is padding from guilt. You forgot, so you round the story up “to be safe.” Rounding policies exist for a reason, and they should be a named rule, not a vibe. If you later turn on 6-minute rounding, the original duration should still be the thing you typed. Inventing 2.0 hours because 1.4 felt stingy is how you train yourself not to trust the report.

A catch-up habit that fits in five minutes

Do this the next morning, not at invoice time. Memory decays; invoices amplify.

1. Open yesterday, not the month. A History view that defaults to today is useful because the miss is usually “this morning” or “late yesterday,” not Q3. Scan for holes next to the entries you did remember to start.
2. Name the leaf, then the duration. Client → project → task. If the work was a meeting, it belongs on Meetings (or Kickoff, Sep 16), not on Implementation. If it was forgotten research, it belongs on research. Time lives on a task. A project total cannot tell you what to invoice.
3. Write the number you can say out loud. “I forgot 30 minutes on yesterday’s standup task” is a complete sentence. “I think I was basically on this all day” is not. If you only remember a lower bound, log the lower bound. You can add a second entry later if a note or a delivered file proves more.
4. Stop when the hole is filled. Do not go on to reconstruct lunch, Slack, and the grocery stop so the day looks “full.” Utilization theater is how burnout starts. Track the work you would defend to the client or to yourself.

Use reminders for the next miss, not as a rewrite engine

Smart reminders — average duration, a time of day, a regular interval — exist so you notice the gap while it is still a gap. They should nudge. They should not start a clock for you, and they should not invent idle time from a dark laptop. If you work between client sites, the useful move is a phone in your pocket: start from the dashboard search when you sit down, or add the manual entry when you get back to the car and still remember which task it was.

Mobile helps because the moment you did the work and the moment you face a browser are rarely the same moment. Voice is fine when your hands are full, as long as you still review the transcript and confirm the write. Forgotten time is a mutation like any other. Guessing in an assistant’s voice does not make the guess true.

Where MinuteShark does the catch-up without a novel

If you already work in MinuteShark, time is tracked on a task inside Client → Project → Task (subtasks on Standard). Manual entries live in History; you can edit start and end there, including after the fact. The dashboard History widget defaults to today, which is the right zoom for “what did I miss,” not for a quarterly archaeology dig. The dashboard widgets guide is the mechanical tour; this piece is the habit.

MinuteShark AI can log forgotten time in plain English after you confirm a proposal card: “I forgot to log 30 minutes on yesterday’s standup task.” You can edit the card before confirm. Many actions can be reverted from chat. Nothing is written until you confirm. It will not silently fill yesterday because a calendar had a hole. Official utterances exist for a reason — the product is built for that sentence, not for “make my timesheet look busy.” The getting started sequence is still Add Client → Add Project → Add Task; catch-up is just “then log the hour you already worked.”

If rounding is on, original duration stays stored and BILLABLE is the rounded-up view (6 minutes / 0.1h is the usual consultant preset). Catch-up entries flow into the same reports and invoices as timer entries. Generate What × Who × When, glance at yesterday, fix the task name while you still remember it. Sarah L., an independent consultant, said MinuteShark “feels like it was built exactly for how I work.” The catch-up path is that sentence: the hour you actually lived, written down late, still attached to the right leaf.

Starter is free if you are testing the habit. Standard is $5/user/month with a 30-day trial and no credit card. You do not need a marketplace of integrations to write down 30 minutes. You need a task, a duration, and a confirm.