How to run a 20-minute group-trip decision meeting

A decision meeting should resolve a small set of prepared questions, not become a live search session with six people watching one person scroll. Twenty minutes works when the research is shared first and the next action is obvious.

In this guide: Use a pre-shared shortlist, unresolved questions and a clear record of the outcome.

1. Prepare a one-page brief

Send the viable shortlist, comparable totals and unresolved questions in advance. Tell attendees what will be decided and what is outside scope. Ask for missing requirements before the meeting.

2. Use a simple agenda

Spend the first three minutes restating constraints, seven on factual questions, five on the choice and five on recording the outcome and owner. These are suggested allocations, not a requirement to rush an unresolved commitment.

3. End with a record, not a vague mood

Write the chosen option, cost boundary, unresolved check, owner and deadline. If the group cannot decide, name the missing fact and the next decision time. Use ballots for people who need to respond asynchronously.

Worked example: what this looks like

Fictional scenario—not a real customer story or executed AI result.

A fictional crew enters with two suitable stays. During the factual-question slot it discovers a missing cleaning fee. The researcher checks it after the call; nobody books on a guess. The meeting still succeeds because it identifies one blocker, gives it an owner and sets the next response deadline.

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.

Agenda for [trip]: constraints, questions on [two options], decision if ready, then owners and deadlines. Please read [brief] first. We will not book while a material cost or suitability question remains unresolved. Notes will go in [shared location].

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.

If research is still incomplete, call the session a planning discussion rather than forcing a decision to justify the calendar slot.

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

• Limbo: current voting guidance

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.

Keep planning

• Build an AI trip plan you can actually use
• Group-trip planning guide