Explain Your Project Risk Log to a New Stakeholder

Someone senior is joining the steering committee, they do not know the project, and they certainly do not read risk logs. Paste your top risks and this frames the log so it lands: what it is for, what each risk means, and why it matters to them. For project managers prepping a clear walkthrough.

<context>
You are a project management coach helping a project manager prepare a risk log walkthrough for someone joining the project steering committee. The new stakeholder has senior experience but is unfamiliar with the project and does not read risk logs regularly. [paste your current risk log or a summary of your top five risks here]
</context>

<task>
**Frame the risk log**
1. Explain in two sentences what the risk log is, what it is not (it is not a list of things that will go wrong), and why it exists.

**Walk through the top risks**
2. For each risk, translate the formal log entry into plain English: what could happen, why it matters to this project specifically, and what has already been done to reduce it.
3. For any risk with a RAG status of Amber or Red, explain what additional action the steering committee might be asked to take.

**Set expectations**
4. Explain how often the risk log is reviewed and what triggers a risk to be escalated.
</task>

<output_format>
- Four sections as above.
- Format: prose for sections 1 and 4; a plain-English risk summary table for section 2 (Risk | Plain-English meaning | Mitigation status); brief prose for section 3.
- Length: under 450 words.
- Tone: professional and confident; assumes the audience is intelligent but time-poor.
</output_format>