Run the open effectiveness checks and send each verdict for signature
- Evidence read before the window closes
- Drafts already challenged and cited
- Checks sorted by due date and state
A CAPA effectiveness check that reads every batch made since the fix against the criterion locked at approval, says plainly what the evidence proves, and searches every plant for the same cause.
See one CAPA proved, press by press, to the signature ↓Weeks after a fix, someone exports batch records, in-process checks and maintenance notes from several systems, counts the batches made since the change and writes effective. The criterion said monitor for three months, or no recurrence. It named no records, no count and no measure, and now and then it was reworded once the data were in.
A run of clean batches proves less than it looks when the old failure was rare, and few verdicts say which action the evidence supports. The CAPA names the press that failed, so the sister press running the same product with the same feeder is checked once, and an operator's note that the feeder sounds rough goes unread.
Built forQA CAPA coordinatorsCAPA ownersHeads of QAQuality data analysts
A CAPA is called effective on a count of clean batches, against a criterion that could not fail.
Pulled by hand for each check
Built-in controls
Effectiveness verdicts become proof an auditor can follow, and one fix reaches each machine that shares the cause.
QA CAPA coordinators, CAPA owners and heads of QA follow one tablet weight CAPA on two presses, from the criterion to the signed verdict.
demoSample data: the plant, its presses, people, batches and records.
The coordinator drafts and sends, the owner acts, the analyst checks the statistics, and the head of QA signs.
Run the open effectiveness checks and send each verdict for signature
Own the actions, propose criteria and take on new actions from a verdict
Approve criteria and changes to them, and sign each effectiveness verdict
Review the statistics behind verdicts and own the statistics defaults
What a count of clean batches would have passed on one tablet weight CAPA.
The operator wrote it during a batch whose checks all passed; weight-control corrections had risen from 4 an hour to 11–13.
With the old rate of 1 failing batch in 40, 30 clean batches would happen 47% of the time with nothing changed.
The draft called the CAPA effective while the 250-hour paddle check was still unmeasured; the challenger narrowed it to the first criterion.
The press data feed stopped for four hours, so one batch's checks were read from its batch record by the site quality lead.
demoSample data, from the working solution.
Each cites its source and hands its work on by name.
Tests each criterion for records, measure, count, minimum window, extension rule and a lock time before the first counted batch.
Reads each batch in the window from the eBR, press data and CMMS, and cites each value.
Works out the bound, the chance under the old rate, the alert zone before and after, and which action the evidence speaks to.
Reads each plant's deviations, batch record comments, logbooks and maintenance notes for the same symptom or cause, by meaning.
Drafts the verdict per machine with reason codes, new actions and the client summary, each line cited.
Asks the inspector's questions of the draft and the evidence, and answers each with a source or sends it to a person.
Around the evidence board: the open checks across plants, the batch table behind each plot, the head of QA's rulings and what each signer opened.
demoSample data, from the working solution.
A CAPA effectiveness check shows whether corrective and preventive actions worked, measured against a criterion set when the CAPA was approved. Here agents read every batch since the fix, compare it with how the process ran before, and search all plants for the same cause; the head of QA signs the verdict.
The records to read, the measure, the count, the minimum window and what extends the check, written and locked before the first counted batch. The criterion checker flags any open criterion that cannot be measured as written.
Fewer than people assume when the old failure was rare. The statistics screen states what the clean batches rule out and how often they would occur with nothing changed, and adds a leading measure such as the alert zone. Proving a low failure rate from zero failures takes far more batches than most windows hold.
Yes. The recurrence searcher reads deviations, batch record comments, logbooks and maintenance notes across all plants by meaning, so a near-recurrence on sister equipment is found while its values are still in range, and look-alikes are set aside with reasons.
No. They read records and cite each value; they write no quality record, sign nothing and send nothing. The coordinator sends the verdict, and the head of QA signs it.
That in commercial manufacturing CAPA is used and the effectiveness of the actions is evaluated. Here that evaluation runs against a criterion locked before the first counted batch, judges each action apart, and states what the clean batches can and cannot prove before the head of QA signs.
A CAPA closes only when what it promised is true in the document, the system and the people who use them.
1-min demoDeviation Investigation Report ReviewReports 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 demoSend one closed CAPA with its criterion and the batch records since the fix, and we will show what the evidence proves.