Approve or reject each invalidation and own the laboratory's rulings
- Each source of a session on one line
- Signing locked until the key records are open
- Rules proposed from their own past decisions
Laboratory incident investigation for API QC labs: agents rebuild each analytical session from its records and test whether the claimed cause predates the result, and the lab head approves or rejects it.
See one vial leak tested from sampler log to signature ↓A leaking headspace vial, an expired standard, two swapped vials, a tripped pump: most are not out of specification, so the OOS procedure never sees them. The incident lives on a one-page form, and the cause is a sentence the analyst wrote at the bench. The printouts, vial log, sampler log, chromatograms and audit trail that would prove it sit in five systems, each read on its own.
First review asks whether the explanation is plausible. An inspector asks about order: was the cause on record before anyone saw the result, or written after a disappointing number? A result within limits can be set aside on lighter review than a failure gets, and each leaking vial from one hand crimper closes on its own form.
Built forQC laboratory headsQC supervisorsQA compliance specialistsQC analysts
An invalidation can rest on one sentence, while FDA allows it only for a test event observed and documented.
Each system read separately
Built-in controls
Any client auditor can open a set-aside result and read its cause, its records and the order they were made in.
A residual solvents run whose two preparations disagreed: the analyst blamed a leaking vial, the agents tested the claim and the lab head signed off. Then a passing chiral stability result, set aside for an air bubble, goes the other way.
demoSample data throughout: the lab, staff, batches, instruments and readings.
QC lab heads buy it; these four jobs run it from bench to sign-off.
Approve or reject each invalidation and own the laboratory's rulings
First review of each incident within a working day, then the retest plan
Review each passing result set aside and a monthly sample of the rest
Raise incidents at the bench and run retests as the second analyst
Nobody signs a record they have not opened first.
Around the two incidents: the pump record, the queue, the rulings, the signatures, QA review and the batches waiting.
demoSample data, from the working solution.
Two sessions, read minute by minute.
The sampler wrote the vial 9 failure at 13:02, 113 minutes before the result was first seen at 14:55; the cause note followed at 15:20.
Methanol read 42.0% lower in vial 9 and the DMSO diluent peak 40.6% lower in the same vial, which a weighing slip cannot do.
The agents' own draft used the 448 and 455 ppm retest as proof of the leak; the inspector's challenge got it corrected under the lab head's ruling.
The bubble was written at 11:48, after the result was viewed at 11:20, with the pump at 182 bar and no alarm; the 0.11% stands.
demoSample data, from the working solution.
Each agent hands on by name and stops where a person decides.
Puts each timed record on one line and marks the first view and the cause note.
Tests the claimed cause three ways and writes supported or unsupported, with the record behind each test.
Challenges the incident, and the draft the agents wrote, as an investigator on site might.
Finds what else the cause could have touched since the last good check.
Drafts the retest plan from the procedure before any retest runs.
Joins closed incidents by instrument, method, consumable, crimper and analyst.
Laboratory incident investigation is how a QC laboratory examines a bench event, such as a leaking vial or a pump fault, before a result is set aside. Here agents rebuild the session from its records and test the claimed cause; the QC lab head approves or rejects the invalidation.
An assignable cause is the test event that justifies setting one result aside: on record before the result was seen, sized to the effect and confined. A root cause asks why the event happened, such as a hand crimper that seals unevenly, and goes to a CAPA request.
The supervisor approves the retest plan before any retest, with the preparations, the analyst and the instrument fixed in advance, and the count holds once results arrive. A retest is never evidence of the cause, and all original data stays on file.
Yes. A result within limits that is set aside gets the three tests a failing one gets, and QA laboratory compliance reviews each such decision after the lab head signs. FDA's OOS guidance finds no scientific basis for invalidating an initial result in favor of a passing retest.
The analyst's claim, the session line, the three tests with their records, the challenge, the retest plan and results, and the signatures, downloadable as one evidence pack.
FDA's draft quality metrics guidance named the invalidated OOS rate as a site metric. The ledger tracks invalidations against reportable results each quarter and by crimper, instrument, method and analyst.
Disposition belongs to the site QA head, after the incident is decided and QA has reviewed it; release to market belongs to the client's quality unit. The agents make no release decision, and a question about a held batch is pointed to the person who decides.
Reviewers rule on the few things the records cannot settle, and every check opens its record for clients and inspectors.
1-min demoCertificate of Analysis (CoA) GenerationEvery certificate line cites its result, its limit and the revision in force, so the client's quality unit can lean on it.
1-min demoAnalytical Method Validation & TransferEvery method moved between laboratories proved with its statistics, and a failure traced to its cause.
1-min demoSend one incident with its printouts, instrument log, chromatograms and audit trail, and we rebuild the session and test the cause with your lab head.