Hold First, Destroy Second: Expired Stock and Clinical Waste
Expired stock and clinical waste are the same control problem wearing two uniforms: something has to leave, somebody has to authorise it, and the record has to survive an inspection. Most facilities have the bin and not the paperwork.
There are two ways stock leaves a clinic without being used on a patient. It expires on the shelf, or it becomes waste after use. Facilities treat these as unrelated — one is a pharmacy problem, the other is a cleaning problem — and in both cases the actual failure is identical: something of value or of risk left the premises and there is no record of who authorised it, what it was, or where it went. That is not an inventory inconvenience. Under Kenyan environmental law it is the specific thing you are required to be able to prove.
The control is the held state, not the bin
The instinct is to control the disposal — a locked store, a signature, a bin that only the matron opens. That is worth having and it is not where the leverage is. The real control is the step before: taking the stock out of circulation the moment it becomes unusable, and doing it as a recorded act that other people can see. Expired stock still sitting in the pickable location is stock that will be dispensed by someone in a hurry, and the fact that you intend to destroy it on Friday is invisible to the person reaching for it on Wednesday.
Separating the two steps also separates two different authorisations, which is the point. Deciding that a batch is no longer fit for use is a clinical or pharmacy judgement. Deciding how it leaves the building — incinerated, returned to the supplier, written off — is an administrative and financial one. Collapsing them into a single act performed by one person is how expired stock gets quietly returned to the shelf, and how valuable stock gets written off as waste.
Anything that cannot be dispensed should stop being dispensable before it stops being present. The gap between those two moments is where every avoidable dispensing error lives.
The one rule worth enforcing in a clinical store
Four destinations, four different treatments
Not everything that comes off the shelf is waste, and treating it all as waste is expensive. A short-dated batch a distributor will take back is a credit, not a loss. A product recalled by the manufacturer is their cost. Something genuinely expired is your write-off. And something contaminated or clinically hazardous is a regulated waste stream with an entirely different set of obligations. The same physical act — removing it from the shelf — has four possible endings, and the ending decides who pays.
| Destination | Who bears the cost | What the record must show | Common failure |
|---|---|---|---|
| Return to supplier | The distributor, as a credit | A returns note, the batch, the agreed window, and the credit when it lands | Nobody checks whether the credit ever arrived, so the return becomes a donation |
| Manufacturer recall | The manufacturer | Every location the batch reached, and quantities remaining at each | Stock already dispensed is untraceable because the batch was never recorded at issue |
| Write-off — expired | You | Batch, quantity, value, reason, authoriser, date | Recorded as a stock correction rather than a write-off, which hides the cost of over-ordering |
| Regulated clinical waste | You, plus a licensed handler | Waste stream, weight or volume, handler licence, and a signed manifest | The handler's paperwork is the only record, and the facility keeps no copy |
The manifest is the document that matters
Kenyan facilities are required to hand regulated clinical waste to a licensed handler and to be able to show that they did. In practice that means three things kept together: a copy of the handler's current NEMA licence, a signed manifest or transfer note per collection, and an internal log that agrees with the manifests. The commonest inspection finding is not that a facility used an unlicensed handler — it is that it used a licensed one and cannot produce the paperwork, because the only copy went with the truck.
Waste volume is a diagnostic, not just a cost
A facility that tracks how much it destroys learns something more useful than the disposal bill. Expiry write-offs concentrated in a handful of items are a purchasing problem — those are the lines being over-ordered, and the reorder point on each is set too high or the pack size is wrong. Expiry spread thinly across hundreds of items is a rotation problem, which is a FEFO discipline failure at the point of picking. The two look identical on a total and require opposite responses, so a single annual write-off figure tells you nothing you can act on.
-
Hold it the moment it is identified
Whoever finds the expired, damaged or short-dated batch takes it out of issuable stock immediately and records why. This is the step that protects patients, and it should require no approval at all — anyone should be able to stop stock being dispensed.
-
Segregate physically as well as in the record
Held stock goes to a quarantine location that is not a pick face. Colour-coded containers for clinical waste, and a locked quarantine shelf for pharmaceuticals awaiting a decision. A flag in a system does not stop a hand in a hurry.
-
Decide the destination, with a named authoriser
Return, recall, write-off or regulated waste — a decision made by someone other than the person who raised the hold, recorded against the batch, with a value attached. This is where the separation of duties actually bites.
-
Execute and keep your copy of the evidence
For a return, the returns note and then the credit. For waste, the manifest, countersigned, filed against the collection date. Photograph it if the original leaves with the handler, because it will.
-
Review the pattern monthly, by item
Not the total — the top ten items by write-off value, every month. Two months of the same item at the top is a purchasing decision waiting to be made, and it is the only way disposal data pays for the effort of collecting it.
The second row is the one that separates a real control from a checkbox. A system that lets one person mark stock as waste and remove it in a single action has given you a bin with a database attached.
Can unusable stock be blocked from issue instantly?
Make them prove it: Ask someone to place a batch on hold and then try to dispense it at the till.
Are the hold and the disposal separate acts?
Make them prove it: Try to dispose of stock that is not currently held.
Does a disposal carry a reason and a value?
Make them prove it: Look at what the resulting document records.
Is the batch identifiable at disposal?
Make them prove it: Check whether the record names the batch or only the item.
Can you produce twelve months of disposals on demand?
Make them prove it: Ask for last year's write-offs by item and reason.
Does the system hold the waste stream and weight?
Make them prove it: Ask where a manifest weight would be recorded.
What AWRA OpsHub does today
- Held stock genuinely cannot be issued. Placing stock on hold moves it out of the sellable set, and every allocation query filters on that — so a held batch cannot be dispensed, sold at the till or picked, and the refusal states the reason rather than failing silently.
- Five distinct hold states — quarantined, inspection-pending, damaged, expired and returned — so why something is out of use is on the record, not in a note.
- Hold, release and dispose as three separate operations, each recording the quantity, the reason, free notes and the acting user.
- Disposal is refused on stock that is not held. You cannot dispose of available stock in one step; it must be placed on hold first. That two-step sequence — the central control in this post — is genuinely enforced, not merely recommended.
- Four disposition routes — scrap, return to vendor, rework and write-off — so a supplier return is a different record from a destruction, which is the distinction the table above turns on.
- One pending disposition per held batch, so the same stock cannot be queued for disposal twice.
- A disposal writes a stock adjustment, with a reference number, a reason, an attachment, a project and debit and credit accounts, moving through Pending → approved → applied. The write-off reaches the ledger as a document rather than as a stock correction.
- Batch-level identity throughout — expiry date, supplier and originating purchase order live on the batch, and full traceability can return every event and every remaining location for a batch, which is what makes a recall answerable.
- A daily expiry reminder across a 30, 60 and 90-day horizon with the value at risk, excluding batches with nothing on hand — so the stock that is about to need this process announces itself.
What it does not do
- Nothing expires stock automatically. An expired status exists and no job ever sets it. The reminder emails a person; a batch that passed its expiry date last week is still available to dispense until somebody places it on hold by hand. This is the single most important limitation on this page.
- No waste stream, weight or volume anywhere. Sharps, infectious, pharmaceutical and general are not categories the system knows, and a manifest weight has nowhere to go. Everything in the regulated-waste row of that table is a separate paper or spreadsheet discipline.
- No handler, licence or manifest record. No place to hold a NEMA licence, its expiry, or a signed transfer note per collection — and nothing warns you when a handler's licence lapses.
- No return-window or credit tracking on a supplier return. Return to vendor is a disposition type; whether the credit ever arrived is not tracked, which is exactly the failure named in the table.
- No write-off report by item, reason or period. Disposals exist as adjustments and can be listed, but the monthly top-ten-by-value review this post recommends is an export and a pivot, not a screen.
- No approval threshold on a disposal by value. The adjustment lifecycle provides an approval step, but nothing varies it by amount — destroying stock worth KES 500 and KES 500,000 pass through the same gate.
- No temperature or sensor integration, so cold-chain excursions — the most common reason a vaccine batch should be quarantined — are invisible unless a human notices and acts.
The two-step control is the part worth checking on a demo, and it is real: stock must be held before it can be disposed of, held stock cannot be dispensed, and the disposal writes an accounting document with a reason and an actor. That is a stronger separation than most inventory systems enforce. The gap is automation and the environmental layer. Nothing takes expired stock out of circulation for you — a person must act on a reminder — and there is no waste stream, weight, handler or manifest anywhere, so your NEMA file stays a NEMA file. Do not buy this expecting the compliance half.
The short version
Hold first, dispose second, and make them different people. Everything else on this page is paperwork around that one sequence — and the sequence is the only part that actually protects a patient.
The upstream cause of most pharmaceutical write-offs is ordering, not rotation, which is where expiry management and clinic supplies procurement meet. And the controlled-drugs register has a stricter version of this same custody logic, covered in controlled medicines custody.
Stock that cannot be dispensed, cannot be dispensed
Five hold states that genuinely block issue, disposal refused unless stock is held first, four disposition routes, and a write-off that posts as an approved adjustment with a reason and a value. Automatic expiry, waste streams, handlers and manifests are not built — the note above is specific.
See clinical stock control in AWRAFrequently asked questions
Why separate placing stock on hold from disposing of it?
Because they are different decisions by different people. Judging that a batch is unfit for use is clinical; deciding how it leaves — returned, written off, incinerated — is administrative and financial. Combining them lets one person decide and execute unobserved, which is how expired stock returns to the shelf and how valuable stock gets destroyed as waste. Anyone should be able to hold; only an authoriser should be able to dispose.
Does expired stock get blocked automatically?
No, and this is worth being clear about. A daily reminder flags batches at 30, 60 and 90 days with the value at risk, but nothing changes a batch's status when the date passes. Expired stock remains dispensable until a person places it on hold. Build the habit around the reminder, because the reminder is the whole mechanism.
What records does an inspection actually ask for?
Three things kept together: a copy of your waste handler's current NEMA licence, a signed manifest or transfer note for each collection, and an internal log that reconciles with those manifests. The usual finding is not an unlicensed handler — it is a licensed one whose paperwork left with the truck, so keep or photograph your copy at the point of collection.
Is a supplier return the same as a write-off?
No, and conflating them costs money. A short-dated batch a distributor will take back is a credit; an expired batch is your loss. Record them as different dispositions, then track whether the credit actually arrived — an unfollowed-up return is a donation to your supplier, and nothing tracks the credit for you.
What should we do with the write-off data?
Review the top ten items by write-off value every month, not the total. Losses concentrated in a few items mean over-ordering — fix the reorder points or pack sizes. Losses spread thinly across many items mean poor rotation at the pick face, which is a FEFO discipline problem. The two look identical on an annual total and need opposite responses.
Can the system track waste weight and streams for NEMA?
No. There is no waste stream, weight, volume, handler or manifest record anywhere — sharps, infectious, pharmaceutical and general are not categories it knows. Keep a dedicated waste log for the environmental obligation and use the inventory system for what leaves stock and what it was worth. Expecting one to do both is how facilities end up with neither.
How do cold-chain failures fit into this?
They are the most common legitimate reason to quarantine a batch and the least likely to be noticed, because there is no temperature or sensor integration — a fridge excursion is invisible to the system. Keep manual temperature logs with a named checker per shift, and treat a recorded excursion as an immediate hold on every affected batch, decided afterwards.
