routerecap

See where the transport day really goes.

routerecap lines up what your clock, your planner, your route system and your telematics each say about the same day. The driver explains the difference at the end of the shift.

Starts on the reports your systems already exportFigures and debrief switch on separately

A Libra Europe product

The end-of-shift debrief on an invented route, and where the driver's answers land.

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

Step 1 of 6: 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.

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
200240280320hrsWeek 1Week 2Week 3Week 4Debrief switched on

Week 1 over plan

+10%

Week 4 over plan

+4%

Step 1 of 4: The planned hours draw first.

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

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
123Road closed · +9 kmDwell 0 min
  • 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.

Step 1 of 5: The plan, as the route system drew it.

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

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

Step 1 of 4: 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.

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

Step 1 of 4: Week 1: the site is slipping.

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

A site can start on the reports it already exports.

  1. 01

    Routes, stops, worked hours and tachograph infringements, uploaded as files to begin with. Connected feeds follow once they have been checked.

  2. 02

    Each worked-hours employee paired with their route driver. Names that match one driver and nobody else pair themselves.

  3. 03

    A portrait touchscreen kiosk at each site, once you switch the debrief on. The figures work without it, so a site can start there.

  4. 04

    Someone to set the site's rules, reason codes and outlier limits. A site can have its own, or inherit them from its client or contract.

The detail behind the claims on this page.

Is it fair to rank drivers?
Nobody is ranked on too few runs: each table has a minimum, three runs by default. Findings about a route or a stop point at the plan or the stop, never at one driver.
What happens when data is missing or wrong?
A missing value stays missing; it is never counted as zero. Each figure states how much of the data it rests on, stale or failed feeds raise alerts, and routes or stops outside the site's outlier limits are listed but left out of the figures.
Which systems does it read?
Time and attendance, the route or planning system, the journey plan, telematics and the tachograph compliance check. Screens use the names of your own systems, set per client, contract or site.
What exactly does it compare?
Planned against actual driver hours and distance for each route, stop turnaround against plan, and arrivals against the planned time or the stop's own delivery window. Worked hours from time and attendance sit alongside, and are never turned into route time.
How are drivers matched across systems?
Each worked-hours employee is paired with one route driver. The pairing is made automatically only when a name matches exactly one driver and nobody else; the rest are left for an operator to map, and an upload warns while any employee is still unmapped.
Can two systems count the same route twice?
Where two sources cover the same day, a data source filter lets the site choose one. When a site names one system as the authority for its routes over a period, copies from other sources are left out for that period.
Do we need an integration project to start?
No. A site can start by uploading the reports its systems already export: routes, stops, worked hours, tachograph infringements and driver login codes. Connected feeds can follow once a connection has been checked and switched on by an operator.
Does it replace our planning or telematics system?
No. routerecap reads what those systems already record and lines it up. They stay the systems of record.
Can we start without the driver debrief?
Yes. The plan-against-actual figures and the driver debrief are switched on separately for each site, so a site can begin with the figures and add the debrief later.
How is the kiosk secured?
Each kiosk is tied to its site by a device token and the site's network. Drivers sign in with their employee number and a four-digit PIN, and the kiosk sets no driver session cookie.
How do new drivers learn it?
Training mode lets a driver practise on a copy of one of the site's own routes. Training sessions and the training driver are kept out of every management figure.
Can it be set up to fit each site?
Debrief rules, severity thresholds, reason codes, note categories and questions, outlier limits, on-time windows and the start of the week are all set per client, contract or site. The most specific setting wins.
Who can see what?
Staff sign in with a role (admin, team leader, depot clerk or observer) scoped to their client, contract or sites. Management changes are audit-logged, and pages that show driver data record who read them.
Is it only for HGV fleets?
It was built for end-of-shift HGV driver debriefs on multi-drop delivery routes, and its measures (stops, arrival windows, turnaround, tachograph) follow that work.

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.

Book a demo