For medical & pharmacy couriers
The chain of custody writes itself.
Your drivers scan, sign and record temperatures as part of doing the job, so the compliance record is finished at the same time the route is. Nobody types it up in the evening, and nobody goes looking for it in a binder in March.
Built for independent operators running 5 to 40 vehicles. No procurement committee and no six-week implementation.
What changes
What stops being your problem
The records request
A client asks for the custody record for a specimen from March. It is produced in seconds, complete, without anyone opening a filing cabinet.
The late delivery you found out about last
Routes at risk of missing their window rise to the top of the board while there is still slack to use. You hear about it from the board rather than from the client.
The evening admin
Nobody types up the day. What the driver captured at the door is the record, timestamped on their device, including at the stops with no signal.
The problem
If this sounds familiar
Custody lives in a binder
The dispatch system tracks where the van is. The chain of custody is on paper in the van, or in a spreadsheet someone types up in the evening.
A client asks for a record from March
Somebody spends an afternoon finding it. Occasionally it cannot be found at all, and that conversation is much worse.
A STAT lands mid-route
Three phone calls to work out who is closest, and a guess about which existing stops you have just made late.
These are the problems the product is built around. Whether they are your problems is what a call is for, and twenty minutes is usually enough to find out. If we are not useful to you, we will say so.
The product
What it does
Dispatch
Today's routes, one column per driver, with the ones at risk of missing an SLA sorted to the top while there is still time to do something about it.
STAT insertion
An urgent pickup shows you which drivers can take it, what it adds to each route, and exactly which existing stops it puts at risk. The decision stays yours.
Chain of custody
Every handover, signature, photo and temperature reading, timestamped on the driver's device at the moment it happened, signal or no signal.
Cold chain
Temperature entry with the required range on screen and an immediate warning if a reading is out of range, while the driver is still at the site.
Works offline
Hospital basements and rural routes lose signal. The driver app keeps working and syncs when it can, so nothing waits on a bar of reception.
The report
A complete custody record for any specimen, produced in seconds. This is the thing clients and auditors actually ask for.
The architecture
We do not store patient data
MapLogics holds the opaque specimen reference your client supplies, and nothing that identifies the person it came from. Identity stays in their system, which is where it belongs and where their own controls already cover it.
There is nowhere to put it
The schema has no field for a patient name. That is a stronger promise than a policy, because there is no setting for anyone to switch off at 2am.
One database per tenant
Your operation sits in its own database, separate from every other courier's. No query can wander into your data because somebody wrote a filter wrong.
Every custody read is logged
Including ours. If our support team opens your data, it appears in your audit log with the reason.
Getting started
Early partners
We are working with a small number of courier operators to build this properly. You get direct access to the people writing the software, pricing that reflects the trade, and real influence over what gets built next.