Escalation Paths | Resolve Blockers Quickly
Define escalation procedures so blockers and risks get resolved quickly. GitScrum's labels, automation rules, and workflows formalize your escalation process.
7 min read
When problems arise, teams need to know exactly how and when to escalate. Unclear escalation paths lead to issues festering, wrong people being bothered, or delays while figuring out who to contact. GitScrum helps formalize escalation with task labels, assignments, and notification workflows.
Escalation Challenges
| Problem | Impact | Solution |
|---|---|---|
| No clear path | Issues linger | Documented procedures |
| Fear of escalating | Problems grow | Blameless culture |
| Wrong escalation | Time wasted | Defined criteria |
| Escalation overload | Leaders overwhelmed | Proper thresholds |
| No tracking | Issues lost | GitScrum workflows |
Escalation Framework
Escalation Levels
ESCALATION HIERARCHY
════════════════════
LEVEL 0: SELF-RESOLUTION
├── Timeframe: 0-4 hours
├── Owner: Individual contributor
├── Actions: Research, ask teammates
└── Escalate if: No progress after 4h
LEVEL 1: TEAM LEAD
├── Timeframe: 4-24 hours
├── Owner: Technical/Team lead
├── Actions: Pair, reassign, unblock
└── Escalate if: Needs external team, authority
LEVEL 2: ENGINEERING MANAGER
├── Timeframe: 24-48 hours
├── Owner: Engineering manager
├── Actions: Cross-team coordination, priority
└── Escalate if: Resource conflicts, org issues
LEVEL 3: DIRECTOR/VP
├── Timeframe: 48-72 hours
├── Owner: Director or VP Engineering
├── Actions: Strategic decisions, major resources
└── Escalate if: Business-critical, exec needed
LEVEL 4: C-LEVEL
├── Timeframe: As needed
├── Owner: CTO/CEO
├── Actions: Emergency decisions, client escalations
└── This is the final escalation level
Escalation Triggers
WHEN TO ESCALATE
════════════════
AUTOMATIC TRIGGERS:
├── Blocked > X hours (by severity)
│ ├── Critical: 4 hours
│ ├── High: 8 hours
│ ├── Medium: 24 hours
│ └── Low: 48 hours
│
├── Customer-reported issue
├── Production incident
├── Security concern
└── Data integrity issue
MANUAL TRIGGERS:
├── Beyond my authority
├── Cross-team dependency
├── Need additional resources
├── Conflicting priorities
└── Technical disagreement
NEVER WAIT TO ESCALATE:
├── Security breach
├── Data loss
├── Customer commitment at risk
├── Legal/compliance issue
└── PR/reputation risk
GitScrum Escalation Setup
Escalation Labels
ESCALATION LABEL SYSTEM
═══════════════════════
LABELS:
├── escalation:level-0 (Blue) - Self-resolution
├── escalation:level-1 (Yellow) - Team lead
├── escalation:level-2 (Orange) - Manager
├── escalation:level-3 (Red) - Director
├── escalation:level-4 (Purple) - C-Level
SEVERITY LABELS:
├── severity:critical - Production down
├── severity:high - Major feature broken
├── severity:medium - Significant inconvenience
├── severity:low - Minor issue
STATUS LABELS:
├── escalation:pending - Awaiting response
├── escalation:active - Being worked
└── escalation:resolved - Issue fixed
Automation Rules
ESCALATION AUTOMATION
═════════════════════
RULE 1: Auto-Escalate Blocked Tasks
────────────────────────────────────
Trigger: Task has "blocked" label
AND: No activity for 24 hours
Action:
├── Add label "escalation:level-1"
├── Assign to team lead
├── Notify via Slack
└── Add comment with context
RULE 2: Severity-Based Escalation
────────────────────────────────────
Trigger: Task has "severity:critical"
AND: Status is "Blocked"
AND: No activity for 4 hours
Action:
├── Add label "escalation:level-2"
├── Assign to manager
├── Notify via Slack + Email
└── Create incident channel
RULE 3: Time-Based Escalation Chain
────────────────────────────────────
Trigger: Task has "escalation:level-1"
AND: No resolution for 24 hours
Action:
├── Update to "escalation:level-2"
├── Reassign to next level
├── Notify original assignee
└── Add to escalation report
Escalation Board View
ESCALATION DASHBOARD
════════════════════
┌─────────────────────────────────────────────────────────┐
│ Active Escalations Last updated: 2m │
├─────────────────────────────────────────────────────────┤
│ │
│ LEVEL 1 (5) LEVEL 2 (2) LEVEL 3 (1) │
│ ──────────── ──────────── ──────────── │
│ │
│ ┌──────────────┐ ┌──────────────┐ ┌────────────┐ │
│ │ API timeout │ │ Cross-team │ │ Client │ │
│ │ @mike 4h ago │ │ dependency │ │ contract │ │
│ │ severity:med │ │ @sarah 18h │ │ @cto 48h │ │
│ └──────────────┘ │ severity:hi │ │ severity: │ │
│ └──────────────┘ │ critical │ │
│ ┌──────────────┐ └────────────┘ │
│ │ DB migration │ ┌──────────────┐ │
│ │ @lisa 2h ago │ │ Vendor issue │ │
│ │ severity:hi │ │ @tom 36h │ │
│ └──────────────┘ │ severity:hi │ │
│ └──────────────┘ │
│ ... +3 more │
│ │
│ 📊 Avg Resolution: L1=6h | L2=20h | L3=48h │
│ │
└─────────────────────────────────────────────────────────┘
Escalation Procedures
How to Escalate
ESCALATION PROCEDURE
════════════════════
STEP 1: Document Current State
────────────────────────────────
In the task, add a comment:
## Escalation Request
**Issue**: Brief description
**Blocker**: What's preventing progress
**Tried**: What I've already attempted
**Impact**: Sprint goal / deadline / customer
**Ask**: What I need to proceed
**Urgency**: Time-sensitive? Why?
STEP 2: Apply Labels
────────────────────────────────
├── Add "blocked" label
├── Add appropriate severity
└── Add escalation level
STEP 3: Assign to Next Level
────────────────────────────────
├── Assign to team lead (L1)
├── Keep yourself as watcher
└── Add to escalation channel
STEP 4: Notify
────────────────────────────────
├── Slack message with task link
├── Brief summary of blocker
└── Clear ask for next step
Receiving Escalations
HANDLING ESCALATED ISSUES
═════════════════════════
WHEN YOU RECEIVE AN ESCALATION:
1. ACKNOWLEDGE (within 30 min)
├── Comment: "I've seen this, investigating"
└── Update status to show active
2. ASSESS (within 2 hours)
├── Understand the full situation
├── Identify what's really needed
└── Determine if you can resolve
3. ACT OR RE-ESCALATE
├── If you can resolve: Do it
├── If you need help: Get it
└── If beyond you: Escalate up
4. RESOLVE AND DOCUMENT
├── Fix the immediate issue
├── Remove escalation labels
├── Document resolution
└── Note any systemic issues
5. FOLLOW UP
├── Check if original work continues
├── Add to retro if systemic
└── Update procedures if needed
Escalation Communication
Templates
ESCALATION COMMUNICATION TEMPLATES
══════════════════════════════════
SLACK ESCALATION (Level 1):
────────────────────────────
🟡 ESCALATION - Level 1
Task: [Task Title](link)
Blocked: [Duration]
Issue: [One-line summary]
Impact: [Sprint goal / deadline]
Need: [Specific ask]
cc: @team-lead
ESCALATION (Level 2+):
────────────────────────
🔴 ESCALATION - Level 2
**Task**: [Task Title](link)
**Blocked Since**: [Date/time]
**Previous Escalation**: [L1 details]
**Issue**: [Summary]
**Business Impact**: [Customer / Revenue / Timeline]
**Needed Decision**: [Specific decision required]
**Options**:
1. [Option A] - [Tradeoffs]
2. [Option B] - [Tradeoffs]
**Recommendation**: [If you have one]
cc: @manager @director
Best Practices
For Escalation Paths
Anti-Patterns
ESCALATION MISTAKES:
✗ Waiting too long to escalate
✗ Escalating without context
✗ Escalating everything (boy who cried wolf)
✗ Skipping levels
✗ Not documenting resolution
✗ Blame when escalating
✗ No follow-through after resolution
✗ Not learning from patterns
Measuring Escalation Health
ESCALATION METRICS
══════════════════
TRACK MONTHLY:
├── Total escalations by level
├── Average time to resolution by level
├── Escalation sources (team/project)
├── Repeat escalations (same issue type)
└── Escalation rate vs. total tasks
HEALTHY PATTERNS:
├── Most issues resolved at L0-L1
├── L2+ escalations are rare
├── Resolution time decreasing
├── No repeat escalations for same root cause
└── Teams feel safe escalating
WARNING SIGNS:
├── Too many L2+ escalations
├── Same issues recurring
├── Escalations taking longer over time
├── Teams avoiding escalation
└── Escalation backlog growing