Traffic Light Project Status Report Template

Standard Operating Procedure: Traffic Light Project Status Reporting

Document ID: SOP-PMO-TLR-001
Effective Date: 2023-10-27
Version: 1.0.0
Review Cadence: Semi-Annual

1. Executive Summary & Purpose

This SOP establishes the standardized methodology for the "Traffic Light" (Red/Amber/Green) status reporting protocol at Template Registry. The purpose is to provide stakeholders with a high-fidelity, instantaneous visualization of project health, ensuring risk mitigation and resource alignment occur at the point of inflection.

2. Scope & Prerequisites

• Scope: All enterprise-level projects under the Template Registry PMO portfolio.
• Prerequisites:
  • Access to centralized Project Management Information System (PMIS).
  • Defined baseline schedule and budget.
  • Software: Jira/Asana (or sanctioned equivalent) and Template Registry Reporting Suite (TRRS).
• PPE: N/A (Digital environment).

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase 1: Data Aggregation & Validation

• Extract quantitative data (Schedule Variance/Cost Variance) from PMIS.
• Cross-reference current milestones against the approved baseline.
• Confirm Resource Utilization rates are within +/- 10% of planned allocation.

Phase 2: Status Assignment (The Protocol)

• Green: Project on track; budget/scope/schedule within defined variance thresholds.
• Amber: Issues detected; mitigation plan in place; potential impact to milestone date or budget.
• Red: Critical failure; variance >15%; immediate steering committee intervention required.

Phase 3: Documentation & Escalation

• Populate the "Status Summary" block with the determined color code.
• Draft "Executive Brief" (Max 3 sentences: Current status, primary blocker, required action).
• Submit to PMIS dashboard for automated distribution.

5. Quality Assurance & Pro-Tips

• Metric Thresholds:
  • Schedule Variance (SV): >10% negative requires mandatory Amber status.
  • Budget Variance (CV): >5% over-burn requires immediate financial impact assessment.
• Pro-Tip (Vance’s Law): Never report a "Red" status without a corresponding "Recovery Plan." A status without a solution is merely noise.
• Common Pitfall: The "Watermelon Effect"—projects that appear Green on the outside but are Red on the inside. Combat this by demanding evidence of completed artifacts, not just "percentage complete" estimates.

6. Frequently Asked Questions

Q: Can a project remain "Amber" indefinitely?
A: No. An Amber status implies an active mitigation effort. If the issue remains unresolved after one reporting cycle (weekly), it must be escalated to the Program Director or reclassified to Red.

Q: How do we handle subjective project health?
A: Subjectivity is the enemy of systemic precision. Every status report must be anchored to the "Project Health Scorecard" (Schedule, Budget, Scope, Quality). If three of four metrics are Red, the project is Red, regardless of sentiment.

Q: What is the primary indicator of a project slipping into Red?
A: Velocity degradation. If your sprint velocity or milestone completion rate drops for two consecutive cycles, trigger a pre-emptive status review.

End of Document. Authored by Julian Vance, Chief Architect.