Project Status Brief
Workflow
- Identify project objective, owner, reporting period, current phase, and target milestone.
- Determine health status from evidence: scope, schedule, quality, budget, resourcing, and stakeholder alignment.
- Extract completed work, upcoming milestones, blockers, risks, and dependencies.
- Convert vague activity updates into outcome-focused status language.
- Call out decisions, escalations, or support needed from leadership.
Output Standard
Use this structure by default:
- Status: Green, Yellow, Red, or Unknown with one-sentence rationale.
- Objective: what the project is trying to achieve.
- Progress This Period: outcomes completed, not just activity.
- Milestones: completed, current, and upcoming milestones.
- Blockers / Dependencies: owner, impact, and requested support.
- Risks: risk, probability, impact, mitigation, and trigger.
- Next Actions: owner, action, due date, and success signal.
- Leadership Ask: decision, escalation, or resource request if needed.
Rules
- Use
Unknownwhen health cannot be inferred from the source. - Do not soften material risks to make the update sound better.
- Make escalation asks specific enough that a leader can act.
- Keep the brief suitable for a dashboard, email update, or operating review.
References
Read references/status-patterns.md when the user asks for RAG scoring, dashboard format, or launch-readiness framing.