The Day a Client Asked for My Time Logs

The Invoice Was Accurate. I Just Could Not Prove It.

The project had run long. Longer than either of us expected. The work was good, the deliverables were solid, but the final invoice was bigger than the client had anticipated.

They were polite about it. They said they were not disputing the quality of the work, just that the number seemed high relative to what they had imagined the project would cost. They asked if I could share my time logs so they could better understand where the hours went.

I went cold.

Not because I had done anything wrong. The hours were real. I had genuinely put in that time. But my records were a disaster. Notes in a text file. Some entries in a calendar. A few rows in a spreadsheet I had started and then abandoned halfway through the project. Nothing that told a clear, professional story.

What I Sent Them

I spent two hours piecing together what I could. I assembled a rough breakdown by week, estimated where I was less certain, and sent it over with a note that said something like "my records are a bit informal but this reflects the actual time as accurately as I can report it."

They accepted it. They paid. But the conversation that followed was uncomfortable. They pushed back on a couple of line items. I could not defend them with specifics because I did not have specifics. I ended up discounting part of the invoice just to close it out cleanly.

The discount was not large. But it was not nothing. And I had earned every single hour.

The Specific Hours I Could Not Account For

Here is the thing that bothered me most. Some of the hours I lost in that negotiation were the hours spent on things that were genuinely hard to explain without data.

The research phase that ran long because the brief was unclear. The version I rebuilt from scratch after a misunderstanding. The hour I spent on a call that the client had requested but had not counted in their head as my billable time.

Without logs, those hours were just my word against their memory. And clients tend to remember the scope they imagined, not the scope that actually happened.

What Automatic Logs Change

After that project, I started using Time-Trak consistently. Not just for the totals but for the entries themselves. Task-level notes. Start and stop times. A record that builds itself as I work.

The automatic screenshots were something I had not thought much about at first. But they matter in exactly this kind of situation. They are a timestamped record of what was on my screen during a working session. They do not lie about whether I was working at 2pm on a Tuesday.

If a client asks for my logs now, I can produce them in a few clicks. Not a reconstructed text file. A clean report with entries, dates, task descriptions, and if needed, supporting screenshots. The conversation changes completely when you walk in with documentation instead of memory.

What I Think Clients Are Actually Asking

When a client questions a large invoice, they are usually not trying to catch you in a lie. They are surprised and they want to understand. They want the story of where the time went.

A good time log tells that story. It shows that the research phase took longer because the direction changed twice. It shows that the revision round was bigger than the first round. It shows Tuesday afternoon was five hours of focused work, not two.

Data does not argue. It just shows.

The Discount I Will Never Give Again

I gave up part of an invoice I had earned because I could not defend my own records. That is the part that still bothers me when I think about it.

The work was good. The time was real. I just had not built a system that could prove it.

Now I have one. And the next time a client asks for my logs, I will send them before they finish the sentence.

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