The Project I Paused and Picked Back Up Wrong
A three-week client pause cost me four hours of unlogged catch-up work because I had no clean stopping point in my time log.
The client went quiet for three weeks. Not unusual. They were waiting on approvals from their own stakeholders. The project was on hold by mutual agreement and I moved on to other work.
When they came back, everything looked fine. I still had my notes. The files were where I left them. I remembered the project well enough.
What I had not documented was where I stopped in my time log.
The Catch-Up I Did Not Count
The first session back took about two hours before I was actually working. I re-read the brief. I went through the email thread to find where the client had landed on the last round of feedback. I re-opened files and reminded myself what decisions had been made.
Then I did another hour the next morning just rechecking a few things I had been uncertain about the night before.
None of that time was logged. It did not feel like project work. It felt like getting back up to speed, which I had mentally filed as my problem, not the client's.
But it was caused entirely by the pause they initiated. And it was three hours of real work I ate.
Why This Keeps Happening
Project pauses are almost never clean. When a client goes silent, you do not finish at a natural stopping point. You stop wherever you are. And when you pick back up, you have to rebuild the context you lost.
If you have a detailed time log with task-level notes, the rebuild is fast. You can read back through your entries, see exactly what was in progress, and pick up without the two-hour archaeology session.
If your log is sparse, you reconstruct from memory and email threads. That reconstruction takes time. And most people do not log it because it does not feel like real work.
It is real work. It just goes unlogged.
What a Clean Stopping Point Looks Like
After that project I started leaving a closing note in my time log whenever a project paused for more than a few days. Not a long note. Just a summary of where things stood, what was decided, what was pending. One entry. Usually five minutes.
When the client came back, I could read that entry and start the new session in roughly the right place. The catch-up time dropped to almost nothing.
Time-Trak makes this easy because the timer log is attached to the project, not to a separate document I might not find. The notes live inside the same log I bill from. When I open the project, the history is right there.
The Billing Problem It Creates
The bigger issue is that unlogged catch-up time distorts your project profitability. If a project pauses twice over a three-month engagement, you might eat four to six hours of re-entry work. At 90 dollars an hour that is 360 to 540 dollars gone.
And because you never logged it, you have no data to change your behavior or your pricing. The next time a client project runs long you do not know why. The hours just disappear into the gap between sessions.
Log the catch-up. Label it clearly. Decide separately whether you bill it. But at least know what it costs.
A pause in a project is not a pause in your responsibility to track it.
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