Incident Report Template

Per-incident template. Each robot’s incident-response page should adapt this to point at the correct Google Form and Slack channel.

---
title: <Incident or Issue Category>
status: stub
applies_to:
  - go2                       # or vega, shared
audience:
  - operator
visibility: restricted_ops
approval_status: draft
owner: TBD
last_source_check: TBD
related_issue_forms: []
related_dashboards: []
escalation_path: []
---

Required body sections

Trigger

What conditions require filing this incident type.

Severity

Per-deployment severity ladder (link to deployment-specific severity definition).

Required fields

What the incident report must capture: timestamp, location, robot state, observed symptoms, corrective actions, environmental factors, photographic evidence.

Where to submit

Google Form URL or library link to /apps-and-tools/issue-reporting/.

Who to notify

Slack channel, on-call rotation, management direct (if time-critical).

Follow-up

Was a reboot required? Re-mapping? Localization recovery? Link to the corresponding troubleshooting SOP.

Source notes

• [SOURCE: ...] — the originating SOP or operations manual that defines this incident category.