Matching names do not prove that someone entered twice. Before the draw, ask each person privately to confirm their own entry. Keep two distinct people under agreed labels; treat a repeated entry as a correction request only after its owner confirms it.
Do not run the draw while an entry's owner remains unclear. Similar wishes are not proof of identity either.
Follow this decision tree
- Give the disputed rows temporary codes, such as A and B, in a private working note.
- If two different people confirm, keep both and agree distinct labels.
- If one person confirms both entries, ask which entry and wish are current.
- If replies conflict or never arrive, leave the issue unresolved and pause preparation for the draw.
Ask through an existing private channel. Do not request identity documents, a birth date or a home address, and do not forward another person's wishes for comparison.
A message you can adapt
> There are matching names on the list. Please confirm your own entry and a label you are happy to use for this exchange. If you submitted twice, tell me which entry and wish should remain current. I will not forward anyone else's entry.
Silence does not confirm a duplicate or consent to participate. Use the invitation templates for the group message, and resolve identity questions privately.
Agree labels and record the decision
For example, two people named Alex may choose “Alex K.” and “Alex M.”, or distinct neutral nicknames. Avoid labels that reveal private circumstances or judge the person.
Keep this small log manually outside Osanta, accessible only to the coordinator:
| Case | Confirmation | Next action |
|---|---|---|
| A and B | Two different people | Agree distinct labels and check both recognise theirs |
| C and D | One person confirms both | Confirm the current entry and check how correction is supported |
| E | No reliable confirmation | Resolve ownership before proceeding |
The log records an agreement; it does not change the service. Remove unnecessary notes from your own external copies once the issue is resolved.
Check how a correction can be made
Do not assume that an existing entry can be deleted or renamed. Check the current interface and consequences first. If the supported route is unclear, stop before allocation and seek help through an available support channel. Never add another entry to balance a duplicate.
This process concerns the stage before the draw. It does not authorise changing pairs already sent. For a group in different cities, consider the separate remote-team arrangements.
Before starting a new exchange
- Every disputed entry has been confirmed privately.
- Different people have agreed distinct labels.
- A repeated entry has one confirmed current version and a verified correction route.
- No unresolved identity issue or publicly shared application remains.
The Osanta game page shows an organiser email as the first step, followed by the name, draw date and budget. The organiser still checks who is behind matching entries separately. If you are preparing a new exchange, finish that check before creating the game.
Organizing a gift exchange?
Create a Secret Santa game online and send the link to participants.
Questions on this topic
Do matching names mean a duplicate?
No. Two different people may share a name. Confirm each entry privately before deciding.
Which labels work for people with the same name?
Use agreed initials or distinct neutral nicknames. Avoid revealing private circumstances.
What if nobody replies?
Leave the issue unresolved and clarify ownership before the draw. Silence proves neither duplication nor participation.
Will a new game fix pairs already sent?
No. Creating another game does not correct an existing allocation. This checklist is for the stage before the draw.