The Subcontractor Whose Hours I Trusted Too Long
I passed a subcontractor's self-reported hours directly to a client invoice for months before I checked the actual work.
I trusted him completely. He had worked with me for two years. Good work, easy to communicate with, never any drama.
So when he started sending weekly hour totals by email, I added them to the client invoice without looking hard at the breakdown. It was a retainer project. He handled one part. I handled another. The client paid monthly.
This went on for about seven months.
When Something Felt Off
It was not a dramatic discovery. I noticed it because a deliverable seemed smaller than the hours suggested. He had logged 18 hours on a phase I expected to take 10. The output was solid. But the numbers did not quite fit what I knew the task required.
I did not say anything yet. I just started paying closer attention.
Over the next two months, the pattern held. His hours were consistently higher than the work suggested. Not dramatically. Maybe 20 to 25 percent above what I would have estimated. But consistently above.
And I had been passing those hours to the client. Which meant the client had been paying for them.
What I Had Built Wrong
The mistake was structural. I had no actual visibility into how he was spending his time. I knew the outputs. I did not know the process. And because I had always trusted him, I had never set up a system that would have caught a drift.
When I brought Time-Trak into the team workflow, I asked everyone working on client projects to log inside shared projects. Not to surveil anyone. Just to have a single source of truth before anything went to an invoice.
The difference was immediate. I could see when time was logged, what task it was attached to, and how it tracked against the project budget. No one had to self-report into a spreadsheet or email me a total. The data was just there.
The Conversation I Had to Have
I sat down with the subcontractor and walked through the last few months of logged versus estimated hours. He had an explanation for some of it. For some of it he did not.
I do not think he was deliberately inflating. I think he had developed a loose logging habit, rounding up, counting time he spent thinking about the work while doing other things, that kind of drift. It is easy for that to happen when no one is checking.
But the client had been paying for it. And I had been signing off on invoices I had not actually reviewed.
What It Cost
I went back through the seven months. My best estimate was that the client had overpaid by somewhere between 1,400 and 2,000 dollars depending on how generously I interpreted the ambiguous sessions.
I did not go back to the client. The relationship was good and I could not prove specific sessions were wrong. What I did was adjust how I structured the next billing period and held that overage in mind when it came time to renew.
The lesson was not that the subcontractor was dishonest. The lesson was that I had built a billing process that required me to trust self-reported numbers with no way to verify them. That is a gap that invites drift even from people with good intentions.
If subcontractor hours are going on a client invoice, they need to come from a shared log. Not an email. Not a spreadsheet. A log you can actually look at.
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