From the Transportation edition of October 30, 2026
Bus passengers save 1.5% in journey time on London routes optimised by CitySwift's AI
CitySwift (vendor); Transport for London and London bus operators · Transit agency · London, United Kingdom
- Publisher
- CitySwift blog
- Original publication
- October 13, 2026
- Source retrieved
- 2026-10-31
What happened
CitySwift reports that customer journey times on routes optimised with its AI platform fell 1.5 percent, measured using TfL's Journey Time Metric combining speed and reliability. It says this equals 27 seconds per optimised journey, projects more than 25 million passenger-hours saved over three years valued at over £230 million, and states more than 40 percent of London's bus network has been reviewed with 200 routes improved at no cost since deployment in 2024.
Why it matters
A measured, modest result using an agency-defined metric is a useful counterweight to larger projections in transit AI marketing; U.S. agencies can ask vendors for similar agency-metric reporting.
Evidence and measured results
Vendor announcement; the metric is TfL's, but the analysis, baseline and attribution method are not published; the hours and value figures are projections.
Limitations and uncertainty
Vendor-authored; no independent evaluation; projections of hours and monetary value; London's franchised bus model differs from most U.S. agencies.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-30; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Improving bus journey times and reliability through data-driven schedule and route adjustments.
- Stakeholders
- Service planning and scheduling
- Transit data teams
- Contracted operators
- Agency leadership
- Discovery questions
- What metric would you require a vendor to report against?
- How good is your AVL and running-time data?
- How would gains be attributed versus other changes?
- Value hypothesis
- Schedule optimization can produce small but measurable journey-time gains when tied to agency metrics.
- Potential engagement
- A bounded metric-design and evaluation plan for AI-assisted scheduling.
- Unsupported claims
- Projected hours and monetary savings
- Independent validation
- Transferability to U.S. operating models
Pre-sales engineering
Role takeaway
- Fit
- Fits agencies with mature AVL and scheduling data.
- Architecture and integration
- Vendor platform ingesting AVL, schedules and running times to simulate and recommend changes.
- Prerequisites
- Clean AVL and GTFS data
- Agency journey-time metric
- Service-change process
- Constraints
- London franchised model
- Vendor-reported results
- Scheduling labor rules
- Security
- Set data-sharing and retention terms for operational data on the vendor platform.
- Proof of value
- Optimised versus control route comparison
- Per-trip journey time change
- Reliability metric change
Delivery
Role takeaway
- Work
- Implement optimised schedules through service changes with matched controls.
- Dependencies
- Scheduling software integration
- Operator agreement
- Data quality fixes
- Ownership
- Agency service planning and scheduling.
- Skills and adoption
- Train schedulers to review and adjust AI-recommended changes.
- Governance checkpoints
- Metric approval
- Service-change review
- Post-change evaluation
- Acceptance criteria
- Proposed: journey-time change measured against control routes
- Proposed: results reported using an agency-defined metric
- Risks
- Gains too small to detect
- Attribution confounded by other changes
- Overstated projections
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
A shared data platform for the authority and multiple operators supports simulating route changes before implementation.
Governance
Who approves, reviews and stays accountable for outcomes?
Using the authority's own metric for reporting is a good practice for vendor accountability.
Security and privacy
What data, permissions and controls need testing?
Operational data shared between authority and operators on a vendor platform; data terms are not described.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Schedulers and planners use the platform; workforce effects are not described.
Procurement
What should contracts, pricing and exit terms secure?
A 'performance partnership' framing suggests outcome-linked contracting, which U.S. agencies could explore.
Operating model
Which teams own the service once it runs?
Authority and operators work on one platform, which depends on London's contracted operator model.
Publication history
- 2026-10-30Transportation · Issue 0213 resources
Stable resource ID: cityswift-tfl-bus-journey-time-results