Individual and shared constraints
Each traveler's pace, interests, dietary and access needs sit alongside the group's fixed points: arrival times, the one dinner everyone attends, the budget.
Use cases · Group travel
Sixteen people, sixteen ideas of a good day, two vans and one dinner reservation. Nova models each traveler's constraints alongside the group's shared ones, then drafts plans that split, rejoin and stay fair — for the organizer to approve.

A group trip isn’t one itinerary. It’s a set of quiet negotiations: between the person who wants to hike at dawn and the one who doesn’t do mornings, between the budget-minded household and the one that wants the good restaurant, between the grandparent who tires by two and the teenager who comes alive at nine.
Most group plans settle those negotiations by accident. The organizer — often unpaid, often exhausted — goes with the loudest voice or the latest message. Preferences live in a group chat. Dietary needs live in someone’s memory. Nobody checks whether everyone got something they wanted.
The logistics multiply, too. Sixteen people means two vans rather than one, a table for sixteen that few restaurants will hold, and arrival times scattered across a day. When one flight is late, the whole first evening shifts.
The answer isn’t a better spreadsheet. It’s treating the group as what it is — a set of individual constraints plus a few shared ones — and planning for all of them at once.
Each traveler's pace, interests, dietary and access needs sit alongside the group's fixed points: arrival times, the one dinner everyone attends, the budget.
Across the trip, every traveler should get at least one thing they ranked highly. The engine tracks it and flags anyone who has been outvoted every day.
When interests diverge, the plan forks into subgroups with their own routes and rejoins at a shared point, with travel times checked so nobody waits forty minutes.
The day is paced for the people who need it most, with optional add-ons for those who want more.
Vehicle seats, table sizes, guide ratios and room blocks are hard limits. A plan that needs a third van says so.
Every trade-off is written down with its reason, so the organizer can explain why the morning went the way it did.
How it works
A hypothetical four-day reunion in northern New Mexico: grandparents in their eighties, three households of adults, four younger kids and two teenagers. One organizer, who would also like to enjoy the trip.
Each household gets a short form by text or email: pace, must-dos, deal-breakers, dietary needs, mobility, budget comfort. Most answer within two days; the organizer fills in the rest.
The draft shows the tension plainly. Four adults want a long ridge hike, the grandparents want gentle mornings, the teenagers want anything involving water, and one cousin is vegetarian.
Morning: the ridge hike for the four, a gallery walk with plenty of seating for the grandparents and younger kids, a guided river float for the teens. Everyone rejoins for a long lunch at one table for sixteen.
Route Engine assigns the two vans so both subgroups reach lunch within ten minutes of each other, and flags that the river pickup needs the larger vehicle.
Every traveler gets at least one top-ranked activity across the four days; the grandparents get two. The organizer sees it at a glance and approves.
Afternoon thunderstorms are forecast. Concierge proposes moving the outdoor block to the morning and holding an indoor option. The organizer approves with one reply, and each household is told only what changed for them.
The plan shows every person's picks and every compromise. I spend my calls with the organizer talking about the trip, instead of refereeing it.
Questions
A handful of questions per household, sent through whatever channel they already use. Anything unanswered falls back to sensible defaults the organizer can see and change.
The organizer, or your trip designer. The system drafts options and shows the trade-offs; a person chooses. Nobody in the group receives a plan the organizer hasn't approved.
Yes. Budgets can be set per traveler, per household or for the whole group, and shared costs — the vans, the group dinner — are split the way you've agreed.
Yes, though the modeling shifts: at that size you're planning cohorts and waves more than individuals. The same constraints — capacity, timing, fairness, access — still apply.
Dietary, health and access details are visible only to the people planning the trip, never to the rest of the group. Shared plans show what changed, not why for any individual.
Related
The one with conflicting requests, tight transfers and a dinner for thirty. We'll show you how the plan would fork, rejoin and stay fair.