Project Status Report Template Red Yellow Green

SOP: Project Status Reporting Protocol (RAG Framework)

1. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the standardized methodology for status reporting at Template Registry. The purpose is to provide senior leadership with objective, data-driven visibility into project health, ensuring rapid identification of risks and consistent application of the Red-Yellow-Green (RAG) classification system.

2. Scope & Prerequisites

• Scope: Applies to all engineering and operational initiatives managed by Template Registry.
• Prerequisites: Access to Enterprise Project Management (EPM) software (Jira/Asana/Monday.com), valid credentials for the Centralized Status Dashboard, and read-access to the current Project Charter.
• Equipment: None (Virtual/Cloud-based).

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase 1: Metric Aggregation

• Extract raw velocity data and sprint burndown metrics from the EPM system.
• Audit "In Progress" vs. "Blocked" ticket counts.
• Verify budget burn-rate against the baseline forecast.

Phase 2: RAG Classification

Determine the status using the following objective thresholds:

• Green (On Track): Milestones met, budget variance < 5%, no critical blockers.
• Yellow (At Risk): Minor delays, budget variance 5–15%, emerging risks requiring management attention.
• Red (Critical/Blocked): Significant deadline breach, budget variance > 15%, or showstopper technical debt/resource unavailability.

Phase 3: Drafting & Dissemination

• Draft narrative summary (max 3 sentences) explaining the RAG status.
• Update the central status dashboard by COB Friday.
• Send status summary to stakeholders via the approved Template Registry reporting channel.

5. Quality Assurance & Pro-Tips

• Metric Integrity: Do not rely on "gut feeling." If a project is missing a milestone, it cannot be Green, regardless of team optimism.
• The "Red" Paradox: Red status is not a failure; it is an early-warning signal for assistance. PMs are encouraged to escalate to Red early to secure necessary resources before a hard deadline is missed.
• Threshold Discipline: Maintain consistent thresholds across the quarter. Arbitrary changing of RAG definitions renders aggregate data useless for quarterly business reviews (QBRs).
• Formatting: Maintain the standard 3-column view: Last Week's Wins, Current Risks, Next Week's Focus.

6. Frequently Asked Questions (FAQ)

Q: My project is Red due to external dependencies I cannot control. How should I report this?

• A: Mark as Red. In the risk narrative, explicitly define the dependency (e.g., "Vendor X API delivery") and the impact on the critical path. This shifts accountability to the vendor and triggers internal procurement/legal support.

Q: How frequently should I change a status from Yellow back to Green?

• A: Only when the underlying blockers are resolved and the critical path is demonstrably cleared. Do not flip-flop statuses within a 48-hour window; if the project is unstable, keep it Yellow until consistent progress is proven over a full sprint cycle.

Approved by: Julian Vance Chief Architect, Template Registry