Weekly Status Report Template Ppt

Standard Operating Procedure: Weekly Status Reporting (WSR)

Document ID: TR-OPS-WSR-001
Effective Date: 2023-10-27
Version: 1.0.4
Review Cadence: Quarterly

1. Executive Summary & Purpose

The purpose of this SOP is to standardize the generation and delivery of the Weekly Status Report (WSR) presentation. This protocol ensures consistent data visualization, stakeholder alignment, and operational transparency across all architectural and engineering workstreams at Template Registry.

2. Scope & Prerequisites

• Scope: Applies to all Leads, Architects, and Project Managers reporting to the Executive Office.
• Tools: Microsoft PowerPoint (latest Enterprise build), Template Registry Official Theme (.potx), Jira/Linear API integration, and corporate VPN access.
• PPE: N/A (Digital environment).

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase I: Data Aggregation (Monday 08:00 – 12:00)

• Export raw performance metrics from Jira/Linear (Velocity, Burn-down).
• Collate "Blockers" and "Risks" logs from the current sprint board.
• Validate "Next Week" targets against the Q3/Q4 OKR roadmap.

Phase II: Template Construction (Monday 13:00 – 15:00)

• Open TR_Master_WSR_Template.potx. Do not edit master slides.
• Populate "Executive Summary" slide (max 3 bullet points, high-level impact).
• Update "Traffic Light" status (Green/Amber/Red) with documented justification.
• Append technical debt reduction metrics to the "Engineering Health" appendix.

Phase III: Review & Deployment (Monday 15:00 – 17:00)

• Run Accessibility Checker on all slides (Alt-text required for charts).
• Perform peer review of financial/budgetary data against procurement logs.
• Export finalized report to PDF (Standard ISO/PDF-A).
• Distribute via internal secure portal and email distribution list.

5. Quality Assurance & Pro-Tips

• The "Rule of Three": Never exceed three bullet points per slide. If more data is required, move it to the Appendix.
• Metric Thresholds: Any "Amber" or "Red" status must include a "Remediation Strategy" slide. Status without mitigation is unacceptable.
• Pro-Tip: Use linked Excel objects for charts to ensure data refreshes automatically upon source update. Do not manually re-key numbers; minimize human error vectors.
• Common Pitfall: Over-reporting granular task completion. Focus on outcomes (value delivered), not outputs (hours logged).

6. Frequently Asked Questions (FAQ)

Q: Can I use custom branding or non-standard fonts for high-visibility reports?
A: No. All WSRs must adhere to the Template Registry corporate identity guidelines. Variations create cognitive load and brand dilution.

Q: If a project status changes to "Red" on Tuesday, should I resend the report?
A: No. Follow the "Immediate Escalation Protocol" (TR-OPS-ESC-002) for urgent blockers. The WSR is a sync point, not a notification system for emergencies.

Q: What is the maximum file size for distribution?
A: Files exceeding 10MB must be hosted on the internal Sharepoint portal with a link provided in the summary email to prevent mail server bloat.

End of Document
Authorized by: Julian Vance, Chief Architect, Template Registry