How to Write a Weekly Client Update Your Client Actually Reads

A weekly client update should take you ten minutes to write and thirty seconds to read. That is the whole standard. If it takes you an hour, you are writing a report. If it takes them five minutes, they will skim it once and stop opening the next one.

Most client relationships do not end because the work was bad. They end because the client stopped knowing what was happening. Silence gets filled in, and it never gets filled in generously. Two quiet weeks turn into "what am I actually paying for", and by the time that question is asked out loud, the trust is already gone.

The fix is boring and it works. Same day every week, same short format, whether or not the week went well.

What should a weekly client update include?

Four things. Nothing else.

What got done. Two or three lines, in plain language, describing outcomes rather than activity. "The booking form is live and took its first real booking on Tuesday" is an outcome. "Worked on booking form" is a timesheet entry. Your client cannot judge effort and should not have to.

What is next. One or two lines about the coming week. This is the part that quietly earns the next invoice, because it shows there is a plan and someone is holding it.

Anything you need from them. Be specific and name the deadline. "I need the logo files by Thursday or the homepage slips a week" works. "Let me know your thoughts when you get a chance" does not, and you will be chasing it for a fortnight.

Anything that changed. A slipped date, a cost that moved, a decision you made on their behalf. This is the part people leave out, and it is the part that matters most.

That is the update. Four short blocks. No status tables, no percentage complete, no colour-coded risk register that neither of you believes.

How long should a client update be?

Under 200 words. Aim for something they can read on a phone, standing up, between meetings, without scrolling twice.

Length is not generosity. A long update is usually a sign that you are padding a thin week, or that you have not decided what actually mattered. Both are worth noticing in yourself. If you genuinely have more to say, attach the detail and keep the update itself short. The client who wants depth will click. The client who does not will still be informed, which is the point.

Here is a complete example:

Week of 12 May

The new booking flow went live on Tuesday and has taken 34 bookings since. Payment errors are down from about 6 a week to zero so far.

Next week I am cleaning up the confirmation emails and starting the reporting screen.

I need your merchant ID for the reporting screen by Thursday, otherwise it moves to the following week.

One change: I moved the reporting screen ahead of the admin settings page, because you cannot see revenue without it and settings can wait.

Ninety words. Your client now knows the state of their money, their project, and their own homework. That is a good week's communication and it took you less time than the meeting you avoided by sending it.

How often should I update a client?

Weekly, on a fixed day, forever.

Weekly is frequent enough that nothing festers and rare enough that it never becomes a chore. Fixed is the more important half. When updates arrive on a predictable day, your client stops chasing you, because there is a known moment when the answer arrives. Unpredictable updates train people to ask, and then you are handling questions all week instead of writing once.

Friday afternoon suits most people, because it closes the week. Monday morning also works, because it sets one up. What does not work is "when there is something to report", which reliably becomes never.

What do I write when nothing got finished?

This is the week everybody goes quiet, and it is the week the update matters most.

Write it anyway. Say what is holding, say why, say what you are doing about it, and say when you expect it to move. A client who hears "the API sandbox has been down since Wednesday, I have a ticket open, if it is not back by Monday I will build against a mock so we do not lose the week" thinks you are on top of it. A client who hears nothing for six days thinks you have disappeared with their money.

Slow weeks are also when you should say what changed even if it makes you look worse. Bad news early is a project management problem. Bad news late is a character problem. Your client will forgive the first and remember the second.

One more thing about difficult weeks: resist explaining the technical reason at length. A short honest sentence reads as confidence. Three paragraphs of justification read as guilt, even when everything you wrote is true.

Should a client update be an email, a document, or its own page?

Email is where updates get read. A shared document is where they go to die, because it needs a login, and it makes your client come to you instead of the other way round.

But email alone has a real weakness: no history. Three months in, nobody can find what was agreed in March, and "I never got that" becomes an unfalsifiable argument. Every freelancer who has been burned once knows the feeling of searching a mail client for a promise they are almost sure they made.

So the arrangement that actually works is both. The update goes out as an email, and it also lives at a permanent link where every past update sits in order. Send it, and it is read. Keep it, and there is a record. When a new person joins on the client side, you send them one link instead of forwarding forty emails.

That link should not require an account. Every login you put in front of a client is a reason for them not to look, and the only thing you achieve is making your record harder to reach than the problem it was meant to solve.

The habit is worth more than the format

You can take everything above and put it in a plain email template today. The format is not the hard part. The hard part is that on the week you are behind, or embarrassed, or genuinely slammed, you will want to skip it, and that is exactly the week your client is wondering whether this is working.

Send it anyway. Ninety words, same day, every week. It is the cheapest client retention there is, and almost nobody does it consistently.

Friday exists to make that habit take ten minutes. One page per client, post an update, they get it by email with a link to everything that came before. No login for them, no chasing for you.