Home/ Product/ Incidents

First incident logged in 41 seconds.

A structured 5-step investigation pipeline — Raised → Immediate Actions → Risk Assessment → Investigation → Interim Controls → Closed. Offline-capable photo capture on-site. Auto-escalates to CAPA by severity.

5-step investigation Offline photo capture 5-Whys + Bowtie RCA Auto-CAPA escalation Cross-module trail
The problem

Incident forms that take 30 minutes to fill out don't get filled out.

The most expensive incident is the one nobody logged. Most platforms make logging an incident a multi-screen, every-field-required ordeal. ENSURE's raise form takes about 40 seconds — the rest of the investigation happens asynchronously through the pipeline.

Raise in 41 seconds. Investigate over days.

The raise step captures the minimum: what happened, where, severity tier, photos. Everything else — risk assessment, RCA, interim controls — happens in subsequent steps, with the right people pulled in at each.

  • 5 short steps with auto-save drafts
  • Step stepper shows progress; later steps unlock as earlier ones close
  • Each step has its own owner — no single bottleneck
Incident · INC-014
Slip on wet floor · Bay 4
HIGH
1
Raised DONE
2
Immediate actions DONE
3
Risk assessment IN PROGRESS
4
Investigation (RCA)
5
Interim controls

Offline-capable photo capture

Lose WiFi in a tank farm, a basement, on a rooftop? The camera input keeps working — photos queue in an in-memory outbox and upload when you reconnect. Client-side resize keeps the storage footprint reasonable.

  • Rare at SMB price points — usually an Enterprise-only feature
  • Photos resized to 2000px / quality 0.82 before upload (typical 4 MB → 300 KB)
  • Outbox UI shows "offline" badge until reconnect + flush
Photo evidence
OFFLINE
QUEUED
QUEUED
QUEUED
3 photos queued ~890 KB
Will upload on reconnect

RCA tools, not free-text boxes

The Investigation step gives you structured 5-Whys and Bowtie diagrams — not a single "Root Cause" textarea where someone writes "human error" and moves on.

  • 5-Whys: chained question/answer pairs
  • Bowtie: threats, top event, consequences, barriers
  • Both saved as structured data, included in the close-out PDF
Step 4 · 5-Whys analysis
1
Slip on wet floor
2
Spill not cleaned
3
No reporting system
4
Shift handover gap
5
No handover protocol ROOT CAUSE

Auto-escalates to CAPA by severity

High actual severity, high potential severity, or repeat detection → ENSURE auto-creates a CAPA on close, linked to the incident with the source_reference preserved. Lower-severity events close without forcing a CAPA.

  • Severity matrix configurable per org
  • Auto-CAPA only when criteria are met — not by default
  • Manual escalate button always available
INC-014
HIGH
SEVERITY · HIGH REPEAT · TRUE
Auto-escalation
CAPA-029
CREATED
Root cause analysis required
Source: INC-014 · linked in audit trail
Connected to everything else

An incident is rarely a single record.

Investigation finds gaps that need formal change control. Interim controls become permanent. New hazards land in the risk register. ENSURE preserves every link.

INC-014
Incident
Slip on wet floor — Bay 4, severity High
CAPA-029
CAPA
Root cause + corrective + preventive action
MOC-007
MoC
Permanent floor coating change — 6-step workflow
RISK-038
Risk Register
Slip risk re-scored after MoC closure

Stop losing incidents to forms nobody completes.

41 seconds to raise. Full investigation over the days that follow. Book a 30-minute demo and we'll walk it through on your workflow.

Book a demo Book a demo →