Paid delegates are missing from the check-in list
The doors are open, a queue is forming, and several delegates say they have paid but the desk cannot find their names.
The short answer
Separate the delegate in front of you from the data problem behind the desk. Agree one person who may authorise admission on proof of payment, and give the desk a script and a place to log each case.
Fix the cause later with finance, once the queue is moving. Reconcile the list against the payment records; do not edit it in a hurry at the desk.
What is known and what is not
Fictional scenario: the Persatuan Fiktif Juruukur Hartanah annual conference opens its registration desk and 14 delegates with payment confirmations are not on the printed list.
In the first ten minutes you know very little. Write down which facts are confirmed and which are guesses.
- Known: the delegate's name, the confirmation they hold, the time they arrived.
- Unknown: whether the payment was actually received, whether the name was entered differently, whether the list was exported before late registrations.
- Unknown: whether the 14 share a cause, for example one payment batch, one group booking or one cut-off time.
- Do not assume fraud or carelessness. Most mismatches are timing, spelling or group-booking issues.
Who has authority to decide
Name the decision owners before the event, and confirm them again at the desk briefing.
If nobody is named, the secretariat head or event owner decides, and tells the desk lead in writing, even if by message.
- Admission on proof of payment: the event owner or a named delegate of theirs.
- Confirming that money was received: finance or whoever holds the payment platform login.
- Changes to the master list: one person only, so the list stays a single version.
- Anything involving a refund or a dispute: the person who handles refunds for the organiser.
Realistic options and what each costs
More than one option can run at once. Choose the least disruptive one that the decision owner is comfortable defending later.
| Option | What it involves | Consequence to weigh |
|---|---|---|
| Admit on proof, reconcile later | Desk checks the confirmation, logs name and reference, issues a badge, finance confirms after the session starts. | Fast queue; some risk the payment is not found later, which the organiser then resolves by agreement. |
| Hold at a help desk | Delegates without a match wait at a separate point while finance checks payment. | Main queue stays clear; the help desk can become its own queue and needs a staffed person with access to payment records. |
| Admit to the room, badge later | Delegates enter for the opening and complete registration at a quieter time. | Fewer people waiting; badge and attendance records are incomplete until completed. |
| Delay the start slightly | Event owner agrees a short delay with the chair and the venue contact. | Protects the opening session; affects speakers, catering and anything timed after. |
| Scale down check-in | Move to name-only check-in for the rest of the queue, record details afterwards. | Speeds the desk; reduces data captured on the day. |
Communications: who says what to whom
Keep messages short and factual. One voice speaks to delegates; one voice briefs the desk.
- To desk staff: "If a name is missing, ask for the payment confirmation, write name and reference on the exception sheet, then follow the option the event owner has chosen. Do not edit the list."
- To the delegate: "Thank you for your patience. Your name has not turned up yet. Please show your confirmation and we will log it so it can be checked."
- To finance: "Please check these references against the payment platform and reply with matched, not found or unclear."
- To the chair or venue contact: "Check-in is running behind for a known reason. We will confirm whether the start time needs to move."
Follow-up and preventing a repeat
After the event, treat the exception sheet as the evidence trail.
- Match every exception to a payment record and note the cause: export timing, name spelling, group booking or payment outside the platform.
- Ask the registration platform owner when the list was last exported and how late changes are included.
- Add a final export time and a named reconciler to the run sheet for the next event.
- Plan desk numbers and help-desk capacity with the check-in throughput estimator, treating its result as a simplified estimate only.
- Record the decisions in a decision log so the next team can see why they were made.
Worked example · Fictional example
14 names missing at 8:15
Fictional organisation and figures, illustrative only.
The event owner chooses admit on proof for delegates with a payment email, and a help desk for the four who have none. The desk logs 14 names with references on one sheet.
By mid-morning finance matches 11 to a payment batch received after the list export, finds two spelling differences, and one unclear case that the owner resolves with the delegate directly.
Use this yourself
Missing-delegate desk card
Print this for the desk lead. Fill the blanks before doors open.
- Who may authorise admission on proof of payment (name and mobile):
- Who confirms payment received (name and how to reach them):
- Chosen option for unmatched delegates:
- Exception sheet columns: name, organisation, reference, proof seen, time, decision, initials
- Master list editor (one person):
- Script for the delegate and for the queue:
- When the list was last exported (date and time):
- Escalate to the event owner when more than this many cases are open:
- After the event: reconcile, record cause, report to the event owner
Handle it in-house, or bring in help?
Your team can usually handle this when
- The list is short and finance can check payments during the day.
- One named person can decide admissions.
- The cause is clear, for example a single late registration batch.
Outside planning help earns its fee when
- Several systems or teams hold registration and payment data and nobody owns the reconciliation.
- The queue is growing while decisions wait for people who are not on site.
- The organiser wants the desk, finance and registration platform coordinated before the next event.
Need someone to coordinate the recovery?
A conference project lead can take over temporary coordination of the agreed recovery tasks: setting the admission authority, running the exception sheet with your team, and reconciling the list with finance afterwards. Your committee keeps every decision about admission and refunds.
Questions organisers ask
Should we turn paid delegates away until we find their payment?
That is a decision for the event owner, weighed against the queue and the risk of a payment not being found later. Many organisers choose to log proof and reconcile afterwards. Agree this before the event.
Can the desk add names to the list directly?
Better that one named person edits the list and the desk uses an exception sheet. Several edits at once create competing versions.
What do we tell delegates in the queue?
State that some names are being checked and that a help point is open. Avoid giving a waiting time unless the event owner has confirmed one.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.