What the TEN-T SUMP Mandate Actually Requires.
By 2027, 431 European cities must have adopted a Sustainable Urban Mobility Plan. That’s not a target — it’s a legal obligation under Regulation (EU), the revised TEN-T Regulation. Most of those cities don’t yet have a plan. Many don’t yet know what a credible one requires.
I’ve spent a significant part of the past years working on SUMP and sustainable urban mobility projects inside IFI programmes — EBRD, UN-Habitat, EU. The gap between what the TEN-T mandate expects and what most cities think it expects is one of the most consistent mismatches I see in the field. This article is an attempt to close that gap.
What is TENT-T in SUMP?
TEN-T stands for Trans-European Transport Network — the EU’s strategic framework for road, rail, aviation, and inland waterway infrastructure across Member States and, progressively, candidate countries. It organises European transport infrastructure into two tiers: the Core Network, covering the highest-priority cross-border corridors, and the Comprehensive Network, covering the broader strategic layer below it.
Urban nodes are the cities where these corridors meet city-level transport systems. What happens inside those cities — how people move from the street to the station to the motorway junction — directly affects how the network performs. That’s why the revised TEN-T Regulation doesn’t just set infrastructure standards. It reaches into city-level planning.
Regulation (EU) 2024/1679 designates 431 urban nodes on the core and extended TEN-T network. Each one must adopt a SUMP by 2027. That’s a hard deadline with a monitoring structure behind it — not a target with a hope attached.
The SUMP must cover the entire Functional Urban Area (FUA), not just the administrative boundary. This matters because mobility problems — and mobility solutions — don’t respect municipal borders. A SUMP scoped to the wrong geography will misread the baseline and set the wrong targets.
The mandate is real.
The SUMP must address multimodal connectivity to the TEN-T network. It’s not a cycling strategy or a pedestrian improvement plan, though it can include those. It’s an integrated mobility strategy that has to account for how the city connects to the European transport network — by road, by rail, by interchange.
The harder question is what a credible SUMP actually requires.
Member States were required to designate national SUMP contact points and establish national SUMP programmes by July 2025. City-level data submission is due December 2027. This is a monitoring architecture: national coordination, city-level delivery, European reporting.
And the mandate doesn’t stop at EU borders. The TEN-T network extends into candidate countries — Serbia, North Macedonia, Albania, Ukraine — and the pre-accession alignment process means cities on these corridors are progressively expected to meet the same standards. EBRD and ADB are active in many of these same cities. For a city of 200,000 in Serbia on the TEN-T Core Network corridor, working with an EBRD transport loan, the SUMP obligation comes from two directions simultaneously: EU accession conditions on one side, IFI loan requirements on the other. These aren’t two separate plans. They shouldn’t be.
Ten-T Policy and Urban Nodes in Europe by the end of 2027 (Cities that should have a Sustainable Urban Mobility Plan (Sump). Source: Polis Network
How SUMP Works Inside an IFI Project
A SUMP delivered as part of an IFI technical assistance project is structurally different from a standalone municipal SUMP. This is where a lot of well-intentioned work goes wrong — and where the brief writing either solves the problem or creates it.
IFI (International Finance Institutions) Frameworks
IFI frameworks have their own scope requirements, reporting structures, and quality assurance processes. The SUMP can’t just meet EU SUMP guideline requirements and call it done. It has to fit the programme logic of the financing instrument it’s attached to.
World Bank urban transport projects typically include a Sustainable Urban Transport Plan or SUMP component tied to the loan appraisal. The baseline assessment feeds the investment case. The action plan shapes what the loan can finance. The monitoring framework generates the data the World Bank tracks at mid-term review and project completion.
EBRD’s Green Cities programme embeds active mobility and transport components inside a Green Cities Action Plan. The GCAP is a loan condition, not a voluntary planning exercise. It has a structured methodology — PSR baseline, prioritised actions, financing framework — and the transport chapter is effectively a SUMP baseline and action plan, even if the brief doesn’t use that word. A consultant scoping an EBRD GCAP transport component who doesn’t understand SUMP methodology will produce weaker work. A consultant scoping a TEN-T SUMP for a city with an EBRD loan who doesn’t understand GCAP will miss the alignment opportunity entirely.
ADB projects in Central Asia increasingly reference SUMP methodology in their scope requirements for multimodal transport components. The terminology varies. The structural logic is consistent.
IFI’s Actual Requirements
What I’ve seen in practice: the SUMP brief written by the city’s procurement team often doesn’t reflect the IFI’s actual requirements. This isn’t negligence — it’s a gap between the city’s understanding of what a SUMP is and what the IFI expects the document to do. The gap gets discovered after consultants are appointed, during scope definition, or worse, during quality review. That’s an expensive point to find a mismatch.
I worked on the Istanbul SUMP in 2024–2026, structured around EU SUMP methodology alongside IFI governance requirements for the EU-funded component. The scope required specific active travel and pedestrianisation components tied to GCAP baselines established in a prior project. Getting the two frameworks to speak to each other was the technical work before any planning work began.
The plan that satisfies EU compliance and the plan that unlocks IFI financing are not automatically the same document. Getting the scope right is where the work starts.
Why Delivery Requires Governance Design from Day 1
Most SUMPs I’ve reviewed fail not in methodology but in delivery. The technical quality is often good — solid baseline, well-argued priorities, realistic action plans. Two years later, nothing has changed on the ground. The consultant has moved to the next project. The municipality has had an election. The plan is on a server somewhere.
I think the problem is almost never the plan.
The governance structure — who owns the SUMP after the consultant leaves, how monitoring is embedded in institutional processes, how implementation is tied to political accountability — determines whether the SUMP produces change or produces documentation.
IFI monitoring creates a lever that municipal planning alone doesn’t. When the SUMP monitoring requirement is written correctly into the loan agreement, the city has a legal obligation to report progress against the action plan before the IFI review meeting. That’s enforcement with consequence, not filing with hope. But the lever only works if the monitoring clause is written as a municipal commitment in the loan covenant — not as a consultant deliverable in the scope of work. A monitoring framework document submitted and filed achieves nothing. The same monitoring framework embedded in a World Bank or EBRD reporting obligation becomes real.
Three things that should be in every SUMP brief from the start.
Named municipal ownership post-delivery. A specific post in the administration, with budget and authority, owns the SUMP action plan. This isn’t a recommendation — it’s a specification in the brief. The tender should ask bidders to propose a post-delivery governance structure.
Monitoring indicators agreed at baseline stage. The indicators that will appear in IFI progress reports need to be identified and agreed during the baseline phase, not retrofitted at the end. If the baseline doesn’t collect the data the monitoring framework needs, the monitoring framework is a fiction.
Political visibility mechanism. An annual progress report to the city council or mayor, publicly available. This keeps the SUMP politically alive across electoral cycles. The incoming administration inherits not just a document but a public record.
The consultant can write a perfect SUMP. Delivery requires an owner.
Build the governance in before the brief goes out.
The TEN-T mandate creates a legal accountability hook in 431 cities that didn’t exist five years ago. It’s the most significant structural intervention in European urban mobility planning in a generation, and most of the cities it covers are still figuring out what it actually requires.
For cities working with IFI programmes, the mandate is also an opportunity. The monitoring framework, the governance requirement, the action plan tied to measurable targets — these are exactly what IFI loan covenants need, and what too many IFI transport projects have failed to produce. Doing the TEN-T SUMP well means doing the IFI component well.
Start with the governance architecture. The plan will follow.