For couriers moving clinical specimens
Labs and hospital systems expect a custody record that holds up. Most courier software wasn't built to produce one, so it ends up on paper in the van.
The workflows this is actually built around
- Routed lab pickups. Fixed daily runs with pickup windows, built from templates so tomorrow's route is not typed from scratch.
- STAT mid-route. An urgent pickup arrives at 10:40. The board shows which drivers can take it, what it adds, and which existing stops it puts at risk, named rather than counted.
- Chain of custody. Scan at pickup, scan at handover, signature at delivery. Each event is timestamped on the device at the moment it happened rather than whenever the phone next found signal.
- Cold chain. Temperature entry with the required range on screen. An out-of-range reading warns the driver at the site, while they can still re-ice the container or call you.
- Driver-to-driver transfer. One driver releases, the other receives, each on their own device. Two attestations, which is what makes a chain a chain.
- The record request. A client asks about a specimen from three months ago. It takes seconds, and it is complete.
We never see patient data. Your client's specimen reference is opaque to us. We track the reference; they hold the identity.How that works →
Where the record has to hold up
Lab clients audit their couriers. Contracts get re-bid on service quality that somebody has to evidence. The point of recording custody as a byproduct of the work is that when someone asks, the answer already exists rather than being reconstructed from a driver's memory and a route sheet.