MapLogicsBook a call

For medical & pharmacy couriers

The chain of custody writes itself.

Your drivers scan, sign and record temperatures as part of doing the job. The compliance record is finished when the route is — not typed up in the evening, not reconstructed from a binder in March.

Built for independent operators running 5 to 40 vehicles. Not a committee sale, not an implementation project.

What changes

Three things stop 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 time to move something — before the client calls, not after.

The evening admin

Nobody types up the day. What the driver captured at the door is the record, timestamped on their device — including where there was 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 exactly what a call is for — we would rather find out in twenty minutes than sell you something you do not need.

The product

What it does

Dispatch

Today's routes, one column per driver, with the ones at risk of missing an SLA at the top — before the client calls, not after.

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. You decide; the software does not.

Chain of custody

Every handover, signature, photo and temperature reading, timestamped on the driver's device — including when there is 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 — 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 an opaque specimen reference supplied by your client — never a patient name, date of birth or medical record number. Patient identity stays in their system, where it belongs.

It is the schema, not a setting

There is no field to put a patient name in. A control nobody can switch off at 2am is a different kind of promise from a policy.

One database per tenant

Your operation is physically separated from every other courier's — not a column in a shared table with a filter in front of it.

Every custody read is logged

Including ours. If our support team opens your data, it appears in your audit log with the reason.

How the no-PHI architecture works →

Getting started

Early partners

We are working with a small number of courier operators to build this properly. That means direct access to the people writing it, pricing that reflects the trade, and real influence over what gets built next.