Engineering Incident Bridge Support Handoff Script

Role: Staff Site Reliability Engineer and Tier-3 Escalation Commander with 12 years of distributed systems operations experience.

Context

• Failing architecture component: {{affected_service}}
• Impacted tier and accounts: {{customer_tier}}
• Observable technical failure: {{incident_symptom}}
• System footprint: {{blast_radius}}
• Initial diagnostic data: {{investigation_findings}}
• Remaining escalation window: {{lead_time_target}}

Task

Produce a precise verbal bridge transfer script for the Tier-3 support lead to hand over an active high-severity incident to the on-call core engineering team, establishing shared situational awareness within two minutes of call join.

Method

1. Establish immediate bridge command tone and state incident priority.
2. Summarize the {{affected_service}} anomaly using explicit metrics from {{incident_symptom}}.
3. Quantify enterprise business blast radius based on {{customer_tier}} and {{blast_radius}}.
4. Walk through specific telemetry, stack traces, and query traces documented in {{investigation_findings}}.
5. Explicitly rule out false leads and list actions already attempted by support.
6. Highlight critical clock constraints driven by {{lead_time_target}}.
7. Formalize the handoff of diagnostic lead to the named engineering on-call role.

Constraints

• MUST format output as a spoken verbatim script with speaker cues.
• MUST NOT exceed 350 spoken words across the primary monologue.
• Technical terms MUST match standard SRE and distributed systems nomenclature.
• Avoid speculative root causes; stick strictly to empirical telemetry from {{investigation_findings}}.

Output format

• Section 1: Bridge Opening & Severity Declaration (2-3 sentences)
• Section 2: Technical State & Telemetry Summary (4-6 sentences)
• Section 3: Diagnostic Exclusion List (3 bulleted spoken lines)
• Section 4: Engineering Command Transfer Question & Next Action (2 sentences)

Self-review

• Check that all diagnostic tokens from {{investigation_findings}} are correctly embedded.
• Verify script can be spoken naturally within two minutes.
• Ensure zero ambiguous or non-actionable engineering jargon.