Build a defensible sustainable mobility plan: define scope, collect commute data, set measurable targets, assign owners, and review.
Most mobility plans fail for a simple reason: they don’t have enough proof behind them.
To sum this up in one line: a plan needs five parts to stand up to budget checks, internal review, and Scope 3 Category 7 scrutiny - a clear scope, a data-based commute baseline, measured targets, named owners, and a set review cycle.
Here’s the short version:
A weak baseline can break the whole plan. For example, if shuttle demand is overestimated by even 10% to 20%, costs can miss the mark fast and the emissions case can weaken.
In plain terms: the job is not to write a nice plan. The job is to write one that another person can check and follow without filling in gaps.
This article shows how to set the scope, build the evidence, choose measures in the right order, and document the plan so it stays clear from first draft to review.
The requirement is not just intent. It is proof.
For large employers, a sustainable mobility plan needs more than a good idea on paper. It needs a documented scope, a data-backed baseline, measurable targets, named ownership, and a review cycle. That’s what turns a workplace mobility mandate into a plan you can defend in budget talks, compliance checks, and Scope 3 Category 7 review.
For a multi-site employer in Germany, the plan should make a few things plain:
Once those requirements are clear, the next step is to set scope, sites, populations, and governance.
A plan that stands up under scrutiny starts with a baseline you can trust. That baseline is what you use to set targets, test measures, and back up the outcome. It needs to be credible, consistent, and repeatable across every site, every shift pattern, and each covered population group, including employees and contractors where that applies. Once the scope is fixed, the next move is simple: build the baseline from actual commute data.
Before you collect a single data point, spell out what sits inside the scope. That includes every site, each shift pattern, and all covered population groups, including employees and contractors where relevant. If the plan covers only one site or one employee group, the gaps will show straight away.
Governance matters just as much as the data itself. Set clear decision rights across mobility, HR, finance, and operations from day one. If nobody owns the budget or the review cycle, the plan can drift off course. A named owner in each function, paired with a documented sign-off process, makes the plan easier to review and manage.
You do not need to start with guesswork. Postal codes (PLZ) of your workforce, shift start and end times, site access constraints, parking occupancy, and any shuttle usage data you already have can give you a structured picture of commuting patterns.
The goal is to see, in plain terms, where people travel from, when they travel, and how demand changes by site and shift. That helps you spot where public transport is already a workable option, where it falls short, and where your measures are most likely to make a difference.
For employers with more than one site, model each site in one consistent framework before comparing measures. triply analyses commutes from minimal inputs, such as PLZ and shift times, without relying on a full employee survey. It then brings that picture together across sites into a single data set for cost, site access, and Scope 3 Category 7 emissions that finance, sustainability, and operations teams can all use.
Just as important, triply produces the data set in a format that maps straight to Scope 3 Category 7 employee commuting emissions. That means the same data used to choose measures can also feed into your CSRD reporting. Use one evidence base for both planning and Scope 3 Category 7 reporting. When you model each site first, you can compare measures before committing budget.
Once you've modelled the baseline, the next step is to turn it into targets and day-to-day indicators. That's what makes a mobility plan something you can approve, track, and stand behind. Targets define the outcome. Indicators show whether the plan is moving in the right direction.
The most useful targets should cover mode share, cost per boarded rider, and Scope 3 Category 7.
Mode share shows how much commuting shifts away from single-occupancy car travel. Cost per boarded rider gives you a consistent way to compare budgets across sites and shifts. Scope 3 Category 7 reduction links the plan straight to your CSRD reporting needs.
Use the baseline as the reference point for every target. For each one, set:
A mode share target, for example, can look like this: increase public transport mode share from [baseline] to [target] by [date].
You should also track load factor for shuttle routes and define a review trigger for services that underperform. In practice, that means your indicator set should include load factor alongside mode share and cost per boarded rider.
Once the targets are fixed, you can choose the measures most likely to move them.
Rank measures by impact and feasibility. Start with active travel support and public transport incentives. Then add carpooling, shuttles on high-demand corridors, and shift changes where the data backs them up.
Each measure should connect to a problem found in the baseline. If your data shows strong demand on one corridor but weak public transport frequency, a targeted shuttle is a sensible move. If cycling distances are short and the main issue is missing infrastructure, active travel investment should come first.
The baseline should set the order. Not guesswork. Not habit.
Before approval, test which measures are worth funding. If you commit budget before you understand likely uptake, you can end up with a plan that looks good on paper but falls short in practice.
A shuttle route is a good example. It may hit a solid load factor in the model, but if only a small share of people use it in real life, it burns money and weakens the emissions case you bring to leadership.
triply lets you simulate shuttle concepts, public transport incentives, carpooling schemes, and schedule changes against the same commute model used for Scope 3 Category 7 reporting. You can compare scenarios by estimated uptake, cost per boarded rider, and emissions reduction before a single euro is committed. That gives finance, sustainability, and operations a shared view of which measures are worth approving and in what order.
Once your baseline, targets, and measures are set, put them into a document that someone else can follow from start to finish. A reviewer should be able to trace the full chain, from baseline to targets, measures, and outcomes, without filling in blanks or making assumptions.
Use a fixed structure so the plan is easy to check. Include site scope and population, baseline method and data sources, targets such as mode share, cost per boarded rider, and Scope 3 Category 7, measures ranked by priority, indicators, and the review cycle. Keep the same labels across targets, measures, and reporting. That way, the whole document speaks the same language.
Also, keep source data separate from modelled outputs. Reviewers need to see what was measured and what was simulated. If those two get mixed together, the trail gets muddy fast.
Good documentation also needs clear ownership and a clear review process.
Assign one named owner to each data stream:
Match the review cycle to your internal budgeting calendar and any reporting deadlines you need to meet. At each review, compare actuals with targets, note what changed, and refresh the baseline when site populations or shift patterns change. If you only look at whether a target was met, you can miss something important: whether the assumptions behind that target still make sense.
Before you commit budget, test the assumptions in the model. If you want to test the plan before budget approval, use triply to model commutes across your sites, simulate measures, and generate Scope 3 Category 7 figures from minimal input data. Explore employee shuttle optimisation modelling and book a demo.
Your scope should cover the parts of your workplace mobility plan that can be reviewed and evidenced clearly. In practice, that means including the relevant sites, travel types, data inputs, targets, and review cycle.
Keep the scope concrete and consistent, so the plan can stand up to scrutiny. This is general information, not legal or tax advice.
To build a plan, you first need the core inputs behind the required elements, data, targets, and the review cycle.
The article context also points to modelling as part of a plan that can stand up to scrutiny. That matters. A plan isn’t just a document you file away. It needs numbers, assumptions, and a review rhythm that people can test, question, and follow.
This is general information, not legal or tax advice.
Review the plan on a regular cycle and any time major changes affect commuting patterns, site operations, or the measures in the plan. The timing should match the mandate that applies to you.
This is general information, not legal or tax advice.
