Event duplicate registration detection
The delegate list has the same person twice, or two people sharing one email address, and the final headcount is in doubt.
The short answer
Duplicate detection needs three decisions: which fields count as the same person, what happens automatically when they match, and who resolves a case the rules cannot settle. Most duplicates are not fraud. They are a delegate registering twice after an error, or an assistant registering a boss who also registered.
Treat a match as a question for a person, not as proof. Block only exact repeats; flag the rest for review.
Match rules, from strict to loose
| Rule | Example | Suggested action |
|---|---|---|
| Same email address and same event | Aina registers twice with the same email. | Block the second entry and show the existing booking. |
| Same name and organisation, different email | Aina Rahman at a fictional bank uses a work and a personal address. | Allow, flag for review by the secretariat. |
| Same email, different names | An assistant registers two directors using their own address. | Allow if the system supports it, and require a name per delegate. See group workflow. |
| Same payment reference on two entries | One payment covers two people. | Flag for finance to confirm which entries it covers. |
| Same mobile number, different names | A family business sharing one contact number. | Flag only. Phone numbers are weak identifiers. |
Decisions to make before building rules
- Which field is the primary identifier. Email address is common, but shared mailboxes break it.
- Whether a booker registering others can reuse their own email, and where the delegate's own email goes.
- Whether a cancelled registration releases the identifier so the person can register again.
- Who reviews flagged cases and within what time, for example before the next confirmation batch.
- What the delegate sees when blocked. A clear message with the existing booking reference avoids a support email.
How to resolve a flagged pair
- Compare the two records: name, organisation, email, category, payment and time of entry.
- If they are the same person, keep the record that has payment or confirmation, and mark the other as merged, not deleted, so the history is readable.
- If they are different people, add a note saying so, so the flag is not raised again.
- Tell the delegate which booking stands, using the confirmation message wording.
- Check the headcount again before sending numbers to the caterer or venue.
Cancelled and merged records
A duplicate that is cancelled should still be visible in reports as cancelled, so counts reconcile with payments. Define the status for merged entries in your status definitions and see the cancellation process for refunds.
Worked example · Fictional example
A secretariat finds the same delegate twice a week before the event
Fictional organisation and figures, written to show the level of detail that is useful.
Persatuan Fiktif Pengurus Logistik has 210 registrations for a one-day conference. A review before the caterer deadline shows Hafiz Karim twice: once with a company email and once with a webmail address, same organisation, same category.
Only the company-email entry is paid. The secretariat marks the webmail entry as merged, emails Hafiz to confirm which address he wants for the badge and receipts, and the headcount drops to 209. The rule is added to the sheet: same name and organisation, different email, flag for review.
Use this yourself
Duplicate detection rule sheet and test delegates
Complete the rules, then run the five fictional test cases through your system before opening registration.
- Primary identifier field:
- Exact-match rule and action (block / flag):
- Fuzzy rules (name plus organisation, payment reference, phone) and action:
- Who reviews flagged pairs and by when:
- Does cancelling release the identifier? Yes or no:
- Message shown to a blocked delegate:
- Test 1: Aina Rahman registers twice with the same email. Expected result:
- Test 2: Aina Rahman uses a second email. Expected result:
- Test 3: One assistant registers two directors from one email. Expected result:
- Test 4: Two entries share one payment reference. Expected result:
- Test 5: A cancelled delegate registers again. Expected result:
Handle it in-house, or bring in help?
Your team can usually handle this when
- Registration is a few hundred delegates with one system.
- The platform already blocks exact email repeats.
- One person can review flagged cases each day.
Outside planning help earns its fee when
- Delegates come from several lists, such as members, sponsors and groups, merged into one.
- Registrations arrive by form, email and spreadsheet at the same time.
- Headcount decides a catering or venue commitment and the list has already been disputed.
Need duplicates settled before numbers go to suppliers?
A conference project lead can set the match rules with your secretariat, review flagged pairs on a fixed rhythm, and give you one clean count to send to the caterer and venue. Decisions about merging or cancelling stay with your team.
Questions organisers ask
Should the system delete duplicate registrations?
Mark them as merged or cancelled rather than deleting, so counts and payments still reconcile. How long records are kept is a question for your data protection contact.
Is email a reliable way to detect duplicates?
It catches exact repeats, but misses people using two addresses and mishandles shared mailboxes. Combine it with name and organisation as a review flag.
What if two colleagues share an email address?
Require a separate name per delegate and ask for a delegate-level contact if you need to send individual messages.
Does the platform we use detect duplicates?
Check the platform's own documentation or support. Do not assume a default behaviour; test it with the fictional cases on this page.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.