The Slow Month That Wasn't Actually Slow

October felt slow. I remember thinking that. Revenue was down from September and I assumed it was just a quiet month, the kind that happens sometimes. I accepted it and moved on.

Then I ran the hours report.

I had worked 142 hours in October. That was more than September. Significantly more.

What That Math Means

If you work more hours and make less money, one of a few things is happening.

You wrote off more time than usual. You were less efficient with billable work. You spent more time on admin and business development that doesn't get billed. Or you had hours that should have been invoiced but weren't.

For me it was mostly the last one.

I went through October entry by entry. I found a client project where I'd logged 22 hours that I hadn't invoiced because the project had gone sideways and I was waiting until we sorted out the scope before I billed. The scope conversation never happened. The month closed. I forgot.

I found a new client onboarding that had taken about eight hours of calls, setup, and back and forth that I hadn't put on any invoice because it felt like overhead, the kind of thing you eat at the start of a relationship to seem reasonable.

I found a revision round on a third project that I'd logged under the project but never included when I built the invoice, because I'd built the invoice before finishing the work and then added more time without going back to update it.

All of it logged. None of it billed.

The Feeling of a Slow Month

This is what bothered me most: I had felt slow. I had the emotional experience of a quiet month even though my logs showed the opposite.

I think what happened is that none of those hours felt productive. The stuck client project felt frustrating. The onboarding felt like overhead. The extra revision round felt like failure. So my brain categorized October as slow even though I was working constantly.

Your perception of a month and your actual output in a month can be completely different. The logs don't care about your feelings. They just count the hours.

What I Could Have Recovered

I did the math on what was sitting unbilled. Not all of it was recoverable. The stuck project was genuinely complicated and I wasn't going to retroactively charge for time spent in confusion.

But the onboarding hours were real work. The revision round was clearly outside the original estimate. Together, those two things were about $1,100 at my rate.

Gone. Not because the work didn't happen. Because I hadn't checked the gap between logged hours and invoiced hours before the month closed and the context dissolved.

The Check I Run Now

At the end of every month, before I do anything else, I pull a report showing total logged hours by project and compare it to what I invoiced that project. If those numbers are close, fine. If there's a gap, I need a reason.

Sometimes the reason is legitimate. I wrote off time on purpose. The hours were duplicated. The task was internal.

But sometimes the reason is that I forgot, or I was waiting on a conversation that never happened, or I built the invoice too early and logged more time after the fact.

Time-Trak makes this comparison fast. Total logged, total billed, difference. If the difference is more than an hour, I look at it before I close the month.

November was fine. Not because it was a better month. Because I ran the check.

October was never actually slow. I just treated it like it was and moved on before I could see what was sitting in the data.

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