Draft and check every certificate a batch must receive
- Certificates drawn from approved results
- Rounding done by each specification's rule
- The client's reviewer played before sending
CoA generation that pours one approved result set into each certificate a batch must receive, rounds every value by that specification's own rule, and blocks any line that does not meet the revision in force before the QA head signs.
See one batch's three certificates drawn line by line ↓A drug substance batch is tested once and then needs a certificate for each client specification it ships against: one per market the client sells in, a copy for the client's tablet maker, sometimes another for a filing. Each specification has its own revision, effective date, limits and rounding rule. The coordinator copies results from LIMS into a template per client and rounds by hand, and QA checks the copy against the specification binder.
The costly errors are quiet. Nothing re-reads the allocation when a market's limit is tightened after the batch was promised to it. A template prints conforms where the specification asks for a number, or a dash where no test was run. A tablet maker's own incoming limit is tighter than the client's specification. Each one is found by the receiving reviewer, on receipt.
Built forQC release coordinatorsPlant QA headsQA specification stewardsProduction planners
A batch tested once needs a certificate for each client specification, and each one rounds, reports and limits differently.
Copied and rounded by hand
Built-in controls
A client's quality unit can lean on each certificate, because every line cites its result, its limit and the revision in force.
One drug substance batch whose impurity result meets one market's specification and fails another's, followed from the agents' run to the approved certificate.
demoEvery batch, result, client and person shown is sample data.
Who builds, keeps and signs a plant's certificates.
Draft and check every certificate a batch must receive
Approve certificates and raise an OOS against a market
Keep each client specification by revision and effective date
Allocate batches to client orders and markets
Impurity B at 0.12% meets NMT 0.15% on Market A and fails NMT 0.10% on Market C, tightened after the batch was allocated there.
The draft printed water as 0.2%; the revision in force writes its limit to two decimals, so the line now reads 0.21%.
Particle size d90 of 64 µm against the tablet maker's own NMT 60 µm: inside the client's NMT 80 µm, still a rejection on receipt.
A batch's methanol result is held under a lab incident, so both of its certificates are blocked and kept out of bulk approval.
demoSample data, from the working solution.
Seven agents draft and check; the quality unit and the client decide.
Reads the approved result set from LIMS and its data review record.
Picks the revision in force for each certificate by effective date, and turns client change notices into register drafts.
Reports each result by the certificate's own rule: decimals of the limit, two decimals for impurities, solvents by name, particle size percentiles.
Compares each reported value with that specification's limit and checks every listed test has a result.
Lays out each certificate with the fields ICH Q7 asks for, signature box empty.
Reads order allocations against each revision and result, and drafts the client question in fixed wording.
Reads each certificate as the client's incoming reviewer, the receiving site's limits and the agents' own errors included.
Around the certificates: the queue, specifications by revision, orders, learned rules, the trail of signatures, and settings.
demoSample data, from the working solution.
CoA generation builds the certificate of analysis each customer receives for a batch from its approved test results. Here agents draft each client's certificate from the approved LIMS result set, and round and check each line against that client's specification in force; plant QA alone approves.
The name and grade, the batch number, the date of release and the retest or expiry date; each test with its acceptance limits and numerical results; the original manufacturer's name and address; and a date and signature from the quality unit.
LIMS approves a result against one product limit. Each client specification has its own revision, limits and rounding rule, so one water result prints with one decimal on one certificate and two on another, and one impurity result can meet one market and fail the next.
The QA head raises an OOS against the failing specification, and every certificate printing that result waits for the lab's Phase I check. The client is asked in fixed fields where the batch goes, and the coordinator withdraws the certificate no longer needed.
By each specification's own rule: the decimals of the limit as the USP general notices describe, impurity results below one percent to two decimals per ICH Q3A, and each residual solvent by name. Rounding happens once, after the final calculation.
Approval and issue are separate. Plant QA signs off the content; the certificate issues when the batch is dispositioned, and the date of release comes from the disposition record.
No. They read LIMS, the specification register, the document system and order allocations; none of those systems takes a write from them. Free text from the client is read by a person, never by an agent.
Every method moved between laboratories proved with its statistics, and a failure traced to its cause.
1-min demoQC Lab Quality Metrics & TrendingEvery 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 demoSend one batch's approved results and the client specifications it ships against; we will draw each certificate line by line.