Eco Route — Recommended
Transit 6 + walk 3 + e-scooter 3 (last mile) · transfers: 1
24MIN
A simulated match-day operations console and multimodal eco-routing engine designed to manage peak arrival traffic across 16 tournament host cities.
A simulated operations console modeled on a peak Toronto match window (Match 14 at BMO Field). When security gate queues swing from 6 to 30 minutes and arterial roads back up, operators and fans need clear, synchronized information. The platform pairs live network telemetry with an eco-routing engine that evaluates public transit and shared micro-mobility directly against driving.
Multimodal green routing (transit + walking + last-mile scooter) bypassed Gardiner Expressway congestion, reducing peak travel time from 45 to 24 minutes.
Standard regional transit fare plus shared micro-mobility totaled $3.50, compared to $18.00 for stadium parking and fuel. Costs surface up front during route comparison.
Modeled per-trip delta between solo driving and multimodal transit, calculated using standard transit and micro-mobility emission factors across the match-day cohort.
Lead product designer covering UX research, design systems, UI design, and web prototyping.
Figma, design token systems, SVG data visualization, HTML/CSS web prototyping, GitHub Pages
Simulated match-day ops console and multimodal eco-route planner for 16 host cities
EcoMove 2026 is a mobility management platform designed for FIFA World Cup 2026 host cities. It connects real-time transit telemetry with an eco-aware route planner to help operators manage crowd surges and help fans choose lower-carbon travel options. Built and tested as a live web prototype using Match 14 at BMO Field (Toronto) as the primary scenario, with planning frameworks cross-checked against MetLife Stadium and Lumen Field.
Ten screens and design artifacts from the EcoMove 2026 build: the match-day operations console, live transit network map, multimodal route comparisons, digital ticketing pass, and design system tokens.
Toronto // Live Match-Day Operations
Real-time congestion around BMO Field and the city's eco-transport response. Simulated match-day data refreshes every 5 seconds.
CO₂ Saved Today 🌱
3.42 t
▲ +12.4% vs Match 12 vs all-car baseline
modeled · upper-bound case
Transit Adoption 🚌
68%
of fans on green modes
scenario assumption
Active Eco-Fans ⚡
24,318
modeled
Congestion Index 🚦
7.2 /10
Heavy near Gate C
modeled
Line 1 headway shortened to 3 min 30 s
ES-4 shuttle dispatched from City Hall hub
+412 fans redeemed the Green Transit Pass
Gardiner Expy delay growing near Gate C
Fleet St dock restocked — 19 e-scooters added
🚗 One car trip to the stadium ≈ +4.2 kg CO₂ + parking risk.
🚇 The eco-route avoids 1.8 kg CO₂e vs driving per fan (modeled).
🎟️ Green-mode fans earn 2× Fan Points redeemable at fan zones.
Transit 6 + walk 3 + e-scooter 3 (last mile) · transfers: 1
24MIN
Dedicated match-day bus ES-4 · non-stop
20MIN
Via Gardiner Expy · includes parking queue
45MIN
One QR for transit + shuttle + docks. Scan at any gate.
Times include security gate wait at the selected match-clock state. Eco fare = bundled illustrative fare. The shuttle is faster but costs ~43% more and avoids 0.7 kg less CO₂e. Timeline is illustrative; segment durations are scenario parameters, not timetable values.
CO₂ Saved
3.42 t
▲ +12.4%
A simulated match-day flow from security gate monitoring to multimodal routing and digital ticketing. Times shown are scenario parameters for the Match 14 BMO Field window.
Select an entry gate to inspect modeled security queue delays across the match clock.
Mega-events funnel tens of thousands of attendees onto identical transport corridors simultaneously. Station platforms crowd, arterial highways back up, and stadium security queues fluctuate rapidly between quiet hours and kickoff windows. Traditional municipal transport tools rely on static schedule tables that cannot guide fans through real-time operational shifts.
In the Toronto BMO Field scenario (Match 14), gate queues shift from 6 minutes during early arrival to 14 minutes mid-afternoon and 17 to 30 minutes in peak pre-match windows. Congestion along the Gardiner Expressway inflates solo driving trips to 45 minutes, $18 in costs, and +4.2 kg CO₂e per attendee. A single-occupancy vehicle emits roughly 171 g CO₂ per fan-km on this corridor, compared to 41 g for express shuttles, 28 g for regional rail, and 0 g for micromobility. Cities have baseline transport data, but lack an integrated interface to actively balance traffic across green modes during peak loads.
Established 7 semantic color tokens, 3 typography families (Plus Jakarta Sans for display, Inter for UI, JetBrains Mono for telemetry), and 100% token coverage across both screens. Tokenizing spacing (4–32px scale), corner radiuses (8/12/18px), and animation timings allowed assembling subsequent screens quickly while maintaining strict visual consistency.
Designed a real-time command dashboard featuring core telemetry tiles, an SVG road network heatmap with corridor state indicators, live security gate queue monitors (CLEAR, MODERATE, HEAVY), and toggleable transit layers. A live network feed logs headways, shuttle dispatches, and hub inventory so operators can make tactical adjustments in real time.
Created an eco-first route comparison interface comparing transit options against a driving baseline on travel duration, carbon emissions, and total fare. Built around full transparency: the lowest-carbon route displays positive net emissions (+2.4 kg CO₂e) and explicitly states avoided emissions (1.8 kg avoided vs driving) rather than claiming zero-carbon transit.
Translated Figma specifications into framework-free, accessible HTML/CSS/JS deployed to GitHub Pages. Structured the codebase with modular files sharing unified tokens and simulated data hooks, enabling straightforward replacement with production GTFS-Realtime APIs.
| Metric | Car Baseline | Eco Route | Impact |
|---|---|---|---|
| Door-to-gate time | 45 min | 24 min | −47% |
| Trip cost | $18.00 | $3.50 | −81% |
| CO₂e per attendee | +4.2 kg CO₂e | +2.4 kg CO₂e | 1.8 kg avoided |
| Match-day scale | Baseline (72% car) | 38% car share (646 converted) | ~1.2 t avoided · $9.4K saved |
Integration with live GTFS-Realtime feeds, predictive egress modeling for post-match surges, accessible routing pathways for mobility-impaired passengers, and progressive web app (PWA) wallet integration for unified multi-operator digital passes.