What transport directors ask before a site starts.

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.

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.

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.

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.

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.

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.

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.

No. routerecap reads what those systems already record and lines it up. They stay the systems of record.

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.

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.

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

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.

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.