Rolling deadlines vs one “book by Friday” deadline

A stream of new ideas needs a different rhythm from a group booking everything on one day. The deadline style should support that rhythm instead of making late proposals impossible to evaluate or early proposals wait unnecessarily.

In this guide: Compare ongoing proposals with a coordinated booking decision.

1. Use a rolling window for ongoing proposals

Each new proposal has its own response period. This suits a longer planning phase where outings arrive gradually. The organiser still needs to prevent a last-minute idea from colliding with a supplier cutoff.

2. Use a shared date for coordinated decisions

A fixed deadline can work when linked bookings need a common decision point. Late proposals then have less time to be read, so set a separate submission cutoff.

3. Keep booking tasks after the vote

Whichever style you choose, reserve time to confirm prices, collect commitments and book. The last voting minute should not also be the supplier’s last payment minute.

Worked example: what this looks like

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

One fictional crew uses rolling windows while collecting restaurants months ahead. Later, it switches its planning process to a shared decision date for accommodation and transport. It asks for proposals early enough to be read, and leaves a booking buffer after the deadline. The change is explained rather than sprung on the crew.

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.

For this phase we are using [rolling windows / a shared deadline] because [reason]. Submit proposals by [time]. Responses are due [how deadline works]. Supplier checks and booking commitments happen after the decision, before [actual cutoff].

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.

Check the trip owner’s settings and the deadline shown on each ballot. A message saying ‘Friday’ is not evidence that every proposal has the intended deadline.

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