Why switching loses time
When you work on one client’s task from start to finish, recording time is easy. The trouble starts when the day fragments. A call comes in, an email needs a quick answer, another client asks for something urgent.
Each switch creates two small decisions: what to do with the time already running, and where to record the new work. If either is put off until later, the record becomes a reconstruction. Short interruptions are the first casualty, because they feel too small to note, yet several a day can add up to a meaningful amount.
The method: pause, switch, return
The most reliable approach is to make the switch at the moment it happens, in three steps.
- Pause the current client’s time. Don’t stop it or leave it running. You want the first session to stay open so it can continue later.
- Start recording the interruption against its own client. Even a four-minute call. Decide later whether to bill it.
- Return to the original work and resume. The first session now has a clear gap where the interruption was.
A worked example
You start reviewing a contract for Smith & Co at 09:12. At 09:58, Fred Williams calls about his property purchase. The call ends at 10:07 and you go back to the contract until 10:55.
Here is how three common ways of recording that morning compare.
| Approach | Smith & Co | Fred Williams | Problem |
|---|---|---|---|
| Timer left running | 1:43:00 | Not recorded | Fred’s call charged to Smith |
| Estimated at day’s end | About 1:30 | Forgotten | Both figures are guesses |
| Pause, switch, return | 1:34:00 | 0:09:00 | None |
Times rounded to the minute for readability.
Recording versus billing
It helps to keep two questions apart. Recording is about what happened. Billing is about what you charge. Record actual time first, then apply your own billing policy, such as rounding to an agreed increment or writing off a short call, when you prepare the bill.
An end-of-day check
Two minutes at the end of the day catches most mistakes while you still remember the details.
- Is anything still running or paused that should be finished?
- Does each session belong to the right client and job?
- Were there calls or emails you handled without recording?
- Does any session look too long because you forgot to pause?
Doing this in TapSpan
The method works with a notebook or a spreadsheet. TapSpan follows the same three steps: Pause, then Switch, choose the caller’s job, and Return when you’re done. Return brings the paused session back to the timer, and you tap Resume when you start working on it again. The paused session keeps its time and the interruption gets its own record.