Registration systems and data structure
Event registration waitlist rules
Registration is full, people keep asking to be added, and nobody has agreed who gets a place when someone cancels.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
A waitlist needs five written rules: who may join, how people are ordered, how an offered place is communicated, how long the offer stays open, and what happens when it lapses. Agree them before registration closes, not after the first cancellation.
Delegates accept a waitlist when the rules are visible and applied the same way to everyone. They object when order or timing looks arbitrary.
The five rules
| Rule | Decision to make | Common options |
|---|---|---|
| Who may join | Which categories and when joining closes. | All categories, or members first. Close the list on a stated date. |
| Order | How position is set. | Time of joining; or time within each category pool. Say which. |
| Offer | How a place is offered and who sends it. | Automatic message from the system, or a manual message from the secretariat. |
| Offer window | How long the delegate has to accept or pay. | A fixed period chosen by the organiser. Shorten it as the event nears. |
| Lapse | What happens when the window ends. | Offer passes to the next person; the first person is told and may rejoin at the end. |
Waitlists and capacity pools
If you hold back places for speakers or guests, a released hold-back place goes to the waitlist only if you have said so in your capacity controls. Decide whether a member waiting on a member pool can take a general place, or the reverse.
Check how your platform handles waitlist offers and whether it promotes people automatically. Use its documentation or support, and test it with fictional delegates rather than assuming.
What delegates should be told
- That joining the waitlist is not a booking and no place is held.
- Their position or order rule, if you choose to share it.
- How long an offer will stay open once made, and how it will reach them.
- That no payment is due until a place is offered.
- The last date on which waitlist offers will be made.
Running the list in the last two weeks
- Review cancellations each working day and release places in list order.
- Contact the next person by the route promised on the form.
- Log the time each offer was sent and the response.
- When a window lapses, move to the next person and note the result.
- After the last offer date, close the list and tell everyone remaining the outcome.
Worked example · Fictional example
A forum releases places after a cancellation
Fictional organisation and figures, written to show the level of detail that is useful.
Persatuan Fiktif Pegawai Kewangan Koperasi has 150 places, all taken, and 14 people on the waitlist. The committee set a 48-hour offer window and a stated closing date for offers.
Three registrants cancel on one morning. The secretariat offers places to the first three on the list, and one does not respond in 48 hours. The fourth person is offered that place and the delegate who lapsed is told they have moved to the end of the list.
Use this yourself
Waitlist rule sheet
Fill this in before registration reaches capacity and publish the delegate-facing lines on the form.
- Who may join (categories) and closing date for joining:
- Order rule (time of joining overall, or per pool):
- How offers are sent and by whom:
- Offer window length, and any shorter window near the event:
- What happens when an offer lapses:
- Do released speaker or guest places go to the waitlist?
- Last date for waitlist offers:
- Wording for the form: not a booking, no payment until offered, how long offers last:
- Offer log columns: name, date and time sent, response, outcome:
Handle it in-house, or bring in help?
Your team can usually handle this when
- The waitlist is short and one person watches cancellations daily.
- Your platform's waitlist behaviour is tested and understood.
- Offers are made by a person, not automatically.
Outside planning help earns its fee when
- Several category pools or sessions have separate waitlists.
- Cancellations arrive from many channels and nobody owns the list.
- Demand is high enough that fairness complaints are likely.
Need someone to run the waitlist in the final weeks?
A conference project lead can agree the waitlist rules with the committee, make the offers on the rhythm you set, and keep the log current, so that places are released in a consistent order. Decisions about exceptions stay with your committee.
Questions organisers ask
Should we take payment when someone joins the waitlist?
Your finance contact should decide. Many organisers take no payment until a place is offered, because a refund process is otherwise needed for everyone not offered a place.
How long should an offer stay open?
Choose a period you can administer, state it on the form and shorten it near the event. The right length depends on how quickly your delegates usually respond.
Can the waitlist be ordered by category instead of time?
Yes, if you say so up front. Be clear whether pools are independent, so a member does not see a non-member offered a place first without explanation.
How does this link to expected attendance?
Use the attendance scenario planner to see how cancellations and no-shows could change the number of places you may need to release.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.