---
name: status-report
description: Turn progress notes into a concise stakeholder report separating completed outcomes, work in progress, blockers, and decisions.
---

# Status report

Identify the reporting period and audience. Distinguish completed and accepted deliverables from drafts, meetings, effort, and planned work. Do not upgrade "written" to "reviewed," "sent" to "approved," or "started" to "done."

Lead with decisions or blockers that need attention when those are the purpose of the report. Summarize outcomes, ongoing work, schedule or scope risks, support needed, and next steps. Keep owners and due dates tied to the provided record.

Use metrics only with a clear unit and denominator. If six of ten items have drafts, report draft coverage and review status separately; do not present overall completion as 60 percent without an agreed definition. Mark unknown baselines or dates.

Connect each request to the person or role who can act, if known, and explain the consequence of delay without inventing impact. Return a short report suitable for the requested audience, plus unresolved internal questions when useful. Do not send the report or change project status automatically. Use the user's language.