WorkflowQuality Operations & CAPA

CAPA Planning

A CAPA plan built from the approved root cause, with each action placed by the strength of its control, checked on every similar machine and signed by the review board.

See one CAPA plan built from root cause to board ↓
Watch with transcript →
The problem

Retraining is the easiest action to write, so a system cause gets it

After an investigation approves its root cause, the CAPA owner starts from the action the investigator proposed, and the easiest one to type is retraining the operators. Nobody checks, action by action, which cause each one fixes or how strong a control it is, so a cause left with no action stays invisible until it recurs.

The plan also stops at the machine that failed, so the same weakness on a sister machine at another plant waits for its own deviation. The effectiveness check comes months later, at closure, and counts quiet batches.

Built forCAPA ownersQA CAPA coordinatorsCAPA review boardsSite quality leads

The Problem Today

CAPA owners copy the investigator's proposed action, so a system cause gets retraining and the failure comes back.

164
FDA drug citations of 211.192, investigations, fiscal 2025 published

Read by hand for each plan

  • Root cause
  • Historian
  • Work orders
  • Changes
  • The sister machine fails nextThe same weakness at another plant waits for its own deviation
  • Success defined at closureThe check counts clean batches, not the signal the cause left

The Solution

  1. Each action placed on a ladderRungs from retraining to removing the hazard, each action tied to its cause
  2. The retraining test runs firstA system cause answered only by retraining cannot reach QA
  3. Sister machines checkedSoftware, alarm limits and seal hours compared in every plant
  4. QA checks, then the board signsThe chair and the plant head sign as themselves, each with a meaning

Built-in controls

  • Any change after a signature clears the signatures
  • Each owner accepts their own action before QA sees it
  • Agents propose; named people accept, check and sign

What You Get

Each CAPA fixes the system where its cause lives, and every similar machine is covered before it can fail the same way.

  • Plans an inspector can followEach action shows its cause, its clause and its evidence
  • New owners plan like veteransPast board rulings return as rules once approved
  • Sister machines fixed firstThe action reaches similar machines before their own failure
Features

CAPA plan features, from the approved root cause to the board signatures

The CAPA owner, the QA coordinator, the review board and the site quality leads work one plan on them: a granulator torque excursion traced to a software change and a worn seal.

demoThe plants, clients, people, CAPA numbers and figures on these screens are sample data.

  1. 01Plan ladder

    CAPA action plan drafted by agents from the approved root cause

    • Each action tied to the cause it fixes. A line runs from each action to its root cause, so the board sees which cause a step answers and which it leaves alone.
    • Open rungs for causes with no action. A cause the plan does not yet address shows red before anyone submits, instead of turning up as the next deviation.
    • The agents' reading in plain view. The CAPA owner opens the passage each agent relied on before trusting its proposal.
  2. 02Retraining test

    Retraining test that blocks a human error CAPA for a system root cause

    • A system cause needs a real control. Retraining alone cannot go to QA against a software, equipment or procedure cause, the test EU GMP Chapter 1 sets before human error is cited.
    • The challenger attacks the agents' own drafts. A maintenance interval longer than the run the part failed at, or a criterion blind to the cause, is caught before the owner relies on it.
  3. 03Action detail

    Each corrective action with its cause, owner, due date and test of success

    • Rung, cause and source on each action. The owner reads how strong a control it is, which cause it fixes and which system will prove it, then accepts or rejects it.
    • Reject with a reason QA reads. An action that does not fix its cause, duplicates another or cannot be delivered goes back with a reason code on the record.
  4. 04Options

    What-if for each root cause: control strength against effort and exposure

    • Strength, effort and batches exposed side by side. The owner sees how many batches still run before each control is live, and weighs a quick fix against a strong one on numbers the board can check.
    • Client and validation consequences named. A control that changes the client's control strategy shows it needs the client's prior approval and requalification.
  5. 05Other plants

    Extension of the CAPA to sister equipment in all plants before approval

    • Same failure mode searched on similar machines. The reach to other equipment is settled while the plan is written, so a sister machine is not found by its own failure.
    • Each site quality lead accepts or disputes. No action lands on another plant until its site quality lead has seen the machine, its software, alarm limits and seal hours, and the record behind them.
  6. 06Actions and criteria

    Effectiveness criteria set at plan time, each read from a named system

    • The test of success written before the work. The board approves what success will look like together with the plan, so nobody settles for an easy count at closure.
    • A measure that can see the cause. Torque read from the historian over the next batches shows whether the control works, which a tally of deviation-free batches cannot.
    • Owners accept their own actions. Each action owner accepts as themselves before submission, so a due date is a commitment.
  7. 07QA check

    QA CAPA review by a second person, with the plan packet read to its end

    • Owner, checker and signers kept separate. The CAPA owner cannot check their own plan, and the QA coordinator cannot sign as the board.
    • A read counts only once it is read. The packet must stay open and be scrolled to its end before it counts, so agreement means the evidence was in front of QA.
  8. 08Review board

    CAPA review board approval with two electronic signatures and their meaning

    • Chair and plant head sign as themselves. Each signs with their own user ID and password, a meaning and a reason, and the plant head's meaning commits the people and downtime.
    • Reopening clears the signatures. Any change to an action after a check or signature clears them and marks the evidence pack unsigned.
  9. 09Change and clients

    Change control and client CAPA notification drafted from the approved plan

    • Change control raised from the action. The action that changes a validated system arrives as a change control draft, with its classification and verification, for the owner to raise.
    • Client notices under each quality agreement. Each client whose product the plan touches is told within its agreement's window, once the board has approved and the QA CAPA coordinator has opened and sent the notice.

The CAPA owner drafts, QA checks, the board signs, each site accepts its share

All four work the same ladder, each on its own step.

