Skip to content
FRSign inBook a walkthrough
CAPAction PlansShared by every suite

Corrective and preventive actions, tracked to verified closure.

In 50 words

A corrective and preventive action (CAPA) fixes the cause of a problem and stops it coming back. In eAviora every action stays linked to the record it came from, the work is verified and the record says by whom, and by default a verified action closes only after an effectiveness review, a policy each organization can switch off.

Case file | ACT-2026-0224Stage 4 of 5, Effectiveness
  • Overview
  • Workflow
  • Linked
  • Discussion
  • History
An action, at its effectiveness check
01Assignment, done02Execution, done03Verification, done04Effectiveness, current05Closure, not reached
Linked toHAZ | AUD | SPI | Evidence Hub
Sample data | Northwind Air, a fictional airline
At a glance

The module, on one sheet.

Module sheet | CAP
SuiteShared by every suite | Shared Workspaces
RecordsACT actions and AEC effectiveness checks
Stages
01Assignment02Execution03Verification04Effectiveness05Closure
Raised fromOccurrences, hazards, findings, barrier ratings, indicator breaches, the risk profile and survey findings
OccurrencesHazardsFindingsBarrier ratingsIndicator breachesThe risk profileSurvey findings
PolicyAn effectiveness review before closure, on by default
  • An effectiveness review before closure, done
What it does

Four things, done on the record.

Linked to where it started
ACT-2026-0224Lower the 24R crosswind limitFrom hazard SMS-HAZ-2026-0031 | Effectiveness
ACT-2026-0241Countersign de-icing records at shift endFrom finding QMS-FND-2026-0118 | Execution
ACT-2026-0231Retrain the touchdown energy calloutsFrom barrier rating, Stable approach callouts | Verification
ACT-2026-0249Review the gust margin on all runwaysFrom indicator breach SPI-RW-07 | Assignment
ACT-2026-0107Inspect the main landing gearFrom occurrence SMS-OCC-2026-0412 | Closed
5 of 41 | Sample data | Northwind Air, a fictional airline
One action list, used by every module
01Linked to where it startedAn action raised from a record keeps that record as its source, so the fix and the problem stay together.
02Every step signed by nameThe record keeps who owned, verified, assessed and approved the action. A small team can do it all.
03A named approver closes itEvery closure names who authorised it, with the reason and anything still outstanding.
04Closed once it workedBy default a verified action closes after a review says the fix worked, or the review is waived on the record.
In the product

An action, at its effectiveness check.

Case file | ACT-2026-0224Stage 4 of 5, Effectiveness
  • Overview
  • Workflow
  • Linked
  • Discussion
  • History
On the recordThe deadline, and how long is left.
Deadline2026-11-30Left18 days
On track
The effectiveness checkThe measure of effectiveness and what it found.
AEC-2026-0031 | due 30 Nov | the verdict is recorded at the end of the window
On the recordThe people assigned.
OwnerA. Laurentcompleted the work 15 Oct
VerifierM. Tremblayverified 18 Oct
AssessorS. Okaforeffectiveness review
Sample data | Northwind Air, a fictional airline
The rule it holds

A verified action closes only after its effectiveness review.

  • On by default and switchable per organization; the review must come after verification, and effective, ineffective or waived all count.Action PlansHolds
03Verificationdone
04Effectivenesseffective, ineffective or waived all count
05Closureonly after the review
Questions buyers ask

Short answers.

Yes. One person may own, verify and close an action, and the record says who did each step. When a verifier is named, that person marks it verified.

Reading | SMS fundamentalsThe Closure Gate, Not the Checkbox: Defensible-by-Construction SafetyReading | SMS fundamentalsHow Airlines Can Connect Occurrence Reporting, CAPA, SPI and Safety Risk ProfilesReading | SMS fundamentalsWhat Happens After an Occurrence Report: The Six Stages
All of SMS fundamentals

See Action Plans on your own records.

A walkthrough with the people who build eAviora.