Weather windows as constraints
Route Engine reads forecast data against each day's exposure: how long the group is above treeline, and when it needs to be down. Exposed segments move to the morning, and the plan shows the margin.
Solutions · Outdoor & adventure travel
Plan for the mountain you'll actually get
Permits, monsoon afternoons, thin air and a group that walks at the speed of its slowest member. Nova models them all as constraints — and leaves the call with your guides, where it belongs.
Timeline
Five days in the mountains above Santa Fe, in July
A composite guided hiking trip in northern New Mexico — the kind we think about a lot, because it starts not far from our office.
- Six weeks out
The roster fills
Eleven guests, eight of them from sea level. One mentions a knee that “does fine on the flat.” The backcountry permit caps group size, and a twelfth guest is waiting on a cancellation.
- Day 1, 6:00 PM
Altitude arrives first
Santa Fe sits at roughly 7,000 feet. By dinner two guests have headaches and a third has decided she's fine. The guide quietly rewrites tomorrow in a notebook.
- Day 2, 5:15 AM
The weather window narrows
Thunderstorm cells are forecast over the high ridges from early afternoon — an ordinary monsoon-season pattern. To be safely off the exposed ridge, the group has to turn around by late morning.
- Day 2, 10:40 AM
Pacing meets reality
The group is well behind plan. The guide has to weigh the summit against the turnaround time with two bars of signal and nobody to check numbers with.
- Day 3, 7:30 AM
Plan B ripples outward
Swapping in the lower canyon route means moving the van shuttle, the picnic drop and the river outfitter's headcount for day four — all by text, from a trailhead.
- Day 6
The office reconstructs the week
For the trip log and the guide debrief, someone pieces together what changed, and why, from notebook photos and a dozen message threads.
What changes with Nova
None of this replaces judgment on the trail. It puts better information in front of the person exercising it, earlier.
Pacing and altitude, budgeted
Each guest's pace and acclimatization are modeled as an energy budget. A sea-level group gets a gentler first day by default, and turnaround times are recalculated for the pace you actually observe.
Permits and capacity as hard limits
Group-size caps, permit dates, campsite allocations and guide-to-guest ratios are hard constraints, so a roster change can't quietly break the trip.
Risk notes guides can trust
Every fallback arrives with its reasons — exposure, distance from the trailhead, what it costs to switch — written for the guide to accept, edit or reject.
The guide decides. Always.
We build for operations where a wrong call can hurt someone, so the rule is simple: Nova drafts, people decide. Route Engine proposes; your lead guide approves anything that changes where a group walks, sleeps or turns around. The day's plan and its fallbacks reach the guide's phone before the group leaves coverage, and every decision is logged with the reason given.
- No change to a route, campsite or turnaround time without a named human approval
- Fallbacks prepared the night before, not improvised at the trailhead
- A clean record for trip logs, debriefs and next season's planning
Recommended modules and services
- ModuleRoute EngineConstraint-based routing with pacing budgets, weather exposure and permit limits built in.
- ModuleConciergePre-trip briefings and in-trip updates for guests by SMS or WhatsApp, with hand-off to your office.
- ModuleBooking FlowShuttles, outfitters, lodges and permit paperwork requested, confirmed and reconciled.
- ModuleSignalsDemand and cancellation forecasts by season, so you know which departures to add or merge.
- ServiceDisruption Response AutomationWeather and closure playbooks written with your senior guides and wired into each trip.
- ServiceCustom Travel Software DevelopmentGuide-facing tools and trip logs shaped around how your field team actually works.
How it works
A sample workflow: a summit day with a monsoon forecast
- 01
The night before
8:00 PMRoute Engine re-runs tomorrow against the latest forecast and the pace the group showed on day one. Two options come back: the summit with an earlier start, or the lower loop.
- 02
The brief
5:00 AMThe lead guide gets both options on their phone, with turnaround times, exposure windows and what each costs to switch.
- 03
The decision
The guide picks the summit with a 10:30 turnaround — or the loop — and approves. That's the only action needed.
- 04
Everything downstream
Booking Flow moves the shuttle pickup, Concierge tells guests the start time and what to pack, and the office sees the change without a phone call.
- 05
On the trail
If the group turns back, the guide logs it in one line, and the afternoon swaps to the sheltered alternative already held.
- 06
After the trip
Forecasts, decisions and reasons feed the debrief, and next season's pacing assumptions.
It doesn't tell me when to turn around. It tells me, at five in the morning, exactly what turning around at eleven would cost us. That's the conversation I used to have with myself in the dark.
Further reading
- Case studyCase study: re-planning on alpine walking toursHut closures, mountain weather and the proposal workflow at a family-run operator in the Alps.
- Field noteHigh-desert lessons on contextWhat northern New Mexico teaches about altitude, light, distance and planning.
- Field notePacing: the hidden variableEnergy budgets, and why the right plan for one group is the wrong plan for another.
Questions
Frequently asked questions
Does Nova make safety decisions?
No. It prepares information and drafts options; your guides and operations leads make every safety call. That line doesn't move.
Where does the weather data come from?
From weather data feeds suited to your terrain, chosen with you during discovery. You set the thresholds: what counts as storm risk on an exposed ridge, and how much margin a turnaround needs.
What happens when the group is out of signal?
The day's plan, fallbacks and turnaround times reach the guide before the group leaves coverage. Updates sync when signal returns; nothing waits on a connection to be safe.
Can it handle permits, quotas and guide ratios?
Yes, as hard constraints. If a roster change would exceed a group-size cap or break a guide-to-guest ratio, the plan says so before anyone books.
Do you understand this kind of terrain?
We're based in Santa Fe, between the high desert and the southern Rockies, and our team spends field days on trails like the ones your guests walk. But your guides know your terrain best; part of the work is turning what they know into constraints the system respects.
Related
Keep exploring
- PlatformRoute EngineConstraint-based itinerary routing that weighs opening windows, travel time by mode, pacing budgets, accessibility, weather and capacity, and explains each day.
- ServicesDisruption Response AutomationPlaybooks for weather, closures and delays that assess impact, draft a re-plan and prepare every message, then wait for a person to approve it.
- WorkAlpine walking-tour operatorHow a family-run walking-tour operator in the Alps cut median proposal time from 3.4 hours to 52 minutes and re-planned closed stages before dinner.
- Field Notes · Route & Itinerary SciencePacing: The Hidden Variable in Itinerary PersonalizationPersonalization usually means picking the right activities. Pacing, what each day costs a traveler, matters as much. An energy-budget model, with numbers.
- Field Notes · Route & Itinerary ScienceHigh-Desert Lessons: What Northern New Mexico Teaches About ContextAltitude, monsoon afternoons, long distances, hard light and community calendars: field notes from Santa Fe on the context that itinerary software misses.
Bring us a trip that went sideways
A storm, a slow group, a permit snag. Walk us through it and we'll show you how the plan and its fallbacks would have looked the night before.