Near-Expiry Medicines Register: Format & Policy

Why inspectors pull out the near-expiry register first

A drug inspector or hospital accreditation auditor walks into your pharmacy store. Before they check the cold chain log or the Schedule H register, they ask for the near-expiry register. It is the fastest proxy for whether the pharmacy actually controls its stock — or just reacts after something expires on the shelf.

If you hand them a printout with gaps, crossed-out rows, and no action column, the conversation gets uncomfortable quickly. If you hand them a clean, dated register with an owner named against every batch, the rest of the audit tends to go smoother.

This post gives you the exact format, the policy logic behind it, and the review cycle that holds up under scrutiny.

What the register needs to capture

A near-expiry medicines register is not a list of expiring drugs. It is a control document — it proves that a responsible person saw the batch, decided what to do with it, and followed through. That distinction matters to auditors.

Every row in the register should carry these columns:

• Item name and strength — generic name, formulation, strength (e.g., Metformin 500 mg tablet)
• Batch number — exactly as printed on the pack; no abbreviations
• Expiry date — month and year, or full date if printed
• Quantity — current physical count at the time of entry, in the smallest dispensable unit
• Action — one of: Return to supplier / Transfer to ward / Markdown & dispense first / Quarantine / Destroy
• Owner — the name or designation of the person responsible for executing the action
• Date of entry — when the row was added
• Closure date — when the action was completed or the stock reached zero

That last column is the one most registers miss. An open row with no closure date is an audit finding waiting to happen — it means no one confirmed the action actually happened.

The policy behind the register

A register without a written policy is a form. A register backed by a policy is a system. The policy does not need to be long — one page is enough — but it needs to answer four questions:

1. What triggers an entry?

Define the near-expiry window in writing. A common approach: any batch expiring within 90 days of the review date is entered. Some hospital pharmacies use 180 days for slow-moving items like specialty injectables. Pick a number, write it down, and apply it consistently.

2. Who reviews the register and how often?

Monthly is the minimum for most pharmacy settings. High-volume wards or fast-moving categories may need fortnightly checks. The policy should name the designation responsible — not a person's name, which changes — and require a signature or dated countersign on each review.

3. What are the permitted actions and their sequence?

Write the decision tree explicitly. For example: first attempt supplier return within the credit window → if refused, transfer to a ward or department that can consume before expiry → if consumption is not possible, quarantine and prepare for disposal under CDSCO guidelines. Without this sequence written down, different staff make different calls and the register becomes inconsistent.

4. How is the register stored and for how long?

Paper registers should be bound, not loose-leaf. Digital records need an audit trail. Retention period: follow the Drugs and Cosmetics Act, 1940 and Rules thereunder — Rule 65 requires certain pharmacy records to be maintained for a minimum period; check the specific sub-rule applicable to your licence category with your state licensing authority.

The hospital pharmacy complication: wards

A standalone retail pharmacy has one physical location. A hospital pharmacy supplies multiple wards, OT, ICU, and outpatient counters — each with its own sub-stock. This creates a near-expiry problem that a single register cannot solve without ward-level ownership.

Picture a typical 200-bed hospital where the pharmacy issues stock to eight wards. A batch of IV fluids nearing expiry sits in the surgical ward's crash cart. The central pharmacy register shows it as issued and closed. Nobody owns the follow-up at ward level. The batch expires in the ward, undispensed, and turns up during an internal audit.

The fix is a ward-indent column or a ward-level sub-register. When stock is transferred to a ward as a near-expiry action, the ward in-charge or nursing supervisor should countersign. That signature is the ward's acknowledgment that they are now the owner of the action — consume before expiry or return to pharmacy.

This is the structural difference between a pharmacy that passes hospital accreditation audits and one that scrambles before them. The hospital outpatient pharmacy mixed inventory pool post covers the broader inventory separation problem if your OPD and inpatient stocks are getting mixed.

Review cycle that actually works

The register is only as good as the review that feeds it. Here is a cycle that works for a mid-size pharmacy without a dedicated inventory team:

Monthly shelf walk — on a fixed date (say, the first working day of the month), a pharmacist physically checks all storage areas against the system stock and flags any batch expiring within the defined window. New rows are added.

Weekly action check — every week, the owner named against each open row confirms status. If the action is complete, the closure date goes in. If it is stalled — supplier hasn't responded, ward hasn't consumed — it gets escalated.

Quarterly policy review — the policy itself is reviewed once a quarter. Are the near-expiry windows still right? Are the permitted actions still aligned with current supplier agreements? This review should be signed off by the pharmacist-in-charge.

For the operational side of what to do with stock once it is flagged — discounting, returns, transfers — the near-expiry stock strategies post covers the full decision set.

Common gaps inspectors flag

• No action column — the register lists expiring stock but does not record what was decided
• No closure date — rows stay open indefinitely; no proof the action happened
• Batch number missing or abbreviated — makes cross-referencing with purchase records impossible
• Owner column blank — collective ownership means no ownership
• Register not dated at review — cannot prove it was actually reviewed on schedule
• Near-expiry window not defined in writing — inspector asks what qualifies as near-expiry; no one can answer consistently

Each of these is fixable before an inspection, not during one.

Software or paper: what each can and cannot do

A paper register, maintained well, satisfies most drug inspector requirements. It is portable, requires no power, and is easy to produce on demand. Its weakness is that it does not alert anyone — you have to go looking for near-expiry stock; it does not come to you.

A digital system can generate the near-expiry list automatically, send alerts before batches enter the window, and log actions with timestamps. The ward-indent workflow — where a ward countersign closes the loop — is particularly hard to manage on paper across multiple locations.

If your pharmacy manages stock across wards or multiple dispensing points, ShelfLifePro's ward-level expiry tracking and near-expiry alerts are worth a look. There's a 14-day free trial, no credit card required.

The one-page policy structure

When you write the policy, keep it to one page so it actually gets read. Cover these five points in plain language:

• Scope — which locations and stock categories this policy covers
• Near-expiry definition — the window (e.g., 90 days to expiry)
• Identification process — who does the shelf walk, how often, using what method
• Action sequence — return → transfer → quarantine → disposal, with the decision criteria
• Roles and sign-off — who reviews, who countersigns, who retains the record

Date the policy, name the version, and keep the superseded version on file. Auditors sometimes ask to see the previous version to confirm the policy has actually been maintained over time, not created the week before their visit.