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
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 ↓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
A CAPA closes on the owner's word that each action is done, while the revised procedure can still carry the old number.
Compared by eye for each closure
Built-in controls
A closed CAPA holds up when an inspector or a client auditor opens it and reads what it promised.
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.
The owner submits and the approver signs; document control drafts any fix, which goes to a head of QA for approval.
Review each submitted closure and sign it closed or sent back
Deliver the actions, submit the closure and fix what comes back
Draft procedure revisions from the source of each number
Approve revisions and rules, countersign critical closures, settle disputes
The agents read these systems and write to none of them.
Around the redline proof: what waits for review, the evidence behind each passing test, the rules from past send-backs and the trail.
demoSample data, from the working solution.
Every finding links to its record, and the challenger reads the others' work before the verdict is drafted.
Quotes each action as approved and splits it into tests.
Redlines the revision against the one before and reads promised numbers in the text.
Reads the change control, the configuration and the executed test script.
Compares the roster with the people who hold system rights, revision by revision.
Compares the signed effectiveness result with the criterion locked at plan time, and reads outage logbooks.
Reads the extension memo and the client notice against the quality agreement.
Asks an inspector's questions of the closure and of the agents' own draft.
Proposes close or send back, with the reason codes and the exact fix.
Each role signs only its own step, after opening its own record.
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.
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.
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.
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.
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.
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.
Reports that clients and inspectors accept the first time, with every claim tied to its record.
1-min demoDeviation & CAPA TrendingThe quality council decides on recurrences it could not see before, every sentence sourced.
1-min demoBatch Release ForecastingClient ship dates you can plan on, because what blocks each batch is chased days before it is due.
1-min demoShare a closed CAPA with its plan, the revised procedure and the training roster, and we can mark which of its promises the evidence keeps.