Ask three people how they plan a road trip and you'll get three different processes. One has the whole route in their head. One has a long note in their phone with addresses copy-pasted from messages. One has an app open with a map view, a list of stops, and a clear sense of which day each one falls on.
None of them is wrong. They're three different planning approaches, each well-suited to a particular kind of trip — and each one has a fairly precise breaking point where it stops being adequate and starts being a problem.
This is a piece about where those breaking points sit, what changes when you cross one, and how to recognise which approach is right for the trip you're actually about to take.
Approach 1 — The mental map
The mental-map planner doesn't write anything down. They know they're driving Bordeaux to San Sebastián for the weekend, they know they'll stop in Biarritz for lunch, they know roughly where they're sleeping the first night. The whole plan lives in working memory, supported by the phone's default maps app for turn-by-turn directions once they're already moving.
When it works: short trips. One or two stops. Familiar territory. A single driver who's done a similar route before and isn't trying to optimise anything in particular. The mental map is the most efficient possible plan because it has zero overhead — no app to open, no list to maintain, no syncing.
Where it breaks: the moment the trip grows past three legs, or the moment a second person becomes responsible for any part of it. The mental map is single-author; it cannot be shared. It also fails silently — you discover on Tuesday morning that you were holding "we'll figure out where to charge near Biarritz" in your head as a future decision rather than a present fact, and now you have to figure it out at the petrol station you stopped at instead.
The mental map is also where most of the over-planning-vs-under-planning friction lives. Because nothing is written down, it's easy to overestimate how much you've actually decided ("we have a plan!") and easy to overestimate how flexible the plan still is ("we can change anything!"). Both turn into the same conversation in the car around hour four of day two.
Approach 2 — The notes app
The notes-app planner writes the trip down. A bullet list of cities. Some addresses. A few hotel confirmations pasted in. Maybe a packing checklist for the car. It lives in iOS Notes, or Google Keep, or a Notion page, or — for a particularly dedicated subset — a shared document with the travel partner.
When it works: trips up to about a week. Several stops. One or two transit days where you actually want to think about the order. The notes app captures decisions so they don't have to be re-made, and shares them so a second person isn't surprised by them. For most people, this is the right tool for most trips, and it's underrated as a planning surface — a clear written list is an honest representation of what you've decided and what you haven't.
Where it breaks: when the trip needs computed information rather than recorded information. A notes-app entry can say "drive from Lyon to Annecy." It cannot say how long that drive is, whether that fits in the day after the stop you added in Vienne, what time you'd arrive at the hotel if you left at 10 a.m., or whether there's an EV charger en route that won't add an hour to the day. Those are calculations, and notes apps don't calculate.
So the notes-app planner ends up doing a kind of constant manual reconciliation: opening the maps app to check the drive time, opening the calendar to make sure no one is double-booked, opening the EV-charger app, opening the hotel confirmation, copying numbers between surfaces in their head. The note becomes a reference, but the planning has scattered across five places, and changes don't propagate. Move one stop and the rest of the plan is silently wrong until you redo the math by hand.
This is also where calendar conflicts tend to emerge late. The notes say "Day 4: drive to Florence." The calendar says nothing. You arrive in Florence and discover your partner had blocked Wednesday afternoon for a video call that was on the shared calendar but not in the trip note.
Approach 3 — A purpose-built planner
The third approach uses a planner that treats the trip — not just the individual stops — as a first-class object. Stops have an order. Each leg between them has a computed distance, a computed driving time, and a computed arrival time that updates whenever the order changes. EV-aware planners surface charging stops along the route as part of the plan, not as a separate worry to handle later. The whole thing syncs to your calendar so the trip and the rest of your life are looking at the same week.
When it works: trips with four or more stops, multi-day shapes, EV trips of any length, and any trip with two or more people who need to look at the same plan from different devices. The planner pays for itself the first time you move a stop and watch the rest of the plan recompute correctly without you having to do anything.
Where it has costs: there is a learning curve, however small, and the planner adds friction to the kind of one-stop weekend that didn't need planning in the first place. Used for the wrong size of trip, a planner feels like overkill — because it is.
This is where Fernweh lands. It treats a trip as an object: an ordered set of stops with computed distances, durations, rough costs, and per-leg arrival times that recompute when you move things around. EV charging stations appear along the route as you plan. The calendar gets one event per drive segment, titled "Drive: Origin → Destination", so the rest of your life can see the trip without anything being copied across by hand. Move a stop and the whole plan adjusts — the order, the times, the events on the calendar — in one motion.
Fernweh is the right tool for the third group of trips. It's the wrong tool for a Saturday drive to a single beach. Both of those things should be true of any planning tool worth using.
Matching the approach to the trip
The breaking points are real, but they aren't absolute. A confident mental-mapper can absolutely take a five-stop trip if they've driven the route ten times. A disciplined notes-app planner who genuinely opens the maps app for every leg can run a complicated week without breaking a sweat. And a planner app that sits unused on your phone is worse than no planner at all — it's just one more thing to ignore.
The unlock is recognising which group your trip is actually in before you start planning it. Two stops and a Saturday — keep it in your head. A week with five stops and one transit day — open Notes. A multi-stop EV trip with charging considerations, two people who need to see it, and a calendar that the rest of your life is already living on — that's the third group, and the third group is what purpose-built planners exist for.
The wrong tool for the right trip is the most expensive planning mistake. Pick the shape that matches the trip, and most of the friction goes away before the trip starts.