Status Report Template Generator

Эксперт по созданию эффективных статус-отчётов для проектной коммуникации на всех уровнях организации.

Core Principles

Foundational Requirements

effective_status_report: principles: - name: "Consistent Formatting" description: "Use consistent structure and hierarchy across all reports"

- name: "Audience-Specific"
  description: "Tailor depth and focus to reader's needs"

- name: "Traffic Light System"
  description: "Green/Yellow/Red for quick visual assessment"

- name: "Data-Driven"
  description: "Include specific dates, percentages, measurable outcomes"

- name: "Actionable"
  description: "Clear next steps with ownership and deadlines"

- name: "Honest"
  description: "Direct communication about issues while maintaining professionalism"

Audience Differentiation

Audience Focus Depth Frequency

Executive Business impact, strategic alignment High-level metrics Weekly/Monthly

Team Operational details, blockers Detailed tasks Daily/Weekly

Client Deliverables, timeline Balanced detail Weekly

Board Strategic metrics, risks Executive summary Monthly/Quarterly

Stakeholders Relevant updates, decisions needed Customized As needed

Standard Templates

Executive Summary Template

Project Status Report: [Project Name]

Report Date: [Date] Reporting Period: [Start Date] - [End Date] Report Author: [Name]

Executive Summary

Overall Status: 🟢 GREEN / 🟡 YELLOW / 🔴 RED

Key Highlights

1. [Major accomplishment with measurable impact]
2. [Important milestone reached]
3. [Significant decision made]

Attention Required

1. [Issue] - [Impact] - Decision needed by [Date]
2. [Risk] - [Mitigation status] - Escalation: [Yes/No]

Decisions Needed

Progress Tracking Section

Progress Summary

Completed This Period

In Progress

Upcoming (Next Period)

Milestone Tracker

Risk Management Matrix

Risk & Issue Management

Active Risks

Risk Scoring: Low=1, Medium=2, High=3 | Score = Probability × Impact

Active Issues

Escalations

Financial Summary

Financial Summary

Budget Overview

Burn Rate Analysis

• Planned Monthly Burn: $100,000
• Actual Monthly Burn: $95,000
• Trend: 5% under budget
• Projected End Cost: $665,000 (5% under budget)

Resource Utilization

Dashboard Templates

Weekly Team Dashboard

Team Weekly Update: [Team Name]

Week of: [Date Range]

This Week's Focus

🎯 [Primary objective for the week]

Wins 🏆

• ✅ [Accomplishment 1]
• ✅ [Accomplishment 2]
• ✅ [Accomplishment 3]

Challenges 🚧

• ⚠️ [Challenge 1] → [Action being taken]
• ⚠️ [Challenge 2] → [Action being taken]

Team Velocity

Next Week Preview

1. [Priority 1]
2. [Priority 2]
3. [Priority 3]

Help Needed

• [Specific request 1] - [From whom]
• [Specific request 2] - [From whom]

Monthly Executive Dashboard

Executive Dashboard: [Project/Program Name]

Period: [Month Year]

At a Glance

┌─────────────────────────────────────────────────────────┐ │ SCHEDULE BUDGET SCOPE QUALITY TEAM │ │ 🟢 🟡 🟢 🟢 🟢 │ │ On Track At Risk On Track On Track On Track │ └─────────────────────────────────────────────────────────┘

OKR Progress

Objective 1: [Objective Name]

Objective 2: [Objective Name]

Strategic Alignment

• Business Impact: [Quantified impact on business metrics]
• Customer Satisfaction: [NPS or CSAT score change]
• Revenue Impact: [Revenue influenced or generated]

Key Decisions Made

1. [Decision] - [Date] - [Impact]
2. [Decision] - [Date] - [Impact]

Upcoming Milestones (Next 30 Days)

Advanced Techniques

Trend Analysis Integration

Performance Trends (3-Month Rolling)

Schedule Performance Index (SPI)

Analysis: Schedule performance improving. Current trajectory suggests on-time delivery.

Cost Performance Index (CPI)

Analysis: Cost efficiency improving. Projecting 5% under budget at completion.

Velocity Trend

Velocity (Story Points) 50 │ ╭─────╮ 40 │ ╭────╯ ╰──── 30 │────╯ └────────────────────── S1 S2 S3 S4 S5 S6

Visual Health Dashboard

Project Health Indicators

Health Matrix

            LOW IMPACT    MED IMPACT    HIGH IMPACT
           ┌────────────┬────────────┬────────────┐

HIGH PROBABILITY │ 🟡 │ 🟠 │ 🔴 │ ├────────────┼────────────┼────────────┤ MED PROBABILITY │ 🟢 │ 🟡 │ 🟠 │ ├────────────┼────────────┼────────────┤ LOW PROBABILITY │ 🟢 │ 🟢 │ 🟡 │ └────────────┴────────────┴────────────┘

Current Risk Distribution

• 🔴 Critical: 1 (Resource availability)
• 🟠 High: 2 (Integration complexity, Vendor dependency)
• 🟡 Medium: 4
• 🟢 Low: 8

Quality Metrics

Predictive Elements

Predictive Analysis

Completion Forecast

Based on current velocity and remaining scope:

Factors affecting forecast:

• ↗️ Positive: Team velocity increasing, key risks mitigated
• ↘️ Negative: Scope additions (+15 points), holiday schedule

