An HR lead at a German IT consultancy describes it like this. Two years ago the company introduced a mobility budget with one package for everyone: a €60 Deutschlandticket subsidy, optional bicycle leasing, a single flat-rate tax treatment. Within the first year it became clear that the same package was failing three different groups for three different reasons. Senior consultants with a company car entitlement found it redundant, because their commute was already covered by private use of the car. Consultants living in the surrounding countryside needed something for a 40-kilometre commute that a public transport pass alone could not solve. Younger consultants in the cities wanted to spend the budget on car sharing and rental bikes, which the configuration did not allow.
Nothing about that is unusual. Mobility budgets get designed as a single object in the concept phase, because modularity looks like complexity and complexity looks like risk. The bill arrives later, when HR has to choose between living with weak take-up and rebuilding the configuration after the fact. Thinking in axes from the start is cheaper than retrofitting them.
What follows sets out the axes a mobility budget can be configured along, how to judge how much differentiation your own workforce needs, and what the usual progression from a simple to a differentiated model looks like.
A uniform design makes the first implementation dramatically easier: one subsidy amount, one set of building blocks, one tax construction for everyone entitled. The cost of that simplicity does not appear immediately. It appears a few months in, and it arrives in two connected forms.
The first is straightforward arithmetic. A workforce is not one group. People commute differently, live differently, and want different things from a mobility benefit. A single budget level and a single set of options can fit the majority at best, and by construction leaves the rest outside.
The second is what that does to how the benefit is perceived. Where the configuration is mostly a public transport subsidy, it works for someone commuting across a city and does nothing for someone driving in from a village, or for someone whose company car already covers the same journey. The first sees a benefit that is irrelevant to them. The second sees one that duplicates what they have. Both conclude that the benefit was designed for a slice of the workforce rather than for the workforce, and that conclusion cannot be talked away. It can only be designed away.
Low take-up follows, and it carries consequences beyond the benefit itself: a weaker internal case at the next budget round, less to say in recruiting, and thinner data for sustainability reporting.
Configuration runs along five axes, and each one can be set coarsely, meaning one value for everyone, or finely, meaning differentiated by group, site, or individual. Seeing them side by side is more useful than reading them in sequence, because the decision on each axis is the same decision: how much differentiation is worth the administration it costs.
The budget level is where the legal exposure sits. Differentiating the amount can collide with the equal treatment principle in § 75 BetrVG, so any difference has to be derivable from something objective. Average commuting distance works. Seniority is defensible but will be questioned. Life stage is the one to be careful with: a family supplement sounds generous and differentiates by a personal characteristic, which raises questions under the Allgemeines Gleichbehandlungsgesetz alongside the works council conversation.
Timing is the axis nobody argues about and everybody underestimates. Whether unused budget rolls over, expires, or gets paid out changes behaviour more than most budget-level decisions do, and it costs nothing to get right at the start.
Create the work place of tomorrow with NAVIT. We are happy to support you with designing the best mobility solution for your company. Get in touch with us!
Contact us
Before choosing a model, it is worth addressing the heterogenity of your workforce as this can point out the model to choose rather than needing to be weighed against each other.
Start with how the workforce splits by function and location. Where more than four in five people belong to the same function group at the same site, a production workforce for instance, a coarse configuration will serve them. Where there are five roughly equal function groups, or people spread across several locations, the same configuration will fit none of them particularly well.
Then look at commuting patterns. A workforce that mostly commutes within a city, with usable public transport and short distances, can work from one simple setup. A workforce spread across urban, suburban, and rural addresses, with commutes running from 5 to 60 kilometres, needs the building blocks to differ by location.
Finally, take stock of what people already have. Where part of the workforce holds a company car and another part has never had a mobility benefit at all, those two groups are starting from opposite positions and a single configuration will read very differently to each. Where nobody has had anything, the design is simpler because there is no legacy to work around.
The three configuration models that have established themselves in practice are not really alternatives to choose between. They are stages, and most companies move through them in the same order.
Almost everyone starts with the uniform model, because it is the simplest thing that can work: one budget, one set of blocks, one tax construction. For a genuinely homogeneous workforce, an industrial company with 700 of its 800 people in production at one site for instance, it is not a stepping stone at all. It is the right answer, with minimal administration and an easy conversation with the works council.
Where the workforce is more varied, the first usage data usually arrives after six to twelve months and shows which groups the uniform model is not reaching. That is the trigger for the group-differentiated model: the entitled population is split into two to four groups, each with its own configuration. Senior management against the wider workforce, company car holders against everyone else, field staff against office staff. Eligibility and tax construction often stay uniform at this stage; it is the building blocks and the budget level that differentiate.
The site-and-group model is where configuration varies along both axes at once, sometimes with life-stage components on top. It suits distributed groups with genuinely heterogeneous workforces, a consultancy with offices in several cities and people at very different levels. It is rarely a starting point. It is usually the end state of a multi-year optimisation, and it should be, because the administrative cost only pays for itself once the differentiation is demonstrably needed.
Because theprogression is normal rather than exceptional, the question to ask a provideris not which model they support but whether they support moving between them. Aplatform that hard-wires the uniform model into its structure has quietlyremoved the optimisation path that most companies will want in year two.Migration capability belongs in the selection criteria, not in the wish list.
Take-up is where configuration decisions turn into economic outcomes, and the mechanism runs as a chain rather than as a set of separate effects.
It starts with fit. Where the configuration reflects how people actually commute, most employees find a building block that matches their situation. Where it does not, only the people whose lives resemble the average configuration find one, and the share of entitled employees with nothing useful available to them maps almost directly onto the share who never activate.
Fit then feeds perception. A differentiated configuration reads as a company that noticed its workforce is not uniform. A single configuration reads as the opposite. That perception shapes whether someone bothers to activate at all, and it matters most in exactly the groups that were left out of the original design, who have the least reason to give it a second look.
And perception feeds the works council conversation. A uniform configuration in a varied workforce generates equal treatment objections, those objections generate renegotiation, and renegotiation delays the introduction. Differentiation defuses this before it starts, because it anticipates the difference the objection would be built on.
Our mobility experts at NAVIT would love to share their knowledge with you about the new mobility product. Feel free to get in touch with us!
Get infoNAVIT supports all three models in one platform, and moving between them does not require changing provider. A company can start uniform and migrate to a group or site-differentiated model after six or twelve months without employees seeing any change in the interface they use.
The five axes are configurable independently of one another. Eligibility can differentiate by employee group, seniority, and contract type; building block availability by group and site; budget level along either; tax construction is applied automatically per building block; and timing covers waiting periods, caps, and carry-over rules. Changing one axis does not force a change in the others.
MERKUR PRIVATBANK KGaA reduced administrative effort for mobility benefits by around 90 % after introduction. The documented comparison basis is the previous receipt process: employees submitted receipts for Deutschlandtickets they had bought themselves, which then had to be checked, settled, archived, and reimbursed through payroll.
At what workforce size does modular configuration pay off?
It is not really a question of size but of variety. A mid-sized company with 200 people across five function groups benefits from group differentiation. A group with 5,000 people in one homogeneous production workforce can run the uniform model perfectly well.
How do works councils react to differentiated configuration?
Usually positively, provided the differentiation rests on something objective. A configuration that treats different groups differently is more inclusive than a rigid single solution. What matters is that the criteria are derivable from something concrete, such as commuting pattern, function group, or site, rather than appearing arbitrary.
How many configuration variants make sense in practice?
Between two and six. Fewer than two is not differentiation at all; more than six creates administration that outweighs the benefit. Most workable configurations settle on three or four clearly distinct variants.
Can we adjust the configuration later?
Yes, provided the platform supports migration between configuration models. Establish before selecting a provider whether later refinement is possible without changing provider. This is one of the more consequential questions in the whole evaluation.
How much administration does modular configuration create?
Little, where the platform supports the axes natively, because the configuration is set up once and then applied automatically to new joiners. Where every configuration decision has to be maintained by hand, the effort rises sharply. This is worth testing in a demo rather than taking on trust.
How does modular configuration differ from site-specific configuration?
Site-specific configuration is a subset of it. It covers the site axis and leaves the other four open. Full modularity means all five are configurable independently.
What if the configuration becomes too complex?
Three signals mark the limit: HR needs more than an hour a month to maintain it, employees start asking detailed questions about their own configuration, or the payroll export becomes error-prone. Any one of those is a reason to simplify, usually by merging variants.
Disclaimer: NAVIT accepts no liability for the accuracy of the information provided. The content on our website is for general information purposes only and does not constitute tax or legal advice. It cannot and is not intended to replace individual, binding tax and legal advice addressing your specific circumstances. All information is provided without warranty as to accuracy or completeness.
Sign up for our newsletter to receive the latest insights about our mobility solution products like the 49 eurojob ticket.
