Project Status Update Template Slide

SOP-TR-PRJ-042: Standardized Project Status Update Presentation

1. Document Control Block

---

2. Executive Summary & Purpose

This SOP mandates the structural and informational requirements for the Project Status Update template. The objective is to eliminate subjective reporting, ensure data parity across the Portfolio, and facilitate rapid decision-making for executive stakeholders.

---

3. Scope & Prerequisites

• Scope: Applies to all engineering, product, and operational projects under the Template Registry umbrella.
• Software Requirements: Template Registry Master Slide Deck (PPTX/Google Slides), access to Jira/Asana API reporting.
• Prerequisites: Validated project data from the current sprint/cycle; finalized financial burn metrics; updated risk registry.

---

4. Roles & Responsibilities (RACI)

---

5. Step-by-Step Procedure

Phase I: Data Extraction

• Pull actuals vs. baseline from the project management system.
• Export RAG (Red/Amber/Green) status for Schedule, Budget, and Scope.
• Extract top three blockers requiring escalation.

Phase II: Slide Construction

• Header: Insert Project Name, Reporting Period, and Reporting Owner.
• Executive Summary: Draft one sentence for Current Status, one for Outlook.
• KPI Dashboard: Populate the traffic-light system (RAG) based on current thresholds.
• Milestone Tracker: Plot current phase against the critical path.
• Risk/Issue Log: List only "High" severity risks impacting the critical path.

Phase III: Review & Validation

• Validate that all RAG markers align with the project management system.
• Ensure "Ask" section clearly identifies the specific decision required from stakeholders.
• Conduct final QA pass for formatting consistency (font, margins, color schema).

---

6. Quality Assurance & Pro-Tips

Best Practices

• The "So What?" Rule: If a slide element does not provide a basis for a decision or immediate action, remove it.
• Data Integrity: Never manually calculate metrics. Use linked source files (CSV/JSON connectors) to prevent transposition errors.

Common Pitfalls

• "Green-washing": Marking a project Green when there is a known delay. If there is a delay, it must be Amber with a recovery plan.
• Excessive Narrative: Use bullet points. Do not include full sentences in the executive summary area.

Metric Thresholds

• Budget Variance: >5% requires an automatic Amber status.
• Schedule Variance: >3 days against critical path requires an automatic Red status.

---

7. Frequently Asked Questions

Q: How do I handle a project that is trending Red?

• A: Do not hide the status. A Red status is an objective measurement of a need for resource intervention. Include a slide detailing the "Recovery Plan" and the specific resource or budget request needed to return to baseline.

Q: Can I customize the template layout?

• A: No. Template Registry maintains a strict visual identity for executive reporting. Use the provided master file only. Requests for structural changes must be submitted via the Internal Tools Request process.