How do I send clients project updates before they ask?

By Ranjit Bhinge, founder of Blur Studio · Updated · 7 min read

Short answer: Pick a fixed rhythm (one weekly update, plus a short note when a milestone lands), pull the same five fields from your project tool every time, let software or AI draft it, and have a person approve it before it sends. Your project tool is where the work is tracked, such as Asana, a project management tool with built-in status updates. A scheduler such as Zapier, a service that connects apps and runs steps on a timer, can collect the changes and send one summary. Keep a send log so nobody gets the same note twice.

Ranjit Bhinge

You want clients to hear from you on a schedule you control, so the "any update?" email never has to be sent.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Clients email "any update?" for one reason. They cannot see what is happening, so they assume nothing is. The fix is not a better reply to those emails. It is a steady, predictable message that arrives first. This guide covers the rhythm, the fields, the build and the checks that keep it from going wrong.

Why clients keep asking

A client who asks for an update is rarely angry. They are anxious, or their own boss asked them. Silence reads as risk. Three things usually cause it:

  • No rhythm. Updates arrive when you remember. The client cannot tell a quiet week from a stuck project.
  • Updates that say nothing. "Work is progressing well" gives them nothing to repeat to their boss.
  • No place to see status. If the only source of truth is your head or a team chat, every update is manual work.

Automation helps with the first and third. It cannot fix the second, because a message built from empty fields is still empty. That is why the fields below matter more than the tool.

Pick a cadence and stick to it

I would use two triggers, not one.

  1. A weekly digest. One message, same day, same time, even when little changed. "No change this week, next step is Thursday" is a good update. It tells the client you are watching.
  2. A milestone note. A short message the moment something client-visible happens: a draft is ready, a review is due, a launch date moved.

Avoid a third, daily, trigger. Clients start ignoring daily messages, and then miss the one that needs an answer. For a long project with a quiet stretch, drop to every two weeks and tell the client in the first message.

The five fields every update needs

Pull the same fields every time. A template your tool fills in beats a blank page. Asana's own status update starts with a health label (on track, at risk, off track, on hold or complete) and lets you add highlights such as finished milestones and overdue tasks. You can copy that shape in any tool.

FieldWhat it answersWhere it comes from
Status labelAre we fine?One value set by a person: on track, at risk, off track
Done since last updateWhat changed?Tasks marked complete in the period
Next upWhat happens now?Next two or three tasks with dates
Needs from youWhat am I waiting on?Tasks tagged "waiting on client"
Risks or date changesAnything slipping?A short note written by a person

The "needs from you" row does the most work. Most late projects are late because the client has not replied. Putting it in every update, with a date, turns a vague delay into a clear one.

Three ways to build it

1. Use the built-in updates in your project tool

Asana, the project tool mentioned above, can send a status update to everyone on a project, and it can remind you the day before one is due. It can also suggest a status and draft text with AI. That helps if your clients are guests in the project. Check Asana's help pages for how guests and external people are handled on your plan. Other project tools have similar features, so check yours before building anything.

2. Collect and send with a scheduler

This is the common route when your tool only reminds you rather than sends. Zapier has a built-in step called Digest by Zapier. It collects entries from many events and releases them as one message on a schedule: daily, weekly, monthly, or after a set number of entries. You can also trigger the release from another Zap (a Zapier workflow). The result goes to an email or chat step as one consolidated message. The build looks like this:

  1. Trigger: a task is completed or a status changes in your project tool.
  2. Filter: only tasks flagged "client visible." This one step protects you from sending internal notes.
  3. Append the task name, date and link to a digest named after the client.
  4. On a weekly schedule, release each client's digest to a draft step (see the approval step below).

If you do not yet use a scheduler, my guide to Zapier and its alternatives covers the options, and business process automation explains where this kind of chain fits.

3. Use a client portal

A portal is a page where each client logs in and sees status themselves. It replaces the message with a place to look. It suits agencies with many clients and long projects. It costs more setup, and some clients never log in, so I would still send a short weekly note that points to it. I compare options in agency client portal software.

The approval step: let AI draft, a person sends

The raw digest is a list of task names. Clients do not speak in task names. An AI assistant such as Claude (made by Anthropic) can turn the list into two or three plain sentences. Asana offers the same idea built in. The risk is a confident sentence that is wrong, or one that exposes something internal. So the draft goes to you, not the client.

A simple rule: a person approves every weekly update, and the approval should take only a minute or two. Milestone notes for routine events (a file is ready) can go without approval once you trust the filter. Anything that mentions a delay, a cost or a problem always gets a person.

