A weekly status email is not a performance report and it is not a list of everything you touched. Done well, it is a small operating system for a client relationship: it shows what moved, what needs a decision, and what happens next.
This matters because clients often experience your work indirectly. You may have cleaned up a process, prepared a batch of drafts, or chased down missing information, but they mostly see whether the right things are clear at the right time. A short, consistent update reduces “just checking in” messages and gives both people a chance to correct course before a small blocker becomes a missed deadline.
Here is a practical structure you can adapt for administrative support, content operations, inbox management, or recurring virtual assistant work.
Decide what the email must accomplish
Before writing a template, define the three questions your client needs answered:
- What was completed or advanced?
- What is blocked, waiting, or at risk?
- What will happen next, and what do you need from me?
Everything else is optional. A weekly email should not become a diary of your workday. If a detail does not help the client understand progress, make a decision, or prepare for the next step, leave it in your internal notes.
The best send time depends on the client’s workweek and time zone. Pick a repeatable window—such as Friday morning or Monday afternoon—and put it on your recurring task list. Consistency is more useful than sending an impressive update only when you remember.
Use a four-part structure
1. A one-sentence headline
Open with a plain-language summary of the week. For example:
This week, the inbox cleanup is complete, the April newsletter is in review, and the vendor spreadsheet is waiting on two missing invoices.
This gives the reader the status before the detail. It also forces you to distinguish finished work from work that merely received attention.
2. Completed and progressed
Use bullets, not a long paragraph. Group related items and link to the relevant document or project board when appropriate.
- Reconciled the shared inbox through Thursday and labeled follow-ups.
- Drafted the customer FAQ updates in the review document.
- Scheduled the approved social posts for next week.
- Updated the recurring tasks and noted two steps that can be removed.
Use verbs that describe an observable result: drafted, reviewed, scheduled, organized, documented, sent, or flagged. Avoid vague phrases such as “worked on several things” or “made good progress.” If an item is only partly done, say what is done and what remains.
3. Waiting, decisions, and risks
This is the section that makes a status email valuable. A blocker should include enough context for the client to respond without searching through old messages.
A useful format is:
- Item: The newsletter cannot be scheduled yet.
- Waiting on: Final link and image approval.
- Needed by: Wednesday to keep Friday’s send date.
- If delayed: The send date will move; no content has been published.
Do not label every inconvenience a risk. Reserve “at risk” for something that could affect a date, quality requirement, access, or agreed scope. A calm, specific note is more helpful than an alarmist one.
You can also separate decisions from requests. “Please approve the subject line” is a decision request. “I need access to the analytics account” is an access request. This distinction helps clients answer quickly.
4. Next week and client asks
End with the next few planned actions, followed by a short list of what you need from the client. Keep the horizon realistic; a weekly email is not a promise about every task that may appear later.
- Finish the FAQ edits after review.
- Prepare the next batch of newsletter links.
- Run the monthly file-archive check.
Client asks:
- Approve the FAQ document by Tuesday.
- Send the two missing invoices.
- Confirm whether the archive should include 2024 files.
If there are no client asks, say so. “No action needed from you this week” is useful information.
Match detail to the engagement
A small retainer may need five bullets. A multi-project client may need headings by workstream. Do not solve a complicated account by writing a giant email. Link to a more detailed tracker and keep the email as the navigation layer.
For recurring work, agree on a few terms early:
- which day the update arrives;
- whether urgent items are sent immediately or saved for the weekly note;
- where supporting files live;
- how a client should mark an item as approved;
- what counts as a changed priority.
These are operating preferences, not a substitute for your contract or statement of work. If the client changes the scope or deadline, document that change in the normal approval process.
A reusable email template
Subject: Weekly status — [project or client] — [date]
Hi [Name],
Here’s the weekly status for [date range]. Headline: [one-sentence summary].
Completed / progressed
- [Result]
- [Result]
- [Result]
Waiting / decisions / risks
- [Item] — waiting on [specific input]; needed by [date].
- [Decision needed] — please confirm [choice].
Next week
- [Next action]
- [Next action]
Client asks
- [Request and due date]
[No action needed from you this week / Thanks, and I’ll send the next update on [day].]
Best,
[Your name]
Read the draft once as the client. Can they tell what is finished, what is not, and what they should do next? If not, shorten the background and sharpen the verbs.
Keep the habit sustainable
Save the previous email or a running status note so you do not rebuild the format every week. During the week, capture completed results and blockers as they happen. A ten-minute Friday review is easier than reconstructing five days from memory.
Be honest about uncertainty. “I expect to finish this next week, assuming access arrives Monday” is stronger than an overconfident promise. The point is shared visibility, not a polished story.
If you are building a broader client-operations routine, the free Mosaic Maker Templates checklist is a practical place to organize recurring admin and follow-ups: https://mosaicmaker5.gumroad.com/l/skgtmh
Top comments (0)