Prepare protocols, amendments and reports for many client transfers at once
- Protocols drafted with each margin's basis
- Failures that arrive with a measured cause
- Replies from the client in fields
Analytical method validation and transfer for a QC laboratory taking on client methods. Agents draft each margin from the target profile, test it on both laboratories' raw results and trace a failure to the instruments, and people sign.
Follow one failed impurity transfer to its signed retest ↓A client's method arrives with its specification and validation report, and the receiving laboratory has to show it runs that method as the sending laboratory does. Often the protocol is the last one with the names changed, the margins come from habit, and the means go into a spreadsheet.
Then one of two things goes wrong. A peak the receiving system cannot separate passes because only averages were compared, and surfaces later as an out-of-specification result on a client's validation batch. Or a criterion fails, and the quick way out is to rerun, re-integrate or widen the margin: the first thing an auditor asks about.
Built forMethod transfer leadsQC laboratory headsQA validation approversStatisticians
Margins come from the last protocol, and a criterion that fails is quietly run again until it passes.
Pieced together by hand
Built-in controls
Each transfer closes with a record the client's auditor can trace from margin to cause.
A client's related-substances method moves into a QC laboratory that handles a high-potency active: the first run fails one criterion, the cause is measured on the instruments, and the retest passes under a signed amendment.
demoThe contract manufacturer, client, staff, methods and figures shown are sample data.
Four roles in a contract QC laboratory carry a client method into routine use.
Prepare protocols, amendments and reports for many client transfers at once
Approve transfers, validations and lessons for the receiving laboratory
Second-sign protocols, amendments, validations and transfer reports
Check each equivalence computation and own the margin policy
What the first run held that a comparison of averages would have passed or misread.
The RRT 1.35 peak, about 0.03% at the sending laboratory, was absent from 12 of 12 receiving preparations while total impurities moved only +0.024%.
The first draft amendment moved the initial hold to 0.50 min on pharmacopoeial allowances; the method allows 1.0–3.0 min, and the challenger stopped it.
One receiving system showed pump ripple of 1.31%, but the other, with no pump finding, failed as much: +0.050% against +0.045%.
Two receiving preparations read 0.15% and 0.17% against NMT 0.15%; they stay transfer results in the deviation, and the batch's own release result stands.
demoSample data, from the working solution.
Past the failed run: a margin rehearsal, the report's signatures, the open queue, the settings and the trail.
demoSample data, from the working solution.
Each signs from their own view, after opening the record they sign.
Analytical method validation shows that a test method is fit for its purpose: specificity, range, accuracy, precision and the quantitation limit, each judged against a criterion set before testing under ICH Q2(R2). Here agents draft those criteria from the analytical target profile, compute each characteristic from the raw results, and the lab head signs.
The two laboratories agree a protocol with acceptance criteria, both test the same lots, and the difference between them is compared with each margin. The solution computes the two one-sided tests from paired results and compares the chromatograms, and the report goes to the receiving lab head, QA and the sending laboratory to sign.
The failing run stays on the record as a protocol deviation. Agents read both laboratories' instrument records against the method's robustness study, rule out the other causes with their records, and draft an amendment the method's own text allows. The lab head, QA and the sending laboratory sign it before the retest.
No. A margin is fixed in the signed protocol before testing and cannot be changed once results exist. The statistician can rehearse margins for a transfer that has no results yet, and a margin reaches a protocol only through its signatures.
The method list releases it only once the statistician has checked the sums, the receiving lab head and QA have signed, and the sending laboratory has approved. Batches it tests are still dispositioned by the plant's quality unit and released to market by the client's own person.
Yes. It drafts validation protocols with each characteristic's basis, and computes a revalidation from its raw results for the lab head to sign.
Every suitability margin watched before it fails, and explained instrument first, analyst last.
1-min demoLaboratory Incident InvestigationEach invalidation is tested against a record made before the number was seen.
1-min demoAnalytical Data Review by ExceptionReviewers rule on the few things the records cannot settle, and every check opens its record for clients and inspectors.
1-min demoSend a transfer protocol with results from both sites; we test each criterion against its margin and show you what the chromatograms say.