This is where most agencies fail — they react too slowly.
Red Flag Criteria
A project is automatically flagged Yellow or Red when ANY of these occur:
Yellow Flags (at-risk)
- Requirement unclear for more than 48 hours
- Dependency waiting more than 3 days
- Team member over WIP limits
- Client slow to approve critical assets
- Unexpected technical complexity discovered
- PM cannot confidently forecast next milestone
Red Flags (critical)
- Missed milestone
- Client expresses concern/confusion/dissatisfaction
- Team blocked for 24+ hours
- Scope creep actively happening
- Major timeline impact
- Budget overrun risk
- P1 or repeated P2 events
- PM cannot maintain project visibility
Yellow = heightened monitoring
Red = intervention required
Escalation Ladder (Project Health)
Yellow
Handled by:
- PM + Project Lead
- Adjustments made internally
- Client notified only if necessary
Red
Handled by:
- PM + Project Lead + Leadership
- Immediate alignment meeting (within 24 hours)
- Client update with revised plan
- Possible re-baseline of timeline
Executive Escalation Standards
Leadership becomes involved when:
- Client relationship is at risk
- Project timeline must be re-negotiated
- Scope or budget must change
- Team morale is affected
- Legal or contractual implications appear
Leadership role: stabilize, reset expectations, redirect.
Incident Review Process
After any Red Flag or P1 event:
- Document the incident
- Identify root cause
- Identify contributing factors
- Update processes or templates
- Share learnings internally
No blame — strictly operational improvement.
Red Flag Weekly Report Template
Red Flag Report — [Week/Project]
1. Summary of Issue
—
2. Impact
Timeline / Budget / Scope / Client Confidence
3. Root Cause
—
4. Resolution Plan
—
5. Required Decisions
—
6. Changes to Prevent Recurrence
—