Methodology
How we decide what to recommend, how we rank options, and how we keep transport recommendations honest.
Our Editorial Philosophy
Our guides are built for travelers who need to make decisions, not for readers who want inspiration. We optimize for clarity, accuracy, and actionable detail — fares, timing, what to avoid, and the fastest way from A to B.
How We Rank Options
When we rank transport modes, routes, or parking options within a guide, we use the following criteria — in this order of priority:
- 1
Usefulness for the Reader's Decision
Does this option help the traveler decide how to get around? Vague picks are cut.
- 2
Reliability & Accuracy
Does the route/operator run consistently? Are the fares and times we documented verifiable?
- 3
On-the-Ground Verification
Has our team or a trusted local contributor verified this personally or via recent reports?
- 4
Value for Traveler Budget
Does the option match its price? We flag both overpriced transfers and underpriced day passes.
- 5
Speed vs. Simplicity Tradeoff
We explain the tradeoff explicitly — fastest isn't always simplest, and we say which is which.
What We Don't Rank By
Understanding what we explicitly exclude matters for trust.
- ✗Affiliate commission rates — high-commission providers get no ranking boost
- ✗PR pitches and media requests from operators
- ✗Social media popularity or influencer endorsements
- ✗Paid placement of any kind
Where Our Data Comes From
Our recommendations synthesize multiple signal types. We prioritize signals in this order:
1. Direct experience
Our team's personal trips, rides, and parking notes
2. Local contributors
Region-based writers with lived experience getting around the city
3. Primary operator data
Official timetables, fares, zones, and parking information
4. Government tourism boards
Official transport advisories and city mobility information
5. Reputable published journalism
Named authors at established publications with editorial standards
Handling Uncertainty
When we can't verify a detail, we say so. Phrases like 'reportedly', 'according to [operator]', or 'unverified as of [date]' appear in our guides deliberately. We'd rather be honest about uncertainty than pretend to know what we don't.
Read our editorial policy for how this process is executed on every guide.