September 18, 2026 · Limbo Crew
What should your travel group decide first?
Order the decisions: spending limits, dates, destination, stay, then activities. Practical steps and a worked example.

Photo: Annie Spratt anniespratt · CC0. Full-frame photograph; cover thumbnails may crop for layout.
Choosing activities first feels productive because activities are fun. But a carefully researched restaurant cannot rescue a trip whose dates exclude two people. Make decisions in the order that reduces the most uncertainty for the least wasted work.
In this guide: Order the decisions: spending limits, dates, destination, stay, then activities.
1. Start with attendance boundaries
Collect available dates, maximum time away and spending limits. Separate hard constraints from nice-to-haves. A person can prefer a longer trip while only being able to attend a shorter one.
2. Resolve the expensive dependencies
Choose the destination and travel window before detailed accommodation comparisons. Then settle the room arrangement and transport approach. Do not treat a provisional flight search as proof of affordable fares for the eventual dates.
3. Leave flexible decisions flexible
Once the important bookings fit, choose a few shared activities. Keep cafés, wandering and optional outings out of the critical path. A shared plan should distinguish ‘decided’, ‘proposed’ and ‘still open’ rather than displaying everything with equal certainty.
Worked example: what this looks like
Fictional scenario—not a real customer story or executed AI result.
Four friends plan a five-night reunion. They first discover that only one date window works, then that one destination requires an extra overnight journey. Removing it saves a hotel comparison round. They settle a two-bedroom arrangement before discussing tours. The restaurant shortlist comes last, after the group knows the neighbourhood and arrival time.

Photo: Vyacheslav Argenberg · CC BY 4.0. Full-frame photograph; cover thumbnails may crop for layout.
Make the decision bookable, not merely popular
A proposal needs a stable meaning from the moment people read it to the moment someone acts on it. Keep the dates, people, total-cost basis and important conditions together. If those facts change, explain the new version instead of silently editing the commitment beneath an earlier response.
Do not confuse three separate stages: an idea is worth considering, the group supports a specific proposal, and the affected people have authorised the booking and their contribution. A ballot helps with the middle stage. It does not verify supplier availability or move money.
Before closing the discussion, write the next action as a sentence with an owner: “Jordan will confirm the exact room arrangement by Thursday, then ask the crew to approve the current booking total.” That is more useful than “sorted”.
A message or brief you can copy
Replace the bracketed fields with your own details. Read the complete text before sending it; copying it here does not send a message or perform an action.
Let’s decide in this order: [dates and attendance], [budget boundary], [destination], [rooms and travel], then [shared activities]. Current decision: [item]. We are not reopening [settled item] unless [material change]. Owner of the next check: [name].
Before you call it settled
- The proposal means the same thing to everyone reading it.
- Hard constraints are handled before preferences are compared.
- Each person chooses their own response; silence is not a payment instruction.
- The actual ballot result and settings are understood.
- A named person owns the next supplier or booking check.
A dependency order is not a rigid rule. If a rare event is the reason for the trip, its date becomes the starting constraint. Write that exception down so the rest of the sequence follows it.
Put the decision somewhere useful
Keep the proposal, current terms and next action with the trip in Limbo. Use the relevant help guide below for the actual workflow; the examples above do not create a booking or determine your configured ballot outcome.
Sources and further reading
Product guidance was reviewed against the local Limbo help content and voting implementation on 19 September 2026. The suggested group process is separate from the actual configured ballot rules.