Status update email: templates and examples for your manager
A status update email tells someone who depends on your work where it stands, before they have to ask. The good ones are short and follow one pattern: what the reader needs to know or decide comes first, and the detail comes after. Below are templates to copy for the common situations: a daily update, a weekly update, a project update for stakeholders, reporting a delay, raising a blocker, and three versions for engineering teams. The names, dates and details in the examples are made up to show the shape.
How to write one
Put the most important thing first. If you need a decision, the first line says so and gives the deadline. If everything is on track and nothing is needed, say that in the first line, so the reader can stop there.
Use the same subject line every time, with the date. Your manager should be able to find last month's updates by searching their inbox.
Write each line as a state the reader could check. "Merged", "sent to the client" and "waiting on legal" are states. "Worked on" and "made progress" tell the reader nothing.
Say what changed since the last update. Repeating last week's news under a new date teaches people to skip your emails.
Skip the long sign-off. Your name is enough.
Subject lines
Status update: Customer portal, 3 Oct
Weekly update, week of 29 Sep (Priya)
End-of-day report, 2026-10-03 (Priya)
Decision needed by Fri: launch date for the pricing page
Delayed: data migration now 14 Oct (was 7 Oct)
When the news is a decision or a delay, put "Decision needed" or "Delayed" at the front of the subject. Those are the emails that must not sit unread.
Daily update email to your manager
Keep a daily update to a few lines. The end-of-day report template covers the daily format in detail; as an email it looks like this:
Subject: End-of-day report, 2026-10-03 (Priya)
Hi Daniel,
Shipped: Onboarding checklist, live for new accounts
In progress: Invoice export; CSV done, PDF left
Blocked: Nothing
Need from you: Nothing today
Priya
Weekly update email
Subject: Weekly update, week of 29 Sep (Priya)
Hi Daniel,
Summary: A good week. Onboarding is live; invoice export slips two days.
Done this week
- Onboarding checklist, live for all new accounts
- Two customer calls on export needs; notes in the shared doc
At risk
- Invoice export: the PDF layout took longer than planned. New date Wed 8 Oct.
Next week
- Finish invoice export
- Start the permissions review
Priya
The summary line does most of the work. A manager reading twenty emails may read only that line, so it has to carry the news, including the bad part. For a fuller weekly report with decisions and links, use the weekly status report template.
Project status update for stakeholders
For people outside your team, give the overall status in a word they can scan, then the dates they care about.
Subject: Status update: Customer portal, 3 Oct
Hi all,
Status: On track for the 20 Oct launch.
Since the last update
- Login and billing pages finished and tested
- Security review booked for 13 Oct
Coming up
- Help page content, due 10 Oct (Marketing)
Risks
- If the security review finds issues, launch moves by up to a week. We will know by 15 Oct.
Questions to Priya.
Name the owner of anything due from another team, and say when an open risk will be settled. "We will know by 15 Oct" lets stakeholders plan without chasing you.
Reporting a delay
A delay email answers four things, in this order: what slipped, the new date, why, and what would help.
Subject: Delayed: data migration now 14 Oct (was 7 Oct)
Hi Daniel,
The data migration will finish on 14 Oct instead of 7 Oct.
Why: the old system stores dates in three formats, and cleaning them is taking a week longer than estimated.
What it affects: the reporting launch moves with it. Nothing else depends on the migration.
What would help: if Ravi can give us two days next week, we can bring it back to 10 Oct.
Priya
Send it as soon as you know, not on the original due date. A delay announced a week early is a planning change. Announced on the day, it is a surprise.
Raising a blocker
Subject: Blocked: need staging access for the payments test
Hi Daniel,
I am blocked on the payments test until I have access to the provider's staging account. Only the finance admin can grant it, and my request from Monday has had no reply.
Could you nudge them, or tell me who else can grant it? Until then I am working on the refund screens, so nothing is idle.
Priya
Say who can unblock you and what you have already tried. The last line matters too: it tells your manager the blocker is not costing the team a whole person.
Engineering versions
Engineering updates have an advantage most teams lack: the work leaves a record. Link it. A pull request, a ticket or a deploy log lets the reader check the status without asking you.
Sprint update
Subject: Sprint 14 update, day 6 of 10 (Payments team)
On track: 9 of 14 tickets done; the rest are in review or in progress.
Done
- Refund API, merged (PR #482)
- Retry logic for failed webhooks, deployed
At risk
- Currency rounding fix: blocked on how to round half-cents. Needs a product decision by Thu.
Links: sprint board, release checklist
Lead with the count or the one-word status, then only what changed or is at risk. Stakeholders do not need every ticket; the board has those.
Release update
Subject: Released: v2.8 to production, 3 Oct
What shipped: bulk invoice export, faster search on the orders page
Who it affects: all accounts; no action needed from customers
Known issues: exports over 10,000 rows are slow; fix planned for v2.8.1
Rollback: the "bulk_export" feature flag switches it off without a deploy
Support and sales read release emails to answer customers, so say who is affected and what is known to be broken.
Incident update
Subject: Incident update: checkout errors (investigating)
Impact: some checkouts failing since 13:55 UTC
Status: cause traced to the payment provider's endpoint; switching to the backup route
Next update: 14:50 UTC, or sooner if resolved
During an incident, the most useful line is the time of the next update. It stops people asking for news every five minutes, and it commits you to sending one.
If you collect updates from a whole team
Writing your own update takes a few minutes. Reading ten of them, chasing the two that did not arrive, and checking which "almost done" is really almost done takes far longer.
Eodly collects a short daily check-in from each person in Slack, Telegram or Discord, weighs it against what moved in GitHub and Linear, and sends you one page each evening. See a sample report.