How to Document a Random Winner Selection
Keep a timestamped, privacy-conscious record of settings and result positions.
Published · Reviewed
How to Document a Random Winner Selection
A useful record contains the promotion identifier, draw time, final eligible count, duplicate rule, tool and material settings, ordered winners and alternates, and the person responsible for verification. It should not retain the entire participant list longer than necessary.
Recommended process
- Record the frozen list count and rule version.
- Export the timestamped ordered result.
- Note eligibility checks and any alternate substitution.
- Delete or restrict source data according to the retention policy.
Worked example
The record states: 407 eligible IDs, exact-ID deduplication, one winner and three alternates, drawn at 18:12 UTC. It stores the selected IDs and verification outcome but not every participant’s email address.
What to check before using the result
- A screenshot alone may omit important settings.
- Use UTC or include the time zone.
- Restrict records containing personal identifiers.
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.