RefillopsCounterFlow UI
PlaybookRefill queues6 min read

Building a refill status queue for busy pharmacy counters

Replace scattered sticky notes with a shared queue your team trusts — and review at the end of every shift.

Operational guidance only. Refillops does not make clinical, coverage, or dispensing decisions.

Pharmacy counter queue tray with prescription labels
Trust note · Workflow guidance only. Pharmacy teams stay responsible for patient care and clinical review.

Section 01

Why a queue beats scattered notes

Sticky notes, voicemails, and side conversations all keep work moving until they don't. A queue gives every blocker one place to live so nothing depends on the memory of whoever was at the counter when it came in.

  • One source of truth across techs, pharmacists, and shifts.
  • Aging is visible, so the oldest blockers stop hiding.
  • Hand-offs at shift change become a 30-second scan, not a meeting.

Section 02

Status labels that matter

Keep the label set small. Five is usually enough — more than seven and the team will stop using them consistently.

  • In queue — newly received, not yet triaged.
  • Claim issue — a rejection needs work before it can fill.
  • PA required — prior authorization in progress.
  • Waiting prescriber — outreach sent, waiting on a response.
  • Ready — resolved, ready for pickup.

Section 03

How to assign owners

Every row needs a named owner — a person or a small named pool. 'The team' is not an owner. Decide the owner at triage, not later.

  • Route by reject code or queue type if your team is big enough.
  • Pair each owner with a back-up so nothing freezes when someone is out.
  • Surface unassigned blockers at the top of the queue at all times.

Section 04

How to avoid repeated touches

Repeated touches are the most expensive thing in a refill queue. They usually come from missing context.

  • Attach the original reject, message, or note to the row, not to a person.
  • Capture the last action and timestamp so the next tech doesn't redo it.
  • Use templates for common outreach so each follow-up takes seconds.

Section 05

What to review each shift

End-of-shift review takes ten minutes and pays for itself the next morning.

  • Top three oldest rows — why are they still here?
  • Any unassigned rows — assign before you leave.
  • Repeated reject codes — flag for tomorrow's standardization.
Common workflow example
"Aisha N. · Lisinopril 20mg · Reject 70 · Owner Maya · 2h in queue · Next action: try alt NDC, then request PA if denied."

Related

Keep reading.

Patient update on phone — pickup, prescriber wait, prior auth status
Patient updates · 5 min

How pharmacies can reduce “is it ready?” calls

Claim rejection slip with payer reject code and next action
Rejected claims · 7 min

Why rejected claims need a workflow, not a note

Want this running in your pharmacy?

See how Refillops turns this guidance into a live, owned workflow your team can run every shift.

See use casesSee pricingBook a demo