CathayGuide has one named editor and a desk workflow for source-heavy pages. City writing comes from repeated China travel and route planning; rule-heavy pages are checked against the documents and app flows a traveller would actually face.
We keep the masthead deliberately small. If a page is wrong, there is no anonymous content farm to hide behind: send the URL, the claim and the source to the corrections desk.
Charles writes and maintains CathayGuide’s independent China travel guides. He is responsible for the site’s practical entry, transport, city-routing and first-trip planning coverage, and for deciding when fast-changing guidance needs to be re-checked.
The desk maintains the source log for pages that can become wrong quickly: visa notices, entry forms, hotel registration, payments, connectivity and rail booking. A page date changes only after the underlying source or on-the-ground process has been re-checked.
Editorial beats
Route planning for Beijing, Shanghai, Chengdu, Xi’an, Guilin, Zhangjiajie and Chongqing.
Visa-free transit, arrival cards, Tibet/Xinjiang restrictions and border-process explanations.
Hotel passport registration, payments, eSIMs, VPNs, DiDi, rail and practical app setup.
Reader reports are triaged by page URL, source type and whether the change affects trip decisions.
Who owns each kind of judgement
A good China guide mixes route taste with operational caution. This is the masthead split: the editor owns travel judgement, the desk owns fast-changing workflows, and corrections decide what gets re-opened first.
Night counts, rail order, airport choice, day-trip pressure and whether a route still works when someone is tired on day three.
Where a visitor will queue, what must be booked first, which address needs saving in Chinese, and when a driver beats public transport.
Payment linking, DiDi setup, eSIM activation, train booking and hotel check-in steps that can fail even when the rule itself has not changed.
Reader reports are sorted by trip impact first: stranded, refused, overcharged, rerouted, then cosmetic or wording issues.
How bylines work here
CathayGuide keeps one house voice so the site is easy to use, but the responsibility behind that voice changes by page type.
When a page says which city deserves more nights, where to sleep, or which sight to skip, that judgement belongs to the named editor.
When a page changes because an app flow, ticketing path or entry form moved, the desk records the check even if the prose stays in one voice.
A reader report can trigger a re-check, but it is not published as a rule until we can reproduce it or tie it to a source.
What sits in the notebook
The author page is not the full rulebook. It shows the editorial judgement we are willing to attach names to: where visitors lose time, where a city route breaks, and which practical details deserve a re-check before advice changes.
- Which China trips can realistically be done without a private driver
- Where first-time visitors lose time: station transfers, ticket windows, hotel desks and app setup
- What English-speaking travellers misunderstand about Chinese city scale
- Which scenic side trips are worth the extra night rather than a rushed day tour
- Where reader corrections reveal a broken workflow, not just a changed fact
Where this masthead appears on the site
Route order, day counts, where-to-stay logic and whether a scenic add-on deserves the time.
Internet, payments, DiDi, rail and hotel registration steps a visitor must solve before the first full day.
Visa-free transit, Tibet, Xinjiang, arrival forms and foreign-plated vehicle entry are desk-checked before changes go live.
Reports with screenshots, dates, city names and provider names get priority because they are fastest to verify.
How to challenge a page
The most useful correction includes three things: the page URL, the sentence that looks wrong, and the source or screenshot that contradicts it. We give priority to corrections that affect entry, money, accommodation, transport or personal safety.
Reach the desk through the corrections page.