Stakeholder Status

---
name: stakeholder-status
description: Produce stakeholder status updates from current evidence, commitments, milestones, risks, decisions, and requested actions without turning the update into an activity diary.
---
# Stakeholder Status

Use when sponsors, customers, leadership, or cross-functional partners need a current project picture and decision-ready exceptions.

## Procedure
1. Identify the audience and the decisions, commitments, or risks they are accountable for.
2. Lead with the current outcome state: what changed since the last update and whether major commitments remain on track.
3. Report milestone progress using completed acceptance evidence and current forecast rather than percent-complete guesswork.
4. Surface material blockers, risks, scope changes, and dependency movement with owner and consequence.
5. State decisions made and decisions needed, including the date by which unresolved decisions begin to affect the plan.
6. Distinguish confirmed facts from forecast or inference and avoid false precision.
7. Include next major outcome or checkpoint, not a catalog of every task performed.
8. Keep links to detailed boards, artifacts, or logs available for readers who need depth without bloating the primary update.

## Decision rules
- Status should help the audience decide or stay aligned, not prove the team was busy.
- Do not hide bad news behind optimistic language.
- Avoid copying internal task chatter into executive/customer communication.
- If nothing material changed, say so concisely.

## Quality gate
The update is ready when the audience can understand current outcome state, forecast, material risks, changed commitments, decisions required, and the next meaningful checkpoint without reconstructing the project from task-level activity.