Every college cultural fest committee learns the same lessons the hard way.
Registration opens on a Google Form. Within two hours, the form has collected 400 entries for a 300-seat hall. Nobody closed it in time. Now the committee is manually counting responses, messaging people who registered after the cutoff, and fielding "is my spot confirmed?" messages at midnight.
For paid events it gets worse. The UPI QR goes up in the batch group. Screenshots land in the treasurer's DMs — some real, some edited, some from last year's event. On the day there is a printed list, one volunteer with a highlighter, and a queue of 200 stretching back to the college gate.
A dozen people wave the same forwarded confirmation screenshot. The name-check queue takes 45 minutes to clear. The opening act starts late. None of this is unique — it is the standard outcome of running a ticketed event on tools that were never designed for it.
What the Setup Actually Needs
Before any product, it helps to be clear on what a college fest actually needs from a ticketing setup.
A shareable booking page — not a form, but a proper event page (name, date, venue, schedule, ticket options) at one mobile-friendly URL you can drop into a WhatsApp group or Instagram story, with no app download for the attendee.
Capacity enforcement without a human — if the hall holds 2,000, the system closes that ticket type automatically at 2,000, not at 2,100 after someone checks.
Separate free and paid tiers — a free general pass, a paid all-access pass, a paid delegate pass, all on the same page, not across three Google Forms.
QR tickets delivered automatically — every confirmed attendee gets a QR code by email immediately on registration, not in a batch three days before.
Duplicate-scan rejection at the gate — a forwarded screenshot of a friend's QR should not get a second person in.
Scan-only access for volunteers — gate volunteers can scan tickets but should not see registration data, phone numbers, or the organiser dashboard.
How Boni Event Ticketing Handles Each of These
Boni Event Ticketing is a hosted platform, live in production, that organisers use to create event pages and run the full booking and gate flow. Here is what it looks like for a 2,000-attendee cultural fest.
The booking page
The committee creates the event — name, dates, venue, description, poster — and adds ticket types (say, a free General Entry capped at 1,400 and a paid All-Access capped at 600). Each type has its own capacity, and when it sells out it closes on the page automatically.
The event gets a public URL the committee shares anywhere. Attendees open it on mobile, pick a pass, fill in name/phone/email, and confirm. For paid passes, payment runs through a hosted checkout (UPI, card, net banking) and the platform handles confirmation — no UPI QR in the group, no screenshots, and the treasurer is not the payment intermediary.
QR tickets by email
Once a booking is confirmed — free and paid equally — the platform emails the attendee a unique QR code within minutes. No batch PDF generation, no manual forwarding.
Gate scanning with scan-only volunteer accounts
On the day, the committee creates scan-only accounts for gate volunteers. These accounts can scan QR codes and see whether a ticket is valid or already used — that is all. No attendee list, no registration details, no organiser dashboard. This matters because gate volunteers are often first-years who rotate shifts; limiting access to exactly what they need reduces the risk of data landing in the wrong place. Volunteers use a web-based scanner on their phones; each scan returns one of three results: entry allowed, already claimed (with a timestamp), or invalid.
Duplicate-scan rejection
The first valid scan claims the code. If the same code is scanned again — a re-entry attempt or a forwarded QR — the system shows "already claimed" with the time and gate of the first scan. A screenshot of someone's QR does not become a valid pass once the original has been scanned.
Free and paid passes on the same page
All pass types live on one public event page. The attendee picks their type, completes that flow, and receives their ticket. For paid passes the organiser never collects payment manually or reconciles screenshots — confirmation is handled before the ticket is issued.
What This Looks Like on the Day
The booking page is shared a week ahead; registrations arrive over several days, and the committee sees in real time how many of each pass type have sold. When the paid tier hits its cap, it closes — nobody has to remember to take the form down.
On the day, four volunteers at four entry points each have the scanner open. The queue moves at the speed of a QR scan — two to three seconds per attendee. A valid scan gets a clear green result; a duplicate gets flagged. No printed list, no name-check queue. After the event, the team has a record of how many passes of each type were actually used, not just registered — useful no-show data for the next edition.
What Is Live and What Is Still Being Built
To be honest about where the product stands: the core flow above — booking pages, free and paid ticket types, capacity enforcement, QR tickets by email, duplicate-scan rejection, and scan-only volunteer accounts — is live and verified with real events.
The platform is currently available through managed onboarding rather than fully open self-serve: you contact the Boni team and they set up your event with you, which lets them catch edge cases before they cause a problem on the day. Some areas are still being developed — deeper analytics, offline-tolerant scanning for venues with unreliable connectivity, and automated waitlist handling. Real gaps worth knowing before you commit.
Who This Works For
Designed for events from a few hundred to a few thousand attendees where the organising team handles everything themselves and needs a setup that works without weeks of integration:
- College cultural fests and tech fests with paid and free tiers
- Annual day and send-off events needing registration and guest confirmation
- Workshops and seminars with paid registration and capacity caps
- Community meetups that want real attendance data, not a form count
It is not for stadium events with complex seating maps, multi-day wristband access, or merchandise sales — those need purpose-built tooling.
How to Start
If the setup above matches what you need, reach out before you are two weeks from the fest date. Setting up the event, testing the booking flow, and getting gate scanning ready takes a little time — not a lot, but enough that the week before is too late.
Boni Event Ticketing is a Boni product; the team is reachable at the link. Explain your event — date, venue capacity, pass types, paid or free — and they will tell you whether it fits. Your gate volunteers deserve a scanner that works, your attendees deserve a confirmation that arrives, and your committee deserves to spend the week before the fest on the event itself, not on spreadsheet reconciliation.
Top comments (0)