GuardTrails
Travel itineraries, calculated, not guessed.
The starting point
An itinerary is usually judged on what it contains. We judge it on its shape: how many stages, how many nights each, where the empty days fall, and what the trip promises without delivering.
That shape is measurable. Measured on trips of two to four weeks sold by different operators, it is surprisingly constant: a different bed every day and a half, everywhere, across four continents and nine years.
Three ways to plan a long trip
An operator takes everything off your hands, including control: the rhythm follows the catalogue, and every change is another round on the quotation. An AI assistant answers what you ask it — you still have to know what to ask, and its answer commits no one.
We do not do their job better. We do something neither of them has as its job: a method, and a format that shows it.
What we bring
A method. You choose what decides a long trip: the balance of culture and nature, the pace of your days, how far you want to walk, the temperature beyond which your day stops. The engine calculates the rest — how many nights per stage, within bounds that avoid a different bed every night, and where to place days with no plan.
A format. Several variants that do not resemble each other, each with its strengths and its choices explained, its rhythm counted, and the share of the territory it really covers.
A traceable calculation. The language model writes; the engine calculates and verifies. Climate comes from the month's records, distances from the real road, consistency from checks that leave a trace. Every figure has a source, and our errors are published.
The ground. Field observations on our own trips, research into how the industry builds its itineraries, and an engine built and tested on more than forty simulated circuits. And all the way to the ground: the route, the stages, the activities and the hikes, day by day, and an app to follow the trip on the spot.
Independence. We do not sell trips, book nothing, and take no commission on accommodation or flights.
What we do not do
We do not replace an operator for those who want to delegate everything.
We do not verify the world in real time. Ferry timetables, mountain-road opening dates and permit quotas have no worldwide source: we detect that a constraint exists, never whether it fits your dates. When that is the case, the page says so.
And we publish no destination whose data says it would be poor for the period requested.
The method, in six terms
Temperature ceiling · register saturation · day with no plan · base-change tolerance · stage or lodging · rain hours
The limits, in writing
The thresholds — a day and a half of consecutive rest, a ceiling of twenty-four degrees — are parameters of the engine, set per traveller, not rules: yours may sit elsewhere, and the engine takes it into account.
Also in the studies: How many hotels for a road trip · Is your itinerary too packed? Four counts · What is your heat ceiling? · Rain days or rain hours · Six campgrounds, six nights