How to write a status update executives read

Executives do not read status updates. They scan them for one thing, which is whether they need to act. A good update answers that question in the first two lines and earns the right to be read in full only when it matters.

Why most status updates fail

The typical update is written in the order the work happened. It opens with what the team did, moves through what is in progress, and mentions the risk somewhere near the bottom. That order is natural for the writer and expensive for the reader. A VP with forty unread messages will stop after the first paragraph, and if the first paragraph is activity, the one thing they needed to know never reaches them.

The fix is not more detail or better formatting. It is a change in sequence. Lead with the state of the project, then the decision or support you need, then the evidence. Activity belongs at the end, if it belongs anywhere.

The four-line structure

Every strong status update to an executive can be reduced to four lines. Write these first. Everything else is optional.

• Status. One word or phrase. On track, at risk, or off track, with the date that matters.
• What changed. The single most important development since the last update.
• What I need. A decision, an introduction, resources, or nothing. Say "nothing needed" when that is true. It is useful information.
• Next milestone. What happens next and when.

Before and after

Example one, a delayed migration

The second version is shorter and says more. It names the risk, quantifies it, asks for one specific action, and gives the executive a date to watch. The reader can respond in one line.

Example two, a project on track

Good news deserves the same discipline. When an update is easy to read on a quiet week, your executive learns to trust the format, and will notice immediately when the status line changes.

A template you can copy

Subject: [Project] status, [On track / At risk / Off track] for [date]

Status. [One phrase and the date that matters.]
What changed. [The most important development, in one sentence.]
What I need. [Specific decision or support, with a deadline. Or "Nothing this week."]
Next milestone. [What happens next, and when.]

Detail, if useful
- [Supporting fact or metric]
- [Supporting fact or metric]
- [Risk and mitigation]

Put the status in the subject line. Many executives will read nothing else, and the subject alone should tell them whether to open the message.

Five rules for writing upward

• Use numbers, not adjectives. "4% of records fail" beats "some issues." Adjectives invite questions. Numbers answer them.
• Name the risk before someone else does. Bad news delivered early is project management. Bad news discovered late is a trust problem.
• Make the ask specific and dated. "Can you help with the vendor?" creates work for your reader. "Approve escalation by Wednesday" lets them say yes in four words.
• Cut the thank-yous and the warm-up. Appreciation belongs in a separate note, where it will actually be read.
• Keep the format stable. Same structure every week. Predictability is a courtesy to a busy reader.

When the news is bad

An off-track update is where this structure earns its keep. Resist the urge to explain before you state. Lead with the status and the new date, then give the cause in one sentence, then the recovery plan. An executive can work with a problem. What they cannot work with is uncertainty about whether a problem exists.

Calm, specific, and already moving toward a solution. That is how you sound like the person who should be trusted with the next project.