What to do when your favourite trip idea gets rejected

A rejected proposal can feel like a rejection of the person who researched it. Usually it is more useful to ask which part failed: cost, timing, effort or interest. Change the problem, not the pressure on the voters.

In this guide: Rework the proposal, explain the trade-off or make it an optional outing.

1. Ask one focused follow-up

Invite practical feedback without demanding public explanations from every no voter. Ask whether the option is fundamentally unwanted or whether one detail makes it unworkable.

2. Change a material part of the offer

Reduce the price, move the timing, shorten the outing or offer a genuinely optional version. A new title on the same expensive plan is not a meaningful revision.

3. Respect the second answer

Explain what changed and let people decide again if a fresh decision is appropriate. If it still fails, leave it off the shared itinerary. An optional subgroup must not leave others paying for transport or costs they did not choose.

Worked example: what this looks like

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

A crew rejects a whole-day private tour. The organiser learns that the problem is losing the only free afternoon, not the destination. A half-day version with a lower cost and an independent return option gets support. Another traveller still skips it and joins dinner. The revised plan works because it changes the trade-off.

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.

Thanks for considering [idea]. The main concern seems to be [issue]. I’ve changed [specific detail], keeping [remaining constraint] clear. Is this a genuinely better option, or should we leave it out? No pressure to change your answer.

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.

Save the research for another trip if needed. The time spent investigating an idea does not create an obligation for friends to buy 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

• 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