Build a commute baseline, simulate route and timetable changes to lower shuttle costs, and use the same data for Scope 3 reporting.
You can cut shuttle spend and report Scope 3 Category 7 from the same data set. Start with employee PLZ data, shift times, route maps, boarding counts, and fleet costs. Then test route, stop, and timetable changes before spending more money.
Here’s the short version:
In plain words: if a shuttle network has trips running at 38% occupancy and a cost per rider near €18,50, expect room to cut spend without cutting access. The article shows that a hybrid setup or better ÖPNV links can lower both cost and emissions output, while giving finance and reporting teams one shared record.
A few points matter most:
If you were reading this to act on it, the takeaway would be simple: model the current network first, compare a few route and timetable options, pick the lowest-cost setup that still gets people to site on time, and use that same model for CSRD-linked Category 7 reporting.
| Focus area | What to check | Why it matters |
|---|---|---|
| Baseline data | PLZ, shifts, routes, boardings, fuel, driver hours | Gives one source for cost and reporting |
| Cost control | Load factor, deadhead km, overlap | Shows where money is leaking |
| Scenario testing | Consolidation, hybrid model, ÖPNV link | Helps compare options before rollout |
| Reporting | Passenger-km, occupancy, emission factors | Supports Category 7 figures |
| Follow-up | 30/60/90-day KPI review | Shows if the change is holding up |
Before you change a route or timetable, you need a baseline. Pull it from HR, site operations, and your shuttle provider. If one of those is missing, it gets much harder to defend the numbers to finance or sustainability teams. That baseline then feeds your route and timetable simulation.
Start with employee home postcodes (PLZ) from your HRIS, not surveys. Surveys go stale fast and can skew what the live network looks like [2][4]. Combine that with shift schedules, headcount by site, and service eligibility rules.
From site operations, collect site addresses, shift start and end times, site entry rules, and parking capacity. In shift-based operations, this can also mean an arrival buffer, such as 15 minutes before a 06:00 factory badge-in [2][5]. From your shuttle provider, collect route maps, stop locations, timetables, trip counts, vehicle capacities, fuel types, and boarding data.
Before you change anything, focus on two numbers:
These are the main efficiency signals. If load factor stays low over time, that usually points to a route design issue, not a small timetable problem [2].
| Data Category | Specific Inputs | Source |
|---|---|---|
| Employee data | Home postcodes (PLZ), shift rosters, headcount per site | HR / HRIS |
| Site data | Site addresses, entry rules, arrival buffers, parking capacity | Facilities / Operations |
| Fleet data | Vehicle capacity, fuel type, route maps, timetables | Shuttle provider |
| Performance data | Boarding counts, deadhead kilometres, dwell times per stop | Shuttle provider / telematics |
| Cost data | Driver hours, fuel, vehicle leases, admin overhead | Finance / Operations |
Once these inputs line up, you can calculate operating efficiency and emissions from the same model. With triply, you can build the commute model from this small data set without surveying every employee. It combines PLZ data, shift patterns, and site rules into one baseline across all sites.
Scope 3 Category 7 covers employee commuting emissions. To build a baseline you can stand behind, you need total kilometres travelled by vehicle and route, average occupancy per trip, and recognised emission factors, such as those from the GHG Protocol or the EPA GHG Emission Factors Hub [1][6]. Write down your assumptions clearly, including the emission factor version you used and how you treated occupancy by trip.
The distance-based method is preferred for accuracy under CSRD because it gives you a per-rider distance ledger instead of survey estimates [2][6]. In plain terms, the same data set that shows where cost leaks also gives you the emissions figure for Scope 3 Category 7 reporting.
Use this baseline to find low-load trips, route overlap, and deadhead kilometres.
This is general information only, not legal or tax advice.
Once your baseline is set, the next step is to look for three common weak points to evaluate your shuttle service: low load factor trips, route overlap, and deadhead kilometres. Deadhead kilometres, or Leerfahrten, are empty repositioning kilometres. That usually happens when a vehicle moves between shifts or heads back to the depot [4].
Low load factor is often the first thing to check. If trips stay far below the target occupancy, that usually points to a route design issue [2]. Route overlap is another common drain on budget. It happens when two vehicles serve the same corridor in the same time band, and neither one fills up [4]. Then there are deadhead kilometres, which add direct cost. Driver labour alone often makes up 40–60% of operating costs in labour-heavy shuttle fleets [4].
For shift-based sites, daily averages don't tell the full story. Track load factor in the peak 30-minute window and by shift band [4][5]. A network can look fine at a system level while still wasting money in low-use night bands [5].
Once you’ve found those weak spots, test them through route, stop, and timetable scenarios.
Simulation lets you see what a change is likely to cost and save before you lock in vehicles, contracts, or driver hours. With triply's simulation capability, you can test route consolidation, stop reductions, revised departure times, and integration with local public transport (ÖPNV) against the same model used for the baseline [2]. Use the same baseline data set for every scenario.
For mid-sized sites, a hybrid network is often the first option worth testing: fixed trunk lines for the two or three corridors with the highest rider density, and dynamic or on-demand vehicles for the long tail of dispersed origins [2]. Even small timetable tweaks can help. Moving pickup windows by a few minutes may cut staging time and deadhead [4]. Stop consolidation in safe, well-connected corridors is another lever to test before retiring any route.
One thing matters here: a route can look lean on paper and still fail in day-to-day use if it misses the arrival buffer. A 06:00 arrival for a 06:00 shift start is not good enough. That is an operational failure [5].
Use a table like this to choose the pilot that cuts cost first without cutting access. The figures below are illustrative.
| Scenario | Annual shuttle operating cost | Peak load factor | Cost per boarded rider | Estimated Scope 3 Category 7 emissions | Notes on access and risk |
|---|---|---|---|---|---|
| Baseline (current network) | €2.400.000 | 38% | €18,50 | High: many low-occupancy trips | Full coverage, high cost per rider |
| Route consolidation only | €2.050.000 | 55% | €14,20 | Moderate reduction | Some thin routes retired, monitor outlying stops |
| Hybrid network (fixed trunk + on-demand tail) | €1.800.000 | 68% | €11,80 | Significant reduction | Best balance of cost and access |
| ÖPNV integration (first/last mile shuttle) | €1.550.000 | 74% | €9,90 | Largest reduction in this illustrative set | Depends on local ÖPNV reliability and shift timing |
This isn’t two separate pieces of work. The same model that helps you cut shuttle cost and emissions also gives you the data for Scope 3 Category 7 reporting [2].
This is general assumption based information only, not legal or tax advice.
Once you’ve picked the best shuttle scenario, use that same trip data to calculate Scope 3 Category 7. Scope 3 Category 7 reporting allows three accepted methods: fuel-based, distance-based, and average-data [7][2].
For shuttle reporting, distance-based is usually the best fit. It uses the same per-trip data that already supports shuttle cost cuts, with passenger-kilometres and actual occupancy built in [2][6].
Use the table below to match the method to your data quality and audit needs.
| Method | Data required | Shuttle fit |
|---|---|---|
| Distance-based | Passenger-kilometres, vehicle type, fuel type | Best: uses the same operational data that drives cost optimisation |
| Fuel-based | Total fuel consumed by fleet | Good: when you control fleet fuel data centrally |
| Average-data | Headcount, average commute distance | Poor: too coarse for proving optimisation savings |
Choosing a method is only the first part. After that, the job is to keep the audit trail clean.
One commute model can produce both operational outputs and Scope 3 Category 7 outputs. Finance can use the same ledger for cost checks, while sustainability teams can use it for emissions totals.
Stick with the same source data, assumptions, and version control used in scenario modelling. Document:
Emission factors should come from recognised bodies such as the EPA, DESNZ, or APTA [7][2]. Under CSRD and ESRS E1, disclose Scope 3 Category 7 when it is material [2][3].
This is general information only, not legal or tax advice.
Once the reporting model is live, keep using it as operations change. After go-live, run the same model again as demand shifts.
Set KPI targets at the start of a programme, not at the end of a quarter. Checking performance at 30, 60, and 90 days after a route change helps you tell the difference between early noise and steady trends [2].
| KPI | Definition | Data source |
|---|---|---|
| Load factor | Actual occupancy divided by seat capacity during peak windows. Target: 60% to 80%; below 45% signals route redesign is needed [2]. | Rider booking and boarding logs |
| Cost per boarded rider | Total operating costs divided by boarded riders. | Finance records and dispatcher data |
| Cost per vehicle-kilometre | Total operating cost divided by total distance travelled, including deadhead kilometres. | Telematics and fuel records |
| Total shuttle operating costs | Sum of driver hours, fuel, vehicle amortisation, and platform licensing. | Finance or ERP system |
| Scope 3 Category 7 outputs | kg CO2e per employee commute from the same distance ledger. | Platform distance ledger and emission factors |
If a KPI moves out of range, treat it as a route-design signal, not just a reporting problem. Re-run scenarios when shift patterns change, a department moves, or headcount changes. Refresh rider rosters and home postcodes first. Then retime handovers before changing route geometry [4].
Finance and sustainability stay aligned when both teams use the same source data. With one shared data set, a route change that lowers cost per boarded rider will also change your Scope 3 Category 7 output.
Start with the baseline. Test route and timetable changes. Compare cost and access. Then pick the option that cuts shuttle cost and emissions without stranding riders.
triply does this by modelling real commutes from minimal data, simulating shuttle and mobility measures before investment, and producing audit-ready Scope 3 Category 7 outputs from the same model. Finance, sustainability, and operations all work from one shared data set.
If you want to see how this works for your sites and shift patterns, book a triply employee shuttle optimisation demo and run your first shuttle cost and emissions scenario.
You need enough detail to understand current workforce commute patterns. The strongest baseline combines anonymised home-to-work location data with employee survey results, so you can spot commute pain points and transport gaps.
For a solid analysis, include residential data by postcode, current commute modes, shift patterns, work schedules, and current transport costs.
A “good” load factor for an employee shuttle network isn’t one fixed percentage. A more useful way to look at it is peak occupancy - especially during the busiest 30-minute window.
When you track load factor at peak times, you can see whether you’re moving the highest number of employees with the fewest resources.
This is general information, not legal or tax advice.
Yes. The same model used for shuttle optimisation can also support Scope 3 Category 7 reporting with the same operational data.
By tracking rider bookings, boarding status, and occupancy, you can optimise shuttle routes and keep the records needed for emissions reporting.
This information is for general purposes only and does not constitute legal or tax advice.
