posthog-escalation

To create an escalation brief, package the triage report findings into a structured markdown document. The brief includes severity, impact assessment, reproduction steps, and follow-up cadence to communicate context clearly to engineering.

The standard escalation format is a markdown document featuring sections for severity, impact assessment tables, evidence, reproduction steps, routing information, and follow-up cadence guidance to ensure complete context transfer.

Assess bug impact by generating an impact assessment table within the escalation brief. This table quantifies the breadth, depth, duration, revenue signal, and data risk associated with the support case.

Yes, you can route data integrity issues using the built-in routing matrix. The matrix maps specific issue types from the triage report to the appropriate PostHog engineering team for targeted resolution.

A markdown incident report for infrastructure problems should include triage evidence, impact assessment, reproduction steps, routing information, and de-escalation criteria to align stakeholders on the resolution cadence.

You need a formal escalation brief when a triage report recommends escalation for a bug, data issue, or infrastructure problem. It standardizes context, evidence, and next steps so engineering receives a complete package.