Routing Incident Template

# Routing Incident Template

This incident packet documents routing risk and resolution evidence. It does not prove that a form, endpoint, webhook, alert, CRM, sheet, or downstream system was fixed or confirmed.

## Incident summary

- Incident title:
- Discovered at:
- Discovered by:
- Issue description:
- First observed behavior:
- Expected behavior:

## Affected asset

- Asset name:
- Asset type:
- Asset URL:
- Owner team:
- Current status:

## Suspected failure class

Use one of: stale_endpoint, wrong_sheet, missing_hidden_field, alert_missing, webhook_mismatch, crm_destination_unknown, route_key_missing, form_unavailable, page_unavailable, destination_mismatch, evidence_missing, other.

## Evidence available

List approved evidence only. Do not include secrets or customer data.

## Evidence missing

List endpoint, field, route key, destination, alert, CRM, sheet, webhook, or resolution evidence still missing.

## Customer or lead-capture impact

Describe risk without inventing lost leads, submissions, or routing failures.

## Temporary workaround

Document proposed manual handling only. Do not claim it is active without confirmation.

## Resolution requirements

List evidence needed before claiming fixed or confirmed.

## Validation checklist

- Routing QA required.
- Hard-contract language required.
- Missing evidence listed.
- Next validation step named.

## Handoff checklist

- Owner team named.
- Target system named.
- Required fields listed.
- Missing fields listed.
- Next human or system action named.

## Status definitions

- open
- investigating
- workaround_ready
- awaiting_fix
- fix_claimed_unverified
- resolved_confirmed
- closed_no_action
- failed_downstream

Last updated: 2026-06-11T10:47:53Z