Editorial
Editorial Policy
This policy explains how we produce travel information, where our data comes from, and what we do when we get something wrong.
Where our information comes from
Route timings, stops, operators and fares come from the same systems that power booking on Shawy — operator schedules and our own booking records. Where an operator publishes official guidance (baggage rules, border requirements), we follow that source and say so.
What we will not publish
We do not estimate figures. If we cannot source a journey time, a distance or a fare, we omit it rather than approximate it, because a confident-looking guess is worse than a gap. We do not present a service as daily, direct, or available unless the operational data supports it.
How articles are written and reviewed
Guides are drafted by the Shawy editorial team and checked against live platform data before publishing. Where an article has been checked by a named reviewer, that person is credited at the end of the article along with their role.
How we handle updates
Bus services change. When a route, schedule or fare structure changes materially, we update the affected articles and record the date of that update on the page. We do not refresh the update date for routine site maintenance, so a recent date genuinely means the content was revisited.
Translation
Our guides are published in multiple languages. Translations are produced from the English original and reviewed for meaning rather than word-for-word equivalence. Where a translation is credited to a named translator, that credit appears with the article.
Corrections
If you find something inaccurate, tell us and we will check it against operator data and correct it if we are wrong. Corrections to material facts are reflected in the article's update date.
Independence
Shawy sells tickets for the operators we write about. We do not accept payment in exchange for favourable coverage, and commercial relationships do not determine which routes we cover or what we say about them.
Spotted something wrong?
Tell us and we will check it against operator data.