Registration systems and data structure
Designing an event registration cancellation process
A delegate writes to cancel three days before the event, and the secretariat realises there is no agreed answer on seats, refunds or the waitlist.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
A cancellation process answers five questions in advance: who may cancel, by when, what happens to the seat, what happens to the money, and who is told.
Decide the money rule with finance and the committee before registration opens, then build the rest of the process around it so staff apply a decision rather than invent one.
Separate the cancellation from its consequences
A cancellation is one event with several effects: the seat returns to stock, a waitlisted person may be offered it, an invoice or payment needs a decision, and suppliers' numbers may change.
List the effects first. Each effect has a different owner, and the process works when each owner knows what they receive and when.
Questions the policy must answer
- Who may cancel: the registrant, the paying organisation, or both?
- Is substituting a colleague preferred over cancelling, and is it free? See change requests.
- What are the dated stages, for example full, partial or no refund, and who approved them?
- Who decides exceptions such as illness or a work emergency, and is the decision recorded?
- What happens to a seat in a capacity-limited session? See capacity controls.
- Does the next person on the waitlist receive an offer automatically or after a secretariat check?
Refund and tax questions go to the right person
The refund percentages, credit notes and any tax treatment are decisions for your finance team and, where relevant, your accountant. This page does not suggest what they should be.
What the secretariat can prepare is a clear question list and the registration data finance needs to answer it, such as the payment date, payer name and ticket category.
The cancellation sequence
- Receive the request in the agreed channel and log it with date and reference.
- Confirm the requester is allowed to cancel, using the registrant or payer rule.
- Offer substitution if your policy allows it and the cut-off has not passed.
- Mark the registration with the correct status and release the seat.
- Pass the payment question to finance with the dates and amounts from the record.
- Tell the waitlist owner, badge owner and caterer contact, then confirm to the delegate in writing.
Wording of the confirmation message
State what has been cancelled, the date it was recorded, and what will happen about payment and who will contact them. Do not promise a refund amount unless the policy and finance have confirmed it.
Keep a line that tells the delegate what to do if they believe the date or amount is wrong.
Worked example · Fictional example
A late cancellation for a two-day members' congress
Fictional organisation and figures, for illustration only.
A fictional trade association has 320 registered delegates and a policy with three dated stages, approved by its council. Delegate B cancels in the middle stage, citing a family matter, and the registration was paid by the employer.
The secretariat logs the request, offers substitution, which the employer declines, marks the record cancelled, and sends finance the payer name and payment date. The council treasurer decides the exception under the policy. The seat goes to the first person on the waitlist, whose offer expires after 48 hours in this example, and the caterer receives the updated numbers at the next agreed cut-off.
Use this yourself
Cancellation policy sheet
Fill one row per stage. Take the money column to finance for completion; do not publish it until they confirm.
| Item | Your decision | Owner |
|---|---|---|
| Who may cancel (registrant, payer, both) | Secretariat | |
| Substitution allowed, until when | Secretariat | |
| Dated stages and their consequence for payment | Finance and council | |
| Exception route and who records it | Chair or treasurer | |
| Seat release and waitlist offer rule | Capacity owner | |
| Suppliers to inform and cut-off dates | Project owner | |
| Confirmation message approved by | Secretariat head |
Handle it in-house, or bring in help?
Your team can usually handle this when
- A single policy already exists and finance has approved it.
- Cancellations are rare and handled by one person.
- There is no waitlist or capacity-limited session.
Outside planning help earns its fee when
- Cancellations arrive through several channels and nobody holds a full list.
- Payments, credit notes and the waitlist interact and need one agreed sequence.
- Committee and finance disagree about stages or exceptions and a neutral coordinator is needed.
Need the cancellation process agreed and running?
A conference project lead can take your committee and finance through the policy questions, write the sequence for the secretariat, and coordinate the notices to suppliers and the waitlist during the registration period. The refund rules themselves stay with your finance team.
Questions organisers ask
Should cancellations be accepted by phone?
Accept them only through a channel that produces a written record, or write one immediately after the call. Otherwise the date and the requester are disputed later.
Who decides refunds?
Your finance team and the committee decide the policy. The secretariat applies it and passes exceptions to the named decision-maker.
Should we offer substitution instead of cancellation?
Many organisers do, because the seat stays filled and the supplier numbers do not change. Decide whether it is free, who verifies the replacement and the last date it is accepted.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.