Client sign-off email before final payment: a template for freelancers

There is a specific kind of silence that happens near the end of a freelance project. The work is done, you have sent it over, and now you need two things from the client in a particular order: a clear "yes, this is approved" and then the final payment. Ask for both at once and the message gets muddled. Ask for neither clearly and the project drifts for weeks with no invoice sent and no feedback given.

The fix is a short, specific sign-off email that separates approval from payment, asks for the first in writing, and only then triggers the second. Below is how to structure it, with templates for the main situations you will run into.

Why sign-off needs to happen before the invoice, in writing

Two things go wrong when freelancers skip this step. First, without a clear approval moment, "final" work quietly turns into round six of revisions, because nothing marked the project as done. Second, if a dispute ever comes up about what was delivered, a vague thread of "looks good, thanks!" messages is weaker proof than one specific line: "I approve the final deliverable as of [date]."

Asking for that line is not bureaucratic. It protects both sides. The client gets a clear record of what they accepted, and you get a clear trigger for the final invoice — one that is hard to argue with later.

Structure the email in three parts

1. State what you are delivering, specifically — not "the project" but "the final homepage design, the three inner pages, and the style guide PDF."
2. Ask for one specific action: approval in writing, by a stated date if you want to keep momentum.
3. Say what happens next: the final invoice goes out once you have that approval, with the payment terms already agreed.

Keeping these separate means the client is never asked to approve and pay in the same breath, which is where a lot of these emails start to feel pushy.

Template 1: the standard final sign-off request

Use this when the project is complete and nothing is outstanding.

Subject: Final sign-off on [Project Name]

Hi [Name],

[Deliverable, specifically] is now complete and attached/linked here: [link]. This covers everything in our original scope.

Could you confirm you approve this as the final delivery? Once I have your sign-off, I'll send the final invoice for [amount], due per our agreed terms.

Happy to answer any questions before you confirm.

[Your name]

Template 2: when a small revision window is still open

Use this when the client has, say, 48 hours to flag anything before the work counts as approved — a common and fair setup if it was agreed in the contract.

Subject: Final files + sign-off window for [Project Name]

Hi [Name],

Here is the final version of [deliverable]: [link]. As agreed, you have until [date] to flag anything that doesn't match the approved scope. After that, I'll treat this as approved and send the final invoice for [amount].

If everything looks good now, you don't need to wait — just reply "approved" and I'll send the invoice right away.

[Your name]

Template 3: after a verbal "it's great, thank you"

Clients often approve work out loud, on a call or in a quick chat message, without realizing that is not quite the same as a sign-off you can point to later. This template turns that moment into a written record without sounding like you doubted them.

Subject: Confirming sign-off on [Project Name]

Hi [Name],

Great to hear you're happy with [deliverable]! Just so I have it in writing for my records, could you reply confirming you approve the final version as delivered? Once I have that, I'll send the final invoice for [amount].

[Your name]

Template 4: following up when sign-off has gone quiet

If a few days pass with no response, the follow-up should stay light and assume a good reason, not pressure the client.

Subject: Checking in: sign-off on [Project Name]

Hi [Name],

Just following up on the final files I sent on [date] — totally understand if you've been busy. Whenever you get a chance, a quick "approved" reply lets me send the final invoice and close this out.

Let me know if you need anything else from me first.

[Your name]

Template 5: when the client wants one more small change before signing off

This is the moment that decides whether the project stays on schedule or quietly reopens. Separate what is a quick fix from what is new work, right in the email.

Subject: Re: Final sign-off on [Project Name]

Hi [Name],

Thanks for the note. [If in scope:] That's a quick fix — I'll have it updated by [date], and we can sign off right after. [If out of scope:] That one falls outside the original scope of [deliverable], so I'd treat it as a separate small addition at [rate]. Let me know if you'd like me to go ahead, or if you're happy to sign off on the current version and handle this as a follow-up later.

[Your name]

What to do once you have the sign-off

The moment you get an "approved" reply, two things should happen immediately: the final invoice goes out, and the approval itself gets saved somewhere you can find it later — not buried in a months-old email thread. A simple log that records the date, the deliverable, and the client's exact words removes the need to scroll back through old messages if a question ever comes up months later, especially on repeat projects where "which version did they actually approve?" gets harder to answer over time.

The Client Approval Log + 50 Client Messages pack includes an Excel log built for exactly this — one row per approval, with the date, deliverable and evidence link — plus ten ready-to-paste messages for approvals and sign-off alone. See it on Gumroad: Client Approval Log + 50 Client Messages.