writing-project-status-reportslisted

# Writing Project Status Reports ## Workflow: Writing a report 1. **Determine report type.** Default to weekly. Use monthly for executive audiences, milestone for phase gates or major events. See [references/02-process-and-culture.md](references/02-process-and-culture.md) for cadence selection guidance. 2. **Select template.** Load the matching template from [references/04-templates.md](references/04-templates.md). For software projects, append the Sprint Status Addendum to the weekly template. 3. **Set the RAG indicator.** Assign RAG per dimension (schedule, budget, scope, resources, risks). Derive overall RAG from the worst-performing dimension. Use quantitative thresholds — not gut feel. Note any transitions from last period. 4. **Write the executive summary.** 2–3 sentences answering: Are we on track? What's at risk? What's needed from the reader? If a reader stops here, they must have an accurate picture. 5. **Fill key metrics.** 4–6 quantitative indicators. Replace vague assessments with numbers: - ❌ "Good progress this week" - ✅ "4 of 6 milestones complete; on track for Mar 15 delivery" 6. **Document risks, blockers, and asks.** Each item needs: description, impact (H/M/L), mitigation, owner, and a specific ask. Use the fact → impact → mitigation → ask structure for bad news. 7. **Assign owners and dates to every action item.** An action without an owner is a wish. An action without a date is a suggestion. 8. **Apply exception-based reporting.** Green workstrea