The Project I Finished and Forgot to Close

The project ended on a Thursday. I know because I sent the final files and got a thank-you email with a thumbs up emoji. Done.

Except I never closed it out. In my tracking setup, the project stayed open. And because it stayed open, I kept logging time to it without thinking. A follow-up question from the client. A quick fix two weeks later. A thirty-minute call I should have put somewhere else.

By the time I noticed, six weeks had passed. The project had $900 in logged hours sitting in it that had nothing to do with the original scope.

How It Happens

Finishing a project feels like the end of something. You send the deliverable, you exhale, you move on. The administrative close-out feels like paperwork and paperwork feels like later.

So you leave the project open. Just temporarily.

Then two weeks later a client emails and you hop on a call and you're already in the habit of logging time to that client name, so you do. You don't think about whether this is a new engagement or a tail end of the old one. You just click the familiar project and start the timer.

Six weeks of that and the data is useless. You can't tell what was in scope, what was out of scope, what should have been a new invoice, and what you should have billed as a change order.

What the Time Log Revealed

When I finally sat down to sort it out, I had to go entry by entry and try to reconstruct what belonged where. Some of it was obvious. Some of it I genuinely couldn't remember.

There were about four hours of legitimate post-project support that I probably should have invoiced separately. There were two hours of what looked like scope creep from the original project that I'd absorbed without documenting. And there were about three hours I couldn't categorize at all because my entry labels were too vague.

I ended up writing off most of it because I had no clean way to invoice it without a conversation I wasn't prepared to have. That's the real cost of leaving a project open. Not just confusion. Actual money gone.

What I Do Now

The day I send final files, I close the project. Not later. That day.

In Time-Trak, closing a project takes about ten seconds. But more importantly, it forces me to look at the total before I walk away. How many hours did I log? What did I invoice? Is there a gap I need to address before the context disappears?

If a client comes back after that with follow-up questions or a small fix, I make a choice: is this a courtesy, or is this new work? If it's new work, I open a new project and start a new timer. That keeps the records clean and keeps me from accidentally subsidizing ongoing support out of old invoices.

The screenshots help too. When I go back to a murky week and can't remember what I was doing on a Tuesday afternoon, the screenshots tell me. That's not a feature I thought I'd need until the one time I desperately did.

The Part That Stings

The client from this story is still a client. The project wrapped fine. She had no idea any of this was happening.

All of it was self-inflicted. I left the door open and walked through it by accident for six weeks, then had to write off the mess because I waited too long to deal with it.

Closing a project when it's actually done is one of those things that sounds obvious until you're staring at $900 in unrecoverable time wondering how you got there.

Now I treat the project close-out like part of the deliverable. The work isn't done until the record is clean.

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