<!-- Source: https://github.com/SuperiorByteWorks-LLC/agent-project | License: Apache-2.0 | Author: Clayton Young / Superior Byte Works, LLC (Boreal Bytes) -->

Status Report / Executive Briefing Template

Back to Markdown Style Guide — Read the style guide first for formatting, citation, and emoji rules.

Use this template for: Weekly/monthly status updates, executive briefings, project health reports, quarterly reviews, sprint retrospectives, or any document that updates stakeholders on progress, risks, and decisions needed. Designed to be read in under 5 minutes by someone with decision-making authority.

Key features: TL;DR at the top for executives who won't read further, traffic-light health indicators, explicit "decisions needed" section that surfaces blockers, metrics table with trends, and risk register with mitigations.

Philosophy: The #1 failure mode of status reports is burying the important stuff in a wall of accomplishments. Lead with what needs attention. If the reader only has 30 seconds, the TL;DR and health summary give them what they need. If they have 5 minutes, the full report answers every follow-up question they'd ask. Never make leadership dig for the thing they need to act on.

How to Use

1. Copy this file for each reporting period
2. Name it by date: status-2026-02-14.md or status-week-07.md
3. Fill in the TL;DR first — if you can't summarize it, you don't understand it yet
4. Be honest about health status — green means green, not "green because I'm optimistic"
5. Add Mermaid diagrams for progress timelines, architecture changes, or risk impact flows

The Template

Everything below the line is the template. Copy from here; commands, API routes, versions, thresholds, and numerical values are illustrative placeholders. Verify them against the actual project before publishing. Follow its existing tracker and PR conventions.

[Project/Team Name] — Status Report

[Reporting period: Week of Month DD, YYYY / Month YYYY / Q# YYYY] [Author] · [Date]

📋 TL;DR

[3–5 bullet points. One sentence each. The most important things leadership needs to know. If they read nothing else, this is it.]

• Overall: [One-sentence project health summary]
• Progress: [Key milestone hit or approaching]
• Blocker: [The biggest risk or decision needed, or "None" if clear]
• Next: [What happens in the next period]

🚦 Health Summary

Status key: 🟢 On track · 🟡 At risk · 🔴 Off track / blocked Trend key: ↑ Improving · → Stable · ↓ Declining

⚠️ Decisions Needed

This section is for items that require action from leadership or stakeholders. If nothing needs a decision, write "No decisions needed this period."

Decision 1: [Specific question that needs an answer]

Context: [Why this decision is needed now — 2–3 sentences]

Options:

Deadline: [When this decision is needed by and what happens if it's delayed]

Decision 2: [Another question]

[Same structure as above]

📊 Key Metrics

<details> <summary><strong>📊 Detailed Metrics</strong></summary>

[Extended metrics, charts, or breakdowns that support the summary table but would overwhelm the main report.]

</details>

✅ Accomplishments

Completed this period

• [Accomplishment 1] — [Impact or outcome. Why it matters.]
• [Accomplishment 2] — [Impact]
• [Accomplishment 3] — [Impact]

Milestones

🔄 In Progress

🚨 Risks and Issues

Active risks

Active blockers

<details> <summary><strong>📋 Resolved Issues</strong></summary>

</details>

📍 Plan for Next Period

Priorities

1. [Priority 1] — [What will be done and expected outcome]
2. [Priority 2] — [What will be done]
3. [Priority 3] — [What will be done]

Key dates

🔗 References

• Project board / Jira / Linear — Live work tracking
• Previous status report (replace with the project link) — For context on trends
• Relevant decision record (replace with the project link) — Background on recent changes

Next report due: [Date]