Weekly Status Report Markdown Template
Report weekly outcomes, overall RAG status, milestones, metrics, blockers, decisions, and next-week commitments in one concise update.
# Weekly Status Report: [Project or Team]
**Reporting period:** [Start] to [End]
**Owner:** [Name]
**Overall status:** [Green / Amber / Red]
**Trend:** [Improving / Stable / Worsening]
## Status summary
[In two or three sentences, explain current health, what changed, and why the selected status applies.]
## Outcomes this week
- [Outcome delivered and who it helped]
- [Decision or learning that changed the plan]
## Metrics and milestones
| Metric or milestone | Target | Current | Previous | Status or note |
| :--- | :--- | :--- | :--- | :--- |
| [Name and period] | [Target] | [Current] | [Prior] | [Context or source link] |
## Blockers and risks
| Item | Impact or likelihood | Owner | Mitigation or next step | Due |
| :--- | :--- | :--- | :--- | :--- |
| [Blocker or risk] | [Context] | [Name] | [Action] | YYYY-MM-DD |
## Decisions needed
| Decision | Decision owner | Needed by | Options or recommendation |
| :--- | :--- | :--- | :--- |
| [Question] | [Name] | YYYY-MM-DD | [Link to context] |
## Next-week commitments
- [ ] [Specific outcome] - Owner: [Name]
- [ ] [Specific milestone] - Owner: [Name]
## Links
- [Plan, dashboard, or source document]
Weekly Status Report: [Project or Team]
Reporting period: [Start] to [End]
Owner: [Name]
Overall status: [Green / Amber / Red]
Trend: [Improving / Stable / Worsening]
Status summary
[In two or three sentences, explain current health, what changed, and why the selected status applies.]
Outcomes this week
- [Outcome delivered and who it helped]
- [Decision or learning that changed the plan]
Metrics and milestones
| Metric or milestone | Target | Current | Previous | Status or note |
|---|---|---|---|---|
| [Name and period] | [Target] | [Current] | [Prior] | [Context or source link] |
Blockers and risks
| Item | Impact or likelihood | Owner | Mitigation or next step | Due |
|---|---|---|---|---|
| [Blocker or risk] | [Context] | [Name] | [Action] | YYYY-MM-DD |
Decisions needed
| Decision | Decision owner | Needed by | Options or recommendation |
|---|---|---|---|
| [Question] | [Name] | YYYY-MM-DD | [Link to context] |
Next-week commitments
- [Specific outcome] - Owner: [Name]
- [Specific milestone] - Owner: [Name]
Links
- [Plan, dashboard, or source document]
When to use this template
Use this for a recurring project or team update where readers need the current health, evidence of progress, and requests for help without attending another meeting.
Section guide
- Overall status
- Summarize health and explain any RAG change.
- Outcomes and milestones
- Report results and measurable movement, not activity alone.
- Blockers and decisions
- Make ownership and requested responses explicit.
How to use this template
- 1
Copy the Markdown
Click the Copy button above to put the full template on your clipboard.
- 2
Paste into your editor
Paste into the mdkit editor, a repository, a notes app, or another Markdown editor. Check tables and task lists in your target renderer because Markdown support varies.
- 3
Fill in your content
Replace bracketed examples with verified information, adapt fields to your context, and remove sections that do not apply.
- 4
Check before you use it
- Define RAG criteria with your team; colors without shared thresholds can mislead.
- Link to source metrics and plans rather than crowding the update with raw detail.
Template details
What it solves
A consistent update exposes delivery changes, obstacles, and decisions early while giving stakeholders a quick evidence-based view.
Key features
- Overall RAG status with rationale and trend
- Outcome, metric, and milestone reporting
- Blockers and risks with owners
- Decision requests and next-week commitments
Pro tips
- >State what changed since the previous report.
- >Use metric definitions and dates so numbers have context.
- >Phrase next-week items as commitments with clear completion checks.
Useful Markdown tools
Start in the Markdown editor, then use a relevant tool when you need to format or export the finished document.
Related templates
Meeting Minutes
Capture a meeting's objective, discussion, decisions, action owners, due dates, status, and parked topics in structured Markdown.
Project Post-Mortem
Review a completed project against its plan using evidence, impact, contributing factors, lessons, and owned follow-up actions.
Product Requirements Document (PRD)
Define a product problem, users, goals, scope, requirements, acceptance criteria, metrics, dependencies, risks, rollout, and open questions.