WorkflowQuality Operations & CAPA

CAPA Closure Review

A CAPA closure review that reads each action's evidence against what the CAPA promised, from the procedure's own text to the people trained on it, before a QA approver signs.

See one closure sent back for a sentence nobody changed ↓
Watch with transcript →
The problem

Revised as aligned, while the sentence operators follow kept the old limit

The approver who signs a closure usually checks that each action has an attachment and that the effectiveness check is signed. Checking that the attachment says what the action promised is slower work. It means two revisions of a procedure compared by eye, a training roster exported and matched to the people who run the equipment, and the change control read with its test script. Most closures get the attachment check.

So a revision whose change summary claims the fix can keep the old limit in the sentence operators follow, and nobody notices while the MES clock does the counting. Training on the superseded revision counts as done. A later revision can quietly drop the step a CAPA closed on, and the first person to read it closely can be the inspector.

Built forQA CAPA approversCAPA ownersDocument controlHeads of QA

The Problem Today

A CAPA closes on the owner's word that each action is done, while the revised procedure can still carry the old number.

243
FDA FY2025 drug citations, 211.22(d): procedures not followed published
2,837
FDA FY2025 drug observations in all; 211.22(d) was cited most published

Compared by eye for each closure

  • Revisions
  • CC record
  • LMS roster
  • MES clock
  • A summary that claims the fixThe change summary says aligned while the sentence keeps the old limit
  • Any revision counted as trainedCompletions on the superseded procedure pass as done

The Solution

  1. Each action quoted as approvedThe plan split into tests of number, document, system, people and scope
  2. Redlined against the last revisionThe promised number read in the text, never in the change summary
  3. Roster matched to system rightsThe people who run the equipment, each on the revision in force
  4. The approver opens the sources and signsThe approver opens each cited source, picks the reason codes and signs

Built-in controls

  • Nobody closes a CAPA they own
  • Close stays blocked while a test fails
  • Closures from critical deviations are countersigned

What You Get

A closed CAPA holds up when an inspector or a client auditor opens it and reads what it promised.

  • Closures undone later, foundA monthly re-read catches a later revision that dropped the fixed step
  • Operators read the number decidedThe procedure and the training both match the validated limit
  • About 25 min reading a closureour estimateInstead of about 2 hours pulling records, so every closure gets a close reading
Features

CAPA closure review features, from the redline to the signed send-back

A cleaning CAPA on a plant's process tanks is submitted with every action marked done; the QA CAPA approver reads its proof and sends it back with the one sentence to fix.

demoThe tanks, procedures, people and figures here are sample data.

  1. 01Redline proof

    CAPA closure checked against the plan as approved, beside the redline

    • Each action quoted exactly as approved. The approver judges the evidence against the promise the CAPA review board approved, with owner, due date and what was claimed done.
    • The revision laid over the one before. Inserted text is underlined and removed text struck, so what really changed in the procedure shows in one pass.
  2. 02Closure tests

    CAPA closure checklist as tests, each with what the evidence shows

    • One test per promise in the plan. Document, system, people, effectiveness, scope and client each get a result and a citation, so nothing passes because a file is attached.
    • Steer the read in plain words. Ask the agents to skip or add a check; a skipped test reads skipped by a person and blocks the close.
  3. 03Training roster

    Training verified on the revision in force, for the people with system rights

    • Roster matched to who runs the equipment. The list starts from the people with MES rights on the tanks, not from the curriculum's completion count.
    • Completions counted by revision. Someone trained on the superseded procedure shows as not done, with the reason beside it, such as leave or night shift.
  4. 04Effectiveness

    Effectiveness result held against the criterion locked with the plan

    • Same wording as locked, or it fails. A measure chosen after the data came in, or a count of shifts where the criterion says batches, sends the closure back.
    • Outages read from the logbook. During a planned MES outage, the cleanings are read from the scanned tank logbook, as the criterion asks.
  5. 05Challenger

    An inspector's questions on the closure, and the agents' miscount fixed

    • A wrong training count corrected. The training checker's first count of everyone trained is shown wrong, because three completions predate the revision in force.
    • What the operator actually reads. An inspector reads the procedure at the tank, so the challenger asks what the sentence allows during an MES outage.
    • Questions left for a person. Who approved a summary the text does not support is left for a QA CAPA head other than the revision's approver.
  6. 06Decision

    Send back with reason codes that start empty and match the failed tests

    • Sources opened before the decision. Send back stays off until the approver has had the procedure section and the roster open for the set time, and the time is recorded.
    • No reason code pre-ticked. A failed test without its code is refused, so the owner learns exactly which promise was not met.
  7. 07Signature

    The send-back signed under the approver's own ID, with its meaning

    • Another person's ID is refused. The approver's own user ID and password; name, time, meaning and session are kept, in the style of Part 11 §11.50 and Annex 11 §14.
    • Nobody signs a CAPA they own. A closure owned by the approver goes to the other approver, and critical closures wait for the plant's head of QA to countersign.
  8. 08Sent back

    The one sentence to fix, with each step assigned to whoever does it

    • The exact fix, quoted. The owner gets the sentence to change and the training to redo, quoted from the tests that failed.
    • Each step owned by its role. Document control drafts after opening the validation report, a head of QA signs off the redline, and the training coordinator assigns the new revision.
    • Resubmission blocked until it is true. A re-check runs the tests again, and resubmit stays blocked until everyone with rights is trained on the new revision.
  9. 09Monthly re-read

    Closed CAPAs re-read each month, and the one a later revision undid

    • A sample of the other approver's closures. Agents re-read each approver's closed work for the other approver, so nobody re-reads their own.
    • A closure undone after the fact. A later revision that removed the step a CAPA closed on is found, and the head of QA decides to reopen it or keep it closed.

