Preventive action¶
A planned management-system change that identifies and reduces the likelihood of a potential nonconformity before it occurs, then monitors whether the intervention was effective.
Core Idea¶
A preventive action changes a management or technical system before an anticipated nonconformity occurs. The target is not an existing defective product but a supported vulnerability revealed by trend analysis, risk assessment, proficiency testing, audit observation, customer suggestion, or comparable evidence.
A complete action moves from risk identification to a responsible plan, implementation, controls, and an effectiveness check. It may also improve efficiency, but ordinary improvement is not enough unless the intervention is tied to avoiding a plausible nonconformity. Once the failure has occurred, containment, correction, and corrective action answer a different temporal problem.
Structural Signature¶
Sig role-phrases:
- potential nonconformity. Names a credible future failure or weakness before occurrence. Constitutive target. If altered: An already observed failure instead calls for correction or corrective action.
- risk evidence. Supports likelihood or consequence through trends, audits, suggestions, or tests. Constitutive basis. If altered: An unsupported improvement preference lacks a preventive rationale.
- planned change. Modifies process, design, control, training, or management system. Constitutive intervention. If altered: Merely recording the risk is not action.
- implementation owner. Assigns responsibility, timing, and resources. Central execution role. If altered: An unowned recommendation may never alter the system.
- effectiveness check. Monitors whether likelihood or vulnerability was reduced. Constitutive closure. If altered: Completion alone does not establish prevention.
What It Is Not¶
- Corrective action. Has the nonconformity already occurred?
- Correction. Is only the immediate defect fixed?
- Continuous improvement. Is a future failure risk identified?
- Risk assessment. Was a controlled change implemented?
Scope of Application¶
Use preventive action for prospective, evidence-based controls with an identified owner and measured follow-up.
- Quality management. Reduces future nonconformance risk.
- Laboratories. Uses trends and proficiency tests.
- Manufacturing. Changes processes before defects.
- Services. Prevents recurring service breakdowns.
- Safety systems. Controls credible precursors.
Clarity¶
The defining boundary is temporal and causal: the failure is potential, while the weakness and intervention are present.
Manages Complexity¶
Risk estimates are uncertain and changes can introduce new risks. Evaluation should compare the intended risk reduction with side effects and avoid claiming that nonoccurrence alone proves causality.
Abstract Reasoning¶
- Define the potential nonconformity precisely.
- Document evidence for its likelihood and consequence.
- Select a change aimed at the relevant weakness.
- Assign responsibility and implement controls.
- Measure effectiveness and unintended effects.
Knowledge Transfer¶
Prospective risk reduction transfers to safety and reliability, but management-system nonconformity, documented change, and effectiveness review delimit preventive action. The nearest stopping boundary is explicit: Corrective action is closest: it removes causes after a nonconformity has occurred, whereas preventive action acts on a potential cause before occurrence. The inclusion test remains: An intervention is preventive action when it responds to supported future nonconformity risk before the failure occurs and includes implementation plus effectiveness review. The structure no longer applies when the case exits when the targeted failure has already happened or no controlled change and follow-up are implemented.
Examples¶
Canonical¶
Trend data show calibration drift approaching tolerance although no result has failed. A laboratory shortens the calibration interval, assigns implementation, and monitors subsequent drift rates.
Mapped back: potential nonconformity → future out-of-tolerance results; risk evidence → drift trend; planned change → shorter interval; implementation owner → laboratory quality lead; effectiveness check → subsequent drift monitoring.
Applied / In Practice¶
A defective batch is quarantined and its machine repaired after the defect appears; that is containment and corrective action, not preventive action for the already realized event.
Mapped back: potential nonconformity → already realized; risk evidence → defective batch; planned change → repair; implementation owner → production team; effectiveness check → post-repair verification.
Structural Tensions¶
T1: early action vs. uncertain risk. Acting early avoids loss but evidence before failure is incomplete. Diagnostic: What signal justifies intervention now?
T2: standardization vs. change risk. A preventive modification can create new failure modes. Diagnostic: How are unintended effects monitored?
Structural–Framed Character¶
Description turns on potential nonconformity, risk evidence, planned change, implementation owner, effectiveness check. Skeletal core. A precursor signal triggers an intervention before an adverse event and is followed by outcome monitoring. Domain-bound accent. Nonconformity, management systems, risk plans, controls, and effectiveness checks define the practice. Transfer remains bounded because Why not prime. Prospective intervention is portable; this is quality-system preventive governance. The negative boundary is concrete: Any repair, containment, complaint response, retrospective correction, generic improvement, risk register entry, or wish to avoid failure is not automatically preventive action. Preventive action is operational-causal: risk evidence motivates a controlled intervention whose future effect must be monitored. Its character: changing a system before a supported nonconformity occurs.
Structural Core vs. Domain Accent¶
Skeletal core. A precursor signal triggers an intervention before an adverse event and is followed by outcome monitoring.
Domain-bound accent. Nonconformity, management systems, risk plans, controls, and effectiveness checks define the practice.
Why not prime. Prospective intervention is portable; this is quality-system preventive governance.
Instantiates / Related Primes¶
- Risk management. Risk evidence motivates the action.
- Corrective action. It responds after a failure and marks the nearest boundary.
- No strict parent is asserted.
Neighborhood in Abstraction Space¶
Preventive action sits in a crowded region of the domain-specific corpus (27th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.
Family — Strategic Decision Biases & Mechanisms (29 abstractions)
Nearest neighbors
- Business performance management — 0.90
- Risk Score — 0.89
- Ex nunc — 0.89
- Face validity — 0.89
- Outside Context Problem — 0.89
Computed from structural-signature embeddings · 2026-10-08
Not to Be Confused With¶
- Corrective action. Tell: Has the nonconformity already occurred?
- Correction. Tell: Is only the immediate defect fixed?
- Continuous improvement. Tell: Is a future failure risk identified?
- Risk assessment. Tell: Was a controlled change implemented?
References¶
- Frozen Wikipedia discovery revision: https://en.wikipedia.org/wiki/Preventive_action (revision 1321849983).
- Preserved source candidate: http://www.matlensilver.com/blog/post/the-pa-part-of-capa.html
- Preserved source candidate: https://web.archive.org/web/20130602024240/http://www.matlensilver.com/blog/post/the-pa-part-of-capa.html
- Preserved source candidate: http://www.qualitysystems.com/support/pages/preventive-action
- Preserved source candidate: https://web.archive.org/web/20151102050059/http://www.qualitysystems.com/support/pages/preventive-action
- Preserved source candidate: https://www.bizmanualz.com/improve-management-systems/what-are-the-top-ten-preventive-actions.html
- Preserved source candidate: http://sunnyday.mit.edu/papers/cacm232.pdf
- Preserved source candidate: http://www.web-strategist.com/blog/2013/01/14/the-difference-between-strategy-and-tactics/
- Preserved source candidate: http://www.skybrary.aero/index.php/Toolkit:Systems_Thinking_for_Safety/Systems_Theoretic_Accident_Model_and_Processes_%28STAMP%29
The frozen Wikipedia revision is discovery provenance. The retained source set was reviewed for identity, formal or operational relation, and scope. The encyclopedia's structural synthesis is bounded to those claims; a thin authority surface is recorded as a nonblocking source-strengthening repair rather than concealed.