7 copy-paste email templates that keep clients informed, prevent the "just checking in" email, and protect your agency when things shift.
No email required·Copy, adapt, and use today·Works with any stack
Why most agency communication breaks down
Clients don't send "where are we?" emails because they're difficult — they send them because they have no signal. A weekly 5-line email eliminates that anxiety. A clear scope-change template prevents scope creep from becoming a dispute. A delay notice sent before the deadline lands as professionalism; sent after, it reads as an excuse. These templates are designed to keep the client relationship on your terms.
Template 1
Weekly Project Status Update
When to send: Every Friday, or at a fixed day/time agreed in the kickoff. 5 minutes to fill in. Client reads it in 60 seconds.
Subject line{{Project Name}} — Week {{N}} Update
BodyHi {{First Name}},
Here's a quick update on {{Project Name}} for the week ending {{Date}}.
✅ Completed this week
— {{Task or deliverable 1}}
— {{Task or deliverable 2}}
— {{Task or deliverable 3}}
🔜 Next week's focus
— {{Priority task 1}}
— {{Priority task 2}}
⏳ Open items / waiting on you
— {{Item you're blocked on, if any — or "Nothing — we're on track."}}
Overall status: On track / Minor delay / At risk (pick one)
Expected delivery date is still {{Date}}.
Let me know if you have any questions.
{{Your name}}
Pro tip: Set a recurring calendar block every Friday at 4pm to send this. The consistency matters more than the content. Clients who receive 10 weekly updates in a row rarely ask "where are we?"
Template 2
Waiting on Client — Unblocking Email
When to send: When you need something from the client to continue — access, content, approvals, feedback. Send as soon as you identify the block; don't wait for the Friday update.
Subject lineAction needed: {{What you need}} for {{Project Name}}
BodyHi {{First Name}},
We're ready to move forward on {{specific phase or task}}, and we need the following from your side to proceed:
📋 What we need
1. {{Item 1 — be specific, e.g. "Admin access to your Google Analytics property"}}
2. {{Item 2 — e.g. "Final copy for the About page (current draft is in the shared folder)"}}
3. {{Item 3 — or remove this line}}
📅 To stay on the current timeline, we'd need this by {{Date — give a specific date, not "ASAP"}}.
If that date won't work, let me know and we can adjust the schedule together. If there's anything blocking your side that we should know about, happy to jump on a quick call.
{{Your name}}
Important: Always give a specific date. "As soon as possible" creates ambiguity and puts you in a passive position. A date like "by Thursday EOD" gives the client a clear target and gives you a documented request if the deadline slips.
Template 3
Scope Change Request
When to send: Before doing any out-of-scope work. This is the template that protects your margin. One email prevents three invoice disputes.
BodyHi {{First Name}},
Following our conversation on {{Date/channel}}, I wanted to confirm in writing the additional work you've requested.
📋 Requested addition
{{Describe the new work clearly — what it is, not just what the client said}}
📐 What was originally in scope
{{Remind them what the original brief covered}}
⚡ Impact
— Additional time: {{X hours / days}}
— Additional cost: {{€X / $X}} ({{based on our standard rate of X/hr}})
— Timeline: This will push the current delivery date from {{Original date}} to {{New estimated date}}
If you'd like to proceed, please confirm by replying "Yes, go ahead" or let me know if you'd like to discuss.
We'll put work on hold for this addition until we have your confirmation in writing.
{{Your name}}
Non-negotiable habit: Never start out-of-scope work before written confirmation. "They seemed fine with it in the meeting" is not confirmation. This template creates the paper trail.
Template 4
Delay Notice
When to send: As soon as you know a deadline will slip — ideally 48–72 hours before it hits, not after. Early notification lands as professionalism. Late notification lands as an excuse.
Subject line{{Project Name}} — timeline update
BodyHi {{First Name}},
I want to flag a timeline update before the deadline arrives.
We're working toward the {{Original date}} delivery, but {{brief reason — be honest, be short: e.g. "the API integration is taking longer than estimated" or "we're waiting on the third-party vendor to respond"}}. We expect this will push delivery by approximately {{X days / weeks}}.
Updated timeline
— {{Milestone 1}}: still on track for {{Date}}
— {{Milestone 2}}: now expected {{New date}}
— Final delivery: {{Original date}} → {{New date}}
What we're doing to recover
{{One or two concrete steps — e.g. "We've brought in an additional developer for this sprint" or "We'll skip the internal review cycle to save 2 days"}}
I'll send a full update on Friday. Let me know if this creates any downstream issues on your side and we can talk through options.
Apologies for the inconvenience — I'd rather you hear this from us proactively than find out at the deadline.
{{Your name}}
Key framing: Own it briefly, explain it briefly, then immediately pivot to the path forward. Clients can handle delays — what they can't handle is silence.
Template 5
Milestone Complete / Deliverable Handoff
When to send: Every time you deliver a significant deliverable or hit a project milestone. This is also when you get formal sign-off — which protects you from "that's not what we agreed" later.
BodyHi {{First Name}},
We've completed {{Milestone name}} for {{Project Name}}.
📦 What we've delivered
— {{Deliverable 1 — include link if applicable}}
— {{Deliverable 2}}
— {{Deliverable 3}}
Access / location
Everything is in {{shared folder / staging URL / drive link}}.
What we need from you
Please review and confirm by {{Date — give a specific date}}.
Once you confirm acceptance, we'll move into {{Next phase}}.
If you have revision requests, please consolidate them into one feedback email or use the comments in the shared doc so we can action them cleanly.
Looking forward to your feedback.
{{Your name}}
Why sign-off matters: "Please confirm acceptance" creates a documented milestone approval. Without it, the project never formally completes a phase — and clients revisit "completed" work indefinitely.
Template 6
Project Completion and Handoff
When to send: On the final delivery. This email closes the project, documents what was delivered, sets expectations for what happens next, and opens the door for the ongoing relationship.
Subject line{{Project Name}} — complete ✓
BodyHi {{First Name}},
{{Project Name}} is complete. It's been great working with you on this.
Here's a summary of everything we delivered:
✅ Delivered
— {{Deliverable 1}}
— {{Deliverable 2}}
— {{Deliverable 3}}
🔑 Access and assets
All final files are in {{location}}. Credentials and access notes are in {{location / password manager / separate email}}.
📝 A few things to know going forward
— {{Anything they need to maintain, e.g. "The CMS requires a monthly plugin update — we recommend setting a calendar reminder"}}
— {{Warranty / support terms if applicable, e.g. "We'll fix any bugs arising from our work in the first 30 days at no charge"}}
💬 One small ask
If {{Project Name}} went well, a quick Google review or LinkedIn recommendation would mean a lot to us. No pressure — here's the link if you'd like to: {{link}}.
We'd love to work together again. If you have future projects, I'm always happy to have a conversation.
{{Your name}}
Template 7
90-Day Re-engagement Email
When to send: 90 days after project completion. This is the single highest-ROI email most agencies never send. Previous clients convert at 3–5× the rate of cold leads.
Subject lineChecking in — {{Project Name}} (3 months on)
BodyHi {{First Name}},
It's been about three months since we wrapped {{Project Name}} — just wanted to check in and see how things are going.
How is {{the website / the campaign / the system / what you built}} performing? Any early results or surprises?
We've been working on a few similar projects since then and have picked up some things that might be useful for you. If you'd like a quick 20-minute call to compare notes, happy to set one up.
Also — if you know any other {{agency owner / founder / marketing director}} who's dealing with {{the problem you solved}}, we'd love an introduction.
Either way, hope things are going well.
{{Your name}}
Timing note: Set a calendar reminder on the day you send the project completion email to ping yourself in 90 days. Put it in your project management tool as a task. This is a discipline problem, not a template problem — having the template ready removes the friction.
Want the complete system?
These 7 templates are part of Agency Onboarding OS — 38 practical docs covering intake, access collection, SOPs, AI automation playbooks, kickoff structure, and ongoing client management.