College Fest Management System with Event Registration, Ticket Booking and Sponsor Tracking

College fests run on spreadsheets, group chats and paper lists, and that is where the chaos starts. A college fest management system with event registration, ticket booking and sponsor tracking replaces that patchwork with one web application for creating events, publishing ticket tiers, confirming registrations and tracking sponsorship money live. Participants browse events, register as individuals or teams, and receive a tiered ticket with a unique booking ID and a QR code for gate check-in. Sponsors are recorded by tier — title, gold, silver or bronze — with committed, received and pending amounts, so follow-ups stop depending on one person's memory. The demo build renders 6 events, 1,248 seeded registrations and 8 sponsors, and booking a ticket issues a booking ID in the TN26-88xx series with a 12 × 12 module QR-style code drawn on a canvas. It suits any college running a multi-day fest with paid events and sponsors.

The system is a full-stack web application: a browser front end, a Node.js and Express back end, and a MySQL database holding events, registrations, tickets and sponsors. An organiser signs in, creates the fest with its dates, and publishes events with a fee, a seat limit and a team size; each event gets general, VIP or team-pass tiers. Participants browse the published events, fill in a registration form and pick a ticket tier, and the back end creates a registration row, a booking with a unique ID, and a QR code that the participant shows at the gate. Gate volunteers scan the code, the booking is marked checked in exactly once, and duplicate scans are rejected. Sponsors are entered by tier with a committed amount, and every payment received is logged against that sponsor until the balance reaches zero. The dashboard reads the same tables to show registrations per event, tickets per tier, revenue collected and sponsorships still pending.

1. The organiser signs in and creates the fest with dates, events, ticket tiers and seat limits.
2. Events go live on the fest site; participants browse them and register as individuals or teams.
3. The participant picks a ticket tier and the back end creates a registration, a booking with a unique ID and a QR code.
4. Payment status is recorded against the booking — paid, pending or cancelled — and the dashboard totals update.
5. At the gate, a volunteer scans the QR code; the booking is marked checked in exactly once and duplicate scans are rejected.
6. Sponsors are entered by tier with a committed amount, and each payment received is logged against the sponsor until the balance is zero.
7. The organiser dashboard shows registrations per event, tickets per tier, revenue collected and sponsorships still pending.

Tech stack:

• HTML5 · CSS3 · JavaScript (frontend)
• Node.js · Express (backend)
• MySQL (database)
• JWT authentication
• QR code ticket generation
• REST APIs (JSON)
• bcrypt password hashing
• Git

The college fest management system is built around four capabilities that carry the whole fest: event registration, tiered ticket booking, sponsor tracking and a live organiser dashboard. Event registration lets organisers publish events with fees, seat limits and team sizes, and lets participants register as individuals or teams without a spreadsheet in sight. Ticket booking sells general, VIP and team passes, issues a unique booking ID with a QR code for every order, and blocks duplicate gate check-ins. Sponsor tracking records every sponsor by tier with committed, received and pending amounts, and flags payments overdue by more than 7 days so follow-ups happen on time. The dashboard pulls it together with registrations per event, tickets sold per tier and the sponsorship pipeline in one view. Role-based access keeps organisers, gate volunteers and participants in separate lanes, and every list exports to CSV for the fest committee.

• [Event creation and registration] Organisers publish events with a fee, seat limit and team size; participants register as individuals or teams and receive a booking ID immediately.
• [Tiered ticket booking with QR codes] General, VIP and team-pass tiers with live totals; every confirmed booking issues a unique booking ID and a QR code for gate check-in.
• [Sponsor tracking by tier] Title, gold, silver and bronze sponsors recorded with committed amount, received amount, pending balance and follow-up status.
• [Organiser dashboard and reports] Registrations per event, tickets sold per tier, revenue collected and the sponsorship pipeline shown live in one view.
• [Role-based access] Separate organiser, gate-volunteer and participant roles, so volunteers can scan tickets at the gate without reaching organiser settings.
• [Registration and payment status tracking] Every registration carries a paid, pending or cancelled status, so the committee always knows who has actually paid.
• [Duplicate-scan protection] A booking ID can be checked in only once at the gate, so a shared ticket screenshot cannot admit two people.
• [CSV exports] Participant lists, booking lists and sponsor reports export to CSV for the fest committee and the college office.

• Complete source code for the web application (frontend + backend)
• MySQL database schema with seed data for 6 events and 8 sponsors
• QR-code ticket generation and gate check-in flow
• Sponsor tracking module with tier, committed and received amounts
• Organiser dashboard with registrations, tickets and revenue views
• Setup instructions and deployment guide
• Project report PDF (background, methodology, architecture, outcomes)
• PPT presentation for final review
• Viva Q&A preparation document