How Outrouted works
How route planning works in Outrouted
Outrouted treats the route as a planning problem. Where the stops are, how they connect, how much time the trip has and the constraints you set all go in before anything is drawn on the map.
Updated 24 Aug 2026about 6 minutes
On this page
1.What you give it
The planner takes one document of preferences. Nothing else about you is part of it.
- Countries, and optionally the specific cities inside them
- Dates, or a length in days if you are still flexible
- Who is going: adults, children, and the children's ages
- A budget for the whole party, and a currency
- Pace, and how you are willing to move between places
- What you are there for, and anything you must have
- A free-text note, if there is something the fields cannot say
2.Two of those inputs do more than they look
Naming cities narrows the trip. List four and say that is all you want, and the planner uses those four and nothing else. It does not treat them as a starting point and add what it thinks you missed.
The note is the only part of the request somebody else wrote, so it is handled differently from the rest. It is cleaned up, then placed in the prompt inside a block marked as the traveller's own words. The instructions around that block say its constraints are binding and that it carries no instructions of its own. A note can tell the planner that somebody in the party cannot manage stairs. It cannot tell the planner to ignore your budget.
3.The steps it actually takes
Planning is a job. You ask for it, the server answers straight away with a job, and the screen polls that job until it succeeds or fails. That is why planning survives a closed laptop and a bad connection: the work is not tied to the request that started it.
The phases the screen reports are the steps the runner takes, in order:
- Reading the catalogue, to assemble the pool of places the plan may use
- Searching flights for the corridors the trip might need
- Searching stays for the places it might use
- Asking the model to choose places, order and nights
- Pricing what comes back as up to three route summaries. Picking one starts a second job, the build, which writes it up, chooses where to sleep and saves it as your trip
4.Asking twice is free
A job is identified by the question it asks: your preferences, the kind of plan, when the trip last changed, and the model. Ask the same question twice and you join the job already running instead of starting a second one, so a double click costs nothing and a refresh loses nothing.
Reading a job also claims it if nobody has, which is what makes the whole arrangement work in an environment that refuses background work.
5.Which places a plan may use
Before the model is asked anything, a pool of candidate places is assembled from the countries and cities you chose. One function answers that question for the entire system: the flight searches use it, the stay searches use it, the prompt uses it, and the prompt's own tests read the same list. There is no second opinion about what is available.
Anything the model returns that is not in that pool is dropped. This checks the place against the candidate pool, not whether rooms can be booked for your dates.
6.What the model decides, and what it cannot
The model proposes places, order and nights per stop. Code checks the total nights and calculates dates, distances, travel estimates and costs. The model does not supply those calculated figures.
Its answer is checked before you see it. Place ids outside the pool are dropped. A night split that does not add up to the length of the trip is re-spread by the product's own code. Money comes from one function, and the model is not part of it.
If the model is slow, unreachable or answers with something unusable, a deterministic planner produces the route instead, through the same interface. You still get a trip, and it is a real one.
7.How the travel between stops is decided
Consecutive stops become a leg. A leg is a flight when there is sea between the two stops, when it runs beyond about 620 miles, or when it crosses a border that is more than a short drive away. A short crossing, like Porto to Vigo, stays a drive. Where you asked for trains or buses, a hop short enough to ride is one of those. Turn flights off and every leg on the same land is driven or ridden. Nobody chooses that per trip; it falls out of the geography and what you said you would use.
A flight needs airports at both ends, so the catalogue resolves the nearest airport selling scheduled seats to each destination, offline, from a generated list. Letting each provider guess its own airport is how two of them end up quoting two different trips.
Driving distance is the straight line between two stops with a detour factor applied, and driving time comes from an average speed. That is a pacing estimate and it is good enough to tell a comfortable day from a punishing one. It is not a road route, and Outrouted does not pretend it is.
8.What happens when you change the route
Edits save immediately and nothing is re-planned between them. Re-planning is the expensive call in this product, and a route rebuilt after every change would be slow and would keep moving things you were in the middle of deciding. The budget still recomputes on every read, because that arithmetic is local and free.
When you ask for the route to be made whole again, the plan stays with what you changed. Stops you left alone are not touched, and the order changes only if you moved, added or removed a stop. The nights add up to the length of the trip again, spread over the stops that are free to move. A stay you pinned or booked is not one of those, and nights you set are kept if they fit. If they cannot all fit, the plan stops and says which stays clash, instead of overriding them. And every stop has somewhere to sleep, unless a pinned stay already covers it.
Removing a stop only marks it, and the next plan clears it out. Until then, putting it back is just a change of mind.
9.What it does not consider
This is where the tool stops. None of the following is part of the route:
- Opening hours, closing days, or seasonal closures at a specific place. A planned visit on a dated day says so and links to a map search, and that is all
- Real road routing, traffic, roadworks or mountain passes
- Live seat availability on a particular flight
- Train and bus timetables, which only give a leg a distance and an assumed speed, and ferries, which are not modelled as legs at all
- Visa and entry rules, which the preparation list links to and never states
- Anything about you other than the preferences you typed