How to Remove Duplicate Entries Before a Draw
Normalize and review repeated entries without accidentally merging different people.
Published · Reviewed
How to Remove Duplicate Entries Before a Draw
Duplicate cleanup should follow an identity rule chosen before the draw. Exact display-text matching is simple, but it can merge different people who share a name or fail to merge one person using different spellings. Stable entry IDs are safer when they are available.
Recommended process
- Choose the identity key stated in the promotion or activity rules.
- Normalize harmless differences such as surrounding spaces.
- Review collisions instead of deleting them automatically.
- Save the cleaned count and apply the same rule to every entry.
Worked example
Two rows named “Alex Kim” should not automatically become one if they have different entry IDs. Conversely, “Entry-104 ” and “Entry-104” can be treated as the same ID after trimming the trailing space.
What to check before using the result
- Do not infer identity from a name alone.
- Document whether multiple entries are permitted.
- Retain only the minimum data needed for review.
How the random step is handled
Random Picker Tools uses window.crypto.getRandomValues() for browser-based selection. Integer results use rejection sampling to avoid modulo bias, and complete list orders use a Fisher–Yates shuffle. This addresses the software selection step; the organizer still controls eligibility, duplicate rules, consent, accessibility and any legal requirements.
Privacy note
Normal picking and shuffling happen in the browser. Use initials or non-sensitive identifiers when possible, avoid storing unnecessary source data, and create a share link only when temporary server storage is appropriate for the people represented in the list.