Step 1
Write the draw rule before collecting the final list
Record who is eligible, the entry deadline, the number and order of prizes, and whether one person may win more than once. Also define what makes a result invalid: an ineligible entrant, an unverifiable identity, a missed response deadline, or an operator error are different situations and may need different remedies.
Treat legal requirements, permits, taxes, disclosures, and geographic restrictions as organizer responsibilities. A wheel can select from the list it receives, but it does not establish that the promotion itself is lawful or that an entrant satisfied the published terms.
Check before continuing
- Name the entry cutoff and source of truth.
- State whether duplicate entries and repeat winners are allowed.
- Set the verification and response deadlines.
- Publish the redraw and alternate-winner policy.
Step 2
Freeze, normalize, and inspect the eligible entries
Export a final list from the registration system and keep an untouched copy. In a working copy, remove headers and blank rows, then resolve spelling variants, duplicate account identifiers, refunded orders, staff exclusions, and late submissions according to the written rule. Do not silently merge two people merely because their displayed names match.
Use an opaque ticket number or public alias on the projected wheel when a full name, email address, or order number would disclose unnecessary information. Maintain the identity lookup separately and restrict it to the people who verify winners.
Step 3
Configure prizes, replacement, and alternates explicitly
For one winner, a single draw from the frozen list is straightforward. For several unique winners, use elimination or a draw-without-replacement workflow so an accepted winner leaves the active pool. If repeat wins are permitted, keep normal mode and document that choice. Weights should be used only when the rules intentionally grant different entry counts and the imported values have been checked.
Decide whether alternates are drawn immediately from the remaining pool or only after a winner fails verification. Label alternates in order and do not present them as confirmed winners. When prizes differ, draw them in the published order so the operator cannot choose which result receives which prize afterward.
Run it in this order
- Load the frozen, public-facing entry labels.
- Confirm the active count against the source list.
- Choose replacement, no-replacement, and weight settings from the rules.
- Name the prize or draw stage before selecting.
Step 4
Rehearse the presentation with non-production entries
Test the projector or stream crop, text size, keyboard controls, result dialog, sound, and reduced-motion behavior before the event. Rehearse with unmistakably fake entries so a test spin cannot be confused with the official draw. Confirm that the host and verifier can both see the final label and active-entry count.
Prepare a plain fallback such as a second browser, a printed ticket container, or an offline copy of the approved list. A technical failure should trigger the predeclared fallback, not an improvised change to eligibility or a series of exploratory spins on the official list.
Step 5
Conduct each official draw once, then verify eligibility
At the start, identify the list version, entry count, prize, and applicable replacement rule. Make the official action unambiguous, announce the displayed identifier, and pause the sequence while a second person checks it against the protected identity record. If the winner is valid, accept the result before moving to the next prize.
If a result is invalid under the written terms, record the result and reason before redrawing. Undo is appropriate for correcting an accidental interface action; it should not erase an inconvenient but valid winner. If the rules did not cover an edge case, stop and have the organizer resolve it consistently rather than disguising the policy decision as another random draw.
Step 6
Retain a useful record without overstating the audit trail
Save the approved input file, rules version, date and time, operator and witness names, results in order, verification outcomes, and any redraw reasons. A CSV result export can support that record, but ordinary browser history and editable files are not tamper-evident. For regulated or high-value draws, obtain an independent process appropriate to the jurisdiction and stakes.
Remove public aliases and identity lookup files according to the event's retention policy. Workspace data persists in the browser until cleared, and exported files remain wherever the operator stores or shares them. Reset a shared event computer when retaining entrant data there is no longer necessary.
Use the right surface
Tools mentioned in this guide
Common questions
Questions about raffle draw checklist
Should I remove duplicate names before a raffle?
Only according to the published entry rule. A duplicate may be a valid additional ticket, a spelling variant, or an accidental duplicate. Reconcile entries by a stable identifier instead of deleting matching display names automatically.
How do I prevent one person from winning twice?
Use a unique identifier for eligibility, draw without replacement or use elimination mode, and verify the person behind each public label before accepting the next winner.
When is a redraw appropriate?
Redraw only for a reason defined in the rules, such as failed eligibility or an expired response deadline. Record the original result and reason; do not redraw merely because the outcome is unpopular.
Does a browser raffle wheel certify a contest as fair or legal?
No. It can make a selection from the supplied entries using its documented method, but the organizer remains responsible for lawful terms, accurate eligibility, operation, verification, and any independent oversight.
What should a raffle result record include?
Keep the frozen input version, rules, count, prize order, timestamps, accepted results, redraw reasons, operator, and witness. Protect the mapping between public aliases and personal information.