The Itinerary Is a Constraint Problem
Every itinerary that falls apart on day two was already infeasible on day zero. Here is how to see the math hiding inside an ordinary trip plan.
Field Notes · Route & Itinerary Science
Travelers don't buy penance. They buy better trips, and on the ground the lower-carbon trip is usually the better one.

The worst way to sell a lower-carbon trip is to make the traveler feel bad about the other one. A red bar next to a green bar, a footprint icon, a line about doing your part. It reads as a lecture at the exact moment someone is trying to look forward to something.
People don’t buy penance. They buy a better trip. And in a surprising number of multi-day itineraries, the version with lower ground emissions is also the one with fewer hotel changes, fewer hours in a vehicle and more time on foot. That’s the version guests tend to rate higher, too. Design for that overlap, say it plainly, and the lecture becomes unnecessary.
This note tears down one itinerary in three configurations, introduces a metric you can compute from data you already have, and sets out the rules we use for presenting the result.
Start by being honest about scope. If your guests fly in from another continent, that flight will likely outweigh everything an operator controls on the ground. Pretending a van swap offsets a long-haul flight is how sustainability claims lose credibility.
What you do control is real, though:
Empty legs are where operators tend to find surprises. A one-way transfer often implies a one-way empty return. A schedule that strands a driver at the far end of a day creates miles nobody planned for.
You don’t need a carbon-accounting platform to start. Compute vehicle-miles per guest, including empty legs, from your own logistics data. Within a vehicle class, it moves in step with ground emissions. It’s easy to explain to a guide, a guest or an owner. And it’s already sitting in your transfer schedules.
When you need an emissions figure, convert vehicle-miles using the factors your chosen reporting method specifies for each vehicle class. Write the method and its version next to the number. A number without a method is just a mood.
The trip: six days and five nights for eight guests, a loop through the high desert of northern New Mexico that starts and ends in Santa Fe. The highlights are a canyon hike, a hot-springs afternoon, a scenic road through mountain villages, a small arts town and a river day. All three versions include every highlight.
Version A, “the hopper.” Two rental SUVs, self-driven, four hotels in five nights.
Version B, “two bases.” One 12-seat van with a driver-guide. Three nights at one base, two at another, with day trips radiating out.
Version C, “two bases, one car-free day.” As B, but one day trip is replaced by a walking and e-bike day from the base, with a shared shuttle for one leg.
Vans burn more per mile than SUVs, so raw vehicle-miles can’t be compared across versions. For this illustration we’ve assumed the van’s per-mile emissions are 1.5 times an SUV’s and expressed everything in SUV-equivalent miles. Use your own method’s factors in practice; the shape of the result rarely changes.
| Measure | A: Hopper | B: Two bases | C: Car-free day |
|---|---|---|---|
| Vehicle-miles, including empty legs | 1,360 (2 SUVs × 680) | 550 van (490 + 60 empty) | 440 van (380 + 60 empty) |
| SUV-equivalent miles | 1,360 | 825 | 660 |
| Per guest | 170 | 103 | 83 |
| Change versus A | — | −39% | −51% |
| Hours in a vehicle per guest | 19 | 13 | 10.5 |
| Mornings spent packing | 3 | 1 | 1 |
| Guests who drive | 2 | 0 | 0 |
| Ground cost index | 100 | 131 | 124 |
Read the bottom half of the table before the top. Version A is cheapest, but two of the eight guests spend about nineteen hours each driving unfamiliar mountain roads. A self-drive trip quietly turns two guests into staff. Version B costs more and includes a guide who knows when the canyon trail falls into shade. Version C cuts the most miles and gives the group a slow day in the middle, which on a six-day trip is a feature in its own right.
The lower-carbon versions won here because they were better trips. That won’t always be true, but it’s true far more often than the guilt-trip framing suggests.
The teardown counted 60 empty van miles. Across a whole operation, empty legs are often the cheapest emissions to remove, because guests never notice them gone.
Take an operator running 30 one-way airport transfers a month, each with a 60-mile empty return. That’s 1,800 empty miles a month that no guest rode. Three scheduling moves usually cut that by a third to a half:
Pairing half of those airport returns saves 900 miles a month, and the fuel and driver hours with them. It’s also the rare sustainability change your finance lead will propose before you do.
If the two-bases version is the trip you would recommend anyway, show it first. Don’t bury it behind a green toggle marked “eco option” with a surcharge attached. Defaults are where most choices get made.
“One unpack, two bases, an extra afternoon at the hot springs.” Then, in smaller type: “about 40% fewer ground-transport emissions than a self-drive loop.” The experience sells; the number confirms.
When the lower-carbon option costs more time or money, say so. When it can’t reach a remote trailhead, say that too. And never call a trip carbon-neutral without an auditable basis for the claim.
Inside a constraint-based router, carbon works best as a limit: find the best trip within this many vehicle-miles per guest. That keeps the optimization focused on the experience, with carbon as a boundary, rather than producing a “greenest” plan nobody wants to take.
You can’t change how guests reach your region, but you can make the journey worth more. Suggest an extra night rather than an extra stop. Stretch a five-night trip to seven on the same flights and the flight’s share of each night falls by more than a quarter, while the ground itinerary gains slack it badly needed. Fewer, longer stays lower per-day emissions and almost always improve the trip.
When the trade-off is real, let the traveler see it. A proposal that sets the hopper and the two-bases version next to each other, with hours driving, hotel moves and cost on one line each, does more persuading than any badge. Proposal tools that generate both configurations from the same brief make this a default rather than extra work for the advisor.
Low-carbon routing has limits, and naming them is part of being trusted.
| Instead of | Try |
|---|---|
| “Reduce your footprint by choosing…” | “Stay put three nights and explore from one base.” |
| A bare tonnage figure with no context | “About 40% fewer ground-transport emissions than a self-drive loop, mostly because you unpack once.” |
| “Offset your trip at checkout.” | Keep any offset offer separate from reduction claims, and explain exactly what it is. |
| “Eco option (+ surcharge)” | “Guided van, two bases: less driving, one unpack.” |
Five numbers, tracked by itinerary and by season:
The last one is the number that ends debates. If guests rate two-bases trips higher, and in our experience they usually do, then the business case and the carbon case are the same case.
Pull your three best-selling itineraries. For each one, compute vehicle-miles per guest including empty legs, count the hotel moves, and add up the hours guests spend in a vehicle. Then sketch a two-bases version and run the same numbers.
If the redesign holds up, make it the default and write the description around the experience. The low-carbon routing use case shows how that comparison can be generated inside every proposal, and operators running multi-day outdoor and adventure trips tend to find the biggest wins first. At Nova Adventure we have rarely heard a guest complain about unpacking once instead of three times.
Questions
Start with vehicle-miles per guest by vehicle class, including empty legs when vehicles reposition without guests. Convert those miles using the emission factors your chosen reporting method specifies, and record the method and its version next to the result. Report flights to and from the destination separately, since the operator rarely controls them.
Not by default. In many multi-day trips, consolidating vehicles and using fewer bases is the better trip, and it can be priced as the standard product. Where a lower-carbon option genuinely costs more, say so plainly and explain what the traveler gets for it.
Keep reading
Every itinerary that falls apart on day two was already infeasible on day zero. Here is how to see the math hiding inside an ordinary trip plan.
Accessibility isn't a property of a venue. It is a property of a particular person's day, and that day can be designed.
Out here, a plan that looks right on a map can be wrong by early afternoon. What the high desert has taught us about modeling context.
Bring the problem this article describes to a 45-minute discovery call. We will tell you honestly whether AI is the right tool for it yet.