How to Write a Weekly Client Update Email (That Clients Actually Read)
Most freelancers know they should send weekly client updates. Most don't. Here's exactly how to write one — what to include, what to cut, how long it should be, and how to make it take 5 minutes instead of 45.
What to include in every weekly client update
Every good weekly update answers three questions the client is silently asking:
- "Is anything happening?" — Did work actually get done this week?
- "Where are we heading?" — What comes next, and is it on track?
- "Is there anything I need to do?" — Are there decisions, approvals, or blockers?
You don't need to answer these at length. A good update does it in 150–200 words.
Essential elements:
- What you completed this week — specific, outcome-focused
- What you're working on next — gives the client a sense of forward motion
- Any blockers or things you need from them — be explicit
Optional elements (add when relevant):
- Metrics or results (if applicable — traffic, conversions, open rates)
- A note on timeline or milestone status
- A brief observation or insight about what you're seeing
What to leave out:
- Apologies for not sending updates (just send it)
- Excessive caveats ("I think maybe I might have...")
- Long explanations of why things are the way they are
- Technical jargon your client doesn't understand
- Everything that isn't relevant to the client's goals
The 4-part structure that works
After reviewing hundreds of effective client updates, here's the structure that works consistently:
Brief greeting
One line. "Hi [Name]," and a quick warm opener. "Hope you had a good week" is fine. Keep it short — clients aren't reading your email to enjoy your opener.
What you completed
2–5 specific items. Bullet points work well here. Start with the most important thing. Use plain language — translate technical work into outcomes the client can understand.
Instead of: "Refactored the authentication middleware to implement JWT token refresh logic"
Write: "Fixed the login issue that was requiring users to sign in twice"
What's next
One or two sentences. This is the "forward motion" signal clients need. Even if you're not 100% sure of next steps, saying "I'm planning to [X] next week" is enough.
Any asks or blockers
If you need something from the client — approval, feedback, assets, a decision — say so clearly here. Make it impossible to miss. "I'll need the final copy by Wednesday to stay on schedule" is clear. "It would be great if you could maybe review..." is not.
Getting the tone right
The best weekly updates feel like a note from someone who genuinely cares about the project — not a corporate report, and not an essay.
Professional but warm
You are a person, not a contractor filing reports. Write like you're updating a colleague you respect. Contractions are fine. "I think this is looking strong" is better than "The deliverable appears to meet the specified criteria."
Confident, not apologetic
Don't over-apologize or under-claim your work. "I've been making solid progress on the mockups this week — here's where we are" is better than "I've been trying to work on some mockup stuff but it's been a busy week."
You did the work. Own it.
Match the client's communication style
If your client sends short, casual messages, your update can be more casual. If they're formal, err toward professional. The goal is to feel consistent with the relationship, not jarring.
Avoid the "I've been so busy" framing
Telling clients how busy you are doesn't build confidence. "This was a heavy week but I still finished X" actually makes clients slightly anxious. Just report what got done.
How long should a weekly client update be?
Shorter than you think. The target is 150–250 words.
Here's why: clients have other emails to read. They're reading your update on their phone. They want to confirm everything is fine, see what happened, and move on. A 400-word update doesn't make them feel more informed — it makes them feel like they have homework.
5 common mistakes in weekly client updates
1. Writing it from memory on Friday afternoon
If you try to reconstruct your entire week at 4pm Friday, you will forget important work, feel stressed, and write a vague update. The fix: keep a simple running note throughout the week. Even one bullet point per day makes Friday trivial.
2. Listing tasks, not outcomes
"Had meeting with designer, reviewed mockups, sent feedback" is a task list. "The new homepage direction is locked in — the designer is moving into hi-fi this week" is an outcome. Clients care about where the project is, not your calendar.
3. Burying the ask
If you need something from the client, don't hide it in paragraph three. Put it at the end with clear language: "Before I can proceed with [X], I'll need [specific thing] from you." Buried asks get missed, causing delays that then look like your fault.
4. Going silent during slow weeks
The update you don't send is worse than a slow-week update. "This week was lighter — I spent most of it on [background work] and will be back to full pace next week" maintains the relationship. Silence makes clients wonder.
5. Being inconsistent
Sending 3 updates in a row, then nothing for two weeks, is worse than no system at all. Clients notice the gap more acutely when they'd been getting regular updates. Consistency builds the expectation that everything is under control.
Real examples of good weekly client update emails
Hi Sarah,
Quick update on the app this week:
I finished the user onboarding flow — it's now live on staging and ready for your review. I also resolved the intermittent login bug that a few users had reported, and added email verification to the signup process as we discussed.
Next week I'm planning to tackle the notification settings panel and start on the dashboard performance improvements.
One thing I need from you: can you confirm the copy for the onboarding screens? I have placeholder text in right now and want to finalize it before we move to production. Any time before Wednesday works.
Best,
Alex
Hi Marcus,
Good progress this week — I completed the three initial logo concepts and refined the color palette based on the feedback from our last call. The direction is feeling strong.
I'm going to develop the strongest concept further next week, with some variations for different use cases (website, social, print).
No asks from my side — just wanted to keep you in the loop. Feel free to review the concepts in the shared Figma file anytime.
Best,
Jordan
How to write a weekly client update in 5 minutes
The reason most freelancers skip weekly updates isn't laziness — it's the blank page. Here's how to make it actually take 5 minutes:
-
Log notes as you work, not at the end.
Open a note on your phone or a quick text file. Every time you finish a task, write one line: "finished homepage mockups." Takes 10 seconds. By Friday you have a list to work from.
-
Group by client, not by day.
Your notes say what you did; sort them by which client they belong to. Now you have a draft update per client.
-
Use a template or a tool.
You don't need to write from scratch every time. The structure is always the same: what happened, what's next, any asks. Fill it in with your notes.
-
Send by 5pm Friday, not after.
Set a recurring calendar event. "5pm Friday — send client updates." Treat it as a deliverable, not an optional task.
The even faster way: Enter your rough notes into WorkPulse. It generates a professional, personalized email addressed to each client — subject line included. The whole process takes about 60 seconds per client.
Generate your next weekly update in 60 seconds
Add your client name, paste your rough work notes, click Generate. WorkPulse writes a real, professional, personalized email. No account. No credit card.