← Back to blog

College Fest Management Checklist

From first committee meeting to post-fest report

Fest season compresses six months of work into six weeks. Use this college fest management checklist as a shared doc for your core committee — tick items off, assign owners, and avoid the classic failures: oversold workshops, missing sponsor logos, and a gate queue that wraps around the block.

8–12 weeks before fest

Planning and approvals

  • Confirm fest dates with college admin and book venues
  • Form core committees: overall, events, marketing, finance, operations, sponsorship
  • Set overall budget and per-event budgets
  • Define fest theme, branding, and key messaging
  • List all events (flagship, workshops, competitions, pro nights) with owners
  • Identify which events are free vs paid

Platform and registration setup

  • Create verified organizer profile on Eventsliner
  • Publish society profile with logo, description, and gallery
  • Create individual event pages for each fest event
  • Set capacity limits and registration deadlines per event
  • Configure custom registration fields (college, year, team name, etc.)
  • Set up paid ticket pricing and early-bird rules where applicable
  • Test registration flow end-to-end with one committee member

Tip: Do not open registration until at least flagship event pages look complete — students judge credibility from the first link they click.

4–6 weeks before fest

Marketing and outreach

  • Release save-the-date poster with official profile link
  • Publish registration links on Instagram, LinkedIn, and WhatsApp — one canonical URL per event
  • Coordinate with partner societies for cross-promotion
  • Submit events for campus discovery on Eventsliner (Delhi NCR feed when live)
  • Prepare sponsor deliverables list (logo placement, stage mentions, booth space)

Finance and sponsors

  • Confirm sponsor MOUs and payment timelines
  • Verify bank account for registration settlement on the platform
  • Assign treasurer dashboard access for live revenue tracking
  • Define refund policy and communicate on event pages

Operations prep

  • Assign event-day point people per venue
  • Plan QR check-in stations and backup offline export
  • Order wristbands / badges if needed for multi-day access
  • Brief security on expected headcount per session

1–2 weeks before fest

Registration final push

  • Review capacity dashboards daily; close high-demand events on time
  • Send reminder posts for events nearing deadline
  • Export attendee lists for events requiring pre-screening (competitions, restricted workshops)
  • Resolve pending payment edge cases

Event-day logistics

  • Final venue walkthroughs: AV, seating, signage, sponsor branding
  • Print minimal backup lists (QR scan is primary)
  • Train gate volunteers on QR scanning app — 15-minute drill
  • Prepare help desk script for "I registered but don't have my QR" cases
  • Confirm certificate template and auto-issue rules if applicable

Communications

  • Pin official event pages (not Form links) in all bio links
  • Prepare day-of Instagram story templates for live updates
  • Share internal run-of-show document with all committee heads

Fest week (daily)

Each event day

  • Open check-in 45–60 minutes before start
  • Monitor live attendance in dashboard vs capacity
  • Flag duplicate scan attempts at gate
  • Post live content for flagship events (with sponsor tags)
  • Log incidents (oversell, AV failure, medical) in ops channel
  • Close check-in when event starts; late-entry policy enforced consistently

Finance (daily during fest)

  • Reconcile paid registrations vs dashboard totals
  • Track on-site cash / sponsor cheque collections separately
  • Note refund requests with event owner approval

Within 1 week after fest

Wrap-up and reporting

  • Export final attendance per event for college report
  • Export revenue summary for finance handover
  • Send thank-you message to attendees via society profile / social
  • Deliver sponsor reports: footfall, social reach, logo compliance photos
  • Issue certificates to eligible participants
  • Hold retrospective with committee — what broke, what to keep

Profile and proof for next year

  • Upload fest photos to society gallery
  • Mark events as completed on profile (builds history for next year's team)
  • Archive registration data exports in society Google Drive
  • Document vendor contacts and venue notes for succession

Common mistakes this checklist prevents

  1. Opening registration before event pages are ready — students bounce; conversion drops
  2. One mega-form for all events — finance and ops cannot split accountability
  3. Manual payment verification — treasurer burnout and lost revenue
  4. Paper-only check-in — slow gates and wrong headcounts for fire safety
  5. No post-fest exports — next year's team starts from zero

Tools map (what goes where)

Task Tool
Event pages + registration Eventsliner
Live dashboards + QR check-in Eventsliner
Internal committee polls Google Forms (fine for internals)
Creative assets Figma / Canva
Run-of-show and docs Google Docs
Day-of chat WhatsApp / Discord

Keep registration, payments, tickets, and attendance on one platform. Everything else can stay in the tools your committee already uses.

Download mentally, execute for real

Print this checklist, assign names in column two, and review it in weekly core meetings. Fests fail in the gaps — the workshop that oversold by 40 because nobody watched capacity, or the sponsor logo missing because marketing and ops had different files.

For registration and check-in specifically, see:

Ready to set up this year's fest? Create your first event.

College Fest Management Checklist for Organizers | Eventsliner