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.

Talk to LibraSee the five sources

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.

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.

The clock records every hour paid for.

The other four systems each record a shorter, or longer, version of the same day.

A control score for each site, and a list of who to talk to first.

Transport control scores how closely the day ran to plan. From 85 it reads In control, from 70 Slipping, and below that Out of control.

Under the score sit the hours lost between the clock and the journey plan, at replan, and on the road. Drivers and routes are ranked worst first, and every table exports to Excel as it sits on screen.

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.

Transport control

Illustrative data
Transport dayDriversRoutesDaily trend

Control score

0

Slipping

Clock → Journey plan6.5 hrs

Paid, never put on a journey

Plan → Journey plan4.0 hrs

Changed at replan

Journey plan → Journey actual3.2 hrs

Drift on the road

Score by day

Drivers: worst to best control

Minimum 3 runs

DriverRunsControl
Driver 0412961
Driver 0187766
Driver 02331172
Driver 0098879
Driver 03561088

Two weeks of plan against actual on one chart.

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. It can also show the control score for each day against its bands.

When you change something on the road, you can see whether the gap closes, and whether it stays closed.

Transport control

Illustrative data
Transport dayDriversRoutesDaily trend
Planned hoursActual hours
MTWTFSSMTWTFSS

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

Every stop keeps its arrival window and its time on site, so a late arrival can be read against the stop's own delivery window.

Route review

Illustrative data
MapStopsIncidentsNotes
123DeviationDwell 48 min

The plan, as the route system drew it.

The planned route, stop by stop, dashed.

The driver's account sits 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.

The transport manager reads those answers beside the route, with the driver's stop notes and the outcome, and can comment or raise an action. The outcome is supportive unless the site's rules call for a conversation with the transport manager.

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.

Debrief review

Illustrative data
SummaryIncidentsNotesComments

Route 14 · Driver 0412

Supportive outcome

3 incidents explained at the kiosk

  • Arrival outside windowStop 3

    Driver's reason: Waiting to unload › Queue at the gate

  • Long dwellStop 3

    Driver's reason: Waiting to unload › Paperwork at goods in

  • Route deviationBetween stops 1 and 2

    Driver's reason: Road closed or restricted

Stop note · Stop 3

The gate opens half an hour after the booked slot.

Team leader comment

Passed to planning to move the slot.

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.

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.
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.

Talk to Libra