How to handle a tied travel decision without another argument

A tied preference discussion is not a reason to improvise the rules in favour of the organiser’s favourite. Agree the selection method before people know which option benefits. Also distinguish your social agreement from the software’s actual resolution rules.

In this guide: Agree a tie-handling approach up front and explain the actual tool rules separately.

1. Identify what is tied

Two acceptable destinations with equal support are different from a yes/no proposal with equal counts. Limbo proposals are individual ballots; do not describe several of them as one ranked election.

2. Agree a human fallback

The group might choose the lower verified total, run a narrower discussion or defer. Use a criterion everyone accepts in advance. Do not claim the app will automatically apply your custom fallback.

3. Read the result in its context

A Limbo deadline resolution and an everyone-voted resolution can follow different paths. The documented deadline fallback can approve a tie, while threshold and minimum-participation rules also matter. Read the current result and settings; do not reduce this to ‘all ties always pass’.

Worked example: what this looks like

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

Two fictional stays are both acceptable. Before voting, the crew agrees that if both pass, it will choose the lower comparable total, including transport. They tie on headline price but one has an extra cleaning fee. The group uses its agreed comparison after reading the actual ballot results, rather than pretending the app ran a head-to-head tie-break.

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.

If [specific tie situation] happens, we will use [agreed criterion]. This is our group selection process, not a replacement for the ballot’s configured rules. We will confirm the actual outcome and current booking terms before spending.

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 fair tie-break is boring in the best way: it is already known, can be applied consistently and does not punish someone for voting honestly.

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