Tier 3 Engineering Escalation Readiness Checklist

Role: Senior Technical Escalation Engineer with deep expertise in full-stack debugging, SaaS architecture, and bug triage workflows.

Context

• Target Software Component: {{saas_platform_component}}
• Customer Contract Tier: {{customer_tier}}
• Defect Description: {{reported_defect_summary}}
• Testing Environment: {{reproduction_environment}}
• Response SLA Window: {{service_level_agreement}}
• Diagnostic Evidence Attached: {{telemetry_logs_available}}

Task

Produce an actionable Tier 3 escalation readiness checklist that verifies reproduction steps, captures required telemetry, assesses customer impact, and structures the ticket for immediate engineering action without back-and-forth communication.

Method

1. Analyze {{reported_defect_summary}} against {{saas_platform_component}} to determine expected versus actual behavioral discrepancies.
2. Evaluate {{telemetry_logs_available}} to confirm the presence of error stack traces, correlation IDs, and payload examples.
3. Map reproduction criteria within {{reproduction_environment}} to isolate software build version, configuration flags, and browser or API client dependencies.
4. Score business blast radius using {{customer_tier}} and align resolution urgency with {{service_level_agreement}}.
5. Draft explicit pre-escalation validation tasks covering account permissions, feature gating, and database state verification.
6. Structure a deterministic set of gating checks that the support engineer must sign off on before tagging engineering.
7. Detail fallback diagnostic procedures if the issue fails to reproduce in staging environments.
8. Formulate a clean handoff summary template to paste directly into the engineering issue tracker.

Constraints

• MUST include explicit pass/fail check boxes for environment isolation and log completeness.
• MUST NOT leave reproduction steps subjective or open to interpretation.
• Handoff instructions must strictly adhere to the response targets in {{service_level_agreement}}.
• Exclude speculative root causes; focus exclusively on verifiable diagnostic data and steps.

Output format

1. Escalation Metadata Overview (summary table of platform component, severity, and SLA)
2. Pre-Handoff Technical Verification Checklist (8-12 numbered checkbox items grouped by Environment, Logs, and Reproduction)
3. Engineering Dispatch Package (formatted markdown template for the engineering ticket body)
4. Immediate Workaround Assessment (short checklist for interim customer unblocking) Total word count must stay between 350 and 550 words.

Self-review

• Are all 6 context variables explicitly incorporated into the verification criteria?
• Is every checklist item binary and verifiable by a support engineer?
• Does the checklist prevent escalations lacking actionable logs or reproduction steps?