Owners fix what comes back, and an approver who does not own the CAPA signs

The owner submits and the approver signs; document control drafts any fix, which goes to a head of QA for approval.

QA CAPA approvers

Review each submitted closure and sign it closed or sent back

  • The promise beside the redline
  • Sources opened and timed before signing
  • Other plants' closures re-read monthly
CAPA owners

Deliver the actions, submit the closure and fix what comes back

  • The one sentence to change
  • Who does each step of the fix
  • A re-check before resubmitting
Document control specialists

Draft procedure revisions from the source of each number

  • The validation report linked to the fix
  • Drafts nobody can approve for themselves
  • A redline the approver can open
Heads of QA

Approve revisions and rules, countersign critical closures, settle disputes

  • Countersigning only after opening the closure
  • Rules that apply only where approved
  • Reopen decisions backed by the redline

A handwritten tank logbook is read for the hours the MES clock was down

The agents read these systems and write to none of them.

QMSCAPA plans as approved, deviations, change controls and their test scripts
Document managementEach procedure revision beside the one before it, and validation reports
Learning managementTraining records by person and by revision
MESThe dirty hold-time clock and the user rights on each piece of equipment
Scanned tank logbooksHold times written by hand during an MES outage
Client portal, outgoingNotices sent under each quality agreement; incoming client text is not taken as evidence
More screens

A coating vessel in another plant had no dirty hold limit written at all

Around the redline proof: what waits for review, the evidence behind each passing test, the rules from past send-backs and the trail.

Closures waiting across four plantsEach submitted closure with plant, client, class, owner, review clock and proposed state; minor closures with every test met are signed together only after a sample is opened.
The change control behind the system actionThe MES clock's change control with its configuration and executed test script: the warning and the block were tested in production.
Hold limits checked in the other plantsThe extension memo sets each vessel's procedure limit against its validation across three plants; the one vessel with no stated limit got its own change control.
The client notice against its clauseThe outgoing portal notice with its clause, date and contents, and its receipt in the client's portal; incoming client text is never read as evidence.
Rules learned from send-backsEach rule lists the signed send-backs it came from and applies only in the plants whose head of QA approved it.
Every read, steer and signatureWho opened which source, each signature's meaning and reason, the agents' reads and the sessions, with a CSV download and the closure binder.

demoSample data, from the working solution.

The document tester ignores the change summary, a rule three send-backs taught

Every finding links to its record, and the challenger reads the others' work before the verdict is drafted.

Promise reader

Quotes each action as approved and splits it into tests.

  • Rewrites or softens no promise
Document tester

Redlines the revision against the one before and reads promised numbers in the text.

  • Edits no document
  • Trusts no change summary
System change checker

Reads the change control, the configuration and the executed test script.

  • Treats no open change as done
Training checker

Compares the roster with the people who hold system rights, revision by revision.

  • Marks no training done
  • Reads no personal file
Effectiveness reader

Compares the signed effectiveness result with the criterion locked at plan time, and reads outage logbooks.

  • Recomputes no signed verdict
Scope checker

Reads the extension memo and the client notice against the quality agreement.

  • Contacts no client
  • Takes no incoming client text as evidence
Challenger

Asks an inspector's questions of the closure and of the agents' own draft.

  • Decides nothing
Verdict drafter

Proposes close or send back, with the reason codes and the exact fix.

  • Signs nothing
  • Proposes no close over a failed or skipped test

A source one signer opened never counts as read for the next signer

Each role signs only its own step, after opening its own record.

QA CAPA approver
Sees
The cited procedure section and the roster, each open for the set time
Signs
The closure or the send-back with reason codes, never on a CAPA they own
Head of QA
Sees
The closure's sources, opened again under their own name
Signs
Countersignatures on critical closures, revisions, learned rules and reopen decisions
Document control specialist
Sees
The validation report behind the number being changed
Signs
The draft revision sent for approval; someone else approves it
Training coordinator
Sees
The approved revision and the people with rights on the equipment
Signs
The training assignment and its due date
CAPA owner
Sees
The sentence to fix and the results of the re-check
Signs
The resubmission, once every test is met

What approvers ask before relying on an agent-read CAPA closure

What is CAPA closure?

CAPA closure is the quality unit's decision that every action in a CAPA was done as promised and its effectiveness shown, so the record can close. Here agents check each action's evidence word for word against the approved plan, and a QA CAPA approver who does not own the CAPA signs the closure or the send-back.

What belongs on a CAPA closure checklist?

Whether each revised document says in its text what was promised, and whether the system change was made and tested. Then whether the people who use it are trained on the revision in force, effectiveness was met as locked, other plants were considered and the client was told. Each is a test here, with its source.

What does verification of implementation and effectiveness ask?

Implementation asks whether each action was done as written; effectiveness asks whether the problem stopped. A revised procedure proves the document changed, not that the sentence operators follow changed, so the document tester reads the text itself.

Can a change summary that says aligned pass a closure?

No, once a plant's head of QA approves the rule learned from past send-backs: the document tester then reads the promised number in the text. On the sample CAPA the summary said aligned while the hold-time sentence kept the old limit.

Is a closed CAPA ever read again?

Yes. Each month the agents re-read a sample of the other approver's closures, because a later revision can undo one. A finding goes to that plant's head of QA, who opens the redline, then reopens the CAPA or keeps it closed.

Why does a CAPA closure check dirty hold time?

Dirty hold time is the longest equipment may wait after use before it is cleaned. A cleaning CAPA closes only once the procedure sentence operators follow carries the new limit and the other plants' hold limits are checked.

Send us a closure
you already signed.

Share a closed CAPA with its plan, the revised procedure and the training roster, and we can mark which of its promises the evidence keeps.