How to write a weekly client status update at an agency

Answer first: A weekly client status update is a short, predictable message that tells a client four things: what was done this week, what's planned next, what you need from them (with a date), and any risk to scope, budget or deadline. Send it on the same day each week, keep it skimmable, and have the account lead approve it, because a status update is where expectations get set.

Why a fixed weekly update helps

Clients who hear nothing tend to ask "where are we?" at the worst moment. A regular update answers that before it's asked, puts blockers in writing, and gives you a record if timelines slip because approvals came late.

The four-part format

1. Done this week: 3–5 bullets, outcomes not hours.
2. Next week: what you'll work on, in plain language.
3. Needed from you: each item with an owner and a date ("Logo files by Thursday").
4. Risks and changes: anything that may move a date, budget or scope. Flag it early; don't bury it.

A copy-ready template

Subject: [Client] weekly update: [date]
Done: …
Next: …
We need from you: … by [date]
Heads-up: … (or "None this week")
Reply with questions, or we'll pick it up on [next touchpoint].

Mistakes to avoid

• Long narratives the client won't read.
• Agreeing to new scope inside a status email; route that as a change request.
• Skipping the update when there's bad news. That's the week it matters most.

Where automation fits, and where a human stays

Pulling finished tasks into a draft and formatting it are reasonable jobs for software. Choosing what to say about risks, dates and money should stay with a person, who approves the update before it goes out. Laborbot.si's planned workers are being designed around that split, with explicit permissions and human review. It's a preview today; early access records interest only.

See how Laborbot.si's planned workflows keep a person in charge. Join early access. No card needed. Unsubscribe anytime.

Frequently asked questions

What should a weekly client status update include?

What was done, what's next, what you need from the client with dates, and any risks to scope, budget or deadline.

How long should a client status update be?

Short enough to read in under a minute: a few bullets per section.

Which day should agencies send status updates?

Pick one day and keep it consistent so clients know when to expect it; many teams choose the end of the working week.

Can software write client status updates?

Software can draft and format them from task data, but a person should approve anything about risks, dates, scope or price.

Is Laborbot.si available now?

No. Laborbot.si is a preview of planned digital workers; live hiring, integrations and execution aren't available yet. Join early access. No card needed. Unsubscribe anytime.