The group itinerary people actually follow
There are two ways to ruin a group trip with an itinerary. The first is the spreadsheet with 9:00–9:45 slots, which dies the moment one person oversleeps and turns its owner into a cop. The second is no itinerary at all, which converts every meal into a forty-minute standoff in a hotel lobby.
The itineraries that work — the ones groups actually follow — share one structure. We call it the anchor method.
Anchors: one or two committed plans a day
An anchor is a plan with a time, a place, and a commitment: the 10am snorkeling boat, the 8pm dinner reservation. One daytime anchor and one dinner is a full day for a group — groups move at the speed of their slowest breakfast. Everything between anchors stays deliberately open.
What makes an anchor an anchor:
- A real time and place. "Beach at some point" is a mood; "Praia da Marinha, meet at 11" is a plan.
- A reservation where one exists — attached to the plan, with the confirmation code, visible to everyone. A booking that lives in one person's inbox is a single point of failure with a sleep schedule.
- An RSVP. More on this, because it's the load-bearing part.
RSVPs make skipping normal — and visible
The unspoken assumption that everyone does everything is what breaks group trips. Someone's tired, someone's broke this month, someone would simply rather sit by the pool — all fine, if the plan knows. Put an RSVP on every anchor. Two things change immediately:
- Skipping becomes a tap instead of a confession, so people do it honestly instead of flaking silently.
- Head-counts become facts: the restaurant gets the right number, the boat isn't half-paid-for, and expenses split among the people who were actually in (which is exactly how cost-splitting should work).
Structure the free time without scheduling it
Between anchors, don't schedule — stock the pond. Keep the group's pile of voted-on ideas nearby (the taco place someone found, the viewpoint, the weird museum), each with a location. When the afternoon opens up, the group picks from a shortlist it already agreed sounded fun, on a map that shows what's close. That's a two-minute decision instead of a lobby standoff — and it's why Outtie keeps ideas, plans and places on one shared map.
Day one and the last day are special
- Arrival day has one job: everyone lands, everyone reaches the lodging, everyone eats. People arrive on different flights at different energies — schedule nothing but dinner, and make it walkable. (Watching everyone's flights converge in one place beats a thread of screenshots.)
- The last day is for slack. No anchor that can't be abandoned for a flight. Checkout logistics eat more of it than anyone plans for.
A shape that works (7 days, as a template)
- Day 1 — land. Anchor: dinner near the lodging.
- Days 2–3 — the big stuff. The two things this destination is for, booked ahead, plus dinners.
- Day 4 — nothing. On purpose. The group splits, wanders, naps. Best day of the trip, every time.
- Days 5–6 — the voted ideas. Whatever rose to the top of the pile, promoted to anchors.
- Day 7 — slack, pack, fly.
This is how Outtie's board works. Plans belong to days, every plan carries an RSVP and its reservation, ideas get voted up and promoted onto the board, and it all sits on the one map the whole crew shares.
FAQ
How many activities per day?
One or two anchors. Groups move slower than individuals; hour-by-hour schedules break by 11am on day one.
Does everyone have to do everything?
No — and the itinerary should make that visible with RSVPs, so skipping is honest and head-counts are real.
Where should reservations live?
Attached to the plan they belong to, visible to the whole group — never only in one person's inbox.