Write the rule before accepting requests
Define capacity, how places are allocated and the closing date. Joining a waiting list does not mean a confirmed booking: explain this in the form and the message sent. Describe the criteria actually used without promising an order you cannot maintain. Request only information needed for contact and organisation, then check who receives the replies.
Track distinct states
Distinguish request received, waiting, place offered, confirmed and withdrawn. For each change record the date, owner and next action. When a place opens, check actual capacity before contacting the next person. Do not change a state merely because a message was sent: no reply is not confirmation. Keep the tracker in a space with appropriate access.
Offer a place with a clear deadline
State the event, offered place, reply deadline and method for accepting or declining. Explain what happens without a reply according to the announced rule. Avoid exposing other participants’ addresses. If someone responds after the deadline, examine current availability before confirming their booking. The tracker should make it possible to understand why a place was reassigned.
Prepare for postponement or cancellation
Separate cancellation, postponement and a venue change. Correct the reference page and messages still scheduled, then contact affected people through the planned channel. Do not promise a refund or replacement place without a confirmed process. Provide a contact for individual questions. Finally close the list and decide how data will be handled according to the organisation’s actual need rather than leaving unnecessary collection open.
A fictional case to apply the process
Fictional example: a free workshop has ten places. Someone withdraws; the team offers the next place with an announced deadline and treats it as occupied only after confirmation. A room change triggers a message to registered participants and an update to the reference page.
Template to adapt
Copy this outline into your working document without passwords or unnecessary personal data.
Event and capacity: Allocation rule: Request state: Place actually available: Offer date: Reply deadline and method: Confirmation received: Change notice: Owner and closure:
Your check before use
0 / 4
Useful questions
Can the waiting list be published?
Prefer individual contact. A public list of names or addresses is unnecessary to announce that an event is full.
Should the list be kept after the event?
Decide what remains necessary and what obligations apply; do not automatically keep contact details for an unplanned new use.
Related steps
Sources and scope
Sources consulted on 10 October 2026 for the points specified below. The method, template and example are editorial proposals; they are not service tests.
- W3C WAI — Writing for Web Accessibility — Structured headings, descriptive links and clear instructions. The proposed process is an editorial method.