In many multi-site LTC pharmacies, the delivery operation runs on what a few experienced dispatchers and drivers know. They know where each delivery goes inside each facility, who's allowed to sign for it, and which outlying account slows down every route it's on.
That works until someone's out sick, a route gets reshuffled, or an auditor asks for a Schedule II record from weeks ago. Running delivery this way also makes cost hard to see and harder to bring down, at a time when reimbursement cuts are squeezing pharmacy margins.
This article looks at three areas where multi-site LTC delivery gets harder to manage: recurring facility routes, nurse station handoffs, and courier deliveries. It also covers what delivery management software needs to handle each one.
Quick answer: How can multi-site LTC pharmacies manage medication delivery effectively across facilities?
- Use AI-powered route optimization that plans recurring cycle-fill routes around each facility's med pass window and the time drivers spend at each nurse station, as well as drive time.
- Choose delivery software that reports cost per stop by facility, so contract pricing reflects what each facility actually costs to serve.
- Assign urgent STAT orders automatically to a driver who can fit them in without missing other delivery windows, or to a delivery partner.
- Set proof of delivery requirements by delivery type and record each handoff at a facility separately, so every signature and count ends up in your records.
- Run courier partners through the same delivery platform as your own drivers, so their proof of delivery arrives the same day instead of on paper days later.
How to Keep Delivery Costs Down Across Multiple Care Facilities
Cycle-fill routes make up a large share of your delivery cost. Because they repeat on a fixed schedule, any inefficiency in a route repeats every time it runs.
Many factors affect that cost, but four are decisions your operations team controls directly: how you plan routes, whether you know what each facility costs to serve, which stops your own drivers take, and how you handle STATs.
Plan recurring routes once, then re-optimize when things change
Some LTC pharmacies run hundreds of recurring routes a week on fixed dispatch windows. If dispatchers rebuild those routes by hand every day or copy them from last week's spreadsheet, they spend time on routes that haven't changed, and any inefficiency in them carries over unnoticed.
If you already use route optimization, the question is what it plans around. An LTC route depends on more than drive time. It also depends on how long drivers spend at each nurse station, and on when each facility needs its medications before med pass. Plan each recurring route around all three once, then re-optimize it when something changes: you add a facility, lose an account, or a building's census shifts.
What to look for: AI-powered route optimization that plans recurring multi-facility routes around service time and each facility's delivery window as well as drive time, and re-sequences stops automatically when STATs come in.
Know your cost per stop by facility
Many pharmacies don't have a clear view of what each facility costs to serve. Their delivery data sits in separate tools, so even the total cost has to be pieced together by hand. That matters because some facilities cost far more to serve than others. One might sit well beyond the rest of the route, for example, while at another, drivers routinely wait at the nurse station.
Once you know what each facility costs to serve, you can bring that number into contract renewals and pricing. Without it, you're negotiating service fees on gut feel, even as reimbursement keeps shrinking.
What to look for: Reporting that breaks down on-time rate, exceptions, and cost per stop by facility, driver, and region.
Consider sending outlying stops to delivery partners
Your own drivers tend to be most efficient on dense, recurring routes they know well. An outlying facility or a home hospice patient far from the rest of the route can take a driver away for a large part of the shift, and the facilities later on that route may wait longer as a result.
For some of those deliveries, a courier or common carrier may be faster or cheaper. The right choice depends on your volume, the distance, how urgent the order is, and what's being delivered. You might keep controlled substances and time-critical orders with your own drivers, for example, and send routine outlying deliveries to a partner.
Whatever split you choose, it helps to agree on clear rules ahead of time, so dispatchers aren't deciding one phone call at a time.
What to look for: Dispatch that sends orders to your own drivers, a courier, or a common carrier from the same system, with the same tracking on each.
Handle urgent orders without delaying scheduled routes
STAT orders are urgent and can't wait for the next scheduled run. Pharmacies with more hospice accounts tend to get more of them.
The risk is in how a STAT gets handled. If a dispatcher pulls the nearest driver off a full route, the STAT arrives on time, but the facilities still left on that route may get their medications late.
A better approach is to give the STAT to a driver who can fit it in without missing any of the delivery windows already on their route. If no driver can, send it to a delivery partner instead.
What to look for: Software that automatically picks the best driver for each urgent order, based on where drivers are, how full their routes are, and the delivery windows they need to meet. It should then reorder the stops on that route for you, so a dispatcher doesn't have to rebuild it by hand.
How to Make Sure Every Medication Handoff Is Documented
Every time a driver hands medications to facility staff, your pharmacy needs a record of it. Yet many delivery tools let a driver mark a stop complete without capturing the right proof, so missing records often surface only when an insurance audit or DEA inspection asks for them.
Four practices help close that gap: recording each handoff separately, setting proof of delivery requirements for each type of delivery, logging returns at the facility, and keeping facility instructions with each delivery.
Record each handoff separately
A single facility address can involve several handoffs. A building with four nursing stations, for example, needs four signatures. At a group home, each resident's medications need their own handoff, because one resident's medications can't be signed for under another's name. If your system treats the whole address as a single stop, drivers end up collecting the extra signatures on paper, outside your delivery record.
What to look for: Delivery software that lets you split one address into separate deliveries, one for each nursing station or for each resident at a group home. The driver still makes one trip into the building, but each handoff gets its own signature and proof of delivery.
Set proof of delivery requirements for each type of delivery
On a single shift, the same driver might make several kinds of deliveries, such as:
- A standard drop at a nurse station
- A controlled substance delivery that requires a joint count with the nurse
- A refrigerated medication
- A pickup of returned medications
- A home hospice delivery signed by the patient or a caregiver
Each one needs a different kind of proof.
Relying on drivers to remember which proof each delivery needs is risky, especially on a busy shift. A missed scan or signature may only come to light during an audit. And without a check on who signs, a busy receptionist may end up signing for a controlled substance that only authorized staff should accept.
What to look for: Delivery software that lets you set proof of delivery requirements by delivery type. The driver app should block a driver from completing a controlled substance delivery without the barcode scans and signature, or a refrigerated delivery without a photo of the medication in the fridge. It should also let you capture the signer's name, role, and license number where your state or facility requires it.
Log returned medications at the facility
Drivers also pick up medications that facilities send back to the pharmacy, and these returns are easy to lose track of. If a driver only writes "3 bags" on a clipboard at the end of the route, nobody can tell later which items came from which facility, who handed them over, or whether everything picked up actually made it back to the pharmacy.
What to look for: Delivery software that records each pickup of returned medications as its own entry, with the item count and the nurse's signature captured at the facility at the moment of pickup.
Keep facility instructions with each delivery
Drivers need facility-specific details at each stop, such as entry codes, which unit and nurse station to go to, and whether medications go to the med cart or the med room. When that knowledge lives only with your most experienced driver, a fill-in driver loses time at every facility they don't know.
What to look for: Delivery software that lets you save facility instructions with each delivery, so they appear in the driver app every time a driver arrives at that facility.
How to Keep Courier Deliveries Inside Your Chain of Custody
Courier deliveries are where many LTC pharmacies find gaps in their chain of custody. Your own drivers may capture proof of delivery digitally, but a courier may send back a photo of a signed paper sheet, sometimes days later. Until it arrives, you can't close out the delivery. And if a controlled substance count is questioned in the meantime, you don't have the proof.
Three practices help keep courier deliveries as well documented as your own: setting one standard for every driver, tracking courier deliveries as they happen, and using the data when courier contracts come up for renewal.
Set one standard for every driver who carries your medications
Start by writing your proof of delivery requirements into the courier agreement, including the same scans, signatures, signer details, and timestamps you require from your own drivers. A written requirement only goes so far, though. If courier drivers record your deliveries in their own app, you still depend on their process and on how quickly they send the records back to you.
What to look for: A platform that dispatches to delivery partners with the same required proof of delivery steps as your internal drivers, so their records land in your system as soon as the stop is done.
Track courier deliveries as they happen
When a facility calls about a late urgent order that a courier is running, your team should be able to answer without having to call the courier first. Live tracking on courier deliveries also lets you step in before a delay causes a missed med pass.
What to look for: Live tracking and ETAs for partner deliveries in the same view as your own fleet.
Use delivery data when renewing courier contracts
When each courier keeps delivery records in its own system, comparing their performance is hard. You may not know which partner is on time most often, which one has the most exceptions, or how their cost per delivery compares with your own drivers'. Without that data, it's harder to negotiate rates, decide which routes to bring back in-house, or build a reliable last-mile carrier network over time.
What to look for: Reporting that compares courier partners and your own drivers on the same metrics, such as on-time rate, exceptions, and cost per delivery, all in one place.
How Onfleet Supports Multi-Site LTC Pharmacy Delivery
Onfleet is AI-powered last-mile delivery software that helps long-term care and hospice pharmacies run facility routes and home deliveries in one place, with internal drivers and delivery partners.
- Recurring routes planned around delivery windows. AI route optimization plans multi-facility cycle-fill routes around drive time, service time, and each facility's delivery window, and re-sequences stops when STATs and admissions come in.
- Required POD steps by delivery type. Choose which proof of delivery steps each task requires, such as a signature, photo, or barcode scan. The driver app won't close the task until every step is captured, and photos carry a timestamp and GPS location.
- Your own drivers and couriers in one place. Auto-dispatch sends each order to your own driver or a courier, with the same tracking and proof of delivery requirements for both. Onfleet Connect adds 150+ vetted couriers, and dispatchers see every delivery in one live view.
- Cost and performance by facility. Delivery analytics break down on-time rate, exceptions, and cost per stop by facility, driver, region, and courier partner.
- Security for healthcare. Onfleet is SOC 2 Type II certified, offers a HIPAA BAA, and uses a no-PHI data model. Details are on the Onfleet security page.
How Bayshore HealthCare scaled medication delivery with Onfleet
Bayshore HealthCare delivers medication and medical supplies to patients across Canada. When a new government contract meant scaling from 300 to 2,000 orders a day, its team replaced hand-built routes with Onfleet. Route planning dropped from 30 to 60 minutes to roughly 5 to 10 minutes per dispatcher, and Bayshore keeps the 90% on-time rate its contract requires.
"They [government auditors] might pick out 14 different orders and tell me to provide proof of deliveries. And that's something we get from Onfleet." Daniel Akinniyi, Logistics Manager, Bayshore HealthCare
Read the full Bayshore HealthCare case study.
With Onfleet, your team can plan facility routes around each delivery window, document every handoff, and manage your own drivers and couriers in one place. Talk to a delivery expert to map out how Onfleet would run across your facility network, including your recurring routes, facility handoffs, and courier partners.
Frequently Asked Questions About LTC and Multi-Site Pharmacy Delivery
What should an LTC pharmacy look for in delivery management software?
An LTC pharmacy should look for delivery management software that handles recurring multi-facility routes and same-day orders in one dispatch view, enforces different proof of delivery requirements by delivery type, and gives courier deliveries the same tracking and records as its own fleet. Reporting on cost per stop by facility, a HIPAA BAA, and a SOC 2 Type II report should be on the list too. Onfleet covers each of these and supports both facility routes and home deliveries for LTC and hospice pharmacies.
Can delivery software handle several signatures at one facility address?
Some delivery software can handle several signatures at one facility address, as long as each nursing station, or each resident at a group home, is recorded as its own delivery at that address. Each delivery then carries its own signature and proof of delivery, which keeps per-resident handoffs separate for HIPAA. In Onfleet, every task can have its own required POD steps, so a driver completes each handoff in the app instead of collecting extra signatures on paper.
How can LTC pharmacies get proof of delivery from couriers faster?
LTC pharmacies get proof of delivery from couriers faster by having courier drivers complete deliveries in the pharmacy's own delivery platform instead of their own app or paper sheets. The signature, scans, and photos are then available as soon as the stop is completed, not days later. Onfleet lets pharmacies dispatch to delivery partners with the same required POD steps as their internal drivers, and Onfleet Connect provides access to 150+ vetted couriers.
Should an LTC pharmacy use its own drivers or third-party couriers?
An LTC pharmacy doesn't have to pick one or the other. Its own drivers tend to work best on dense, recurring facility routes, while third-party couriers can cover outlying facilities, after-hours orders, and extra volume. What matters is that both follow the same proof of delivery requirements and appear in the same tracking view. Onfleet lets pharmacies manage internal drivers and delivery partners on one platform, and Onfleet Connect gives them access to 150+ vetted couriers when they need more capacity.
Is Onfleet HIPAA compliant for LTC pharmacy delivery?
Onfleet supports HIPAA compliance for LTC pharmacy delivery. It offers a business associate agreement (BAA), holds a SOC 2 Type II report, and uses a no-PHI data model, which means it doesn't store protected health information. More detail is on the Onfleet security page.