Live Event Streaming Ticket Escalation Checklist
Triage and resolve critical streaming degradation tickets during high-concurrency live entertainment broadcasts.
Use this template when live sports, concerts, or pay-per-view events suffer stream degradation, buffer spikes, or DRM failures. It generates a systematic triage and technical verification checklist for NOC and broadcast support engineers.
Role: Principal Broadcast Operations Engineer & Live Stream Incident Specialist
Context
- Streaming Platform: {{streaming_platform_name}}
- Live Event Profile: {{broadcast_event_type}}
- Incident Ticket ID: {{incident_ticket_id}}
- Geo/Playback Scope: {{affected_playback_regions}}
- CDN Infrastructure: {{cdn_provider_matrix}}
- Viewer Tier Impact: {{subscriber_tier_impact}}
Task
Generate a time-critical live incident triage and resolution checklist for ticket {{incident_ticket_id}} during {{broadcast_event_type}} on {{streaming_platform_name}}, ensuring streaming stability across {{affected_playback_regions}} without service interruption.
Method
- Extract telemetry metrics, player error codes, and manifest fetch patterns recorded in {{incident_ticket_id}}.
- Correlate reported error spikes against {{cdn_provider_matrix}} edge health logs and origin egress capacity.
- Map user impacts against {{subscriber_tier_impact}} to determine routing and failover prioritization.
- Construct an immediate ingress and origin health verification sub-checklist to rule out source encoder drift.
- Build an edge routing and CDN multi-homing reconfiguration sub-checklist targeted at {{affected_playback_regions}}.
- Formulate DRM license server throughput and key rotation validation steps.
- Detail player-side fallback verification checks (ABR ladders, audio sync, sub-second latency switches).
- Outline ticket communication milestone checks for executive dispatch and customer care scripting.
Constraints
- MUST prioritize non-disruptive remediation steps before recommending hard encoder restarts.
- MUST NOT suggest clearing CDN caches globally without targeting specific affected edge pops in {{affected_playback_regions}}.
- Every checklist item must include an operational owner, expected telemetry threshold, and pass/fail condition.
- Checklists must be executable within a 15-minute operational triage window.
Output format
- Executive Incident Summary: 1 concise paragraph (max 100 words).
- Tier 1: Origin & Ingestion Verification Checklist (4-6 actionable checkbox items).
- Tier 2: CDN Edge & Regional Routing Checklist (4-6 actionable checkbox items referencing {{cdn_provider_matrix}}).
- Tier 3: DRM, Manifest & Player Playback Checklist (4-6 actionable checkbox items).
- Ticket Closure & Runbook Update Action Items: 3 specific operational items.
Self-review
- Ensure every checklist item contains clear verification criteria.
- Verify all 6 context variables are deeply integrated into the steps.
- Check that no generic IT troubleshooting steps dilute broadcast-specific streaming protocols.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.