The Week I Tracked Every Apology I Made to a Client

A client told me I seemed distracted. Not in an aggressive way. Just an observation. She said the last two deliverables had small errors she would not have expected from me and asked if everything was okay.

Everything was okay. I was just overloaded and managing it badly.

After that call I started an experiment. For one week I logged every time I apologized to a client or corrected something I had done wrong. Not to beat myself up. Just to see what was happening and when.

The Log Filled Up Fast

By Wednesday I had seven entries. Some were small. A typo in a document. Forgetting to attach a file. One was significant. I had sent the wrong version of a deliverable to the wrong client. I caught it before they saw it, but it was a close call.

Each time I logged the apology I also wrote what I had been working on in the ten minutes before the mistake. I wanted to see if there was a pattern.

There was.

Every single error happened when I had been context switching. A client call followed immediately by writing. Reviewing one project and jumping to send something for another. Trying to answer a message while finishing a task for someone else.

The Time Logs Already Knew This

When I went back through my actual time logs for that week, the pattern was obvious in the data. I had been switching between client projects at a pace that looked productive on paper. Lots of logged hours. Good billable numbers. But the switches were frequent and the sessions were short.

I had been averaging about eighteen minutes on a task before something interrupted me. I had not noticed because each session was logged and it all added up to a full day. The logs showed me working. They also showed me never settling.

What I Changed

I started blocking client work by client. Not by task type. Not by deadline. By client. Monday mornings were for one client only. Tuesday afternoons were for another. I would not switch until the block ended.

I also added a buffer between any client call and the next piece of client work. Fifteen minutes minimum. Just enough time to close the mental tab on what I had just done before opening a new one.

The apology log stopped filling up. Not because I got better at the work. Because I stopped doing the work while mentally holding five other things.

The Embarrassing Part

I had been proud of how much I was logging. Full days. High billable hours. Felt like momentum.

What my logs were actually showing was a day built out of fragments. Lots of starts. Not many completions. When I measured by sessions that ran longer than thirty minutes without interruption, I was getting maybe two or three a day. The rest was noise dressed up as productivity.

Time-Trak's own timer history made this obvious once I looked. Short entries stacked back to back. Project names cycling. No depth.

What a Good Day Actually Looks Like in the Logs

Now I look at my daily entries before I finish for the day. I want to see long sessions. I want to see blocks where the project name does not change for an hour or more. That shape in the log is what actually produces work I do not have to apologize for.

The hours are not just a billing record. They are a map of how the day actually went. And if the map shows me bouncing around every twenty minutes, that is not a full day. That is a scattered one.

Tracking the apologies was uncomfortable. But it pointed at something the billing logs had already captured. I just had not looked at them that way before.

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.

macOS + Windows · Floating widget · Auto screenshots