Project sign-off email template for freelancers

The last email of a project matters more than most freelancers think. It is the moment the work officially becomes "done", the invoice becomes due, and any later request becomes a new request rather than an unpaid fix. Without a clear sign-off, projects drift: a month later the client asks for "just a small tweak", and you cannot point to the day the work was accepted.

A sign-off email fixes that in five minutes. Below is a template you can paste, three short variants for common types of work, and the follow-ups you need when the client does not reply or asks for one more thing.

What a sign-off email has to do

A good sign-off email does four jobs at once:

• States that the agreed deliverables are complete and lists them.
• Asks the client for one explicit confirmation ("Please reply 'Approved'").
• Sets a deadline after which the project is considered accepted.
• Explains what happens next: handover, final invoice, and how future changes are handled.

If your email does those four things, it works. Everything else is tone.

The main template

Replace the brackets. Keep the list short and factual: it should match the scope you agreed at the start.

Subject: [Project name]: final delivery and sign-off

Hi [Name],

The [project name] is complete. Here is what has been delivered, as agreed on [date of agreement]:

1. [Deliverable 1, e.g. Homepage, About and Contact pages, responsive]

2. [Deliverable 2, e.g. Source files in Figma]

3. [Deliverable 3, e.g. Two rounds of revisions, both completed]

You can review everything here: [link].

To close the project, please reply to this email with "Approved" by [date, 5 business days out]. If I do not hear back by then, I will treat the project as accepted and send the final invoice on [date].

Any changes after sign-off are welcome and will be quoted separately as a new piece of work.

Thank you for the smooth collaboration. It was a pleasure working on this.

Best,

[Your name]

Three details make this template work. The dated list ties the delivery to the original agreement. The explicit "reply with Approved" gives the client one tiny action instead of an open question. The acceptance date stops a silent client from freezing your payment.

Variant for design work

Designers often hand over files in several formats, so the list should name them.

Hi [Name],

The [brand identity / landing page design] is complete. Delivered today:

1. Final logo files: SVG, PNG (transparent), PDF, in colour, black and white

2. Brand sheet with colours, typography and spacing rules

3. Editable source file (Figma link, edit access granted to [email])

Please check that the files open correctly on your side and reply "Approved" by [date]. After that date the project is considered accepted and the final invoice follows.

If you need new formats or additional assets later, just ask and I will send a quick quote.

Variant for development work

For code, the sign-off should mention where the code lives and what "working" means.

Hi [Name],

The [feature / website / app] is deployed to [production URL] and the code is in [repository]. Delivered:

1. [Feature A], tested on [browsers or devices]

2. [Feature B], including the admin page

3. Documentation for deployment and environment variables ([link])

Please run through the checklist we agreed ([link]) and reply "Approved" by [date]. Bugs found within [14] days that are covered by the original scope will be fixed at no charge. New features or changes to the agreed behaviour will be quoted separately.

Mentioning a short bug-fix window is optional but useful. It reassures the client, and it draws a line between "a bug in what we agreed" and "a new idea".

Variant for writing and content work

Writers get the most "small tweaks" after delivery, so the sign-off should name the revision rounds that were used.

Hi [Name],

The [article series / website copy / ebook] is complete. Delivered:

1. [Number] pieces, final versions in the shared folder ([link])

2. Two rounds of revisions, both incorporated

3. Meta descriptions and suggested titles for each piece

Please reply "Approved" by [date] so I can close the project and send the final invoice. Further edits after sign-off are billed at [rate] or as a new project, whichever suits you better.

When the client does not reply

Silence after a final delivery is common. It usually means the client is busy, not unhappy. Send one gentle reminder two or three days before your acceptance date.

Hi [Name],

A quick reminder that the sign-off for [project] is due on [date]. If everything looks good, a one-word "Approved" is enough. If anything needs attention, tell me and I will take a look.

If I do not hear back by [date], I will consider the project accepted as described in my previous email and send the final invoice.

If the acceptance date passes with no reply, send the invoice with a short note that refers back to the sign-off email. You have given fair warning twice, in writing. That record is what protects you.

When the client asks for "one more small change"

This is the moment most sign-offs fall apart. The right answer depends on whether the request is inside the original scope.

If it is a genuine fix to something that was agreed, do it, and say so:

Thanks for catching that. It is part of the agreed scope, so I will fix it today and resend the sign-off email once it is done.

If it is new work, be friendly and specific:

Happy to help with that. It was not part of the original scope, so I will send a quick quote. In the meantime, could you confirm sign-off on the delivered work so I can close this phase and invoice it? The new request can be its own small project.

Separating the two keeps the payment for finished work moving while the new request gets its own price.

Three habits that make sign-off painless

Say what sign-off means at the start. Put a sentence in your proposal: "The project is considered accepted when you confirm in writing, or five business days after final delivery." Then the final email is not a surprise.

Keep a dated record. Note in one place when you sent each deliverable, who approved it and in which message. A simple spreadsheet is enough. When a question comes up months later, you can answer with dates rather than memory.

Use the same wording every time. Clients who work with you more than once learn the rhythm: delivery, "Approved", invoice. The process itself becomes part of why they trust you.

Want the templates ready to copy?

The Client Approval Log + 50 Client Messages kit includes this sign-off email together with 49 other short messages for approvals, scope creep, extra revisions and late payments, plus an Excel log for recording every approval with a date and a link to the evidence. It is $9 on Gumroad: Client Approval Log + 50 Client Messages.