What happens to your billing when you forget to track a week

The week passed. You worked — the calendar has the events — but none of them have client tags. No [ClientA], no [ProjectB], just titles like “work block” or “deep work” or a client’s first name typed in a hurry.

Now it’s the end of the month.

Start with what’s already there

The calendar has more than you think. Even without proper naming:

• Meetings with clients are usually there by subject line. “Q3 roadmap call with Sarah” is enough to attribute it.
• Recurring blocks you planned are there, even if unnamed.
• The 3-hour block you set for a specific project is there, even if it just says “writing.”

Go through each day. For each event, one question: can I attribute this to a client from what’s written here?

If yes — done. Add the bracket and move on. If no — you need external sources.

What external sources actually help

For the unnamed blocks, ordered by how useful they are:

Email threads. What you sent during those days timestamps your work. A long reply to a client Tuesday morning ties that block to that client. An outgoing draft or feedback comment places you in a specific project.

Slack. Same principle. If you solved a problem for Client B on Thursday, the messages are there with timestamps.

Git commits, file modification dates, browser history. If the work left a digital trace, it has a date and time. A commit pushed Friday at 3pm is a calendar event in hindsight.

Client project tools. Notion activity logs, Linear updates, Asana task completions. If a client uses these, your contributions are visible with timestamps.

How much you’ll actually get back

The recovery isn’t complete. Accuracy in reconstructing hours degrades fast: 90% the day of, 75% after 24 hours, around 30–40% after a week. By the time you’re doing this, you’re in the 30% zone.

What you’ll recover reliably: scheduled meetings (they were on the calendar), large project blocks with obvious attribution, recurring work for predictable clients with clear deliverables.

What you’ll miss: short prep sessions, async communication that happened outside calendar blocks, the 30-minute overrun you mentally rounded down. This is exactly the category described in why freelancers lose billable hours without noticing — the boundary-creep and absorbed overhead that never had a label in the first place.

The recovery process

Treat it like a billing audit for that one week. Block 30 minutes:

1. Open the calendar. Go day by day through the missing week.
2. For each event: attribute it or flag it as unattributable.
3. For flagged events: check email, Slack, git for that day.
4. Accept the gap. Don’t invoice time you can’t verify.

The total you recover is what you invoice. Some hours are genuinely gone.

The five-second prevention

The bracket naming convention — [ClientA] at the start of the event title — takes five seconds when you create the event. You did the work. Those five seconds are the only thing that determines whether that work is recoverable or not.

One untracked week costs you 30 minutes of detective work and a percentage of your billing that week. Across a year, the pattern adds up — and the cost of that reconstruction is less surprising than it should be.

Timescanner reads tagged calendar events from any iCal-compatible calendar and generates billing reports per client. Google Calendar, Outlook, Apple Calendar, Proton Calendar — if it exports iCal, Timescanner reads it.