Incident management from first report to verified closure

An incident begins as a report, often originating from an observation that crossed the severity threshold. The system auto-titles the incident, captures evidence (photos, witness statements, equipment state), and routes it to the appropriate investigator based on type and location.

The investigator runs PEEPO first to identify contributing factors across People, Equipment, Environment, Process, and Organization. Each significant factor then gets a 5 Whys chain to drive to root cause. The combination produces both thorough and deep investigations.

Every root cause maps to a corrective or preventive action. Each action has a named owner, a deadline, and a required verification step. Closure requires evidence; signatures alone do not close a CAPA.

AI handles the repetitive work that slows investigators down. Auto-classification removes triage typing. Similar past incidents surface automatically from the historical record, giving investigators relevant context from the start. Suggested PEEPO focus areas reflect which categories most often contribute for similar incident types.

Once an investigation is complete, AI helps generate a draft CAPA plan that the investigator reviews and refines. The investigator still owns every decision; the system removes the empty-page problem.

When the same root cause shows up across multiple incidents, the original corrective action failed. Most operations never see this pattern because their investigation records sit in separate spreadsheets.

Haloehs runs recurrence detection continuously. When a new incident's root cause matches one previously closed, both the investigator and the safety manager are flagged. The previous CAPA is surfaced for review. The next corrective action is informed by the failure of the last one.