You send the update at 4:40 on Friday. By Monday it has eleven opens and zero replies. Then Thursday, someone books a 30-minute "alignment" call to ask the one question you already answered in paragraph three.
That's not a stakeholder problem. It's an update problem.
Most status emails fail for the same reason: they're written to document what happened, not to help a reader decide what to do next. A stakeholder opening your email at 7:15 a.m. on a phone, between school drop-off and a standup, has about eight seconds. If the first two lines don't tell them whether they need to act, they'll tap out and come back with a meeting invite.
Here's a template I've used across product, ops, and finance teams — plus the specific edits that turn a wall of status into a message people actually respond to.
The template
Subject line: [Project] — [Status word] — [one specific ask or "no action needed"]
Example: Checkout redesign — On track — need your call on launch date by Thursday
Body:
Bottom line: [One sentence: what changed or what you need, and the deadline.]
Where we are: [Two or three bullets, max. Each one is a fact, not a feeling.]
What I need from you: [Named person, specific decision or action, date. If nothing, write "No action needed — this is FYI."]
Risks worth your attention: [Only real ones. One line each. Skip if none.]
Next update: [Date.]
That's it. No "hope you're well," no paragraph of backstory, no attachment unless the attachment is the actual decision document.
Why the subject line carries half the weight
The subject line is the only part of your email guaranteed to be read. Most people waste it on "Weekly Update - Week 14", which tells the reader nothing except that you're organized.
Compare:
Weekly Update - Week 14Checkout redesign — At risk — decision on scope needed by Wed
The second one gets opened because it answers three questions in nine words: what, so what, and by when. Put the status word (On track / At risk / Blocked) in the subject and you've done more for stakeholder trust than a 40-slide review.
One rule: never put "At risk" in the subject without a specific ask or a specific mitigation in the body. A red flag with no next step reads as panic. A red flag with a named decision reads as competence.
The "Bottom line" line is doing the work
If a reader only reads one sentence, this is the one. Write it last, after you've drafted the body, and force yourself to keep it under 25 words.
Weak: "We've been making progress on the checkout redesign and wanted to share a quick update on where things stand."
Strong: "We're two weeks behind on checkout because of the payment API delay; I need your sign-off on the revised launch date by Thursday."
The weak version is a mood. The strong version is a decision. Stakeholders respond to decisions.
Bullets that read like facts, not feelings
"Where we are" is where most updates rot. People write things like "Making good progress on the backend work" or "Still working through some edge cases." These are unverifiable and unhelpful. They also train readers to skim.
Replace adjectives with numbers or names:
"Good progress on backend."→ "Payment service rewritten; 14 of 16 endpoints migrated. Two remaining (refunds, chargebacks) by Friday.""Working through edge cases."→ "Found three edge cases in the refund flow. Two fixed. Third needs a product call on partial refunds — see ask below.""Team is stretched."→ "Two engineers out next week. Timeline holds if the API contract doesn't change."
If you can't put a number or a name against a bullet, it probably doesn't belong in the update. Save it for the standup.
The ask section is the whole point
This is the part almost everyone gets wrong. "Let me know if you have questions" is not an ask. "Would love your thoughts" is not an ask. An ask has three parts:
- A named person. Not "leadership." Not "the team." A person.
- A specific decision or action. "Approve the revised launch date." "Confirm the budget line." "Introduce me to the security reviewer."
- A date. "By Thursday EOD." "Before the Friday steering meeting."
If you have no ask, say so explicitly: "No action needed — this is FYI only." That sentence is a gift. It tells the reader they can archive the email in two seconds and trust that you'll flag them when you actually need them. Updates that always seem to want something get ignored; updates that are honest about needing nothing get read.
Risks: name only the ones you'd bet on
Most risk sections are padded with hedged non-risks ("there's a small chance the vendor timeline might slip") that train readers to ignore the section entirely. Reserve it for things that could actually change the outcome: a dependency that hasn't committed, a decision that's still open, a person who's overloaded.
One line each. If a risk needs more than one line, it needs its own document and a link.
The cadence question
Weekly is the default, but the cadence should follow the decision rhythm, not the calendar. If your stakeholders make decisions every two weeks, a weekly update creates noise. If they make them daily, weekly is too slow.
A simple rule: send an update whenever a stakeholder would otherwise have to ask you a question. If nobody's asking, you're either doing great or you've trained them not to bother — and the second one is a problem you'll discover at the worst possible moment.
What to do this week
Open your last three status emails. For each one, ask: could a reader who only saw the subject and the first sentence decide whether they needed to act? If the answer is no, rewrite the subject and the bottom line using the format above, and send the next update that way. You'll know it worked when the reply is a one-line "approved" instead of a calendar invite.
Generated by Reportify AI — Automate your team's status reports, standups, and weekly updates. Try free →