The Hours That Move Between Clients Without You Noticing
Time logged to one client often includes work done for another, and that quiet distortion costs you money every single billing cycle.
It Happens Slowly
You're deep in a session for client A. A message comes in from client B. You handle it quickly. You don't stop the timer because it only took a minute.
Then another one. Then you draft a quick email. Then you're back.
At the end of the session, you logged two hours to client A. But 25 minutes of that session belonged to client B.
Multiply that by a full month. Now you've undercharged client B and overworked yourself on client A without even realizing it.
This Is a Data Problem Before It's a Billing Problem
Most people think of billing errors as the risk. And yes, you might be undercharging a client. That's real money left on the table.
But the deeper problem is that your time data is wrong. Every report you pull is distorted. Your profitability numbers are off. Your sense of how long things take is built on inaccurate logs.
When you try to quote a similar project six months from now, you'll price it based on data that never reflected reality.
Where Cross-Client Time Usually Hides
Communication is the biggest culprit. Responding to a client while you're in a session for another client is so common it feels normal. It is not free.
Admin work is the second one. Filing, updating project notes, sending follow-ups. If you're doing client B admin while a client A timer runs, that's a mislog.
Context switching itself costs time. Opening a client B thread and then mentally re-entering client A work takes minutes you don't count.
Screenshots Surface This
Automatic screenshots during tracked sessions are useful here in a specific way. When you review them after a session, you can see exactly what was on your screen during logged time.
If your screenshots show a client B email thread during a client A session, you have evidence of the problem. Not to punish yourself, but to fix the data and build better habits.
This is one of the less obvious reasons screenshots matter. It's not just about proving work to clients. It's about keeping your own records accurate.
The Fix Is Mostly Behavioral
Stop the timer when you switch clients. Even if you think the switch will be quick. Especially then.
If client B pulls you for two minutes, stop the client A timer, log two minutes to client B, restart client A. Yes, it adds friction. That friction is the point. It makes you feel the cost of the switch.
Most people who do this for a week find that they voluntarily batch client communication rather than deal with the timer interruption constantly. That's a productivity improvement and a billing accuracy improvement at the same time.
Block by Client, Not Just by Task
One structural fix that helps: schedule your day in client blocks. Two hours for client A, then a communication window, then two hours for client B.
During the deep work block for one client, you don't handle another client's messages. The timer runs clean. The log is accurate.
This also makes your time reports more useful. When you pull a report for client A, you're actually seeing client A's hours.
What to Do With the Distorted Data You Already Have
If you've been logging this way for months, your historical data is blurry. You can't fix all of it retroactively.
What you can do is run a realistic audit going forward. For the next 30 days, track cleanly. Stop timers when you switch. Log everything to the right project.
At the end of 30 days, compare to the previous month. The difference will tell you how much distortion you were working with.
Clean data costs a few extra seconds per session. Distorted data costs you accuracy on every quote, every invoice, and every business decision you make from your reports.
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