Handling event registration change requests
A delegate has asked to swap a colleague in, correct a name or move to another day, and nobody is sure who may say yes.
The short answer
Sort change requests into three groups before registration opens: changes the delegate makes alone, changes the secretariat approves, and changes that need a decision from the committee or finance.
Write the group, the approver and the response time for each type of change, then log every request so the answer is the same whoever picks up the inbox.
Why change requests need their own rule set
Cancellations and confirmations have their own pages. A change request keeps the registration alive but alters something that other work depends on: a name on a badge, a seat in a workshop, an invoice, a dietary note.
Each of those changes touches a different person. The badge printer, the caterer and finance all hold a copy of the old facts, so a change that is accepted in the system but not passed on creates a mismatch at the desk.
The three approval groups
| Type of change | Who decides | What else must be told |
|---|---|---|
| Correct a spelling in a name or job title | Delegate through the confirmation link, or secretariat on request | Badge list, certificate list |
| Update a dietary or access note | Delegate; secretariat checks the note is readable | Caterer and venue contact, before the agreed cut-off |
| Substitute another person for the same ticket | Secretariat, using the substitution rule | Badge list, invoice contact, member verification if the rate depends on membership |
| Move between sessions or days | Secretariat if seats remain; otherwise the capacity owner | Session counts, waitlist if one exists |
| Change ticket category or rate | Finance or committee | Invoice or credit note, receipt |
| Change the company name or tax invoice details after issue | Finance | Registration record and accounting file |
Decide the cut-off dates first
Every change type needs a last date after which the answer becomes no, or becomes a request for a named person to approve. Work backwards from the earliest supplier cut-off: badge printing, caterer numbers, certificate lists.
Publish the dates in the confirmation message so delegates know them. A cut-off the delegate has never seen is hard to enforce politely.
A simple sequence for each request
- Log the request with the date, registration reference, requester and what they want changed.
- Classify it using the table above. If it does not fit, mark it as needing a decision and name who decides.
- Check the effect: seats, price, badge, invoice, supplier counts.
- Apply the change in one place, the registration record, then notify the people who hold a copy.
- Send the delegate a short confirmation stating exactly what changed and what did not.
Where the registration system helps and where it does not
A system can let delegates edit some fields themselves and can keep an audit trail. It rarely knows your substitution rule or your supplier cut-offs.
Test each rule with fictional delegates before launch, using the registration testing checklist, and review which fields should be editable with the field minimiser tool.
Worked example · Fictional example
A substitution request ten days before a one-day forum
Fictional organisation and figures, for illustration only.
Persatuan Fiktif Pengurusan Aset receives an email: a member firm wants to replace Delegate A with a colleague. The registration is a member-rate ticket, and the rule says substitutions are allowed within the same firm until seven days before the event.
The secretariat logs the request, confirms the colleague is on the firm's member list, updates the record, and informs the badge list owner and the finance contact. The reply to the firm says the badge will carry the new name and the invoice name is unchanged. Three days later a second request asks to change the invoice name, which the log routes to finance.
Use this yourself
Registration change-request log
Copy these columns into a shared sheet. One row per request, never deleted.
- Request date and registration reference:
- Requester (delegate, colleague, finance contact):
- Change type (correction / note / substitution / move / category / invoice):
- Approval group and approver named:
- Cut-off date for this type of change:
- Effect checked (seats, price, badge, invoice, supplier counts):
- People told (badge, caterer, finance, venue):
- Decision and date sent to the delegate:
- Open issue or exception, with owner:
Handle it in-house, or bring in help?
Your team can usually handle this when
- Registrations are a few hundred and one person owns the inbox.
- Your system already lets delegates correct their own details.
- Rates do not depend on verification that takes several days.
Outside planning help earns its fee when
- Several people answer delegates and give different answers.
- Substitutions, member rates and invoices interact and finance disputes the outcomes.
- Supplier cut-offs sit with different parties and nobody holds the full picture.
Want someone to run the change rules for you?
A conference project lead can agree the approval groups and cut-offs with your committee, test them with sample delegates and keep the change log current in the weeks before the event. The decisions stay with your organisation; the follow-through is what the lead takes on.
Questions organisers ask
Should delegates be able to edit their own registration?
Allow it for low-risk fields such as spelling, dietary notes and contact details until a stated date. Keep ticket category, price and invoice details with the secretariat or finance.
How long should we take to answer a change request?
Choose a response time you can keep, state it in the confirmation message, and give one named person the job of watching the inbox during busy weeks.
What if a change request arrives after the cut-off?
Treat it as an exception, record who approved it and what it cost, and tell the affected suppliers. Over time the exceptions show whether the cut-off was set at the right date.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.