GuardTrails
Our current benchmark: about 4 h 30 of manual groundwork for an 8-day circuit, against 5 to 10 minutes of calculation. Stages, nights, distances, climate, activities, geographic consistency — even with Google and ChatGPT. The engine books nothing: it does the groundwork. The 5 to 10 minutes are the engine's calculation time, not the time to deliver a validated circuit: the human review remains your responsibility. Estimate, measurement under way.
Send us one circuit: the free review
We run it through the engine and show you what it finds. Free, no commitment, no account: proof on your own data. We run it for you; it is not a self-service tool.
Get an itinerary reviewed for free — for a full, graded report, see the feasibility check below.
What you do today
For each circuit, someone places the stages on a map, measures the legs, checks the month's weather, looks up activities and how long they take, then cross-checks everything. Copy, paste, start again. And what nobody checks, nobody sees: a driving day dressed up as a sightseeing day, a climate that does not fit, a stage inside an advised-against area.
The cost of not checking
41 itineraries tested · 3 real defects · 0 false positives. On 16 September 2026 we applied a single geographic consistency rule to forty-one itineraries.
Two stages in Syria and Lebanon on a Jordanian circuit. And a night planned in Afghanistan on a Tajik circuit — a country under a formal "do not travel" advisory from the British Foreign Office. Nobody had spotted it.
This is not a matter of style. It is a matter of exposure — legal, insurance, and reputational.
How long it takes, and what we do instead
Our current benchmark for an 8-day circuit (13 stages, 12 legs), excluding booking: we book no hotels, flights, cars or activities. These are starting estimates, measurement is under way: we will publish the method and the results.
| Average agency time | Check everything (premium) | With the engine | |
|---|---|---|---|
| Skeleton of an 8-day circuit | about 4 h 30 | about 8 h 30 | 5 to 10 minutes of calculation |
| One stage: place, lodging, climate, photo, trail | 8 min | 19 min | included |
| One leg: distance, real time, feasibility | 3 min | 4 min | included |
| One day: composition, weather plan B | 8 min | 13 min | included |
"Average time" is what an agency does in practice, skipping what takes too long — the climate of each stage, for example. "Premium" is everything the engine does, done by hand. Reading over the result is the same in both cases: we do not count it.
The order of magnitude: four and a half hours by hand is about €100 at the lowest hourly rate. Our cost target is below €20 per calculated circuit; pricing will be tiered by volume — contact us.
See it on published itineraries
The result reads on real circuits, calculated by the engine. Each one shows the nights per stage, the road distances, three ways to travel it with what you gain and what you leave aside, and what you need to check yourself before booking.
- Northwest Highlands, 14 days — a long circuit: 6 bases in its classic version, 595 km stage to stage.
- Stockholm and its archipelago, 4 days — a short stay.
- A weekend in London — from a weekend to a long trip, the same method.
The feasibility check of an existing circuit
You already have a circuit: your own, one from a ground handler, or the quote a client brings you. We run it through the engine and send you back a confidential report: a grade from A to D, and what it rests on, dimension by dimension.
- Roads and driving time: the real legs, day by day, and the days when the road eats the visit.
- Pace and nights per base: one-night bases, stages too short for what they hold.
- Season, climate, closures: the climate of the month at each stage, seasonal roads and sites.
- Access and gateways: how you get in, how you get out, connections with limited departures.
- Budget: the advertised price against our estimate.
- Gaps and repetitions: what is missing, what repeats.
The report also sets the circuit against agency circuits in the same area — length, pace, number of bases. It states its assumptions, and when a piece of information is missing it does not guess: it writes down the question to ask the agency. Done by hand, this check repeats most of the table above: every stage, every leg, every day.
An example, fictitious — a 12-day circuit between islands and mountains, graded C:
- Access: the crossing on day 5 depends on a ferry with limited departures, and the circuit does not say which one. Not verified: confirm before selling the date.
- Season: the track to the day-8 hut is usually closed in May. Probable closure, check first.
- Budget: inconclusive. The gap with our estimate turns on a single question, to ask the agency: is the international flight included in the advertised price?
- Pace: three one-night bases in a row, days 2 to 4; comparable circuits in the area have one or two.
The report stays between you and us: we never quote a checked circuit, nor the agency that built it. One case of stage-by-stage checking: The cost of not checking an itinerary.
Request a feasibility check — the service is in beta: the form below opens with "Check an existing circuit" already ticked; leave your address and we will get back to you.
What it does
It flags what will not hold: materially impossible days, repetitions nobody asked for, the gap between what was ordered and what is delivered.
It calculates where to go. When the window of dates is fixed, the destination becomes the variable: the engine starts from the real climate of the month — temperature and rain during active hours — and from the ceiling the traveller tolerates.
It calculates how long the content needs, and what each week removed takes away, stage by stage.
It proposes incompatible variants, not variations. Each carries its promise and its trade-off, written down.
It counts the rhythm: stages, nights, days with no plan, driving days dressed up as sightseeing days.
What it does not claim to know
Ferry timetables, mountain-road opening dates and permit quotas have no worldwide source. The engine detects that a constraint exists, never whether it fits specific dates — and it writes that down rather than filling the gap.
A tool that names its blind spots is a tool whose rest you can check.
Who this is for
Tour operators. Cut the time it takes to build a circuit and catch costly mistakes: someone owns repeat rate, complaints or satisfaction, not only volume.
Itinerary software vendors. Add a consistency check underneath your tool without rebuilding your planning engine: your users compose programmes with no step checking them.
Destination management organisations. Model visitor flows across less-visited territories and test alternative itineraries.
Are you a ground handler, tour operator, tailor-made agency, platform or software maker? For your profession: what the engine adds to your expertise, and what it does not do.
We do not sell trips and will not: we are nobody's competitor on that market.
Write to us: contact form
See it run
Parameters in; variants, stages, measures and warnings out. We show it to you by video call, on a destination of your choice.
Request a demo — tell us who you are and which destination you want to see calculated.
Integrate it by API
Itinerary generation, checking of existing itineraries, rhythm and coverage measures — inside your own tool.
Early access on sign-up. Tell us what you would use it for.
Designed to sit underneath your tool, not replace it: you keep your interface and your booking stack.
Your clients, under your brand. The guides (V1 and V2) can be handed over without the GuardTrails name, with yours, at the price you set. See what you get (public prices, examples) and the business terms (white label, volume discount, confidentiality).