Home/ Product/ CAPA

Corrective. Preventive. Closed.

Structured root-cause analysis, owner-assigned corrective actions, preventive measures that survive past the fix. Every CAPA stays linked to whatever raised it — incident, audit finding, NCR, drill or MoC.

RCA tools built-in Owner-assigned actions Action register sync Evidence attachments Source-linked audit trail
The problem

"CAPA" in most tools means a textarea and a due date.

A real CAPA has a root cause, distinct corrective actions (fix the symptom), preventive actions (stop recurrence), assigned owners, evidence of closure, and an effectiveness check. ENSURE captures all of that as structured data — not as one big "Notes" field someone fills in 10 minutes before an audit.

Root cause, captured properly

Drop into 5-Whys or Fishbone for structured root-cause analysis. The result is searchable, reportable data — not paragraphs the auditor has to read line by line.

  • 5-Whys with chained question/answer pairs
  • Fishbone with categorised contributing factors
  • Root cause classification (system / process / human / external)
CAPA-029
IN PROGRESS
Root cause
No handover protocol between shifts at the Bay 4 wet-process line.
CATEGORY · PROCESS METHOD · 5-WHYS

Owner-assigned actions, synced to the Actions register

Every corrective and preventive action gets an owner from your user list, a due date, a status. They land in the central Actions register automatically — bidirectional live sync — so the assignee finds them alongside actions raised from incidents, NCRs and MoCs.

  • User picker for owner — no free-text names
  • Marking complete from either side propagates instantly
  • Per-org SHA-256 cache on attachments
Corrective actions
JD
Write shift handover protocol
J. Davies · due 22 May · ACT-091
OPEN
MT
Train wet-process operators
M. Tan · due 29 May · ACT-092
IN PROGRESS
Synced to Actions register LIVE ↻

Evidence is mandatory before closure

Upload the signed procedure, the training certificate, the inspection photo. Without evidence on each completed action, the CAPA can't be closed.

  • File attachments on every action row (PDF, image, doc)
  • Photo uploads auto-resize to 2000px / quality 0.82 before upload
  • Evidence preserved in the audit trail forever
ACT-091
Update SOP-014
DONE
Evidence attached
PDF
sop014_v3.pdf
214 KB
IMG
training_log.png
312 KB · resized from 4.1 MB

Source link survives forever

Every CAPA remembers what raised it — INC-014, AUD-002, NCR-009, DRILL-003 or MOC-007. Auditors can walk the trail from finding to root cause to corrective action to closure evidence in three clicks.

Raised from
INC-014 Slip on wet floor · Bay 4
AUD-002 Internal audit Q1
CAPA-029
IN PROGRESS
Root cause + corrective + preventive
Spawned
MOC-007 Floor coating · permanent change
Connected to everything else

CAPA is rarely the start, never the end.

In ENSURE, a CAPA sits in the middle of a longer trail. It's raised by something upstream and feeds something downstream. The links are preserved on both sides.

AUD-002
Audit finding
Major non-conformity — Clause 8.2
CAPA-029
CAPA
RCA · Corrective · Preventive · Evidence
ACT-091
Action
Owner-assigned, due-dated, status-tracked
MOC-007
MoC (if needed)
Permanent process change with full approval

Stop closing CAPAs that don't actually fix anything.

Structured RCA, owner-assigned actions, mandatory evidence. Book a 30-minute demo and we'll walk it through on your workflow.

Book a demo Book a demo →