Why the weekly update is the most important email you send
The weekly client update is not just communication — it's relationship maintenance. When a client hears from you proactively, they stop worrying. When they stop worrying, they stop sending "just checking in" emails. When those stop, you can focus on the work instead of managing anxiety.
The problem is that the weekly update often gets deprioritized. It's not billable. It's not part of the deliverable. And after a week of real work, the last thing you want to do is write a summary of it. So it doesn't get sent. The client gets anxious. The relationship suffers.
Briefly makes the weekly update a 30-second task instead of a 30-minute one.
What makes a great weekly status update
- What got done this week. Specific, concrete, not vague ("worked on the project").
- What's coming next. What should the client expect to see or hear from you next.
- Any decisions needed. If you're waiting on client input, say so clearly.
- Status indicator. Are you on track? Behind? Ahead? Say it directly.
- Confidence signal. The tone should make the client feel confident, not anxious.
Example: weekly status update
Hi Laura,
Here's a quick update on the E-commerce Site Redesign for the week of April 21–25.
Completed this week: Homepage mockup finalized and sent for review Thursday afternoon. Mobile navigation design completed and included in the same file. Both sections are ahead of the original schedule.
Waiting on: Your feedback on the homepage mockup before proceeding to product listing pages. If you can share thoughts by Monday, I can maintain the current pace for the May 10th launch.
Next week: Product listing page layouts and the cart/checkout flow — provided homepage feedback comes in as planned.
Overall, we're on track. Let me know if you have any questions.
Best,
Sam
How often should you send client updates?
For active projects, weekly is the standard. For projects with significant milestones, updates at each milestone make sense. The key principle: the client should never have to wonder what's happening.
If a week passes without meaningful progress, still send a brief note. "I'm heads-down on the backend integration this week — will have a more substantial update next Friday" is better than silence.
The difference between a good and bad weekly update
Bad update
"Hi, just a quick update — I've been working on the project this week. Things are progressing. I'll have more to share next week. Let me know if you have questions!"
This tells the client nothing. It reads as a placeholder. It increases anxiety.
Good update
Specific completed items. Specific next steps. Clear ask if one exists. Confident, brief, professional. The client reads it and thinks: they're on top of this.
Frequently asked questions
My notes are really rough — will Briefly still work?
Yes. Briefly is designed for rough notes. Bullet points, incomplete sentences, abbreviations — all fine. The more specific the details, the better the output, but messy input is expected.
Can I use this for monthly reports too?
Yes — Briefly also has a dedicated monthly summary type. The full tool at briefly-meridian.fly.dev lets you choose from 8 email types including weekly updates, monthly summaries, milestone reports, and more.
Is there a limit on how many updates I can generate?
The free tier gives you 5 emails per day with no account required. Briefly Pro is $9/month for unlimited emails across all 8 types.