The Day a Client Asked Me to Prove I Had Worked

The message came on a Thursday morning. The client wanted to discuss the latest invoice. They had a question about the hours logged for a particular phase of the project. Could I provide supporting documentation?

I had the hours. I had logged them. But I had a problem.

The hours were logged in my tracker. The tracker showed durations. But the client wanted to understand what I had actually been doing during those sessions. They were not accusing me of fraud. They had a stakeholder above them who needed justification before approving payment. They needed something they could show someone else.

What My Logs Contained

My time entries for that phase were honest but vague. Three hours: research. Two hours: drafting. One hour: review. These descriptions were accurate. But they did not look like anything. Anyone could type those words into a time entry. They were impossible to verify.

I had no screenshots. No work-in-progress saves I could timestamp. No record of what I had looked at or opened or produced during those sessions. I had a number with a label and nothing underneath it.

The Conversation I Did Not Want to Have

I explained my process as best I could. I described what the research phase had involved. I named the sources I had consulted. I walked them through the structure of the draft and what thinking had gone into it.

The client was sympathetic. They believed me. But they told me their finance team needed something documentable and a verbal explanation from the contractor was not going to satisfy the requirement.

We worked it out eventually. They paid. But it took three extra weeks and involved more back and forth than the entire rest of the project.

What Automatic Screenshots Would Have Done

After this I set up Time-Trak and turned on automatic screenshots. Not because I expected to be accused of anything. Because I had just spent three weeks in a documentation dispute and I never wanted to do that again.

The screenshots are not intrusive. They capture randomly during tracked sessions. Over time they build a record of what was actually on screen during a work session. A client who questions an invoice can see a timestamped visual history of the work. Not just a number someone typed.

The next time a client asked me about a phase of work, I pulled the screenshot history for those dates. They could see exactly what I had been working on. The conversation lasted about four minutes.

What This Is Not About

This is not about clients who are difficult or suspicious by nature. The client who questioned my invoice was reasonable and paid in the end. The problem was structural. I had a process that produced no verifiable evidence of work happening.

Most clients will never ask. But the ones who need to escalate internally or who work inside an organization with procurement rules will ask. And when they do, a time log without supporting documentation is a weaker position than it looks.

The Practical Result

I now have a record of every work session that includes both the logged time and a visual trail of what was happening during it. When I generate an invoice I can attach a report that includes both. No client has questioned an invoice in a way that required extended back and forth since I set this up.

The proof of work serves a purpose I did not understand until I needed it. The time log answers how long. The screenshot record answers what you were actually doing. Both questions are legitimate. Having answers to both is not about distrust. It is about being able to finish the conversation quickly and get paid.

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