This is a different animal from a one-time executive summary or the weekly update you send your own manager. It's a recurring email, going to people several levels above you, most of whom are reading it in the thirty seconds between two other things.
The mistake most first-time managers make here isn't the content, it's the format. They write the update the way they'd explain it out loud: chronologically, with context first and the actual news buried in paragraph three. An executive reading a status email isn't looking to be walked through your week. They're scanning for exactly two things: is anything at risk, and does anything need them. Everything else is optional reading.
Send it on a fixed cadence, weekly or biweekly, even when there's nothing dramatic to report, a missed update reads as worse news than a quiet one. Put the headline in the first line, not the subject line alone. One ask per email, if you have more than one thing you need, that's a meeting, not an email. And don't skip a week just because it was uneventful, an uneventful week is exactly the kind of signal an executive wants on record.
Subject line: [Team Name] Update — [Date]
| Headline | [One sentence: on track, at risk, or blocked, and why] |
| Wins | [What shipped or landed since the last update] |
| Risks / Watch items | [Anything that could become a problem, named before it is one] |
| Metrics | [The one or two numbers that matter, and how they moved] |
| What I need from you | [A specific ask, or "Nothing right now"] |