---
name: Stakeholder Update Email
description: Converts project notes into a concise 200-300 word stakeholder email with a consistent four-section RAG structure, drafted in Microsoft 365 Copilot.
---

# Stakeholder Update Email

> **TL;DR:** This skill converts raw project notes into a concise 200-300 word stakeholder email with a consistent four-section structure, a RAG status, and explicit escalations that are never buried.

## How do you draft a concise stakeholder update email?

The skill converts raw project notes, meeting actions and status into a concise stakeholder email with consistent structure and tone. Drafted inside Microsoft 365 Copilot as the host, it applies the RACE prompt-engineering framework: the Role is a project manager reporting upward, the Action is to summarise status, decisions, actions and risks, the Context is the supplied notes or transcript, and the Expectation is a 200-300 word email in plain professional Australian English. The output always leads with a Red / Amber / Green status so the recipient grasps the picture in a sentence before reading further.

## When should you run this skill?

- "Send a stakeholder update"
- "Draft the steering committee email"
- "Summarise this week's progress for the sponsor"

## Required sections, in order

- **Status** — overall RAG status with one sentence justification
- **Decisions** — decisions made this period (bullets)
- **Actions** — actions completed, in flight, or required (bullets, owner + due date)
- **Risks / Escalations** — material risks and any escalations for the recipient

## How this skill works, step by step

1. Read the project notes or transcript provided.
2. Identify the four sections above.
3. Set the overall RAG (Green / Amber / Red) based on schedule, scope, and budget.
4. Keep total length 200-300 words — trim verbose items, never lose escalations.
5. Write in plain professional Australian English, no marketing language.

## Output format

- Subject line: `Project update: <name> — <yyyy-mm-dd>`
- Body in Markdown with `##` headings per section
- A small RAG indicator at the top: green / amber / red plus one-line justification
- Sign-off block at the end (name, role, contact)

## Scope and safety

This skill does NOT:

- Send the email (drafts only — the sender reviews before sending).
- Invent status that is not in the source notes (if a section is empty, say "Nil this period").

## Licensing and permissions

### Licences and add-ons

| Capability used | Minimum licence |
| --- | --- |
| Drafting the email inside Microsoft 365 Copilot | Microsoft 365 Copilot licence |
| Running the skill on supplied notes outside Copilot | Claude licence |

### Least-privilege roles

- No administrator role is required; the user runs this skill on project notes they already hold.

### Microsoft Graph permissions (read-only)

- None. This is a content-generation skill that works on notes or a transcript the user supplies; it does not read tenant data through Microsoft Graph and does not send the email.

## Sources and compliance

- Output in Australian English.
- Keep escalations explicit and addressable — never bury them under "general updates".
- If the recipient is a sponsor or steering committee, lead with the RAG; if peers, lead with decisions.
- Reference: [https://learn.microsoft.com/en-us/copilot/microsoft-365/microsoft-365-copilot-overview](https://learn.microsoft.com/en-us/copilot/microsoft-365/microsoft-365-copilot-overview)