GuardTrails
.jpg){kind=link}
On 16 September 2026, we applied one geographic-consistency rule to 41 itineraries. It found 3 real defects, and no false positives.
Two stages in Syria and Lebanon on a Jordan tour. A night planned in Afghanistan on a Tajik tour, a country that on that date was under a formal “advise against all travel” notice from the UK Foreign Office. We say nothing else about those tours: not who wrote them, not their length, not their price.
What the rule found, and what it does not say
As we read it, the rule spots stages that do not match the zone the tour announces. It does not say whether a stage is dangerous: the travel advice does.
Three defects out of 41 is few. But one of them, a night in a country under a do-not-travel notice, is enough to require revising the tour before selling it.
What not checking costs
The check itself is a per-tour task: reading the travel advice, stage by stage. It is one of the tasks that usually gets skipped when time runs short; how long to build a tour itinerary gives the task list.
The cost comes afterwards. A stage is reworked when the tour has already been described. A choice has to be explained to a client, a local partner, an insurer, without always knowing what they expect of you. That cost has no figure in this study, and we do not invent one.
Checking travel advice, stage by stage
Five moves.
- List the country of each stage and each night, including excursions and stops near a border. A stage is named by the zone you visit there: see stage or lodging.
- Open the travel advice for each country, from the authority your clients depend on: in France, the foreign ministry's Conseils aux voyageurs; in the United Kingdom, the Foreign Office; in Germany, the Auswärtiges Amt.
- Read the level by region, not only by country: an advisory can target a specific zone.
- Note the level found and the date consulted in the file. Advice changes: what you read one day is not what it will say on departure day.
- Repeat before departure, and at every change of stage.
The full list of checks for a review, beyond geography, is in how to check a tour itinerary. The difference between working by hand, an AI assistant and an engine is in operator, AI assistant or engine.
What the feasibility check adds
The feasibility check on /pro, in beta, runs an existing tour through the engine. The report is confidential: a grade from A to D, six dimensions, written assumptions and, when data is missing, the question to ask the operator rather than a guess. The engine detects that a constraint exists (a ferry, a mountain road, a permit), never whether it is compatible with a precise date. It does not replace reading the day's travel advice before departure.
If you want a tour checked
Fill in the beta form on /pro and tick “Check an existing circuit”. We are the ones who run the tour through the engine.
What we do not know
41 itineraries, one date, one rule: that tells you what this rule found that day, not how frequent defects are elsewhere.
We do not say where the 41 itineraries come from, and they allow no conclusion about any category of business.
Travel advice changes: the level cited holds for 16 September 2026, not for the day you read this.
The rule spots a gap in zone, not a risk. It does not replace your own reading.
Measured and dated fact: on 16 September 2026, one rule applied to 41 itineraries. Checking procedure: method definition.
A figure looks wrong to you, or has an advisory changed since? Write to us — corrections are published.