Invitations and attendance communication
Communicating with an event waiting list
The event is full, people are still asking to come, and the secretariat needs to say something honest without promising a place.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
A waiting list needs three messages: an acknowledgement that states the person is not yet registered, an offer when a place is released with a clear reply deadline, and a close-out note if no place opens. Agree the order of offers before the first message goes out.
Each message must say what the person can rely on. A place is only theirs once you confirm it in writing, and everything else is information.
Agree the rules before writing the messages
- The order of offers: first come first served, by category, or by decision of a named person.
- How long a person has to accept an offered place, and whether that window shortens as the date nears.
- Whether people on the list may be added by invitation only, or by anyone who asks.
- Who is allowed to release a place: the secretariat, and on whose instruction.
- The date after which the list closes and what you will tell those still on it.
The three messages and what each must say
| Message | When it goes | It must say |
|---|---|---|
| Acknowledgement | As soon as someone joins the list | They are on the waiting list, not registered. Places are offered in the stated order. No payment or travel commitment yet. |
| Offer | When a place is released | The place is offered, how to accept, the reply deadline, and that the offer passes to the next person after it. |
| Close-out | When the list closes or the event is held | No place became available, thanks, and how they will hear about future events. |
Keep the list honest and current
Record every person with date joined, category, contact route and status. When a place is returned through the transfer policy or a cancellation, check the list order before anyone is contacted.
If an offer lapses, move to the next person the same day and record it. A visible log protects the secretariat when someone asks why another person was offered the place.
Handle the awkward cases
- A senior guest asks to jump the list: route the request to the named decision owner and record the outcome.
- Someone is offered a place and accepts after the deadline: apply the rule you wrote, and tell the next person only if the place is actually taken.
- Capacity changes because the venue releases more seats: confirm the change in writing with the venue, then decide whether to open offers to the whole list.
- Contact details on the list are used only for this event unless the person agreed otherwise. Ask your data protection contact what wording to show when someone joins.
Worked example · Fictional example
A full one-day forum
Fictional organisation and figures, for illustration only.
A fictional fintech association closes registration at 220 for a one-day forum and 35 people ask to join a waiting list. It offers places in order of joining, with a 48-hour reply window that shortens to 24 hours in the final fortnight.
When eight places are returned over three weeks, the secretariat offers each in turn, records two lapsed offers and one decline, and sends a close-out note to the remaining people the day after the final reminder.
Use this yourself
Waiting-list message set and log
Copy the three messages and the log columns, then fill in the brackets from your agreed rules.
- Acknowledgement: Thank you for your interest in [event]. You are on the waiting list, which means you are not registered. If a place is released we will offer it in the order [rule]. Please do not make travel arrangements until we confirm in writing.
- Offer: A place is available at [event]. Please reply by [date and time] to accept. If no reply arrives, the place will be offered to the next person.
- Close-out: [Event] is now taking place and no further places became available. Thank you for your interest. [How they will hear about the next event, subject to the data protection contact's wording.]
- Log columns: name, category, date joined, order, offer sent, reply deadline, response, status.
- Rule to confirm: who may release a place and on whose written instruction.
- Question for the data protection contact: what notice and retention period apply to waiting-list details after the event?
Handle it in-house, or bring in help?
Your team can usually handle this when
- The list is short and one person controls releases.
- The order of offers is simple and nobody expects an exception.
- The registration system or a spreadsheet can show status clearly.
Outside planning help earns its fee when
- Releases arrive from several sources, such as cancellations, transfers and venue capacity changes.
- Senior guests and categories compete for the same places.
- The list is long enough that missed deadlines and duplicate offers have become likely.
Want the list run to a clear rule?
A conference project lead can agree the order of offers with your committee, keep the log current as places are returned, and issue each offer and reply on time. You keep the final say on exceptions. Send the current registration position and the rule you intend to use.
Questions organisers ask
Should we tell people their position on the list?
Only if you can keep it accurate. A position that changes without explanation causes more questions than it answers. Stating the order rule is usually enough.
Can people be on the waiting list and registered elsewhere?
Decide this up front. If a person already holds a place for a different session or date, say whether joining the list affects that place.
How many people should we expect to release a place?
Do not assume a figure. Use your own registration history and the attendance scenario planner to test a range, and record where each number came from.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.