In this guide 6 sections
Release errors start when lot status lives only on a coloured tag or a stock sheet, because tags peel, pallets move and a green label survives a failed retest. A system status tied to the lot blocks issue until QA approves it, wherever in the store the container sits and whoever happens to be on shift.
Where the tag and the truth drift apart
Yellow means quarantine at the gate. When QC passes the lot, someone pastes a green label over the yellow one or tears it off, while the paper record lags behind. Humid stores make it worse. Adhesive labels curl, handwriting smudges, and a pallet wrapped in stretch film hides the very tag the storekeeper needs to read, and in that gap memory takes over.
Nobody lies. The tag is a copy of a decision made in the QC lab, and a copy cannot update itself when the decision changes. The sample was approved on Monday, but the retest came back out of limit on Thursday and the green label is still on the drum.
The stock sheet fails the same way, because it is updated when someone remembers, usually at day’s end, from scribbled notes and whatever the storekeeper can still recall.
- Labels peeled in humid stores or cold rooms
- Partial drums split without a new tag
- Pallets moved between racks with stale labels
- Retest dates passing without a status change
- Handwritten sheets copied late from memory
How a wrong issue actually happens
A dispensing request arrives for an excipient. The storekeeper finds a drum with a green tag, checks the sheet, which agrees, and sends it up to the dispensing booth. The lot had been moved to rejected an hour earlier by a QA officer, who recorded it in the register and walked back to the lab.
The error surfaced at the next audit, after the batch was packed, and by then the material had been blended into three batches that each needed an investigation. The cost went beyond three investigations. Stock was written off, a customer waited for dispatch, and weeks went into explaining the gap to the auditor and rewriting the release procedure.
Look at your near misses. They are free lessons. If a tag, a register and a sheet each hold a separate version of the status, you already have the conditions for this error.
What a system status changes at the rack
In software the lot has one status field, either quarantine, approved, rejected or on hold, and only QA can change it, with each change recording who, when and why. No other copy exists. The storekeeper, the dispensing operator and the QA officer all read the same field, so a decision made at the QC bench is visible at the rack within seconds.
The issue screen reads that field. A drum scanned by its lot barcode shows a clear stop if the lot is not approved, and the storekeeper cannot confirm the pick. The screen decides. Nobody has to judge at the rack.
Tags still help the eye, but they become a printout of the record and never again the source of truth that anyone relies on at the rack.
Handle expiry, retest and partial containers
Status is not only approve or reject. A lot that passes its retest date should drop to a hold, and the system flags it weeks ahead so QC can sample before the date, not after.
Partial containers need their own identity. When a drum is opened and half-used, the remainder keeps the lot number, the balance quantity and an opened date, so the next person knows what is left. Weighing a split updates stock at once. Counting the balance after each split on a calibrated scale and posting it straight to the lot avoids the common problem of three half-used drums that nobody can reconcile.
Move rejected stock physically too. A system block is a safety net, not a substitute for a segregated cage with a locked gate and a posted sign.
- Expiry and retest dates held on the lot
- Automatic hold when a date passes
- Balance and opened date for partials
- Rejected cage location recorded in the system
Test the blocks before you trust them
Run a trial with real lots. Take a quarantined drum, an approved one and a rejected one and try to issue each, because only the approved lot should pass the screen. Ask the storekeeper to try to beat the screen, because the person who issues stock all day is the best judge of whether a block can be bypassed.
Then try the awkward cases: an expired lot, a lot on hold for a deviation and a lot scanned in the wrong warehouse. Record each result on one sheet. Show the sheet to QA.
Retire the colour sheet only once a full month of trial results shows no block was bypassed and no wrong lot reached the booth. Not before.
Lot status block test sheet
Eight test cases run down the page: quarantined, approved, rejected, on hold, expired, past retest, partial drum and wrong location, each in its own row. Alongside each go the lot number scanned, the screen message, whether issue was blocked, the tester, the date and the QA initials for sign-off.
Open a blank worksheet to printQuestions owners ask
Do we still need physical labels?
Yes, labels help people at the rack. Print them from the system, so the colour always matches the record and a status change reprints the label for every container of that lot.
Who should be allowed to change a lot status?
Only QA staff with the right role. Storekeepers and production staff can see the status but cannot edit it, and every change keeps a reason, a timestamp and the name of the QA officer.
What happens to stock already on the rack today?
Do a physical count by lot, enter each lot with its present status, and have QA confirm the list before switching the issue screen on.
Can the system stop issue to the wrong batch?
It can check each scanned lot against the batch’s bill of materials, and a lot outside the approved list for that product shows a stop at dispensing.