When the Project Ends but the Requests Don't

The project was done. You sent the final files. The client said everything looked great. You marked it complete in your tracker and moved on.

Then, three weeks later, an email arrived. A small thing. Just a quick update on the files you sent. Totally minor. Should only take a few minutes.

You did it. You did not bill for it.

Then another email came.

The Post-Project Zone

There is a period after a project ends that does not have a clear name, but every freelancer knows it. The client still considers you their person. The deliverables are out in the world and things keep coming up. Small things, usually. Questions. Tweaks. One more change that was overlooked.

Each one individually feels too small to invoice. Together, over a few weeks, they can easily add up to several hours of unbilled work.

And because the project is technically closed, you often do not start a timer. You just handle it. It feels like customer service, not work.

Why This Keeps Happening

The root issue is that most projects end without a clear agreement on what post-delivery support looks like.

If the contract does not say anything about what happens after delivery, the client's default assumption is that you are still available. After all, they paid for something, it is in use, and things come up.

Your assumption might be that the project is done and any additional work should be scoped and billed separately. Neither of you has said this out loud, so neither of you has adjusted.

The first few small requests feel easy to absorb. By the time it has happened enough times to be a real problem, the pattern is established and it feels awkward to suddenly start charging for something you have been doing for free.

What a Time Log Shows You

If you are tracking time, even informally, you can catch this pattern early.

When you spend 45 minutes on a post-project email thread, log it. Tag it to the original project. Do this every time.

At the end of the month, look at how many hours you have logged against closed projects. If the number is significant, that is work you did for free after the scope ended. That is the number you need to use when you decide how to handle the next client conversation about post-delivery support.

You might decide to include a short support period in your project quotes. You might create a small retainer option for ongoing access. You might simply respond to the next request with a quick note that additional work is billed at your standard rate.

All of those are reasonable choices. What is not reasonable is doing the work indefinitely without knowing how much of it you are doing.

How to Close a Project Properly

When you send final deliverables, include a clear note about what comes next. Something direct: what this delivery includes, how you handle questions after delivery, and what the process is if they need additional work.

This does not have to be a long legal document. One clear paragraph is enough. It sets expectations before the ambiguous zone begins.

If a client sends a request after that, you have something to reference. You are not making up a new rule. You are pointing back to what you both already agreed on.

The Real Cost of Staying Vague

Clients who send ongoing small requests are not always doing it deliberately. Often they genuinely do not know where the line is. They liked working with you, the project went well, and they see you as a resource.

That is actually a good thing. It means they want to keep working with you. But wanting to keep working with you is not the same as paying you for your time.

The way you keep good clients from becoming expensive habits is by being clear from the start and then tracking everything that happens afterward.

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