The Project I Took On at the Wrong Moment

The brief looked good. The client seemed reasonable. The pay was fair.

I said yes the same afternoon they sent the proposal, without opening a single project file or checking how my current week actually looked.

That decision cost me more than just sleep.

What I Was Already Carrying

At the time, I had two active projects. Both were in the middle phase, which sounds stable but is actually the most demanding stretch. Deliverables are due. Clients are checking in more. Revisions start overlapping with new work.

I knew this in a general way. I just did not have a clear picture of what my actual available hours looked like. I was not running capacity checks. I was working by feel, which sounds efficient until it is not.

I said yes to the new project because I had done similar work before and it felt manageable. What I missed was that my existing projects were already using more hours per week than I had realized.

The Week It Collapsed

Three weeks in, all three projects hit crunch at the same time. Deadlines stacked. Revision requests came in simultaneously from two clients. The new project turned out to have a faster turnaround requirement than I had understood from the brief.

I worked that week the way you are not supposed to work. Long days, bad decisions at the end of them, work that had to be redone because I was too tired to do it right the first time.

I was logging my hours during this period, which is the one thing I did right. And the logs were clarifying in a painful way.

What the Timer Showed

By the end of that week, I had logged over sixty hours across the three projects. But the distribution was wrong.

The new project, which paid the most, got the least attention because it was the newest and I kept deprioritizing it to handle urgent messages from the established clients. The work I delivered on it was rushed. I knew it and they eventually said so.

The existing clients got more of my hours, but those hours were fragmented. Lots of short sessions. Lots of stopping and restarting. The screenshots I review later showed a browser full of open tabs, constant switching, no sustained focus anywhere.

The hours were there. The quality was not.

The Client Conversation I Had to Have

The new client came back with substantial revision requests. Not unreasonable ones. Just ones that reflected work that had not been done at the standard I normally hit.

I did the revisions. I did not charge for them, because honestly they were fair. But they cost me about eight hours I had not budgeted for.

I also had a hard conversation with one of the existing clients about a missed deadline. I had never missed a deadline with them before. The relationship recovered but it took effort and a few months of being extra careful.

The Process Change That Came Out of It

Now before I say yes to anything, I do one thing first. I pull up my active projects and look at where they are in their timeline. Then I check my current weekly hour logs to see what I am actually using, not what I think I am using.

Those two numbers together tell me whether I have real capacity or just theoretical capacity.

Real capacity is what you have after you account for meetings, communication time, and the ramp-up each project needs when you context-switch into it. Theoretical capacity is the hours left on paper when you subtract nothing.

I used to book off theoretical capacity. I book off real capacity now.

That one shift has made me slower to say yes. It has also made every yes much easier to deliver on.

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