A short client-facing status they can answer without a call: delivered, in progress, one ask, and the next checkpoint.
Status update
Keep it answerable: what changed, what you need, and when you check in next.
Runs in your browser. Auto-saves on this device. Nothing is uploaded.
Your draft
Live
When the draft is ready, paste it into Today’s end-of-day fields.
Open Work Dashboard
Blank, example, and short versions
Blank status update
To:
Project:
Date:
Delivered:
In progress:
Needs from you:
Next checkpoint:
Risks:
Realistic status example
To: Ana
Project: Northwind proposal site
Date: 2026-09-13
Delivered:
- Pricing table live on staging (https://staging.example.com/pricing)
- Invoice #184 sent for August retainers
In progress:
- Case-study captions (2 of 4 done)
- FAQ section 5 outline only
Needs from you:
- Confirm pricing tiers look right on staging (reply yes, or list changes)
- Choose whether the shipping FAQ stays or cuts (comment A or B on the doc)
Next checkpoint:
15 Sep with final captions and FAQ section 5 drafted after your replies
Risks:
MSA clause 4 still with your Legal team; design work can continue, contract signature cannot
Shorter version
Project / date:
Delivered:
In progress:
Needs from you:
Next checkpoint:
About this template
What this is for
Send a client a status they can answer without a call: what shipped, what is in flight, the one decision or asset you need, and when you check in next.
When should you use it?
Use on your agreed cadence, after a milestone ships, or when silence would look like nothing is happening.
When should you skip it?
Skip days with no material change unless the client expects a heartbeat. Do not bury bad news or scope changes inside a routine status; send those in their own message. For an internal blocker that only teammates must act on, use the blocker update.
Why this example works
Delivered leads with proof (links and invoice). Needs from you gives reply shapes (yes/list, A/B). Checkpoint has a date. Risks name what is blocked without burying the asks.
Job this solves
Clients do not need your hours worked. They need proof of progress, one clear ask, and a trustworthy next checkpoint. This template keeps the update short enough to answer from a phone.
How to fill it
List Delivered as visible outcomes the client can recognize (prefer links).
Keep In progress short and tied to the next checkpoint.
Put one primary ask under Needs from you, with a reply shape when you can.
State Risks factually without apology essays.
End with the next checkpoint date you already promised.
Cadence tip
Match the rhythm you already sold. Surprising a client with daily notes after agreeing on twice-weekly updates creates noise and distrust.
Common mistakes
Reporting hours worked instead of outcomes delivered
Stacking three soft asks so none get answered
Hiding a risk inside a long paragraph of good news
Rewriting the update in chat after sending the formal note
Sending a status on a no-change day without a reason