Prizes and coupon numbers
Set up the prizes and the code format. Coupon numbers are generated for you rather than typed into a spreadsheet the night before.
Prize draws on stage
Winners are picked and recorded before the screen is ever told to spin. A projector that reloads mid-animation, a laptop that dies, a network that drops at the worst possible second — none of them can change or lose who won.
Prize 2 of 4
Grand Prize Draw
Why a draw is harder than it looks
A lucky draw is the one moment of your event where a software failure is watched by every person in the room. It has to be fair, it has to be seen to be fair, and it has to survive the room's network.
The winner is decided and written down first; the reel on the big screen is theatre over a settled outcome. A screen that reloads mid-spin rejoins a draw that already has an answer.
The pick is uniform and without replacement, drawn from the operating system's cryptographic randomness rather than a naive shuffle — and the database independently refuses to record the same entry winning twice.
The MC, the AV operator or a sponsor's host runs the draw. None of them have an organizer account, and none of them should need one.
A projector browser open since four in the afternoon has to still be working at eight. The stage screens run as their own deployment, untouched by an app release mid-event.
How a draw runs
Set up the prizes and the code format. Coupon numbers are generated for you rather than typed into a spreadsheet the night before.
Eligibility is expressed as audience rules — ticket type, and the other attributes you already segment on. The same rule editor governs who may be checked into a session.
Eligibility is applied to the attendee list once and written down as entries. The draw then reads that pool, so a five-minute ceremony is predictable rather than re-computed live.
Arm a prize, draw, redraw, reset — from a phone or a laptop at the side of the stage, over a link the organizer mints.
A separate presentation view for the projector. The link that drives it can only watch, so leaving it open on an unattended laptop gives nothing away.
Every draw and win is stored as the record of a public announcement — not as a screenshot somebody took of the screen.
For the organizing team
The draw is configured where the rest of your event is configured, then handed to whoever is running the stage — with the authority to give away a prize kept separate from the ability to watch.
FAQ
The pick is uniform and without replacement, using the browser's cryptographic random source rather than a simple shuffle, and the database enforces independently that the same entry cannot win twice. The result is also recorded before it is displayed, so what the audience sees is what was stored.
Nothing changes. Winners are picked and stored before the screen is told to animate, so a reload, a flat battery or a dropped connection cannot alter or lose the outcome — the screen simply rejoins a draw that already has a result.
No. The organizer mints a signed link for the host, and a separate one for the projector. That is deliberate: the MC or AV operator running the stage usually has no login and should not need one.
No. The screen role can only watch. Arming, drawing, redrawing and resetting belong to the host link alone, which is why the projector link is safe to leave open on an unattended laptop.
Whoever your eligibility rules select — for example, a ticket type, or any attribute you already segment attendees by. The rules are resolved into a fixed pool of entries before the draw, so the ceremony itself is predictable.
Yes. The host console can redraw or reset, and each draw is recorded, so the redraw is part of the event's record rather than an undocumented decision.
For organizers
Fair, recorded, and built to survive a venue network and an unattended projector.