WorkflowManufacturing Intelligence

Mock Recall & Batch Genealogy

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 ↓
Watch with transcript →
The problem

The drill stopped at the dock, and two cases were never booked in

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

The Problem Today

Recall drills are pieced together from six systems and a mailbox, and often end at the dock with no proof each case arrived.

765
FDA drug recall entries with report dates in 2025, openFDA published

Exported and joined by hand

  • Batches
  • Warehouse
  • Shipments
  • Emails
  • Receipts answered in free textClient centers reply by email, days after the request
  • Holes an inspector finds firstSplit deliveries, uncounted samples, stock still in a bin

The Solution

  1. A signed drill scenario starts the clockThe quality head signs which lot is assumed suspect
  2. Back to the supplier, forward to each packReceipts, dispensing, batches, packaging lots and shipments, level by level
  3. Each center answers in fixed fieldsCases received and the carrier's proof, read only from those fields
  4. Challenged, then signedAn inspector-minded challenger reads it before the quality head signs

Built-in controls

  • A drill, never a recall: the client decides a real one
  • Each gap closed by a person who opened its record
  • Nobody signs a drill report they ran

What You Get

Clients and inspectors get a recall plan proved to the unit, each number tied to the record behind it.

  • Holes found in a drillA split delivery and a draft error closed before signature
  • Lessons carried into the next drillEach drill's gaps become checks once the quality head approves
  • Clients answer a short formTheir centers confirm receipts without a single email
Features

Mock recall features, from one suspect lot to a signed drill report

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.

  1. 01Drill clock

    Mock recall drill timed against the procedure's target

    • A drill scenario the quality head signed. The assumed suspect lot and the target are fixed before the clock starts, so the drill tests the plan as written.
    • Six levels, one bar each. Supplier lot, receipt, batches, packaging lots, finished packs and shipments each fill only from their own record.
    • Marked as an exercise, never a recall. The drill states that a real recall is the client's decision, made by its own recall committee.
  2. 02Backward trace

    Backward traceability to the supplier lot and its certificate

    • Receipt to certificate. The backward tracer reads the ERP receipt and the supplier's certificate of analysis for the lot.
    • Variance inside the tolerance. Dispensed, sampled, in-stock and weighing variance add up to what was received, and the variance is checked against the warehouse procedure's limit.
  3. 03Batch genealogy

    Batch genealogy forward through dispensing, batches and packaging lots

    • In equals out at each level. The reconciler checks that tablets made equal tablets packed plus QC samples, retains and rejects destroyed on the line.
    • Each pack accounted, shipped or not. Finished packs split into shipped cases, stock still in the warehouse and reserve and QC samples.
    • Widened to other plants mid-run. Mid-run, the compliance manager can widen the trace to other plants that drew from this lot.
  4. 04Client portal

    Receipt confirmations answered by the client's centers in fixed fields

    • A short form instead of an email. The client's supply chain lead enters cases received and attaches the carrier's proof; a note never changes a count.
    • Only fields and attachments count. The receipt chaser reads the structured answer and the proof of delivery, so free text cannot slip a number into the report.
  5. 05Gap

    Lot traceability gaps shown hatched until a person closes them

    • The gap is drawn, not hidden. Two cases booked short at one center stay hatched on the shipments bar until a record accounts for them.
    • The clock keeps running. The drill is not done while any quantity is unaccounted, so a near miss cannot be reported as complete.
  6. 06Proof of delivery

    A second truck's proof of delivery, matched to the serialization record

    • Label codes matched to serialization. The receipt chaser matches the case label codes on the proof to the serialization record for the two cases.
    • Accepted by a person after reading. The compliance manager opens the proof, reads it and accepts it with a reason; the center is then asked to book the cases into stock.
  7. 07Challenger

    A challenger asks what an inspector would, and corrects the agents' draft

    • The agents' own error caught. Draft one said every finished pack had shipped; the warehouse bin held cases of one lot, and version two says so.
    • Answers accepted only from the source. Each answer is accepted after the compliance manager opens the record behind it, or rejected with a reason.
    • Plan questions go to a person. When a question is about the recall plan itself, the agents say they cannot answer and a person writes it.
  8. 08Drill report

    Mock recall report reconciled level by level and signed with its meaning

    • Each number links to its record. The report reconciles delivered and accounted quantities at each level, as EU GMP 8.29 asks of a recall's final report.
    • Prepared by one, approved by another. The compliance manager signs as preparer, and the quality head approves after reading the report and the person-written answer.
    • A change reopens the report. A recount that differs clears both signatures and adds a version, and the copy sent to the client is marked superseded.
  9. 09Lessons

    Each drill's gaps become checks for the next drill, once approved

    • A gap becomes a standing check. A short receipt in one drill becomes a search for a second proof of delivery in every later drill.
    • Approval before any check runs. Proposed checks wait for the quality head, so a new QA specialist runs the next drill with the last one's lessons built in.

