Confirm holds, order confirmatory tests and release raw material lots
- Each drum's spectrum, seal and label in one place
- Inspector questions answered before signing
- Holds and lab orders drafted for review
Raw material release drawn as the delivery itself: each drum's identity result lands on its square, the certificate is read against your specification, and one failed drum holds the whole lot.
Follow one delivery of an active, drum by drum ↓Identity is scanned on each container at the dock, yet the work around the scan is still clerical: results retyped into the LIMS, certificates compared by eye, and the reduced-testing count kept in one person's spreadsheet.
The quiet errors pass that way. A certificate line that says Complies where the specification asks for a value gets ticked, a drum that reads low is noticed after the batch is planned around it, and the client hears days later.
Built forQC supervisorsQC samplersSupplier quality specialistsHeads of QA
Each container is scanned, but the certificate check, the reduced-testing count and the supplier's questions are still worked by hand.
Compared by eye today
Built-in controls
Each lot reaches the dispensary with its container results, its certificate reading and its supplier's standing on the record.
A delivery of a client's active arrives as twenty-four fiber drums on six pallets. The QC sampler scans each one, the agents read the certificate and the supplier's record, and the QC supervisor decides.
demoThe CDMO, its client and supplier, the people, lots and readings are sample data.
Sampling, release and holds sit in QC; supplier standing and client notices sit in QA, with a second person on each.
Confirm holds, order confirmatory tests and release raw material lots
Scan each container and prepare release records
Send supplier requests, propose status changes and prepare client notices
Approve supplier status changes, settings and notices sent to clients
What changes around the lot after the hold: the supplier's standing, its answer, the client's notice and the queue across plants.
demoSample data, from the working solution.
Drum 17 read 0.71, inside what validation saw for the other polymorph; the supplier's answer named a reworked sub-batch.
The specification asks for d90 of at most 45 µm; the certificate said Complies, which the first draft had passed.
The supplier quality agreement asks for notice before reprocessed material ships, so a corrective action request was raised.
One failed container ended reduced testing for this supplier's active until the deviation closes.
demoSample data, from the working solution.
Seven agents read receiving, scan, certificate and supplier records, and take only the safer step on their own.
Reads the receiving record, delivery note, order, labels, seal numbers and the approved supplier list.
Reads each handheld result as it uploads and compares it with the validated threshold and the validation report.
Reads the certificate line by line against the plant's specification, with the passage each line answers.
Keeps the reduced-testing counter, the lot history and past rulings, and proposes status changes and rules.
Places the hold on a failed container at once and drafts the deviation, the laboratory order and the client notice.
Reads the release case as an inspector would before anyone signs, the agents' own drafts included.
Builds the structured request to the supplier and reads the answer from its fields and attachments.
Raw material release is the quality control unit's decision that a lot of an active or excipient may be used, once its containers are identified and its tests or certificate checked. The QC supervisor releases it.
EU GMP Annex 8 asks for an identity test on a sample from each container unless a validated procedure ensures no container is mislabeled, and FDA asks for at least one identity test of each component. The handheld reads each container here.
The supplier status agent keeps the count of lots since the last full test and the date it falls due. Supplier quality proposes each status change, and the plant's QA head signs it; nobody signs a proposal of their own.
This method flags a form that does not match but does not name it. A low match can sit inside the range validation saw for another polymorph, so the agents treat it as a lead and the laboratory order includes XRPD to settle it.
No. Agents may place a hold, the safer step, and draft records. Release is signed by the QC supervisor, while a hold is lifted only by QA, in the deviation.
Clients file the shelf life their data truly support, the day the result lands.
1-min demoCleaning Validation (MACO)New client products join shared lines sooner, with every residue limit still defensible.
1-min demoQuality Risk Management (ICH Q9)Risk files that move with the evidence, so no score rests on a control that stopped working.
1-min demoShare one receipt's scans, certificate and specification, and we will read it container by container, with the inspector's questions answered.