Every stop. Every minute. Every handoff.

A single real-time model guarantees a dispatcher, a driver, a practice and their records never diverge.

A weekly driver roster showing early, day and late shifts across a service area.
The Operion live operations board: courier routes drawn as rows of stops, each with its planned pickup window printed above and the time the driver was actually recorded printed below.
A practice's routing behaviour: a row per weekday, each with its pickup window and six weeks of visits behind it.

Driver en route

Pickup recorded

STAT · 24 min

One dashboard for
the whole day.

Every route, every driver, every practice and their current status. Colours reflect pickup obligations and status circles reflect practice obligations.

Live operations LIVE
The live operations board in full: eight courier routes for one day, each route a row of stops with planned windows above and recorded times below, and a status badge saying whether the route is running, completed or unassigned.

Route engine

Builds the day against every practice’s window and every driver’s shift — then keeps checking it while the day runs.

STAT dispatch

STAT orders are absorbed into existing routes based on driver availability. Exceptions raised to dispatchers.

Live operations

Planned against actual, stop by stop, for every route at once. One picture, and it changes when the day does.

Chain of custody

Every arrival, scan and handoff recorded once and never edited. Who had it, and when, still answerable years later.

The live operations board, showing every route for one day. A practice's visit history: a row per weekday, each with its pickup window, a productive-visits count and six weeks of individual visits behind it. A weekly roster grid: nine drivers down the side, days across the top, and a coloured shift block for each working day.
01

The dashboard

All daily routes on a single page. Contractual pickup window above each stop, actual arrival beneath. Colours indicate compliance.

The live operations board, showing every route for one day.
02

Practice history

Six weeks of visit history for each practice. Weekday by weekday and window by window.

A practice's visit history: a row per weekday, each with its pickup window, a productive-visits count and six weeks of individual visits behind it.
03

The schedule

Indicates driver shifts, workdays, time-off and coverage a week or month at a time per service area.

A weekly roster grid: nine drivers down the side, days across the top, and a coloured shift block for each working day.

The real-time route,
in a pocket.

A driver app that operates in lock-step with dispatchers. One stop at a time, record and report issues, status in real time. If a STAT comes in mid-run, it drops straight into the driver’s queue — no phone call needed.

The driver app sign-in screen, noting that signing in here signs you out of any other phone.
Sign in —
one phone at a time
The driver's day: the next stop with its distance and due time, the stops still to come, and the ones already done.
My day —
next stop, then the rest
A stop in the driver app: the drop box and its code, how to get in, who to ask for at the front desk, and how much margin is left.
The stop —
box, code, who to ask for
A new STAT pickup arriving mid-route, showing where it fits, which stop moves, and by how much.
A STAT lands —
and what it moves
Most lab operations run in pieces — planning tools, routing tools, spreadsheets, drivers on phones, paper notes — nothing ties them together. Each piece is right — together they never are.

Minutes matter.

Request early access