TTime-Trak/Blog
Download →
Story·3 min read·November 21, 2026

The Week I Let the Timer Run on the Wrong Project

I billed Client A for work I did for Client B, and nobody caught it until the relationship almost broke.

It was a busy week. Two deadlines, three clients, back-to-back calls on Tuesday. I was switching contexts fast and I was not being careful.

I billed Client A for four hours of work I had actually done for Client B.

Client A paid without question. Client B got an invoice that looked light and did not ask about it. For about six weeks, nothing surfaced. Then Client B asked for a summary of hours by task phase, because they were planning a follow-on project and wanted to scope it accurately.

I pulled the log. The hours did not match the work. I knew immediately what had happened.

What Context Switching Actually Costs

I had been tracking time. That was not the problem. The problem was that I was starting timers without checking which project was selected. In a fast week, that is easier to do than it sounds.

I would finish a call with Client B, stay in the headspace of that project, and start a timer. But the last project I had open was Client A. So that is where the hours went.

The error was not dramatic. It was quiet. No alarm fired. No warning appeared. The numbers just went to the wrong place, and both invoices looked plausible enough that neither client pushed back.

The Fix Was Simple and I Resisted It

After this happened, I set a rule for myself. Before I start any timer, I look at what project is selected. I do not start the clock and then check. I check first.

That sounds obvious. It took a real billing mistake for me to actually do it every time.

I also started using more specific project codes. Instead of a single entry for a client, I had phases. That made it harder to accidentally slot hours somewhere wrong, because I had to actively choose the phase, not just the client.

The Conversation I Had to Have

I refunded Client B the difference and rebilled Client A correctly. Client A was fine. Client B was more confused than angry, which was almost worse. They trusted me to track the work accurately, and I had not.

I did not lose either client. But I spent a lot of goodwill on something that was entirely preventable.

The thing about billing errors is that they almost always come out eventually. Sometimes a client catches it. Sometimes you catch it too late. Sometimes the error is in your favor and you feel vaguely guilty for months.

What Running Multiple Projects at Once Actually Requires

You cannot manage two or three active client projects on memory and habit. Memory is not a system.

What I do now is keep the floating timer visible on my screen at all times. I glance at it before I sit down to work. I make sure it shows the right project before I open a file or reply to a message. That thirty-second check has saved me from repeating this mistake many times.

I also do a quick audit at the end of each day. Five minutes, no more. I look at what I logged and ask if it matches what I remember working on. Usually it does. When it does not, I catch the error the same day, while the work is still fresh.

The Part Nobody Tells You

Tracking time is not enough. You have to track it accurately, against the right project, with enough detail to audit later.

A time log that is full of hours but missing context is almost as useful as no log at all when something goes wrong. You need to be able to open it three months from now and understand exactly what you were doing and why it was billed to that client.

The week I let the timer run on the wrong project was an expensive lesson in what accurate time tracking actually means. It is not just running the clock. It is running the clock on the right thing.

Track your time, bill every minute.

Time-Trak is a native Mac and Windows time tracker with a floating timer, automatic screenshots, and one-click invoicing.

Free during beta.

Download Time-Trak →

macOS + Windows · Floating widget · Auto screenshots

More like this

← All articles·time-trak.com