Transport Management System
A transport management system built for employee shuttles, not freight.
RideTandem's Transport Management System (TMS) is purpose-built for passenger shuttle operations. It handles booking, boarding, routing, live tracking, driver dispatch, incident alerts and GHG Protocol emissions reporting in one platform. Unlike spreadsheets or freight-first TMS products, it's designed around worker shift patterns, multilingual riders and the 24/7 reality of staff transport.
.png)
One platform, three connected apps
The operating system behind every RideTandem shuttle.
Definition
What is a transport management system?
A transport management system (TMS) is software used to plan, run and report on the movement of people or goods. A passenger TMS for employee shuttles manages bookings, boarding, routing, live tracking, driver dispatch and emissions reporting in one place - so an employer can see and account for every staff journey in real time.
Most TMS products on the market are freight-first: built for pallets, carriers and loads. Spreadsheets are worse still - no live tracking, no audit trail, no rider-facing language support. A passenger TMS has to handle booking behaviour, live incident response and the emissions accounting that freight platforms simply don't track.
- Freight TMS has no rider-facing layer. Goods-focused platforms manage vehicles and loads, not passengers - there is no booking app, no QR ticket, no live alert for the person actually travelling. Gartner Transport Management Systems market definition
- No multilingual UX for a multilingual workforce. UK industrial and agency sites routinely run on five or more first languages at ground level. English-only tools lose riders before they book. Food & Drink Federation workforce data - source to confirm
- The wrong emissions category. Freight TMS tracks Scope 3 Category 4 (upstream transport). Employee commuting is Category 7 - a different calculation that freight tools don't produce. GHG Protocol Corporate Value Chain (Scope 3) Standard
- Spreadsheet sprawl leaves no audit trail. DBS status, attendance and incident logs scattered across sheets can't be assured, version-controlled or access-restricted. ISO 27001 information-security control requirements
What it includes
What should a passenger-first TMS include?
Six things separate a staff-shuttle TMS from a repurposed freight tool or a folder of spreadsheets.
-
9-language Rider AppQR tickets, live tracking and journey alerts in the rider's first language.
-
Driver App with boarding scanTurn-by-turn navigation, manifest, QR boarding scan and incident reporting.
-
Live Client Hub dashboardBookings, boardings, GPS, punctuality and emissions, all in real time.
-
Auto-dispatch for incidentsBackup vehicles triggered automatically so passengers still reach site.
-
Journey-level CO₂eGHG Protocol Category 7 emissions, CSRD- and SECR-ready.
-
API + CSV integrationSync passenger lists with your HR, rota and payroll systems.
How it works
How RideTandem's TMS runs a day of service.
From the first booking to the post-journey report, the same data flows through three connected apps - no re-keying, no spreadsheets, no gaps.
-
1
Riders book
Workers open the Rider App in their first language and book a seat against a specific shift. QR tickets are issued instantly.
-
2
Driver dispatched
The Driver App shows the route and live boarding manifest, then scans each rider's QR code on boarding.
-
3
Live journey
Boardings and GPS update the Client Hub in real time. Our 24/7 ops team watches the same view and auto-dispatches a backup vehicle on any incident.
-
4
Post-journey data
Usage, punctuality and journey-level CO₂e are reported automatically - ready to export to your HR, finance or ESG team.
Comparison
How does a staff-shuttle TMS compare to spreadsheets and freight TMS?
| Capability | RideTandem TMS | Spreadsheets | Freight TMS | Source / basis |
|---|---|---|---|---|
| Built for passengers | Yes | Manual | Freight-first | Product architecture |
| Rider app in 9 languages | Yes | No | No | RideTandem product spec |
| Live journey alerts | Yes | No | Partial | Incident auto-dispatch |
| Scope 3 Cat 7 reporting | Yes | No | Cat 4 only | GHG Protocol |
| Auditable every journey | Yes | No | Yes | ISO 27001 control |
| HR / payroll integration | API + CSV | Manual | Rare | RideTandem integration guide |
Using the Dashboard is dead easy. We've had no issues at all onboarding drivers onto the Driver App - they find it very straightforward.
FAQ
Transport management system, frequently asked questions
Yes. We support secure API and CSV integration with common HR, rota and payroll tools, so passenger lists stay in sync with your shift patterns without manual re-keying.
Employee data is encrypted in transit and at rest, with role-based access in the Client Hub. We align our practices to the ISO 27001 information-security standard.
The TMS is provided as part of our managed shuttle service rather than as standalone software. If you have a specific licensing need, speak to our team and we'll talk it through.
It's journey-level. We record distance, vehicle type and fuel for every trip, then apply DEFRA/BEIS emissions factors to output CO₂e per journey - auditable against the GHG Protocol, not estimated from a survey.
Yes. The Client Hub is accessible on both web and mobile, with the same live data and alerts on either.
See the TMS in action.
Book a 20-minute demo with a Transport Specialist and we'll walk you through the Rider App, Driver App and Client Hub on a real shuttle network.