Client status updates that build trust, with templates to copy
What to put in an update, how often to send it, and why a place to check beats another email.
On this page
A good client status update is short and arrives on a fixed day. It tells the client what you finished, what comes next, what is blocking you and what you need from them. Send it every week, or give the client a page where they can check status themselves, and you stop being the person they have to chase.
Silence is what clients punish
Clients seldom leave because a project took longer than hoped. They leave because they could not see what was going on, and they filled the gap with worst-case guesses.
The numbers back this up, with a caveat about who ran the surveys. In the Setup Marketing Relationship Survey for 2024, 48% of clients named dissatisfaction with delivery as the top reason they end an agency partnership, up 14 points from the year before. Agencies ranked it seventh of eight on their own list of why clients leave. That gap is the whole problem: the client is worried about visibility while the person doing the work assumes the work speaks for itself.
A later churn report from Focus Digital, as summarised by TapClicks, repeats the 48% figure and says clients feeling uninformed about activity is a high-impact churn driver for small agencies. TapClicks sells reporting software, so treat its framing with care, but the pattern matches what the independent survey found.
Early relationships are the most fragile. Duda cites the same Setup research, which found that nearly 40% of brands are likely to switch agencies within their first six months. The first months are when a client has the least evidence that you are reliable, so that is when updates matter most.
None of this requires a project to go badly. A client left in the dark on a healthy job still gets nervous, still sends "any update?" and still remembers the anxiety when it is time to renew. If your clients also go quiet when you need an answer from them, our post on why clients ignore feedback requests covers the other side of the same trust gap.
What a good update contains
A useful update answers the questions the client is quietly asking and nothing else. Keep it to four parts.
Progress is what moved since the last update, in plain terms. "Home and pricing pages are designed and ready for your review" beats "made good progress this week."
Next step is what you are doing now and roughly when it lands. This calms people because it shows the project has a direction.
Blockers are anything slowing you down, named honestly. A blocker mentioned early is a shared problem. The same blocker revealed at the deadline is your failure.
What you need from them is the most skipped part and the most valuable. If you are waiting on copy, logo files or a decision, say so and give a date. Vague asks get ignored. A specific ask with a deadline usually gets answered.
Leave out the apologies, the filler and the hour-by-hour diary. The client does not need every hour accounted for. They need to know the project is under control and whether the ball is in their court. When you need a sign-off, make the ask impossible to misread; our email templates for asking a client to approve work show the wording.
Length matters. Five sentences a client reads beat five paragraphs they skim. If an update takes you twenty minutes to write, it takes them too long to read.
Set a rhythm and keep it
Pick a day and hold it. For most projects, one update a week is the floor. For fast or high-stakes work, send two. The exact day matters less than the fact that it never slips.
Trust is built by predictability. A client who knows an update arrives every Friday stops sending anxious check-ins on Wednesday, because you answered the question before it was asked.
That is the difference between proactive and reactive updating. Reactive means replying to "how is it going?" after the client got nervous enough to ask. Proactive means sending the news before they think to. One reads as a person in control. The other reads as a person being managed.
Customers say this matters. Zendesk's CX Trends 2026 research, which surveyed more than 11,000 consumers and business leaders across 22 countries, reports that 86% say responsiveness and accurate resolution strongly influence what they buy. Responsiveness is not only how fast you reply. It is how rarely the client has to reach out in the first place.
Two habits protect the rhythm. Put the update in a fixed slot in your week so it does not compete with the work. And send it even when there is little to say. "Quiet week, still on track for Friday, no blockers, nothing needed from you" is a useful message because it tells the client that silence was intentional.
Give clients a place to look
The strongest update is one the client does not have to wait for. When files, approvals, messages and invoices live in one place the client can open, status stops being an email you have to remember and becomes a page they can check.
This matters because chasing information is a real irritation. The same Zendesk research found that 74% of consumers are frustrated when they have to repeat information. A client who emails you to learn the stage of the project, then emails again to find the latest file, is living that frustration.
A shared record also protects you. When a client says they never knew about a revision round, the record answers it, and you do not need a memory contest. The client can see what was delivered, what they approved and what is still open.
Research on project communication points the same way, though it is older. The Project Management Institute's work on communication and project success, published in 2013, found that effective communication separated high-performing projects from the rest. The details have aged, but the idea has not. For the trade-offs between a portal and an email thread, see our comparison of a client portal against email for delivering work.
Templates you can copy
You do not need to reinvent the wording each week. Two templates cover most cases.
The weekly update
Subject: [Project] update, week of [date]
>
Hi [name],
>
Quick status on [project].
>
Done this week: [what you completed] Up next: [next task], expected by [date] Blockers: [none, or the specific thing slowing you down] Need from you: [the item and the date you need it, or "nothing right now"]
>
On track for [milestone or deadline]. Reply if anything looks off.
The blocker flag
Send this the moment something stalls, not at the next scheduled update.
Hi [name], flagging this early so it does not cost us time. I need [the specific item] to keep moving on [task]. Without it, [task] slips by about [estimate]. Could you get it to me by [date]? Everything else is on track.
Both do the same job. They keep the client informed, put anything that belongs to them in their court with a date, and leave a written record of who owed what and when.
How Delivvo turns updates into a page the client can open
Delivvo gives each client a portal, so most "where are we?" emails never get written. You still send a short note when something needs their attention, and the portal shows everything else.
This is how it works:
- When a client accepts your quote, Delivvo creates the client, the project, the contract, the invoice and the payment schedule together, so there is a project page from day one.
- You upload work to the portal. Each file has versions, so the client always sees the latest and can look back at earlier ones.
- When something needs a decision, you request an approval on that file. The client approves it with their name and the time recorded, which settles later arguments about what was signed off.
- Messages sit beside the files, so a question about version two stays attached to version two.
- A money line on the portal shows what has been invoiced, what has been paid and what is due.
- The client opens all of this with a one-time code and no password, so there is no account to forget.
If you work with a team, tasks in the team workspace carry an assignee, a brief, a due date and files, and the client only ever sees the file you approve to show them, under your business name.
One detail that is not obvious: every invoice and contract carries a verification code. If a client's accountant wants to check a document, they enter the code on the verify page.
Your clients pay through your own gateway, and Delivvo takes 0%. See the client portal and client approvals.
Next, look at Delivvo for teams or how the CRM fits around it.
FAQ
How often should I send a client a status update?
Weekly is a safe default, and twice a week suits fast or high-stakes work. Consistency matters more than frequency. If the update always arrives on the same day, clients stop sending nervous check-ins.
What if there is nothing new to report?
Send a short update anyway. "Quiet week, on track, no blockers, nothing needed from you" tells the client the silence was planned. Skipping the update is when worry starts.
Is a client portal the same as a status update?
No. An update is something you push to the client on a schedule. A portal is something the client can check whenever they like. A portal cuts down how many updates you write, but a short note still helps when the next move is theirs.
How long should a status update be?
Five or six lines is enough. Use four parts: done, next, blockers and what you need. If it needs more, link to the file or the portal page.
Delivvo runs the whole client cycle for service businesses, from the first inquiry to the quote, contract, deposit, invoice and delivery, so clients can see where their project stands without having to ask. Clients pay you directly through your own gateway, and Delivvo takes 0%. Start free