The person who ran the drill can never approve its report

QA compliance runs the drill and the quality head signs it, while the warehouse and serialization leads answer what the systems cannot.

QA compliance managers

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
Heads of quality

Sign drill scenarios, approve reports and approve the checks drills teach

  • A drill tested against the procedure's target
  • The person-written answers to read before signing
  • Lessons that run only once approved
Warehouse and logistics leads

Hold the stock, the dispatch records and the bills of lading

  • Recount requests with the bin named
  • Cases still in a bin found before the report
  • Dispatch records read where they sit
Serialization leads

Keep case label codes and aggregation for each shipment

  • Proofs matched to case label codes
  • Aggregation lookups for a split delivery
  • No manual export for each drill

Thirty cases the draft said had shipped were still in a warehouse bin

A split delivery the center had not booked

One shipment was booked short; a second truck's proof of delivery, its label codes matched to serialization, accounted for the cases.

Stock the draft said had shipped

The warehouse bin still held cases of one packaging lot, and the agents corrected their own draft.

A retained-sample count the draft did not show

The reserve and retain log split reserve samples in the marketed pack from bulk retains kept by site practice.

A plan tested only in office hours

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.

Only one agent sends anything out: structured requests to the client's centers

They read the systems of record and the client's structured replies, and never contact a supplier or a consignee.

Backward tracer

Walks from the scenario's start record back to the supplier lot: receipt, certificate and identity test.

  • Contacts no supplier
  • Changes no lot status
Forward tracer

Walks forward through dispensing, batches, packaging orders, case aggregation and shipments.

  • Contacts no consignee
Reconciler

Checks at each level that what came in equals what went out, plus samples, rejects, stock and variance inside the tolerance.

  • Closes no gap by itself
  • Rounds no gap away
Receipt chaser

Sends structured receipt requests through the client portal and reads only their fields and attached proofs.

  • Takes no free text as a count
  • Closes no short receipt without a person
Report writer

Drafts the drill report with each number sourced, and versions each change.

  • Signs nothing
  • Calls nothing complete below a full count
Inspector challenger

Reads the draft report as an inspector might and lists the questions one would ask.

  • Leaves its own points for a person
  • Passes no report
More screens

Inside the four-hour target, with the last two cases found on a second truck

What the drill looks like when nothing is unaccounted, and the records and plans around it.

Nothing unaccounted, inside the targetAll quantities confirmed against their records, the clock stopped inside the procedure's target, and the report ready to open.
The reserve and retain logReserve samples kept in the marketed pack, under 211.170(b), set apart from bulk and raw material retains kept by site practice.
A person's answer, kept word for wordThe challenger's points accepted from their sources, and the out-of-hours question answered by the compliance manager, marked for the approver to read.
The drill plan across products and plantsThis year's drills and next year's plan by plant and client, with targets and results; a new drill starts from a lot, a batch or a packaging lot.
Receipt confirmations by centerEach structured request by distribution center, the fields each reply carried, its attachments, and the short receipt with its proof.
Reads and signatures, in orderEach approval, acceptance and record read, in time order, with what each signature meant; the CSV export travels with the drill.

demoSample data, from the working solution.

A drill starts only from a signed scenario, and a drill never starts a recall

Whether a real recall happensThis is an exercise. A real recall is the client's decision, made by its own recall committee.
Closing a gapThe QA compliance manager opens the record behind it, then accepts it or rejects it under a reason code.
Signing the drill reportThe quality head approves it after reading it, and nobody approves a drill they ran.
Whether product may be used or shippedThe assistant answers no such question and names the person who decides.
Starting a drillA drill starts only from a scenario the quality head signed.

Questions quality teams ask about a mock recall

What is a mock recall?

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.

What does a mock recall procedure need to prove?

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.

How is batch genealogy different from a mock recall?

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.

Do the client's distribution centers need new software?

No. They answer a short structured form on the client portal with cases received and the carrier's proof of delivery.

What is forward and backward traceability?

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.

Can a drill trigger a real recall?

No. It is an exercise, and the screens say so. A real recall is the client's decision, made by its own recall committee.

Pick the lot you would
least like to trace.

Send one lot's receipts, batch records and shipping records, and we will run it as a drill that shows where each pack went.