
Transportation models support billions of dollars in infrastructure decisions every year — yet they are routinely blamed when projects produce unexpected outcomes. The problem is rarely the software. It's how models are developed, interpreted, communicated, and applied.
A transportation model does not predict the future. It estimates what is likely to happen under a defined set of assumptions. Change the assumptions — change the forecast. That is not a flaw. That is the entire point.
Models reduce uncertainty. They never eliminate it.
What will happen?
What is likely to happen if we implement this project under these assumptions?
No modelling software — however sophisticated — can overcome inaccurate or outdated assumptions. Garbage in, garbage out remains the most fundamental truth in transportation modelling. When inputs are flawed, every downstream output inherits that flaw, often invisibly.
Outdated counts, flawed forecasts, missing network data
Sophisticated software amplifies and propagates every flaw
Flawed forecasts, misguided decisions, wasted investment
Poor inputs do not stay contained — they contaminate every analysis, every scenario, and every recommendation that flows downstream from the model.
Every transportation model is designed to answer a specific set of planning questions. Using a model beyond its intended scope does not produce better answers — it produces misleading ones. Understanding a model's boundaries is just as important as understanding its capabilities.
Credible toll revenue forecasts require explicit representation of Value of Time (VoT), toll choice behaviour, and route choice sensitivity. Without these, revenue estimates are speculative at best.
If Uber, Lyft, and similar services are not represented in the mode choice structure, the model cannot estimate mode shifts, ride-hailing demand levels, or induced trip generation from these services.
E-scooters, bike-share, and autonomous vehicles require specific behavioural parameters. Models built before these modes existed cannot reliably forecast their impacts without explicit recalibration.
A thermometer isn't broken because it can't measure wind speed. Neither is a transportation model. Know what your model measures — and what it doesn't.
Software defaults rarely represent local travel behaviour. Every city has unique driving patterns, transit usage levels, freight dynamics, and congestion characteristics. A model running on default parameters is an unproven model — regardless of how sophisticated the underlying software may be.
During calibration, the model's behavioural mechanisms are adjusted — trip generation rates, gravity model decay functions, mode choice utilities, and assignment parameters — until the model reproduces observed base-year conditions. The focus is on tuning the mechanisms that drive travel behaviour.
During validation, the resulting model outputs are compared against independent observations not used in calibration, and checked for reasonableness and credibility. This confirms that the model's outputs — volumes, travel times, mode shares — are accurate and defensible.
Models routinely report outputs like:
These numbers look authoritative. They are not exact. They are estimates — and presenting them as certainties misleads decision-makers.
Present low, base, and high forecasts that bound the likely range of outcomes rather than a single deterministic result.
Test how forecasts change when key assumptions shift — population, mode share, fuel cost — to reveal which inputs most influence outcomes.
Document and communicate every major assumption explicitly so decision-makers understand the basis — and the limits — of each forecast.
A transportation model cannot compensate for poor problem definition. When the wrong question is asked at the start, even the most rigorous modelling effort will produce answers that are technically correct but strategically irrelevant. The framing of the question determines the value of the analysis.
Should we widen the road?
This question presupposes a solution before the problem has been defined. It constrains the analysis and limits the alternatives considered.
Transportation models are analytical tools. They are not decision-makers. The most common — and most costly — mistake in transportation planning is allowing a model output to substitute for experienced professional judgment. Results must always be interrogated, not just accepted.
Experienced practitioners always ask: Does this result make sense? Does it match what we observe in the field? Is there a coding issue, a missing behaviour, or a policy shift that could fundamentally alter travel patterns? These questions are not second-guessing the model — they are essential quality control.
Successful transportation projects follow a disciplined, transparent process that integrates rigorous modelling with clear communication and professional judgment. Great modelling builds confidence in decisions — not just in forecasts.
Clearly articulate the infrastructure or policy decision that modelling must inform.
Frame the planning question around the actual problem — not a presumed solution.
Collect current, representative traffic counts, demographics, land use, and transit data.
Match the model type and scope to the specific planning questions being evaluated.
Adjust parameters to reproduce observed conditions and verify model reasonableness.
Evaluate low, base, and high cases alongside alternative investment strategies.
Present ranges, sensitivities, and key assumptions transparently to all stakeholders.
Combine model outputs with field observations, local knowledge, and professional experience.
Use the full analytical picture to support defensible, transparent infrastructure investments.
"The goal of transportation modelling is not to predict the future with certainty — it is to improve today's decisions by making future outcomes more understandable."
The value of transportation modelling lies not in producing precise numbers, but in helping decision-makers compare alternatives, understand trade-offs, and make more informed, defensible investments.
Why Transportation Models Fail Decision Makers — And How to Avoid It