One Page Project Status Report Template Powerpoint

SOP-PM-042: One-Page Executive Status Report (PPTX)

1. Executive Summary & Purpose

This procedure defines the standardized format and data-injection protocol for the "One-Page Executive Status Report." The purpose is to provide stakeholders with high-signal, low-latency project health visibility, facilitating rapid decision-making while eliminating narrative bloat.

2. Scope & Prerequisites

• Scope: All active projects within the Template Registry portfolio.
• Software Requirements: Microsoft PowerPoint (v.365), Adobe Fonts (DIN Next), Corporate Template TR_Executive_Dashboard.potx.
• Data Source: Project Management Information System (PMIS) (e.g., Jira, Asana, or Azure DevOps).

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase I: Data Extraction & Verification

• Export raw metrics from PMIS (Milestone status, Budget Burn, Resource Utilization).
• Validate "Actual vs. Plan" variance against the baseline.
• Identify top 3 critical risks with associated mitigation strategies.

Phase II: Dashboard Construction

• Open TR_Executive_Dashboard.potx.
• Update Project Pulse (RAG Status: Red/Amber/Green) based on objective metrics.
• Populate Key Milestones (Limit to 5 upcoming items).
• Insert Budget Burn chart (Actuals vs. Forecast).
• Summarize Blockers/Escalations using the "Impact-Action" syntax.

Phase III: Quality Review & Distribution

• Perform "Self-Correction Check": Ensure all text is legible at 10ft/10sec viewing.
• Verify hyperlinks to source documentation are functional.
• Export final document as PDF (Size: < 2MB).
• Distribute to project distribution list via encrypted internal channel.

5. Quality Assurance & Pro-Tips

• The 10-Second Rule: If a stakeholder cannot identify the project health (RAG status) and the primary blocker within 10 seconds, the slide is over-engineered.
• Metric Thresholds:
  • Green: All KPIs on track; budget variance < 5%.
  • Amber: Slippage of 1-2 weeks on non-critical path; budget variance 5-10%.
  • Red: Critical path impact; budget variance > 10% or scope creep requiring Steering Committee intervention.
• Pro-Tip: Never use bullet points for status. Use "Current State" vs "Target State" to illustrate momentum.

6. Frequently Asked Questions (FAQ)

Q: Should I include detailed gantt charts in the one-page report? A: No. Use a placeholder link to the live PMIS Gantt view. The One-Pager is for executive-level trajectory, not task-level auditing.

Q: If the project is "Red," how should I handle the presentation? A: Lead with the recovery plan. Red status is acceptable if paired with a clear, time-bound mitigation strategy. Never present a Red status without a recovery path.

Authorized by: Julian Vance, Chief Architect