Editorial & Verification Policy
How we research, cross-examine, and publish accurate transport information for Dubai commuters.
1. Source Hierarchy
We rely exclusively on primary, governmental, and official operator sources:
- Tier 1 (Primary): Official Roads and Transport Authority (RTA) documentation (`rta.ae`), Dubai Government official portals, and RTA mobile apps (S'hail, nol Pay).
- Tier 2 (Official Operators): Official partner operators including Dubai Taxi Corporation (DTC), Nakheel (Palm Monorail), and Dubai Airports (DXB).
- Excluded Sources: We never cite unverified forum rumors, social media speculation, or unofficial transit aggregators.
2. The Facts Registry System
Every dynamic transit fact (fares, minimum balances, operating schedules, interchange configurations) is recorded inside our centralized structured facts registry (`/data/facts.json`).
Each registered fact must have three mandatory attributes:
- The exact numerical or textual value.
- The direct official URL citation from which it was extracted.
- The exact date it was verified by an editorial staff member.
3. Prohibition of Fabricated Data
If a particular station exit, feeder route, or future fare is not yet published in an official RTA gazette, we refuse to make an educated guess. Instead, we mark the item with an internal verification hold and exclude it from public guides until primary confirmation is achieved.
4. Live Today vs. Announced Milestones
Dubai rapidly innovates. When a new initiative is announced (such as Account-Based Ticketing or future metro lines), we explicitly label the status as "Announced / In Rollout" alongside the target date, ensuring readers never confuse future capabilities with features operational at smart turnstiles today.
5. Monthly Audit Cycle
On the first day of each calendar month, our team conducts a full verification audit of all registered facts in accordance with our documented protocol in CHANGELOG-CONTENT.md.