From rejected idea to approved plan: a worked voting story

Sometimes the most useful outcome of a no vote is a better proposal. The difference between helpful revision and repeated lobbying is whether the new version addresses the actual problem. This story is fictional, not a customer case study or a claim about conversion rates.

In this guide: Use a labelled fictional example showing how one useful revision changes the proposal.

1. Start with the rejected version

Five friends consider a whole-day excursion with a fictional AUD 180 per-person budget. It uses the only free afternoon and requires everyone to share the same transport. The group does not support it.

2. Find the constraint behind the answer

The organiser asks what made the option unsuitable. The issue is not lack of interest: two people need a slower day and one has a tighter activity budget. They are not asked to disclose personal finances.

3. Create a genuinely different option

The revised idea is a shorter local outing with a fictional AUD 70 ceiling, optional participation and an independent return route. Its cost and availability still need checking. The organiser states what changed and requests a fresh decision on that exact scope.

Worked example: what this looks like

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

In the simulated outcome, four people choose the shorter outing and one stays behind, meeting the group for dinner. No one is charged for the option they skipped. The organiser verifies the quote before booking and keeps the shared evening unchanged. Success means the plan fits the crew; it does not require turning every no into a yes.

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.

Version two changes [duration], [cost boundary] and [participation]. The original concern was [issue]. The revised option is [details], subject to [checks]. Please decide on this version only. If it still does not work, we will keep the free time instead.

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 lesson is to revise the offer, not reinterpret the people. Keep the old decision as context and record the new terms clearly.

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