MapLogicsBook a call

Dispatch. Drive. Prove.

The compliance record is not a separate task at the end of the day. It is what falls out of the driver doing their job.

1 · In the office

  • Today's routes, one column per driver.
  • Routes at risk of missing an SLA sort to the top, with how much slack is left — enough time to phone the driver rather than the client.
  • Unassigned work is prominent, and an unassigned STAT is the loudest thing on screen.
  • Drag a stop to another driver. Pin a stop and the optimiser will not move it.

2 · In the van

  • Today's stops in order, with the access notes — the buzzer code, the dock — up front.
  • One tap to navigate. Arrive and depart recorded with the device's own timestamp.
  • Scan the specimen, or type the reference. Both work; neither blocks the other.
  • Signature, photo, temperature — whichever the client's rules require for that stop.
  • No signal is not an error. Everything completes on the device and syncs later. A basement dock does not stop a driver working.

3 · When someone asks

  • A complete custody record for any specimen: who held it, when, and what they recorded.
  • Temperature history with any excursion flagged, not buried.
  • Exceptions with the reason, the photo, and what was done about it.

The record is append-only. A correction is a new entry that explains itself, not an edit that quietly replaces what was there before — which is the difference between a record and a document.

See it on a call