How to wrap up a project without the follow-up dragging on

The deliverable is sent. The client says “great, thanks.” And three weeks later a small request lands in your inbox. Then another. The invoice is still unpaid because “we’re just reviewing a couple of things.”

You’re not on the project, but you’re not off it either.

This isn’t a difficult client. It’s a project that ended without actually closing.

Delivered and closed are not the same thing

Most freelancers treat delivery as the close. It isn’t.

Delivery is the technical act of handing over work. Close is the moment both parties acknowledge the project is finished, everything promised has been delivered, and nothing outstanding remains. Without that moment, the project stays open — in the client’s head and in yours.

The sequence that closes a project: delivery → sign-off → handover → final invoice.

Skip any of those steps and you’re not closing, you’re just stopping.

What sign-off actually does

Sign-off is written confirmation from the client that the deliverable meets what was agreed.

It doesn’t need to be a formal document. An email that says “this is exactly what we needed, looks good” is enough. What matters is that it exists, it’s written, and it covers the full scope.

Without it, “final delivery” is contestable. The client can always come back with “we hadn’t fully approved that yet.” With a written sign-off, there’s a clear line in time: the work was accepted, changes from this point are new work.

Getting sign-off also surfaces any real issues before you invoice. If something isn’t right, better to know before you ask for payment than after.

Handover is where most open loops live

The long tail of post-delivery requests usually isn’t bad faith. It’s a client who doesn’t have what they need to operate without you.

They need the source files. They need the credentials. They need to know how to update the thing you built. They need the documentation that explains decisions you made.

Handover is the package that answers all of that. It closes the open loops before they become requests.

What a handover includes depends on the project type. For a design project: source files in agreed formats, style guide, asset library. For a development project: credentials, deployment documentation, codebase notes. For any project that involves ongoing operations: a short guide on how to do the most common tasks.

It doesn’t have to be long. It has to be complete.

Invoice after sign-off, not before

The timing matters. If you invoice before sign-off, payment becomes entangled with any remaining issues. The client has a reason to wait, and you’ve lost the natural closing sequence.

Invoice immediately after sign-off — the same day if possible. By then, the client has confirmed the work is complete, the handover is done, and there’s nothing unresolved. The invoice is a formality, not an opening for negotiation.

Before you send it, go through the actual billing record. If you’ve been tracking your work in your calendar, Timescanner generates the full summary in a few minutes: every session, total hours by client and project, total amount. The invoice reflects exactly what was worked. If a client ever questions a line, the calendar is the record.

What to do when requests come in after the close

They will. The close reduces them — it doesn’t eliminate them.

If a request is genuinely minor (under 30 minutes, clearly a gap in the handover): do it without making a billing conversation out of it. Not everything needs to be invoiced. The goodwill is worth more.

If it’s substantive: “This is outside the scope of what we wrapped up. I’m happy to take it on — my rate is [X] and I can start [timeline]. Want me to send a quick proposal?”

That’s not a confrontation. It’s a clear boundary. Most clients who have a complete handover don’t push back on it — they know they’re asking for new work.

When sign-off doesn’t come

Sometimes the problem isn’t post-delivery requests. It’s a client who just won’t confirm. They keep “reviewing.” Weeks pass.

That’s either a scope issue (what “done” looks like was never clearly defined) or a relationship issue (they’re buying time before disputing something). In either case, patience alone doesn’t solve it. If the project has genuinely stalled, ending it cleanly and formally — with or without a signed-off final deliverable — is sometimes the only way out.

The close isn’t just about getting paid on time. It’s about what comes after. The projects that close cleanly are the ones that lead to referrals and repeat work. How well you close is part of the relationship — which is why the offboarding conversation matters, not just the final invoice.

Timescanner reads your calendar and generates the billing summary for any period — by client, by project, total hours, total amount. Works with any iCal-compatible calendar.