EIT Urban Mobility Strategic Innovation Open Call (2026-2028)
A multi-beneficiary EU-anchored call for urban mobility projects with up to €2 million per project, a total call budget of €60 million for 2026-2028, and staged deadlines through 2027.
EIT Urban Mobility Strategic Innovation Open Call (2026-2028)
EIT Urban Mobility’s Strategic Innovation Open Call is a recurring, pan-European funding route for mature mobility innovations that can move from development to real-world deployment. The call is explicitly designed to support urban mobility solutions with strong market relevance and scale potential, especially where cities and mobility providers can use external support to de-risk implementation and speed deployment.
The call page indicates a multi-year structure (2026-2028) with a significant budget envelope, and the key advantage for applicants is that the call is open through multiple cut-off windows rather than a single once-a-year deadline. For teams in the EU and associated countries, this means you can align internal portfolio planning around a coming cut-off, while using earlier windows to strengthen a proposal sequence.
This is especially relevant for your requested 2026 and 2027 targeting because the pages show active and upcoming rounds across both years. The programme’s explicit focus on market-critical projects and its explicit funding model make it materially different from early-stage grants: this is not a seed idea contest, it is a late-stage pilot-to-scale mechanism with clear expectations for implementation realism.
Quick details at a glance
| Field | Detail |
|---|---|
| Opportunity | Strategic Innovation Open Call (EIT Urban Mobility) |
| Type | Multi-beneficiary grant-style call |
| Official period | 2026-2028 |
| Confirmed grant budget | €60 million (total call funding allocation) |
| Max grant per project | Up to €2,000,000 EIT contribution |
| Co-funding | EIT up to 65% of eligible costs; minimum 35% co-funding |
| Current listed deadline (source page list) | 29 September 2026 |
| Published additional windows | 23 Sept 2025, 12 Feb 2026, 18 Jun 2026, Feb 2027, Jun 2027 |
| Eligible scope | Urban logistics, public transport, mobility data management, electrification and alternative fuels, health and mobility |
| Eligible format | Multi-beneficiary proposals, minimum 2 independent legal entities |
| Review model | Two-stage (portal expert screening then panel hearing/selection committee) |
What this opportunity is and why it is operationally different
Many European calls are idea-stage, single-disciplinary, or tied to very specific mission categories. This call is different because it is explicitly structured around piloting, deployment, and scale-up readiness within urban mobility contexts. The call text describes this as support for impactful solutions already shaped enough to enter practical implementation pathways.
The call states that it supports:
- tested solutions with strong market potential,
- projects with a credible path to market by implementation end,
- solutions that help cities and mobility providers scale proven innovations,
- collaboration across education, research, business, and city stakeholders.
In practical terms, this means an applicant should be prepared to describe more than a concept. The reviewers expect at least a plausible trajectory from technical design to procurement, deployment, and measurable impact. Proposals that stay conceptual and do not define rollout logistics are unlikely to rank well against better-advanced peers.
The “strategic” element in this call is also important: it is not only a technology competition but a market-coordination mechanism. EIT Urban Mobility expects projects to be placed within real mobility system constraints (public transport, city planning, freight logistics, data ecosystems, energy systems, and mobility-health interactions). That makes it appropriate for project teams that already have an implementation context and active partners.
Targeted funding architecture and why amounts matter
The page states a total call allocation of €60 million for 2026-2028 and a maximum of €2 million EIT funding per project. This matters in at least three ways:
- It positions the call as suitable for portfolio-scale pilots, consortium implementation, and commercial validation, rather than very early prototypes.
- The split between EIT contribution (up to 65%) and required co-funding (35% minimum) means your proposal needs substantial partner commitment. Teams should not treat this as self-funding; project finance architecture is part of eligibility quality.
- Since many applicants will be in SMEs or research-backed spinouts, the call naturally supports projects where external finance can unlock the missing commercial bridge.
The co-funding rule in this call is straightforward but operationally strict. If a project budget is €1,000,000 of eligible costs, at least €350,000 must come from non-EIT sources (ineligible claims or late co-funding confirmation can delay admissibility). If your proposal has a multi-party budget where contributions are uneven, show a clean table of committed, conditional, and contingent resources so reviewers can see financial readiness.
The call is best suited for groups that have already built proof points and need support for city-level testing, deployment preparation, and scale-out. This reduces the risk that funds are spent on unproven technical direction and increases the chance of a credible timeline for commercialization outcomes.
Confirmed eligibility and consortium requirements
The call is explicitly labeled as a multi-beneficiary call. There must be a minimum of two independent legal entities, and these must be in two different European Member States and/or Horizon Europe associated third countries.
That is a hard structural requirement, not a scoring preference. Teams should treat consortium formation as part of proposal strategy from day one:
- Confirm that legal entities are independent and traceable in the portal.
- Confirm that at least two entities sit in different states/approved associated territories.
- Confirm that project roles are clearly split so partners are not nominally separate but functionally the same entity.
The source page also mentions special cases (for instance Switzerland and Hungarian universities) and points to the Call Manual. In practice, this means there can be jurisdiction-specific interpretation for some partners, so use the official manual and portal guidance rather than a generic consortium template.
Beyond geography and legal structure, this call is best fit for groups with:
- a working implementation relationship with cities, mobility providers, or mobility-related users,
- credible commercial pathway (not “idea only”),
- a realistic partner mix (public sector, academia, startup, SME, or NGO where role clarity exists),
- and the willingness to provide staged data from pilot activities.
Because this is a consortium call, solo applications are not the target profile. A technically strong solo startup is less likely to score well unless it is already embedded in a strong collaboration framework and can prove partner deliverables.
Application process (practical sequence)
The call page directs applicants to the EIT Urban Mobility Programmes Portal for application submission and partner registration. While exact portal workflow changes over time, the documented process includes:
- Register in the programmes portal.
- Select the current open cut-off for this call.
- Submit the application within the published cut-off time.
- Undergo a two-stage review.
Stage 1 is described as expert evaluation of submitted proposals in the portal. Stage 2 includes panel hearing and selection committee decision. Because this is explicitly two-stage, the proposal should already be complete at first submission and not “best-fit later” through revisions.
To reduce preventable delays:
- Ensure the legal registration entry is complete before writing the final narrative.
- Complete partner information and confirm all consortium entities can be represented in the same application context.
- Keep proposal materials in stable file names and consistent numbering for figures, financial tables, and references.
- Maintain one “compliance copy” with only required attachments and mandatory fields completed.
The page includes official contact support for registration issues, including the innovation team email. Use it early if portal registration blocks partner details or PIC linkage, rather than waiting to discover it on deadline day.
Timeline and key dates (how to build your internal calendar)
The source page lists several cut-off dates. There is also a current-call listing entry showing a separate “Strategic Innovation Open Call” deadline of 29 September 2026. Treat these as follows:
- Use the currently published portal entry as the active submission date for the round you are targeting.
- Read the full call page section for historical and additional dates, since it also explicitly names 2025/2026/2027 windows.
- Build internal planning around two gates: application draft and quality checkpoint.
At minimum for 2026/2027 planning:
- Now to summer 2026: consortium commitments, role definitions, and proof of feasibility.
- By each cut-off window: full draft ready one week earlier to allow document updates.
- Post-submission: admissibility checks can take up to ~1 week.
- Evaluation phase: up to ~6 weeks for invitation decision, then hearing and portfolio selection period.
If you are planning for 2027 windows, align internal budgets for repeated or rolling submissions. Because this is an open-call pattern, teams often improve proposals across cycles if they plan for one cycle of feedback and one cycle of refinement.
Preparation playbook for a stronger proposal
Treat this call like a market implementation project, not a pure research submission.
1) Start with deployment hypothesis, not technology narrative
Begin from a concrete deployment hypothesis: which city, operator, corridor, or service provider context will test the solution; what barrier is addressed; what changes if the pilot succeeds. The call language rewards projects that show readiness for large-scale deployment and city/provider adoption.
2) Build the consortium around execution
A compelling consortium is not a list of logos; it is an execution architecture.
- One partner should lead delivery and technical integration.
- One partner should own user context (public agency or operations-side partner).
- One partner should anchor commercialization and market model (SME or startup with sales path).
- If a university or research partner is included, define its role in validation and evidence generation.
3) Tie milestones to fundable outcomes
Map every milestone to the funded scope:
- milestone 1: technical readiness and test protocol;
- milestone 2: pilot deployment and operational acceptance data;
- milestone 3: scale route and investor/public adoption plan.
4) Prepare evidence packs in two tracks
Track 1: technical evidence (performance metrics, baseline baseline, risk management). Track 2: market evidence (users, procurement logic, cost/benefit, adoption pathway). Do not merge these into one generic appendix; show clear link between development and rollout readiness.
5) Use the portal field logic early
Because submission is portal-driven, field-by-field planning avoids late errors. Build a mirrored outline where your internal sections map exactly to portal sections. Include glossary and KPI expectations from the call references where possible.
Common mistakes that weaken applications
Incorrect consortium assumptions
Many strong teams fail on the first review because partner structure is not genuinely independent or cross-country enough. If all partners are legally independent but practically linked, reviewers may still treat it as weak.
Underestimating co-funding discipline
The call is not full-cost funding. Teams that present aspirational budgets without confirmed co-funding sources often struggle at admissibility stage.
Overbuilding “technology story” and underbuilding deployment path
This call is for solutions with strong path-to-market and large-scale deployment readiness. If the proposal is primarily a research concept, it may perform poorly compared with implementation-ready peers.
Ignoring the multi-stage nature
Some teams submit material assuming iterative correction after Stage 1. In two-stage calls, quality at first stage is the gate. Panel hearing strength depends on how clearly Stage 1 evidence already demonstrates implementation realism.
Missing deadlines while assuming one global cycle
The call is open via several cut-offs. Treat each as separate windows and track date changes via official listings. Late submission habits are especially risky because portal systems can close in short windows.
FAQ for immediate decision-making
Is this call only for companies?
No. The wording explicitly mentions collaboration across education, research, business and cities, and uses a multi-beneficiary design. This invites broader consortia with strong municipal and knowledge partners.
Can a newly formed startup apply?
A startup can apply if it forms a compliant consortium and demonstrates readiness for commercialization and deployment. On its own, startup-only submissions are unlikely to satisfy the multi-beneficiary profile and co-funding expectations.
What if my city is not in the EU?
The page states entities must be in different EU Member States and/or Horizon Europe associated countries, with special handling for specific cases. You should verify eligibility of your legal entity location in the call documents before finalizing the consortium.
Are there later 2027 windows?
Yes, the key-date list includes cut-offs in February and June 2027, meaning this call remains relevant beyond 2026. Use the portal listing to confirm the currently open date before final submission.
Is there an application fee?
No public fee is indicated on the official call page.
Official links and follow-up actions
- Official call page:
https://www.eiturbanmobility.eu/call-for-proposals/strategic-innovation-open-call/ - Calls list and programme page:
https://www.eiturbanmobility.eu/call-for-proposals/ - Application portal: EIT Urban Mobility Programmes Portal (linked from the call page as the submission system)
- Support contact: [email protected] (for portal and general technical issues)
For a practical internal workflow, create a one-page internal tracker with:
- confirmed cut-off window,
- lead partner and legal IDs,
- co-funding commitments,
- deployment milestones,
- and decision dates for admissibility and hearing.
If you are aligning for 2027, do not use one proposal exactly repeated from 2026. Use 2026 as a data-gathering and partner-validation window, then apply lessons to the next cut-off with a cleaner deployment section and stronger commercial narrative.
