Methodology for Consequence Analysis of Future Mobility Scenarios: The SPROUT Framework

Elpida Xenou, Georgia Ayfantopoulou, Beatriz Royo, Sara Marie Tori, Marco Mazzarino

Research output: Contribution to journalArticlepeer-review

40 Downloads (Pure)


The various social, political, environmental, and economical mega-trends together with the
rapid rise of digitalization are shaping cities worldwide including the way that citizens and products
move within the urban environment. New mobility services are popping up which are showing the
path toward more on-demand and personalized mobility patterns. The transformation of the urban
mobility environment though constitutes a great challenge for policy-makers, as little is known about
the impact of these trends on the city’s current mobility environment while the assessment of the
future state of a mobility system can be considered a quite complex process taken its multi-parametric
and multi-dimensional nature. This paper aims to simplify this process by presenting a coherent
multi-actor consequence analysis framework as a tool for assessing future mobility scenarios which
was developed in the framework of the H2020 SPROUT. This paper presents in detail the main
components of this framework together with the list of key performance indicators used for assessing
the performance in terms of sustainability of future mobility scenarios as well as indicative results
from its use by the city of Padua.
Original languageEnglish
Pages (from-to)453–466
Number of pages14
JournalFuture Transportation
Issue number2
Publication statusPublished - 18 May 2022

Bibliographical note

Funding Information:
This research was funded by the “Sustainable Policy RespOnse to Urban mobility Transition—SPROUT” project in the framework of the HORIZON 2020 European Programme, Grant Agreement No. 814910.

Publisher Copyright:
© 2022 by the authors.


Dive into the research topics of 'Methodology for Consequence Analysis of Future Mobility Scenarios: The SPROUT Framework'. Together they form a unique fingerprint.

Cite this