Incidents

Incidents

Purpose

This page records and reviews significant events so teams can maintain an accurate timeline and support compliance reporting.

Prerequisites

  • Relevant alerts or actions should already be available.
  • Users need access to view and update incident records.
  • Evidence sources (logs, notes, attachments) should be ready.

Main Actions

  • Create or review incident records.
  • Capture timeline details and affected scope.
  • Link supporting alerts and corrective actions.
  • Finalize incident outcomes for audit and reporting.

Field/Status Reference

  • Incident Status: Current stage (for example open, under review, closed).
  • Severity/Impact: Business or safety impact level.
  • Timeline: Ordered events showing what happened and when.
  • Linked Records: Connected alerts and corrective actions.
  • Outcome Summary: Final findings and prevention notes.

Workflow

  1. Open an incident when escalation criteria are met.
  2. Add event timeline entries with timestamps.
  3. Link supporting alerts and corrective actions.
  4. Review findings with stakeholders.
  5. Close the incident once outcome and prevention actions are documented.

Connections

  • Aggregates data from Temperature Checks and Corrective Actions.
  • Supports downstream reporting, audit readiness, and policy reviews.
  • Can inform updates to threshold settings, procedures, or training.

Common Mistakes

  • Delaying timeline updates until details are forgotten.
  • Closing incidents without linking the related action history.
  • Omitting impact notes needed for management review.

Troubleshooting

  • If timeline entries seem incomplete, verify linked records and filters.
  • If status changes are blocked, check role permissions and required fields.
  • If audit data looks inconsistent, reconcile timestamps and ownership notes.

Quick Tips

  • Log events as they happen, not at end of shift.
  • Keep incident summaries factual and concise.
  • Capture prevention actions before closing the record.