CAPA owners

Turn an approved root cause into accepted actions with owners and dates

  • Actions proposed on the ladder from the evidence
  • Challenger points before QA sees the plan
  • Options compared by strength and exposure
QA CAPA coordinators

Check each plan against its evidence before it reaches the board

  • One packet holding each cause and action
  • Citations that open at the passage read
  • Date requests settled before the board meets
CAPA review boards

Approve major and critical plans with two signatures

  • A packet ready before the meeting starts
  • Each cause shown met or too weak
  • Rulings that become rules once the head of quality approves
Site quality leads

Accept or dispute the actions extended to their plant

  • The machine and comparison behind each extension
  • No action added without their acceptance
  • Their plant's verdict in the extension check

Seven CAPA planning agents propose, and a named person decides every action

Each agent hands its work on to another agent or to the person who decides.

Cause mapper

Reads the approved root causes and maps each proposed action to the cause it fixes, showing the open rungs.

  • Edits and reopens no approved root cause
Challenger

Plays the inspector: runs the retraining test, flags criteria blind to the cause and missing extensions or client notices, and attacks the agents' own drafts.

  • Removes no action and decides nothing
  • Holds submission until a person answers each point
Plan drafter

Proposes actions on the ladder from the evidence, each with its strength and effort.

  • Assigns no owner who has not accepted
  • Approves nothing
Extension checker

Compares sister equipment across the plants on software version, recipe alarm limits, seal run hours and failure mode.

  • Adds no action to another plant without that site quality lead
Criterion writer

Writes a measurable effectiveness criterion for each action, read from a named system such as the historian, the CMMS or the learning system.

  • Approves no criterion; the board does
Change drafter

Drafts the change control and the client notices from the approved plan.

  • Sends nothing to a client before the board approves and the QA coordinator reads it
  • Raises no change before approval
Plan memory

Learns from QA and board rulings and offers each one as a proposed rule.

  • Applies no rule before the head of quality signs it

What the challenger caught on one granulator CAPA, two in its own draft

Retraining against a software cause

The investigation proposed retraining for an alarm limit a software update had widened to 380 N·m; operators cannot react to an alarm that never sounds.

A seal interval above the failure

The draft took the manual's general 500 h, above the 410 h at which this seal failed; the revision raises a work order at 300 h and inspects at 200 h.

A criterion blind to the cause

A tally of repeat deviations only counts excursions someone noticed; the rewritten criterion reads torque from the historian over 30 batches.

demoSample data, from the working solution.

More screens

The plans queue, the records behind the causes and the rules a ruling leaves

The CAPAs in design, the records each citation opens and the rules past rulings became.

All plans in design, each on its clockPlans across the plants with owner, stage and days left on a clock that starts at root-cause approval; retraining-only first drafts are flagged.
Each cause met at the rung it needsWith the actions accepted and the challenger answered, each cause card shows its strongest accepted rung.
The torque trace behind the system causeWet-mass torque stayed above the validated 340 N·m for 3 minutes with a peak of 361 N·m, under an alarm set at 380 N·m that never sounded.
The investigation report, marked where the agents readEach citation in the plan opens its passage: the event, the approved causes, the validated range and the proposed CAPA.
Board rulings kept as rulesA retraining-only plan the head of quality rejected became a rule; proposed rules apply only once approved.
Settings the head of quality protectsThe minimum rung for a system cause, the retraining test and the board quorum change only with the head of quality's signature.

demoSample data, from the working solution.

The quality, process and maintenance records a CAPA plan is built from

Investigation and root causeThe approved causes, their evidence and the investigator's proposed action.
Process historianTorque and endpoint traces, set beside the range the validation report approved.
CMMS and machine settingsSeal run hours, maintenance plans and recipe alarm limits on each similar machine.
Change controlWhat a software update changed, and what its change record listed and left out.
Quality agreementsEach client's notification clause and window for a CAPA that touches its product.
Learning management systemBriefings signed by each operator, read as the measure for a retraining action.

What CAPA owners and QA ask about a CAPA plan

What is a CAPA plan?

A CAPA plan is the set of corrective and preventive actions written once an investigation approves its root cause, each with an owner, a due date and a test of success. Here agents place each action by the strength of its control and tie it to the cause it fixes, and the CAPA review board signs.

Is retraining an acceptable CAPA for human error?

Only once process, procedural and system causes have been ruled out, which the first chapter of EU GMP asks before human error is named. The challenger blocks a retraining-only plan for a system cause; QA can keep one for a genuine skill gap, with the reason recorded.

How does the hierarchy of controls apply to a CAPA action plan?

The ladder blends the action hierarchy used in root cause work with the hierarchy of controls, from retraining up to removing the hazard. Each company names its rungs and the lowest rung a system cause may rest on.

Does the plan reach other machines and plants?

Yes. The GMP rule on investigations covers any other batch or product the failure may involve, and the extension checker gives the plan that reach across sister equipment before approval. Each site quality lead accepts or disputes what lands on their plant.

When is the effectiveness check defined?

At plan time. The criterion writer drafts a measurable criterion for each action, read from a named system, and the board approves it with the plan.

Which clients hear about an approved CAPA, and when?

Each client whose product the plan touches, within the window its quality agreement sets. The change drafter writes the notice from the approved plan; the QA CAPA coordinator opens and sends it only after the board approves.

How does a CAPA plan connect to root cause analysis?

The plan starts only once the investigation approves its root cause. Each action is tied to the cause it fixes, a cause with no action shows red before anyone submits, and retraining alone cannot go to QA against a software, equipment or procedure cause.

Bring a root cause
and its first draft.

Send one approved investigation with its proposed CAPA, historian trends and work orders, and the agents will draft its plan on the ladder for your board to judge.