The short version
- Executives read for exceptions and decisions. A report organised by workstream buries both, so they message you instead.
- Five lines: confidence, what changed, the one risk, the decision you need, and what happens next.
- An honest confidence word is the whole value of the format. Three weeks of green followed by red destroys it permanently.
- The direct message after the report is inevitable and specific. It should reach the project's record, not your evening.
Status reports are written for completeness and read for exceptions, which is why a thorough report reliably produces a direct message asking something it contained. The mismatch is in the structure, not the effort.
"I send the report and the CEO DMs me anyway."
What an executive reads for
Three things, in this order. Is anything going wrong that I need to know about. Is there a decision waiting for me. And has anything changed that affects a commitment I have made to someone else.
What most reports lead with is a summary of activity by workstream, which answers none of the three and requires the reader to extract them. An executive with eleven reports to read does not extract; they skim, form an impression, and follow up on whichever project they have a nagging feeling about.
The five-line report
Confidence. On plan for 12 March. Or: at risk. Or: slipping, new date 19 March.
Changed. What is different since the last report. One or two sentences. If nothing, say nothing changed.
Risk. The single thing most likely to move the date, and who owns it.
Decision needed. What you need, from whom, by when. Or: nothing this week.
Next. What happens between now and the next report.
Under a hundred words. The two hardest disciplines are naming one risk rather than five, and writing "nothing changed" when nothing changed, which feels like admitting idleness and is actually the most useful line you can send.
The confidence word
The first line carries the entire value of the format, and only if it is honest. A project reported as on plan for five weeks and then reported as slipping has not just delivered bad news; it has told every reader that the first line means nothing, and they will read the rest of your reports differently forever.
Two rules make the word trustworthy. Say at risk as soon as you believe the date depends on something outside your control, not when it becomes undeniable. And when you move a date, say so once, with the new date, and do not move it again without new information.
Executives are generally far more tolerant of an early warning than of a late one, because early means they still have options. Late means they have already told someone else.
After the template: the DM
Even a perfect five-line report generates follow-ups, because a broadcast cannot anticipate one reader's specific commitment. Someone will want to know whether the export is affected, because they told a customer it would be there.
The question is where that lands. Currently it lands on you, often in the evening, often asking something you already know. With StandIn, the report is a brief and the project has its own: a Project StandIn answers from what the people doing the work wrote down, in their words, with a source under every answer, and it never guesses. The executive asks about the export and gets what the team recorded about the export, at whatever hour they read the report.
The report stays five lines and the follow-ups stop arriving as interruptions. See how StandIn works, and the person-level version in project updates stakeholders read.
Common Questions
What should a project status report for executives contain?
Confidence against the date, what changed since last time, the single biggest risk with an owner, any decision you need, and what happens next. Under a hundred words, sent at the same time every week.
How often should I send a status report?
Weekly, at a fixed time. Fortnightly invites "any news?" messages in between, and predictability does more for confidence than detail does.
Should I report red or amber if I am not sure?
Report at risk as soon as the date depends on something you do not control. Early warnings preserve the reader's options; late ones remove them, which is what actually damages trust.
How do I stop executives asking things the report answered?
Make the project's detail retrievable rather than only broadcast. A sent report is gone from an executive's view within a day, so the answer needs to be somewhere they can ask again without asking you.
When you're off, your StandIn is on.
It answers your teammates' questions from work you've already done, in your words, with a source under every answer.