The Project Nobody Decided Was Over

It did not have a finish line

The project had a clear scope at the start. A website redesign. Five pages, one round of revisions, handoff on delivery.

Six months later I was still answering emails about it.

Not complaints. Just questions. Small requests. Things that fell just inside the boundary of what we had agreed on, or close enough that I did not feel comfortable saying no.

At some point the project stopped being a project and became something else. A loose, ongoing obligation with no contract and no billing attached.

The moment it became free work

I sent the final invoice when I delivered the files. The client paid. That should have been the end.

But a week later they had a question about the CMS. I answered it. Two weeks after that, they wanted a small copy change. I made it. Then another question. Then a request to adjust a button color.

Each thing was small. Individually none of them were worth raising. But they were adding up.

When I finally looked at my time logs, I had logged nearly four hours of post-invoice work on a project I considered closed. Four hours I never billed. Four hours that just disappeared.

Why this keeps happening

There is no clear ending. The files get delivered, the invoice gets paid, but nobody explicitly says the project is done. So the relationship just continues in this ambiguous state where you are not sure what is support and what is new work.

Freelancers tend to absorb the ambiguity. It feels easier than having the conversation. And each individual request is too small to fight over.

But four hours at your billing rate is not nothing. Across a year of clients, that kind of drift can represent a significant chunk of revenue you worked for and never collected.

What the time logs reveal

The only reason I caught this was because I was still logging time on that project. Out of habit more than anything. The timer was still set up, I was still clicking it when I worked on anything related to that client.

When I sat down to do a billing review at the end of the month, the hours were just sitting there. Logged, labeled, unbilled.

Without that record, I would never have known. The work would have vanished completely.

How to actually close a project

When you deliver final files, send a short closing note. Not a formal legal document. Just a clear sentence that says the project is complete as scoped, and that any future requests will be handled as new work under your standard rates.

Most clients do not push back on this. They just needed someone to draw the line.

For ongoing support, set up a small retainer or an hourly rate for post-project requests. Some clients will take it. Some will not need it. But now you have a structure instead of an open tab.

The billing habit that protects you

Keep the project open in your time tracker until you have actively decided to close it. Not when the invoice goes out. When the relationship genuinely moves into a new phase or ends entirely.

That way any time you log after delivery is visible. You can decide to bill it, roll it into a support arrangement, or write it off. But at least you are making a choice, not just losing hours by default.

Projects without finish lines are not unusual. Clients do not always think about where the work ends. That is not their job. It is yours.

Track everything up until the real end. Then make the end official.

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