How to stop the loudest friend from planning the whole holiday

The first confident suggestion can become the default before quieter people have worked out what they want. Giving everyone the same speaking time is useful, but collecting independent preferences before the debate can be even more practical.

In this guide: Collect independent preferences before debating the options together.

1. Collect individual inputs first

Ask each person for one priority, one hard constraint and one thing they can compromise on. Offer a private response route for sensitive details. Do not publish personal ceilings just to prove a point.

2. Use identical proposal formats

Research every shortlisted option to the same depth. Let different people own checks such as rooms, transport and cancellation terms. This stops the organiser’s favourite from being the only option that looks complete.

3. Separate questions from persuasion

Give the crew a question window, then a clear ballot window. Explain sealing if used, and avoid posting hints about the score. After the result, discuss the next action rather than interrogating dissenters.

Worked example: what this looks like

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

In a fictional reunion, the most vocal friend proposes a packed road trip. Independent briefs show that three people want unstructured time and one cannot drive. The group compares the road trip with a two-base version using the same table. The original proposer still has a vote, but no longer controls the framing by default.

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.

Before we discuss options, send [person] your priority, constraint and possible compromise. We’ll prepare comparable proposals and collect questions first. Everyone makes their own choice; nobody needs to defend a personal budget in the group chat.

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.

Do not turn this into a campaign against an enthusiastic organiser. A better process distributes the work and the influence without assigning a villain.

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