Budget Forecast

Scope Creep Indicator

Scope Growth Rate 15% │ ╭──── Warning Zone ──── 10% │────╯ 5% │ 0% │════════════════════════ Week 1 2 3 4 5 6

Current Rate: 8% | Threshold: 10%

Report Types by Context

Client Status Report

[Project Name] - Client Status Report

Report #: [Number] Date: [Date] Prepared for: [Client Name]

Project Overview

Overall Status: 🟢 On Track

We're pleased to report continued progress on [Project Name]. This week, we achieved [key milestone] and remain on track for [upcoming deliverable].

Deliverable Progress

Completed Deliverables

In Progress

Timeline Update

[Visual timeline or Gantt chart summary]

Items Requiring Your Input

1. [Decision Item]
   • Context: [Brief context]
   • Options: [A, B, C]
   • Recommendation: [Our recommendation]
   • Needed by: [Date]

Next Steps

• [Action 1] - [Date]
• [Action 2] - [Date]

Meeting Schedule

• Next Status Call: [Date/Time]
• Demo Session: [Date/Time]

Steering Committee Report

Steering Committee Report

Program: [Program Name] Meeting Date: [Date] Prepared by: [PMO]

Executive Summary

[2-3 sentence summary of overall program health]

Program Dashboard

Portfolio Status

Resource Allocation

Decisions Required

Decision 1: [Title]

• Background: [Context]
• Options:
  • Option A: [Description] - Cost: $X, Risk: Low
  • Option B: [Description] - Cost: $Y, Risk: Medium
• Recommendation: Option A
• Impact of No Decision: [Consequences]

Strategic Risks

Financial Summary

• YTD Spend: $X of $Y budget (X%)
• Forecast: On/Under/Over budget by X%

Best Practices

Do's ✅

best_practices: timing: - "Send reports consistently (same day/time each period)" - "Allow 24 hours for review before meetings" - "Distribute before, not during, status meetings"

content: - "Lead with executive summary" - "Use data and metrics, not just descriptions" - "Include both wins and challenges" - "Provide clear action items with owners and dates" - "Quantify everything possible"

formatting: - "Use consistent templates across projects" - "Apply traffic light colors sparingly and consistently" - "Include visual elements for quick scanning" - "Keep executive summary to one page"

distribution: - "Create audience-specific versions" - "Archive for historical analysis" - "Make searchable and accessible"

Don'ts ❌

common_mistakes:

• mistake: "Burying critical issues" impact: "Stakeholders blindsided by problems" fix: "Lead with issues requiring attention"

• mistake: "Activity reporting vs outcome reporting" impact: "No clarity on actual progress" fix: "Focus on completed deliverables and business impact"

• mistake: "Vague language" impact: "Ambiguity and miscommunication" fix: "Use specific numbers, dates, percentages"

• mistake: "Missing action items" impact: "No accountability or follow-through" fix: "Every issue needs owner and deadline"

• mistake: "Over-optimistic assessment" impact: "Lost trust when reality emerges" fix: "Honest assessment with mitigation plans"

• mistake: "Too much detail for executives" impact: "Key points lost in noise" fix: "Executive summary + detailed appendix"

Automation Integration

JIRA Integration Query

-- Sprint progress query for status report SELECT sprint_name, COUNT(CASE WHEN status = 'Done' THEN 1 END) as completed, COUNT(CASE WHEN status = 'In Progress' THEN 1 END) as in_progress, COUNT(CASE WHEN status = 'To Do' THEN 1 END) as todo, SUM(CASE WHEN status = 'Done' THEN story_points ELSE 0 END) as completed_points, SUM(story_points) as total_points, ROUND(SUM(CASE WHEN status = 'Done' THEN story_points ELSE 0 END) * 100.0 / NULLIF(SUM(story_points), 0), 1) as completion_percentage FROM issues WHERE sprint_id = :current_sprint GROUP BY sprint_name;

Slack Status Bot Template

// Automated status collection bot const statusPrompt = { blocks: [ { type: "section", text: { type: "mrkdwn", text: "Weekly Status Update\nPlease provide your status for the week:" } }, { type: "input", element: { type: "plain_text_input", action_id: "accomplishments", multiline: true, placeholder: { type: "plain_text", text: "What did you accomplish?" } }, label: { type: "plain_text", text: "Accomplishments" } }, { type: "input", element: { type: "plain_text_input", action_id: "blockers", multiline: true, placeholder: { type: "plain_text", text: "Any blockers or challenges?" } }, label: { type: "plain_text", text: "Blockers" } }, { type: "input", element: { type: "plain_text_input", action_id: "next_week", multiline: true, placeholder: { type: "plain_text", text: "What's planned for next week?" } }, label: { type: "plain_text", text: "Next Week's Focus" } } ] };

Лучшие практики

• Консистентность важнее красоты — используй один и тот же шаблон

• Executive summary всегда первым — руководители читают только его

• Честность в оценках — лучше предупредить о рисках заранее

• Конкретика вместо общих фраз — "завершено 75%" вместо "почти готово"

• Action items с владельцами — каждый риск и issue должен иметь ответственного

• Архивируй отчёты — они нужны для post-mortem и планирования

• Адаптируй под аудиторию — разная глубина для разных читателей