Search "road trip planner" and you'll get turn-by-turn navigation apps, generic travel diaries, spreadsheet templates, and a handful of tools that actually mean something specific by the phrase. They all call themselves the same thing. They're not doing the same job.
This is a piece about what the category actually requires — not a ranking, not a pitch, just an honest look at where the label gets stretched too far and where it means something real.
What a road trip planner is NOT
A turn-by-turn navigation app is not a planner. It's excellent at the thing it does — get you from point A to point B, minute by minute, recalculating when you miss a turn. But it has no concept of a trip. Ask it what day three looks like and there's no day three; there's only the next turn. Close it and reopen it a week later and it remembers nothing about where you were headed.
A generic travel diary is not a planner. It's a place to write down what you did or intend to do — notes, photos, a loose itinerary in prose. It's genuinely useful for capturing a trip's memory. It doesn't compute anything. It doesn't know that moving day two's hotel three hours down the road changes day three's drive time.
A spreadsheet is not quite a planner either, though it gets closer. A well-built spreadsheet can hold stops, dates, and rough distances, and a diligent person can keep the totals updated by hand. But the moment a stop moves, every downstream number is stale until someone manually fixes it. The spreadsheet doesn't know a trip is a sequence — it just knows it's a table.
None of these are bad tools. They're just not planners in the sense this piece means. The category requires something more specific.
What the category actually requires
A road trip planner treats the trip itself as the object, not a byproduct of a route calculation or a list of addresses. That distinction sounds abstract, but it has concrete consequences:
Per-leg timing, not just total timing. A real planner tells you the drive time and distance for each leg — Bordeaux to Biarritz is different information than "the whole trip is 9 hours." Per-leg timing is what lets you actually reason about a day: is this too much driving before lunch? Does the third stop still make sense if the second one runs long?
Costs that come with the plan, not bolted on afterward. Fuel or charging cost estimates per leg — not a total you calculate separately in your head at the end.
Recalculation when the plan changes. This is the sharpest dividing line. If you move a stop, add one, or remove one, does everything downstream update itself, or do you have to redo the math? Fernweh recalculates the route, timing, and — where the trip syncs to Apple Calendar — the calendar events themselves when a trip changes: stops added, removed, reordered, or the route recalculated, the corresponding events update or delete to match the new state. That's the behavior a spreadsheet can't give you without someone doing the update by hand.
If a tool doesn't do at least these three things — per-leg timing, cost awareness, and automatic recalculation — it's something else. Useful, maybe. Just not a planner in the full sense.
What separates good-enough from good
Meeting the bar above gets you a functional planner. A few things separate good-enough from good, and they tend to matter more the longer or more complicated the trip is.
EV awareness. For an EV driver, charging stops aren't optional extras layered onto the route — they're load-bearing parts of the plan. A planner that treats charging as a first-class part of the day (not a separate app, not a mental side-calculation) is doing meaningfully more work than one that assumes every stop is a gas station or nothing.
Calendar sync that's actually sync, not export. A one-time export to a calendar app is a snapshot; it goes stale the moment the trip changes. Real sync means the calendar reflects the current state of the plan — automatically, without a manual re-export step.
Collaboration. Road trips are frequently planned by more than one person — a couple, a family, a group of friends splitting research duties. A planner that only one person can edit forces everyone else back into a group chat or a shared note just to stay in sync, which defeats the purpose of having a planner at all. Fernweh trips can be shared with others via iCloud sync, so more than one person can see and shape the same plan.
None of these are exotic requirements. They're just the difference between a tool that holds information and a tool that actively keeps that information correct as the trip evolves.
Where the line sits today
The road trip planning category has gone through a few shapes. Paper maps and printed itineraries used to be the whole toolkit — genuinely planner-shaped in the sense that they held the whole trip, but static; nothing recalculated itself. General-purpose mapping apps arrived and solved point-to-point navigation extremely well, which is a different problem than trip planning and gets conflated with it constantly, mostly because navigation is the more visible, more frequently used feature. Along the way, note-taking and spreadsheet workflows filled the gap for anyone whose trip was more than a single point-to-point drive, because nothing purpose-built existed yet.
What's changed recently is narrower: tools that treat the trip — not the route, not a single leg — as the thing being planned, with per-leg timing and costs that update automatically as the plan changes. That's a small, specific capability, and it's the one this piece has been describing throughout.
Fernweh is one implementation of that idea — a multi-stop trip planner built around per-leg timing, EV-aware charging stops, and Apple Calendar sync that updates when the trip does. It's not the whole category and it doesn't claim to be. But if you're evaluating whether something calls itself a "road trip planner" honestly, the three questions from this piece are a reasonable filter: does it know your trip has legs, does it know what each one costs, and does it keep up when you change your mind.