A multi-day pass is a lovely thing to sell and a nightmare to police if you get the setup wrong. One festival goer buys a three-day ticket, walks in on Friday, then hands the same QR code to a mate over the fence for Saturday. If your system cannot tell the difference, you have just given away a ticket. This guide is about selling multi day event tickets that let genuine holders come and go across the run, while quietly making pass-sharing more trouble than it is worth. No fences required, just the right controls.
The core idea in one line: a multi-day pass should be redeemable once per day per person, tied to the buyer, and either refreshed or re-scanned at each entry so a screenshot cannot do the rounds. Get that logic right and you can offer flexible re-entry (the thing attendees actually want) without opening the gates to everyone's cousin.
Why multi-day passes get shared in the first place
Sharing happens because a static ticket is just an image, and images travel. A QR code screenshotted on Friday morning works exactly the same on Saturday afternoon unless something stops it. The three usual leaks are simple: the same code being scanned twice on the same day (two people, one pass), a code being passed to a different person between days, and a screenshot circulating in a group chat because nothing invalidates it after use. Fix those three and you have fixed most of the problem.
A multi-day pass should feel generous to the person who bought it and pointless to anyone they try to lend it to.
Daily scans and single-use-per-day: the workhorse control
The single most useful control for multi day pass check-in is a scan limit that resets each day. The pass is valid for the whole run, but it can only be redeemed once within any given day. Scan it Friday, and it will not scan again until the clock rolls over to Saturday. That one rule kills the most common abuse (two people trying to enter on the same pass on the same day) while still letting the real holder leave and come back.
Layer re-entry on top of it. Plenty of festivals let people exit and return within a day. The clean way to handle that is to scan out as well as in, or to issue a physical credential at first entry that speaks for itself on the way back, so re-entry does not burn the person's daily redemption. The pass stays flexible for the buyer and rigid for a stranger.
Wristbands vs QR codes: which anti-sharing tool for which event
The credential you hand out matters as much as the software behind it. Here is the honest comparison for festival wristband tickets versus phone-based QR entry.
| Control | How it stops sharing | Best for | Trade-off |
|---|---|---|---|
| Static QR on phone | Barely, on its own | Small, low-risk events | Screenshots travel freely |
| Dynamic or timed QR | Code refreshes or expires after a scan | Paid events with resale risk | Needs the official app or live connection |
| Printed wristband | Goes on once, stays on all run | Multi-day general admission | Can be tampered with if cheap |
| RFID wristband | Encrypted chip, hard to clone, deactivates on misuse | Larger festivals, higher budgets | Hardware and setup cost |
For a two-day conference, single-use-per-day QR plus a name check at the desk is usually plenty. For a big outdoor festival, a wristband that goes on at day-one check-in and stays on for the whole run is the classic answer: guests exit and re-enter daily just by showing the intact band, with no re-scanning needed, which saves your gate staff a great deal of time. Higher up the scale, RFID wristbands carry encrypted data that is hard to clone and can be deactivated the moment the system spots a pass-back attempt.
Dynamic QR codes: killing the screenshot
If you are staying phone-based, the upgrade that matters is a QR code that does not stay still. Dynamic codes refresh on a timer or become invalid after a single scan, so the screenshot someone fired into a group chat is stale by the time it reaches the gate. This is the same principle transport apps use for barcodes that shimmer and regenerate: the code you see is only good for a moment. It does mean attendees need the live ticket in an app or a connected wallet rather than a saved image, so weigh that against your crowd's patience and your venue's signal.
Tie the pass to the buyer
Anti-sharing is far easier when the pass is attached to a named person, not just a code. When each credential is linked to the original buyer's record, your gate team can do a quick name-and-photo-ID check on higher-value passes, and your system can flag a pass that suddenly behaves like it belongs to three different people across a weekend. This is exactly the logic behind season passes and bundled tickets, and if you also sell those, our guide on selling season tickets and memberships covers the same per-occurrence redemption model.
Staffing the gate so the tech actually works
The best controls fall over if the gate is chaos, so a little planning goes a long way. Give every staff member their own scanning login so you can see who scanned what and when, run enough lanes that people are not tempted to wave through a queue to clear it, and brief the team on what a rejected scan means (already used today, wrong day, deactivated) so they respond calmly rather than guessing. For the wider mechanics of moving a big crowd through the door fast, our walkthrough on checking in 1,000 attendees with nothing but phones pairs neatly with the anti-sharing rules here.
Tell attendees the rules before they arrive
Half of gate friction is people not knowing how their pass works, so the cheapest anti-sharing control is clear communication. Spell it out in the confirmation email and on the ticket itself: the pass is personal, it scans once per day, and re-entry works in whichever way you have chosen. When people know a shared code will simply fail at the gate, most do not bother trying, and the ones who do are not surprised when it bounces. A confused attendee argues with your staff. An informed one just holds up their wristband.
It also heads off the awkward edge cases before they become a queue. State plainly what happens if a band is lost or damaged (usually a trip to the box office with ID, not a free replacement for anyone who asks), whether children need their own pass, and how late-in-the-run buyers get their credential. A two-line policy on the ticket saves your team from improvising the same answer two hundred times over a weekend.
A quick anti-sharing setup checklist
Set the pass to redeem once per day, resetting each day of the run.
Decide your re-entry model (scan out and in, or physical credential) so returns do not burn a redemption.
Choose your credential to match the risk: single-use-per-day QR for small events, wristbands or RFID for large festivals.
Use dynamic or timed QR codes if you want to defeat screenshots on phone-based entry.
Tie each pass to the buyer so misuse is visible and checkable.
Give staff individual scanning logins and enough lanes to avoid wave-throughs.
Honest note to close: no system makes sharing literally impossible, and you should not bankrupt yourself trying. For a free community weekend, a friendly wristband and a name list is proportionate. The controls scale with what a ticket is worth: the more a pass costs, the more it pays to lock it to a person and a day. If you want to see how per-day redemption, individual scanning logins and buyer-linked passes work in one place, take a look at the eventcloud platform.
