Corrective Action Request¶
A quality-system artifact — instantiates Compensating Transaction
A formal request raised against a defect or nonconformance that drives it to root cause, demands a corrective action, and stays open until the cure is verified effective.
A defect that has already shipped or already occurred cannot be un-made — the nonconforming parts are on the line, the incident happened. A Corrective Action Request (CAR) is the formal instrument that refuses to let such a nonconformance be quietly patched and forgotten: raising one opens a tracked record that demands the responsible party find the root cause, commit to a corrective action, and prove the cure actually worked before the request can close. Its defining feature is the closed loop with a learning obligation at its center — a CAR is not satisfied by fixing the symptom; it is satisfied only when the cause is understood, addressed, and the fix is verified effective, so the same failure does not recur.
Example¶
An assembly plant discovers that a batch of brackets from a supplier is drilled ≈0.4 mm out of position — enough to fail final fit. The parts are already received and partly consumed; the effect can't be reversed. Quality raises a Corrective Action Request against the supplier. The CAR is the trigger that formalizes the demand and starts the clock. The supplier works it through the disciplines of a structured 8D response: contain the suspect stock, drive to the root cause (a worn drilling jig that drifted over a production run), implement the corrective action (jig replacement plus an added in-process gauge check), and — critically — the CAR stays open until effectiveness verification: a run of subsequent lots measured in-position confirms the cause is actually gone. Only then does quality close the request. The root cause and the evidence are captured on the record, feeding the supplier's own prevention.
How it works¶
The CAR is raised against a specific, evidenced nonconformance — it is a governed trigger, not an informal complaint, and it names an accountable respondent and due date. It then forces a progression the respondent cannot skip: containment of the immediate effect, root-cause analysis to the actual cause rather than the symptom, a defined corrective action, and effectiveness verification that checks the cure held over subsequent output. The request remains open — visibly, in the quality system — until verification passes, which is what stops premature closure. The root cause and verification evidence are recorded on the CAR itself, making it both a repair instrument and a learning artifact.
Tuning parameters¶
- Root-cause depth — how far analysis must go (symptom, proximate cause, or systemic cause). Deeper analysis prevents recurrence but slows closure and costs investigation effort.
- Containment urgency — how aggressively suspect output is quarantined before the cause is known. Fast containment limits spread; over-containment halts good product too.
- Effectiveness-verification window — how long and how much subsequent output must be checked before the CAR closes. A longer window catches drift; a shorter one closes faster but risks reopening.
- Escalation threshold — severity or recurrence level at which a CAR escalates to a formal supplier or systemic review. Lower thresholds catch patterns early but generate more escalations.
When it helps, and when it misleads¶
It is the right tool wherever a nonconformance must be driven to cause and proven fixed, not merely reworked — supplier quality, regulated manufacturing, and any ISO 9001-style corrective-action system rely on it precisely because it forecloses the fix-and-forget reflex.[1]
It misleads when the loop is run for compliance theater — a root cause written to satisfy the form ("operator error," "will re-train") and an effectiveness check that never really tests recurrence — so the CAR closes without the cause being touched. The classic misuse is closing on the corrective action taken rather than the corrective action verified effective, which lets the same defect return under a new ticket. The discipline is to hold the request open on evidence of effectiveness and to treat a recurrence as a reopened, escalated CAR rather than a fresh one.
How it implements the components¶
compensation_trigger— raising the CAR is the formal trigger that starts repair against an evidenced nonconformance, rather than an ad-hoc fix.failure_learning_record— the mandated root-cause analysis, captured on the request, turns the event into recorded learning that feeds prevention.reconciliation_verification— the effectiveness check gates closure: the CAR stays open until subsequent output proves the cause is actually gone.
It does not scope, sequence, and staff the corrective work toward a stated end-state — that is Remediation Plan — nor aggregate actions and residual risk across many incidents, which Incident Corrective Action Register owns.
Related¶
- Instantiates: Compensating Transaction — it is the archetype cast as a formal, closed-loop request that ends only on verified cure.
- Sibling mechanisms: Remediation Plan · Incident Corrective Action Register · Contract Cure Provision · Operational Reconciliation Workflow · Saga Pattern · Financial Reversal or Credit · Service Recovery Playbook · Customer Make-Whole Credit · Clinical Correction Protocol
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: A corrective-action request remains open against an evidenced nonconformance while accumulating ownership, containment, root cause, cure, deadlines, and effectiveness verification, so its operative form is an accountable case record.
Nearest alternative: Protocol, Workflow & Routine — The request forces an ordered repair progression, but the persistent open item and its evidence history are what prevent skipped steps and premature closure.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Single lineage
Present-day reach: Specialized
Rationale: Industrial quality assurance cohered formal corrective-action requests that require root-cause analysis, durable remedy, and effectiveness verification for nonconformance.
Related originating lineages:
- Organizational & Management Science — Quality-management systems institutionalized assignment, escalation, supplier response, and tracked closure of CARs.
Review resolution: A CAR is a specialized quality-engineering artifact even though organizational governance commonly owns and escalates it; broad transfer does not change its disciplinary provenance.
Review outcome: Reconciled after independent review; high confidence.
References¶
[1] Corrective (and preventive) action — CAPA — is a core requirement of quality standards such as ISO 9001; structured responses like the 8D (Eight Disciplines) method formalize containment, root-cause analysis, corrective action, and effectiveness verification before a request is closed. withdrawn registry ↩