Summarise a Long Project Status Report Into What a Senior Stakeholder Needs to Know

The status report is thorough and detailed and your senior stakeholder will not read it. This converts it into the four things they need: the RAG status and why, the three key facts, any escalated risks, and the decisions or actions that require them specifically. Short, honest, and ready to forward.

You have a project status report that needs to be communicated upward to a senior stakeholder who has fifteen minutes and wants to know whether the project is on track, what the risks are, and what decisions are required of them.

Summarise the report into four sections: first, a single-sentence RAG status (Red, Amber, or Green) with a one-sentence reason; second, the three most important facts about where the project stands right now; third, any risks or issues that have escalated since the last report, with the likely impact if unresolved; fourth, a list of any decisions or actions required from the stakeholder, each with a deadline.

If there is nothing requiring a decision, say so. Do not pad the summary.

[paste the project status report here]