Five records of one transport day, lined up and explained.

routerecap reads what your clock, planner, route system and telematics already record, and the driver explains the difference at the end of the shift.

One transport day, created five times.

Every site runs the same five systems. Each gap between them has its own owner and its own fix.

Driver hours, one day, one site

Illustrative data

080160240320

hrs

0 h

Clock

Time and attendance

0 h

Plan

The planner

0 h

Journey plan

Route system

0 h

Journey actual

Proof of delivery

0 h

Actual

Telematics

owner

A50 h

Rota and labour planning

B37 h

Transport office

C+28 h

Driver and store

D+37 h

Driver debrief

The clock records every hour paid for.

On this invented day, 312 driver hours. The other four systems each record a shorter, or longer, version of the same day.

A · Paid, never planned.

Hours paid for that no route ever used. Owner: rota and labour planning.

B · Changed at replan.

Transport rewrites the plan before dispatch. Owner: transport office.

C · Lost on the road.

Late starts, dwell and detours on the day. Owner: driver and store.

D · Off the record.

What the vehicle did that nobody logged. Owner: driver debrief.

Every gap now has an owner.

Four gaps, each measured in hours and each with the person who can close it. That is the list a transport director works from.

The planned route and the vehicle's trace, on one map.

Every stop keeps its delivery window and its time on site, so a late arrival or a long dwell is read against the slot the stop was given.

Route review

Illustrative data

MapStopsIncidentsNotes

R14 Midlands Loop · Sam W. · Tuesday

06:10

1Store 104, Ashby
07:30 to 08:30On time
2Store 211, Coalville
10:00 to 10:3014 min late
3Store 112, Hinckley
11:30 to 12:300 min on site

Fix raisedOwner: planning

Move stop 3 to the 12:00 slot.

From the driver's note: the gate opens half an hour after the booked slot.

The plan, as the route system drew it.

Three stops on an invented route, each with its delivery window.

The vehicle's trace, from telematics.

The clock runs as the vehicle drives. Stop 1 lands inside its window.

A road closure, pinned where it left the plan.

The detour adds 9 km, and stop 2 arrives 14 minutes late.

A long dwell at stop 3.

48 minutes on site, counted where it happened.

The dwell becomes a named fix.

The driver's note says the gate opens late, so planning moves the slot. The fix has an owner.

The driver's account lands beside the figures.

At the end of the shift the driver signs in at a touchscreen kiosk on site, sees their route on the map and explains each flagged incident with the site's own reason codes.

Debrief review

Illustrative data

SummaryIncidentsNotesComments

R14 Midlands Loop · Sam W. · Tuesday

3 incidents1 stop noteDebriefed 14:22Score 74

Supportive outcome

Route deviationStops 1 to 2 · from the kiosk
Driver's reason: Road closed or restricted
Late arrivalStop 2 · from the kiosk
Driver's reason: Road closed or restricted › Diversion
Long dwellStop 3 · from the kiosk
Driver's reason: Waiting to unload › Gate opens after the slot

Stop note · Stop 3

The gate opens half an hour after the booked slot.

Team leader · Jo B.

Action raisedMove stop 3 to the 12:00 slotOwner: planning · Due Friday

Each incident arrives with the driver's reason.

A route deviation, a late arrival and a long dwell, each explained at the kiosk with the site's own reason codes.

The stop note, and the team leader's reply.

The driver's note on stop 3 lands with the incidents, and the comment follows the same day.

An action with an owner.

Planning moves stop 3 to the 12:00 slot, due Friday.

A supportive outcome for the driver.

The outcome is supportive unless the site's rules call for a conversation.

See routerecap on demo data before you decide.

We will walk through the five sources, the scores and the debrief with your sites in mind.

Talk to Libra about routerecap

Tell us which systems your sites run and we will shape the walk-through around them.