Client approval email template: 7 messages that get a yes

Most approval requests fail for a boring reason: they ask the client to think. "Let me know what you think" invites a long, slow reply, or no reply at all. A request that works tells the client exactly what they are approving, shows them where to look, and gives them a one-word way to say yes.

Below are seven client approval email templates for the moments freelancers meet most often, from a first draft to a final hand-off. Each one is short enough to paste into email, Slack or a project tool. Replace the brackets with your details.

What every approval email needs

Before the templates, the pattern. Every message below follows the same five lines:

1. What you are sending and which version it is.
2. Where to find it.
3. What exactly you need approved (not "thoughts", but a decision).
4. How to say yes: "Reply Approved".
5. When you need the answer and what happens if it does not arrive.

That fifth line is the one most freelancers skip, and it is the one that makes the difference between a two-hour reply and a two-week one.

1. Approval of a first draft or concept

Use this when you want direction confirmed before investing more time.

Subject: [Project]: concept v1 for approval

Hi [Name],

Attached is the first concept for [deliverable] ([link]). It covers [what it covers] and follows the brief from [date].

At this stage I need a decision on the direction, not the details. If the overall approach is right, please reply "Approved" and I will move on to [next step]. If not, tell me what feels off and I will adjust before going further.

I would like to hear back by [date] to keep the [deadline] on track.

Asking for a direction decision, and saying so, stops the client from spending their reply on typo-level comments.

2. Approval of a design or layout

Designs attract the most opinions, so narrow the question.

Subject: [Project]: design for approval, round [2]

Hi [Name],

Here is the updated design with your round-one feedback applied: [link]. The changes are listed in the file under "What changed".

Please check the three items you asked about: [item], [item] and [item]. If they look right, reply "Approved" and I will start [production / development / final files]. Changes after this point are still possible, but this is the last included revision round, so it is worth gathering any remaining comments in one message.

Could you confirm by [date]?

Naming the revision round, and the fact that it is the last included one, is not a threat. It is information the client needs to decide how carefully to review.

3. Approval of a scope change or an extra

When the client asks for something outside the agreement, turn their request into an approval.

Subject: [Project]: adding [request], please confirm

Hi [Name],

Thanks for the request to add [request]. It was not part of the original scope, so here is what it would take:

- Extra cost: [price]

- Extra time: [days], moving the delivery date to [new date]

If that works for you, reply "Approved" and I will include it. If you would rather keep the original plan and schedule [request] as a second phase, that is fine too. I will continue with the agreed work either way.

Writing the price and the new date in two bullets makes the decision easy to make and easy to find later.

4. Approval of a quote or proposal

A clear approval request for a quote avoids the "I thought we agreed" problem before the project even starts.

Subject: Proposal for [project]: approval

Hi [Name],

Attached is the proposal for [project]: [link]. It includes the deliverables, [number] revision rounds, the timeline and the price of [amount], with [deposit] due at the start.

If you are happy to proceed, please reply "Approved" and I will send the invoice for the deposit and book the start date of [date]. If you would like to change anything, tell me and I will update the proposal.

The dates in the proposal are held until [date].

Holding the dates for a limited time gives the client a reason to answer this week rather than next month.

5. Approval of a milestone before the next payment

Milestone approvals keep cash flow and progress tied together.

Subject: [Project]: milestone [2] complete, approval and next invoice

Hi [Name],

Milestone [2] is complete: [what was delivered], available at [link]. It matches the plan we agreed on [date].

Please review and reply "Approved" by [date]. Once approved, I will send the milestone invoice and start milestone [3] on [date]. If you find anything that does not match the plan, let me know and I will fix it before invoicing.

Connecting approval to the start of the next phase is the most natural deadline there is. The client wants the next phase to start, so they approve.

6. Final approval and sign-off

The last approval should list everything so there is no "we also agreed on" later.

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

Hi [Name],

The project is complete. Delivered, as agreed on [date]:

1. [Deliverable]

2. [Deliverable]

3. [Deliverable]

Everything is in [link]. Please reply "Approved" by [date] to close the project. If I do not hear from you by then, I will consider the work accepted and send the final invoice on [date]. Any later changes will be quoted as new work.

Thank you for a smooth project.

For a longer version of this message, with variants for design, development and writing work, see our guide to the project sign-off email.

7. Follow-up when the approval has not arrived

Use this three or four days after any of the messages above.

Subject: Re: [original subject]

Hi [Name],

A quick nudge on the approval for [item]. If everything looks right, a one-word "Approved" is all I need. If something is holding you back, tell me and I will sort it.

I have kept [date] in the plan so far; if I do not hear back by [date], I will [pause the next step / proceed as described / send the invoice as planned].

Keep follow-ups to one reminder per request. A second nudge can go to a different channel, a short call or a chat message, rather than another email.

Small changes that get faster approvals

Ask for a word, not a paragraph. "Reply Approved" is easy. "Let me know your thoughts" is a homework assignment.

Send one request per email. Three decisions in one message means the client answers the easiest one and forgets the rest.

Put the link where the eye lands. The first or second line, not buried after the explanation.

State the consequence of silence. "If I do not hear back by Friday I will proceed as described" respects the client's time and protects yours.

Record the answer. When the "Approved" arrives, note the date, the version and who sent it in one place. A dated log turns later disagreements into a quick lookup instead of an argument.

Want all of these ready to paste?

The Client Approval Log + 50 Client Messages kit contains these seven messages and 43 more, grouped by situation, together with an Excel approval log for recording every yes with a date and a link to the evidence. It is $9 on Gumroad: Client Approval Log + 50 Client Messages.