My longer notes on this pattern are in AI client reporting, and the same approve-then-send idea applies to client reporting automation and to monthly reports.

A worked example (made-up figures)

Take a small design studio with 12 active clients. These numbers are invented to show the arithmetic, not a measured result.

  • Writing each update by hand: 10 minutes, so 12 clients is 120 minutes a week.
  • Reviewing an automatic draft: 2 minutes each, so 24 minutes a week.
  • Time saved: about 96 minutes a week, or around 80 hours over a year of 50 sends.

The real gain is fewer "any update?" emails. Count them for four weeks before you build. If you receive two a week, you now know what you are fixing.

Keep a send log so nobody gets two copies

Automations repeat themselves. A timer fires twice after an edit, or a task is reopened and closed again. Keep a simple log, a sheet or table with one row per client per update:

ClientPeriodDraft madeApproved bySent at
Example Client AWeek of 9 NovYesSamMon 9:12

Before any send, the automation checks for a row with the same client and period. If one exists with a sent time, it stops. The log also answers "did the client ever get it?" in ten seconds.

Give questions somewhere to go

Do not send updates from a no-reply address. Send from a real person's address, and say in the first line how to ask a question. Route replies to one shared inbox so a reply is never lost in one person's mailbox. My guide on a shared inbox covers the setup.

On email rules: the US Federal Trade Commission's (FTC) guide to the CAN-SPAM Act, the US law on commercial email, treats messages as transactional or relationship messages only if they stick to narrow categories, such as completing a transaction the client agreed to or delivering the service they bought. It warns that the law reads these narrowly and that a message can become commercial if the subject line looks like an ad. Keep status updates about the project only. Also set up sender authentication (SPF or DKIM, two standard checks that prove the email really came from you) on your domain: Google's sender guidelines require SPF or DKIM for mail sent to Gmail addresses and ask senders to keep spam rates in Postmaster Tools below 0.3 percent. Do not add promotions to them. If you want to add an offer, send it as a separate email. This is general information, not legal advice. Ask a lawyer if you send in many countries.

What goes wrong, and who should not do this

  • Internal notes leak. Fix: only tasks flagged client visible can enter the digest.
  • Stale data. If your team does not mark tasks done, the update is wrong. The automation exposes the mess; it does not clean it.
  • Tone problems. AI drafts can sound cheerful while you are late. A person reads every update that carries bad news.
  • Too many clients on a shared template. A client with a special contract needs their own wording.

If you have three clients, write the updates by hand. Automation pays off from about eight to ten active clients, or earlier if updates take you more than an hour a week. If you want a bigger view of where else this kind of work can be automated, see AI for small business. For new clients, a good first update starts in client onboarding.

How I'd approach this

I would not buy anything first. I would pick one day a week, write the five-field template, and send it by hand to three clients for a month. That shows me which fields clients actually read. Then I would automate only the parts that are the same every time: collecting finished tasks and next tasks. The status label and the risk note stay human.

I would add the AI draft last, with approval on. A weekly update is a promise. One wrong sentence costs more trust than the minute it saves. If you would rather have someone wire the collecting, drafting, approval and log together on the tools you already use, that is the kind of small build I do. Fixes and finishes start around $1,500, and I will tell you if a free habit change would do the job instead.

Questions people ask

How often should I send client project updates?

Weekly is the safe default, plus a short note when a milestone lands. Daily updates get ignored. For a slow stretch, every two weeks is fine if you tell the client up front.

Can Asana send client status updates automatically?

Asana can send a status update to everyone on a project once you post it, and it can remind you the day before one is due. It can also suggest a status and draft text with AI. A person still posts it. Check Asana's help center for how guests are handled on your plan.

How do I combine many task changes into one weekly email?

Use a digest step. Digest by Zapier collects entries and releases them as one message daily, weekly or monthly, or after a set number of entries. See my guide to Zapier and its alternatives if you are choosing a scheduler.

Should AI write the update?

AI can turn a list of finished tasks into plain sentences, which is a good use of it. A person should approve every weekly update and every message about a delay or a cost. See AI client reporting.

Do status update emails count as marketing under CAN-SPAM?

The FTC says transactional or relationship messages must stick to narrow categories, and a message can be treated as commercial if the subject line reads like an ad. Keep updates about the project and send offers separately. This is general information, not legal advice.

Is a client portal better than emailed updates?

A portal gives clients a place to look, but some never log in. Many agencies send a short weekly note that links to the portal. Compare options in agency client portal software.

How do I stop duplicate updates going out?

Keep a send log with one row per client per period, and make the automation check it before sending. If a row with a sent time exists, the step stops.

More in this topic: Problem solving: automating service business work (21 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…