How TableJourney decides what to publish, and how we know it is still true on the day you read it.
Every entity is verified
Every restaurant, bar, cafe, market, festival and food tour we publish carries a verification record. We save the source we cited, the address quoted from that source, whether the venue is currently operating, and the date a human editor last cross-checked it. If a venue does not have that record, it does not get published.
The date the editor last verified the entry is shown on every page in the facts panel as "Last verified." It is set by a human, not auto-stamped.
One human editor signs off
Every city is read end-to-end and signed off by Lewis Vaughan before it goes live. AI tools help with research synthesis, copy edits and source-URL checks; no page is published as raw AI output. Every factual claim is cross-checked against a primary source.
What we will not publish
- An entity we cannot verify is still operating at the address we cite.
- A booking link pointing to a directory (Yelp, TripAdvisor, Michelin Guide) rather than a real reservation flow.
- A festival date carried forward from a previous year without operator confirmation.
- Hours, phone numbers or addresses we could not corroborate.
Weekly drift check
Every Sunday we re-probe every source URL on the site for drift. Sites go dead. Operators move. When we find a change, it gets fixed that week and the affected pages get a fresh verification stamp.
Editorial scoring
The number next to each entity is our editorial verdict, on a 1.0 to 4.9 scale. It is set by the desk, not aggregated from external rating sites. A 4.5 means we will send a friend there without hedging. A 3.0 means the chapter would feel incomplete without it.
Corrections
If a venue has moved, closed or changed hands, the contact page is the way. Material corrections are called out at the bottom of the affected page with the date the change landed.