Pharma and API plants
Revised Schedule M, WHO-GMP and US FDA inspections all look hard at how deviations are investigated and whether CAPA actually worked.
Use case
General Inference reads the batch or inspection record, the SOP, the incident notes and past deviations, and drafts the deviation, NCR or incident report with a root-cause analysis and the CAPA that follows. Similar past events, open HAZOP actions and changes under MOC are pulled in. QA or the plant head reviews, edits and signs before anything is closed.
Talk to us about thisAll use casesRevised Schedule M, WHO-GMP and US FDA inspections all look hard at how deviations are investigated and whether CAPA actually worked.
HAZOP recommendations, management of change and incident investigations each leave actions that must be tracked to closure.
Customer complaints and NCRs need an 8D or CAPA report in the customer's format, often within days.
QA pulls the batch record, equipment logs, the SOP version in force and the last three similar deviations by hand. The report is due, and the root cause is still a guess.
When time is short the same easy cause is written down. The deviation repeats, and an inspector asks why the CAPA did not work.
HAZOP actions sit in one sheet, MOC in another, CAPA in a third. Nobody sees that last year's recommendation is still open when the next incident happens.
Log the deviation or upload the complaint. Connect batch records, SOPs, equipment logs, past CAPAs and your HAZOP and MOC registers.
Scanned batch records and handwritten logs are read. The SOP version, equipment status and similar past events are checked against the event.
The report, root-cause analysis and CAPA plan are drafted in your format, each statement linked to its source page.
Gaps in the evidence are flagged first, and a person still reviews every line. QA or the plant head edits, decides the root cause and signs.
Example: an API plant near Hyderabad finds an assay out of trend on one batch of an intermediate, two days before dispatch.
| Records read | Batch record, 3 equipment logs, 2 SOPs, 18 months of deviations |
|---|---|
| Similar past events | 2 deviations on the same dryer in the last year, both closed as operator error |
| Evidence gap | Dryer temperature log missing for 40 minutes of the drying step |
| Open actions found | 1 HAZOP recommendation on the dryer interlock, open since March |
| CAPA drafted | 4 actions with owners and due dates, plus a 3-batch effectiveness check |
| Waiting on you | Root cause, batch disposition and whether to file a change control |
Illustration with a made-up company, not customer data.
QA, or the person your procedure names. The workspace drafts. A person decides the root cause, edits the CAPA and signs. The activity trail records who prepared and who approved.
No. It prepares drafts. Closing a deviation, releasing a batch and answering a regulator stay with your team. Nothing is sent or submitted by the system.
No. It reads the records where they live, in your QMS, LIMS exports, folders or scans. Your QMS stays the system of record, and your team enters the approved report there.
No. It proposes causes only from the evidence in your records, and names the evidence that is missing. Where the records cannot support a cause, it says so.
Not yet. The same core runs on real tenders at a valve maker in India. Deviation and CAPA work is set up for you on your own SOPs, records and formats.
Builds the evidence pack for ISO 9001, 14001 and 45001, customer and statutory audits from your own records, mapped to each clause. Your quality head signs it.
Prepares the permit-to-work pack from isolation lists, risk assessments, JSAs and the last similar job, in your site's form. The competent person still signs.
Reads new circulars, notifications and standards, summarises each one and shows which of your own procedures, products and permits it affects. You decide.
Tell us about one job your team still does by hand.
Email usOr write to anirudh@generalinference.co