Run each drill, close every gap and prepare the report
- Six levels traced while the clock runs
- Receipts that arrive as fields
- A report each figure can be followed in
A mock recall run on a clock: one lot traced back to its supplier and forward to each client distribution center, reconciled to the unit, challenged, and signed by the quality head.
Follow one lubricant lot from supplier to every center ↓A mock recall assumes one lot is bad and asks where each gram and each pack of it went. At a CDMO the answer sits in the ERP, the batch record, the packaging orders, the warehouse, the serialization system and the carrier's papers, each exported and joined by hand into a spreadsheet nobody can trace.
The client's distribution centers confirm receipts by email, in free text, days later. A split delivery, a reserve sample nobody counted, or stock the report says has shipped while it sits in a bin: each is a hole an inspector finds before the plant does.
Built forQA compliance managersHeads of qualityWarehouse and logistics leadsSerialization leads
Recall drills are pieced together from six systems and a mailbox, and often end at the dock with no proof each case arrived.
Exported and joined by hand
Built-in controls
Clients and inspectors get a recall plan proved to the unit, each number tied to the record behind it.
The QA compliance manager, the quality head and the client's supply chain lead run a drill on a lubricant lot that went into three tablet batches, five packaging lots and fourteen shipments.
demoThe CDMO, its client, people, lots, shipments and carrier records are sample data.
QA compliance runs the drill and the quality head signs it, while the warehouse and serialization leads answer what the systems cannot.
Run each drill, close every gap and prepare the report
Sign drill scenarios, approve reports and approve the checks drills teach
Hold the stock, the dispatch records and the bills of lading
Keep case label codes and aggregation for each shipment
One shipment was booked short; a second truck's proof of delivery, its label codes matched to serialization, accounted for the cases.
The warehouse bin still held cases of one packaging lot, and the agents corrected their own draft.
The reserve and retain log split reserve samples in the marketed pack from bulk retains kept by site practice.
EU GMP 8.30 asks for out-of-hours tests too; the agents could not answer, so the compliance manager did, in their own words.
demoSample data, from the working solution.
They read the systems of record and the client's structured replies, and never contact a supplier or a consignee.
Walks from the scenario's start record back to the supplier lot: receipt, certificate and identity test.
Walks forward through dispensing, batches, packaging orders, case aggregation and shipments.
Checks at each level that what came in equals what went out, plus samples, rejects, stock and variance inside the tolerance.
Sends structured receipt requests through the client portal and reads only their fields and attached proofs.
Drafts the drill report with each number sourced, and versions each change.
Reads the draft report as an inspector might and lists the questions one would ask.
What the drill looks like when nothing is unaccounted, and the records and plans around it.
demoSample data, from the working solution.
A mock recall is a timed drill: assume one lot is bad, then prove where each gram and pack of it went. Here agents trace the lot back to its supplier and forward to each distribution center, and the quality head signs the reconciled report.
That the distribution of each lot can be readily determined, and that delivered and accounted quantities reconcile. The drill runs against the target in the plant's own procedure, and the clock stops only when nothing is unaccounted.
Batch genealogy is the map of where a lot went. A mock recall proves that map to the unit against a clock, reaches the client's centers for receipts, and ends in a signed report.
No. They answer a short structured form on the client portal with cases received and the carrier's proof of delivery.
Backward traceability follows a lot from its start record back to the supplier lot, with its receipt, certificate and identity test. Forward traceability follows it through dispensing, batches, packaging orders, case aggregation and shipments to each distribution center. A drill runs both and reconciles the quantities at each level.
No. It is an exercise, and the screens say so. A real recall is the client's decision, made by its own recall committee.
Drift caught while the batch is still in the plant, and traced down the link that moved.
1-min demoProcess Drift DetectionDrift caught batches before a result fails, with what the drifting batches share.
1-min demoEnvironmental Monitoring TrendingA hot spot is ringed at alert level, weeks before an action result.
1-min demoSend one lot's receipts, batch records and shipping records, and we will run it as a drill that shows where each pack went.