A group voted yes—but is everyone ready to book?

A yes vote can mean ‘I like that plan’. It does not automatically mean ‘charge my card now’. Keep the decision, supplier availability and payment instruction separate so a successful ballot does not become an unexpected financial commitment.

In this guide: Separate approval of a proposal from deposits, confirmed availability and permission to pay.

1. Read the scope of approval

Check what the proposal actually covered: dates, product, travellers, price ceiling and refund conditions. If any of those are missing, resolve them before treating the result as booking-ready.

2. Recheck the supplier

Confirm the exact room, fare or ticket still exists at the expected price and terms. An approved screenshot can be stale. Record the current offer and any change from the version people voted on.

3. Get a clear booking instruction

Name the booker, payer, collection arrangement and deadline. Ask each affected person to confirm their share and commitment. Store confirmations where the crew can find them; do not confuse an expense record with a money transfer.

Worked example: what this looks like

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

Six people approve a fictional AUD 1,800 stay. Before booking, the organiser discovers the quoted rate covered only four adults. The corrected rate is higher. They do not interpret the six yes votes as permission for the increase. They share the corrected occupancy and total, obtain a new agreement, then collect the agreed amounts.

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.

The proposal is approved. Before booking, please confirm your place and [amount + currency] share under [cancellation terms]. Current supplier quote: [link + checked time]. [Name] will book only after [condition]. If terms change, we will come back to the group.

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.

The handoff from vote to booking should be explicit enough that a different organiser could follow it. Enthusiasm is not a payment method.

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