Plan beside actual for every route, driver, stop and day.

A control score for each site, the trend behind it, the route on the map and the driver's own account, each on one screen.

Plan against actual, before and after the debrief.

The daily trend draws each source of hours as its own line, so the planned hours and what actually ran sit together, day by day.

Transport control

Illustrative data

Transport dayDriversRoutesDaily trend

Hours by sourceLast 4 weeks · Site North

Planned Actual

Week 1 over plan

+10%

Week 4 over plan

+4%

The planned hours draw first.

Four weeks of planned driver hours at an invented site, weekdays heavier than weekends.

What actually ran sits beside the plan.

For the first two weeks the actual hours run well over plan, day after day.

Week 3: the debrief switches on.

Drivers start explaining their shifts and the actual line closes in. The shaded gap is the cost, and it is where their explanations point.

From 10% over plan to 4%.

The weekly gap in week one, before the debrief, and in week four, after it.

Watch the control score as coaching takes hold.

An invented site over eight weeks, with the debrief switched on in week three. Transport control scores each week against plan and ranks every driver worst first.

Transport control

Illustrative data

Transport dayDriversRoutesDaily trend

Site North

Week 1 of 8

71Slipping

Debrief on

W1W2W3W4W5W6W7W8

3 drivers in the red

Below 70: worth a coaching conversation

Drivers: worst to best control

Min 3 runs

#DriverRunsSince W1Score

1Sam W.23·58
2Priya D.21·64
3Tom H.24·69
4Aisha K.22·74
5Lewis M.20·79
6Grace O.25·86

Week 1: the site is slipping.

A control score of 71, with three drivers in the red. Below 70 is worth a coaching conversation.

Week 3: the debrief starts.

Drivers explain their incidents at the kiosk, and team leaders coach from the answers.

The league re-sorts as coaching lands.

Drivers who started worst climb as their runs come back closer to plan. Nobody is ranked on fewer than three runs.

Week 8: the site is in control.

The score has passed 85, and the conversations move on to the routes still drifting.

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.