Client Communication Templates for Freelancers: 14 Copy-Paste Emails
By Zhaosheng Lin, independent developer behind FreelanceMail
Quick answer
Most client problems on a freelance project start as a missing email: no clear next step after the contract, feedback with no deadline, a delay nobody mentioned. Below are 14 short client communication templates for the moments between signing and the last invoice (welcome, asset request, kickoff recap, weekly update, feedback request, a client who goes quiet, your own delay, revisions used up, time off, handoff, check-in, rate increase, saying no, ending the work), plus a communication policy you can paste into your proposal.
When Each Message Goes Out
Getting the client is one set of emails. This article is about the next set: everything between "they said yes" and "the last invoice is paid." If you're looking for first-contact emails, see the freelance cold email templates instead.
Here is when each template in this article is used on a typical project:
| Project moment | Message | Template |
|---|---|---|
| Contract signed | Welcome and what happens next | 1 |
| Same day | What I need from you | 2 |
| After the kickoff call | Written recap of decisions | 3 |
| Every week, same day | Status update | 4 |
| Each draft or milestone | Feedback request with a deadline | 5 |
| Feedback is late | The quiet client | 6 |
| You're going to be late | Your own delay | 7 |
| Revision rounds are used | Revisions used up | 8 |
| You'll be away | Time-off notice | 9 |
| Work is done | Delivery and handoff | 10 |
| A few weeks after launch | Check-in | 11 |
| Raising your prices | Rate increase | 12 |
| A project that doesn't fit | Saying no | 13 |
| The relationship isn't working | Ending the work | 14 |
Two common situations aren't repeated here because they're covered in emailing as a freelancer: handling a scope change and following up on a late invoice.
Set the Rules Once: A Communication Policy
Most of the friction in client communication comes from expectations that were never said out loud. Put a short policy in your proposal or contract, then repeat it in the welcome email. Adjust the details to how you actually work:
How we'll communicate
- Where: email for anything that needs a decision or approval. [Slack / phone] is fine for quick questions, but I'll confirm decisions by email.
- When: I work [Monday–Friday, 9–5 your time zone] and reply within one working day.
- Updates: you'll get a short written update every [Friday].
- Feedback: please collect comments from your team and send them together, by the date in each review email. The quote includes [two] rounds of revisions per deliverable.
- Delays: if feedback or materials arrive late, the delivery date moves by the same amount.
The last line does most of the work. It turns "the client is late" from an argument into a rule you both agreed to.
Template 1 — Welcome and What Happens Next
Send it the day the contract is signed. The client just committed money and is wondering what happens now.
Subject: Welcome — next steps for [project]
Hi [Name],
Thanks for signing. I'm looking forward to working on [project] with you.
Here's what happens next:
1. [Date]: kickoff call ([link to book] or [time we agreed]).
2. [Date]: [first deliverable, e.g. homepage wireframe] for your review.
3. [Date]: [final delivery].
To start on time, I need a few things from you by [date]. I'll send that list separately so it's easy to find.
How we'll work: I reply within one working day, send an update every [Friday], and confirm any decisions by email.
[Your name]
Template 2 — What I Need From You
Keep the asset request in its own email with a clear subject line. Clients forward it to whoever has the files.
Subject: [Project]: what I need from you by [date]
Hi [Name],
Here's everything I need to get started:
- [Logo files, ideally SVG or high-resolution PNG]
- [Access to the website / hosting / analytics. Please add me as a user at [email] rather than sending passwords]
- [Existing copy or the brand guidelines document]
- [Name of the one person who will give final approval]
If anything on the list doesn't exist yet, just tell me and we'll work around it.
[Your name]
Asking for user access instead of passwords protects both of you, and it's easy to remove at the end of the project.
Template 3 — Kickoff Call Recap
Anything decided on a call should exist in writing. Send this within a day of the call.
Subject: Recap: [project] kickoff, [date]
Hi [Name],
Thanks for the call. Here's what we agreed, so we both have it in writing:
- Goal: [one sentence]
- Decisions: [e.g. keep the current colors, drop the blog page from phase 1]
- Open questions: [e.g. which of the two taglines to use. You'll confirm by Wednesday]
- Next deliverable: [what], on [date]
If I've misunderstood anything, reply and I'll correct it.
[Your name]
Template 4 — Weekly Status Update
The same four headings every week. It takes a few minutes, and it means the client almost never has to ask "how's it going?"
Subject: [Project] update — week of [date]
Hi [Name],
Done this week: [1–3 bullet points]
Next week: [1–3 bullet points]
Waiting on you: [specific item and the date you need it, or "nothing right now"]
On track? Yes. [Or: one sentence on any risk to the date.]
[Your name]
"Waiting on you" is the most important line. It puts open requests in front of the client every week without you having to chase them.
Template 5 — Feedback Request With a Deadline
"Let me know what you think" invites slow, scattered feedback. Ask for specific feedback by a specific date, from one person.
Subject: [Deliverable] ready for review — feedback by [date]
Hi [Name],
[Deliverable] is ready: [link].
The most useful feedback right now is on [e.g. the structure and the headline, not the final images, which are placeholders].
Could you send consolidated comments from your team by [date]? That keeps us on track for [next milestone]. This is review round [1] of [2] included in the project.
[Your name]
Template 6 — The Quiet Client
Feedback or materials are late. Don't send "just checking in" again. Name the one thing you need, what it blocks, and what you'll do by default.
Subject: [Project]: need [item] to keep [date]
Hi [Name],
I haven't received [feedback on the homepage draft / the product photos] yet, and it's the one thing holding up [next step].
If I have it by [date], we're still on track for [delivery date]. If not, I'll [pause work on this and move the delivery date to [new date] / go ahead with [default choice], which we can change later].
Either way is fine, I just want the timeline to be clear for both of us.
[Your name]
Giving a default choice ("I'll go ahead with version A") often gets a reply faster than a question, because silence now has a visible result.
Template 7 — Your Own Delay
When you're the one who's late, tell them early. The day before the deadline is already late.
Subject: [Project]: new date for [deliverable]
Hi [Name],
I need to move [deliverable] from [original date] to [new date]. [One honest sentence on why, e.g. the data migration took longer than I estimated.]
To keep things moving, I can send you [partial deliverable, e.g. the finished homepage and the first two inner pages] on the original date.
The final launch date [stays the same / moves to [date]].
[Your name]
One sentence of explanation is enough. A long apology makes a small delay sound like a big problem.
Template 8 — Revisions Used Up
The client wants more changes after the rounds included in the quote. Be friendly and give them a way to continue.
Subject: Re: [Deliverable] changes
Hi [Name],
Thanks for the notes. We've now used the [two] review rounds included for [deliverable], so I want to be upfront before I start.
Two options:
1. I make these changes as an extra round for [price], ready by [date].
2. We pick the [two or three] most important changes and I include them as a final tweak at no charge.
Which works better for you?
[Your name]
Option 2 is optional. Use it if the changes are small and the relationship is worth more than the hour.
Template 9 — Time-Off Notice
Send it at least two weeks ahead, and again a few days before you leave.
Subject: Heads-up: I'm away [dates]
Hi [Name],
A quick heads-up that I'll be away from [date] to [date] and won't be checking email.
Before I go, I'll finish [items]. [Deliverable] is still on track for [date] / will arrive on [adjusted date].
If anything urgent comes up while I'm away, [what to do, e.g. "the site host's support line is [link]" or "[name] can help"].
[Your name]
Template 10 — Delivery and Handoff
Make the end of the project clear: what's done, where everything is, and what's still open.
Subject: [Project] is complete — files, access and next steps
Hi [Name],
[Project] is finished. Here's everything in one place:
- Final files: [link]
- Logins and access: [what you're handing over; remove your own access or say when you will]
- How to [update / maintain] it: [link to a short guide or video]
- Final invoice: #[number], attached, due [date]
I'll keep an eye out for any issues over the next [two weeks] at no charge. After that, I'm happy to help with changes at [rate].
Thanks for working with me on this.
[Your name]
Template 11 — Check-In After Launch
A few weeks after delivery, check how it's going. This is a natural point to ask for a testimonial if they're happy.
Subject: How is [project] working out?
Hi [Name],
It's been a few weeks since [project] went live. How is it working for you? Anything that's confusing or broken?
If you're happy with it, would you be willing to write two or three sentences I could share on my site? No pressure either way.
[Your name]
For a longer version focused on referrals, see the testimonial template in emailing as a freelancer. For reconnecting with someone months later, use the past-client template in freelance cold email templates.
Template 12 — Rate Increase
Tell existing clients in writing, with notice. State the new rate and date; don't over-justify.
Subject: My rates from [date]
Hi [Name],
I wanted to let you know in advance that from [date], my rate for new work will be [new rate] (currently [old rate]).
Anything we've already agreed, including [current project], stays at the current rate. If you'd like to book work before [date] at the current rate, just let me know.
Thanks for the work together so far. I'm looking forward to more.
[Your name]
Template 13 — Saying No to a Project
Declining well keeps the door open. Be brief, be clear, and if you can, point them somewhere useful.
Subject: Re: [Project]
Hi [Name],
Thanks for thinking of me for this. [It's outside what I do / I don't have the capacity to do it well before [date]], so I'm going to pass on this one.
[Optional: You might want to talk to [name or type of specialist].]
I'd be glad to help with [the kind of work you do want] in the future.
[Your name]
Template 14 — Ending the Work
Sometimes a client relationship isn't working: constant scope changes, late payment, or a poor fit. End it in writing, calmly, without listing grievances.
Subject: Wrapping up our work together
Hi [Name],
After [current project / this month], I won't be able to continue working on [type of work] for [Company].
To make the handover smooth, I'll [finish X by [date] / deliver all files and documentation by [date]] and transfer [access / accounts] to you. The final invoice will be #[number].
Thanks for the work together, and I wish you all the best with [project or business].
[Your name]
Check your contract's notice period before sending, and give at least that much.
Five Rules That Apply to Every Template
- Use dates, not "soon." "By Thursday the 14th" can be planned around; "soon" can't.
- One ask per email. If you need two decisions, number them so both get answered.
- Say what happens if there's no reply. It replaces nagging with a plan.
- Put decisions in writing. A chat message or call is fine for discussion, but confirm the outcome by email so there's one record to search later.
- Keep the subject line findable. Start with the project name. Your client has many other emails.
Where FreelanceMail Fits
These templates are for clients you already have. FreelanceMail helps with the step before: finding them. Paste a prospect's website and describe your service, and it reads their homepage and about page, then drafts a first cold email and two follow-ups about something specific on their site. You can try one on the homepage without signing up.
Frequently asked questions
What should a freelancer send after a client signs the contract?
A welcome email the same day: thank them, say what happens next and when, list exactly what you need from them with a date, and explain how you'll communicate (where, how often, how fast you reply). It sets the rules before the first misunderstanding.
How often should a freelancer update a client?
Pick a fixed rhythm and keep it, usually once a week on the same day. A short update with what's done, what's next and what you're waiting on is enough. A predictable update means the client doesn't have to ask.
What do I do when a client stops responding during a project?
Send a short note that names the one thing you need, explains what it blocks, and says what you'll do if you don't hear back by a specific date (for example, pause and move the deadline). Stating the consequence calmly is more effective than repeated reminders.
How do I tell a client I'm going to miss a deadline?
Tell them as soon as you know, not on the due date. Give the new date, one sentence on why, and what you can deliver on the original date if anything. Don't over-explain or over-apologize.
How should a freelancer announce a rate increase?
Give existing clients notice in writing, state the new rate and the date it starts, and say what stays the same. You don't need to justify it at length. A month's notice is a reasonable minimum, and it's fair to honor quotes you've already agreed.
Write the first draft from their website
Paste a prospect's website and FreelanceMail reads their homepage and about page, then writes a first email plus two follow-ups for your service. One free try, no sign-up.
Try it on a prospect's site