Itinerary planner
Build a plan you can actually walk
Eight answers, no account. The engine is deterministic — the same answers always produce the same plan — and it never schedules a stop while its place is closed.
What happens when you press the button
Four stages, all of them arithmetic. Candidates are scored against your interests and the importance data; the scored pool is clustered geographically so a single day never zigzags across the city; each cluster is ordered into a walking sequence; and only then is the sequence scheduled against real opening hours and your day window.
Nothing is generated by a language model at the moment you press the button, which is why the same nine answers always give the same plan, and why a plan can be checked rather than trusted. Two rules hold without exception: no stop is scheduled while its place is closed, and a day never exceeds its own window once visit time, travel time and breaks are added up.
Before you start
Why is tempo a multiplier and not a number of stops?
Because a stop is not a unit of time. Tempo stretches or compresses the visit duration at each place, and the number of stops is then whatever fits in the day — an output, not something you set.
What happens on a place’s closing day?
It is not scheduled. The engine reads recorded opening hours per date, and a stop is never placed while its place is shut. Where no hours are recorded at all, the place is scheduled conservatively inside the middle of the day and marked as unverified.
What if the city has fewer places than my days need?
You get shorter days rather than filler. The planner would rather hand you three good days than pad five days with places that are not worth the walk.
Do I need an account?
No. The plan is built from the answers on this form and nothing is stored against you. Your itinerary lives in its own URL, which you can bookmark or send to someone.
Popular right now
Every city catalogued so far — pick one to prefill a starting point.