Hackathon Organizer — Tips & Best Practices

Comprehensive guide for planning and running successful hackathons, from first-timers to experienced organizers.

Reference Files

• references/planning-and-logistics.md — Timeline, venue, food, day-of operations, and post-event checklist
• references/judging-and-prizes.md — Judging formats, criteria design, judge recruitment, prize strategy

When to Activate

• User asks how to organize, plan, or run a hackathon
• User asks about hackathon logistics, timelines, or budgets
• User asks about sponsor outreach or management
• User asks how to set up judging or prizes
• User is planning an event on the Oatmeal platform and wants strategic advice

When NOT to Activate

• User wants to use the Oatmeal API to create/manage a hackathon (use hackathon-cli instead)
• User is attending a hackathon as a participant (use hackathon-attendee instead)
• User is writing hackathon platform code

Planning Timeline

3-6 Months Before

• Define your hackathon's identity — theme, target audience, size, format (in-person/virtual/hybrid), and duration (24h, 36h, 48h, weekend)
• Set the date — avoid exam periods, holidays, and competing events. Weekends work best. Check local university calendars
• Secure a venue — needs reliable WiFi, power outlets everywhere, breakout rooms, and a presentation area. Universities, coworking spaces, and corporate offices are common choices
• Build your organizing team — assign clear roles: logistics lead, sponsor lead, marketing lead, tech lead, volunteer coordinator
• Start sponsor outreach early — sponsors take 4-8 weeks to commit. Prepare a sponsorship deck with tiered packages (title, gold, silver, bronze). Lead with what sponsors get: brand exposure, recruiting access, API/product adoption

1-3 Months Before

• Open registration — use a platform (like Oatmeal) to manage signups. Collect dietary restrictions, t-shirt sizes, and experience level
• Recruit mentors and judges — aim for 1 mentor per 5-8 teams and 1 judge per 10-15 submissions. Judges should have diverse backgrounds (technical, business, design)
• Plan the schedule — include opening ceremony, hacking time, workshops, meals, fun activities, judging, and closing ceremony
• Order swag and supplies — t-shirts, stickers, lanyards, extension cords, whiteboards, markers, snacks
• Set up communication channels — Discord or Slack workspace for announcements, team formation, and Q&A

1-4 Weeks Before

• Send reminder emails — event details, what to bring, parking/transit info, schedule preview
• Confirm catering — plan for breakfast, lunch, dinner, and midnight snacks. Account for dietary restrictions (vegetarian, vegan, halal, kosher, gluten-free). Budget ~$20-30/person/day
• Brief your volunteers — create a volunteer handbook with roles, schedules, and emergency contacts
• Test all tech — WiFi capacity, AV equipment, streaming setup (if hybrid), submission platform
• Prepare judging criteria — finalize and publish so participants know what they're optimizing for

Day Before

• Set up the venue — tables, chairs, power strips, signage, registration desk, sponsor booths
• Do a full tech check — WiFi, projectors, microphones, streaming
• Pre-stage food pickup/delivery — confirm all catering orders

Budget Planning

Category	% of Budget	Notes
Food & drinks	40-50%	Biggest expense. Don't skimp — hungry hackers don't hack well
Venue	15-25%	Often free if sponsored or at a university
Prizes	10-15%	Cash, devices, subscriptions, or experiences
Swag & supplies	5-10%	T-shirts, stickers, lanyards
Marketing	5%	Social media ads, posters, email tools
AV & tech	5%	Rentals, streaming equipment
Contingency	5-10%	Always have a buffer

Cost per attendee benchmark: $30-75 for a 24h event, $50-120 for a 48h event.

Sponsor Management

What Sponsors Want

1. Recruiting pipeline — access to talented developers. Let sponsors set up booths, give lightning talks, and collect resumes
2. Product adoption — API challenge prizes drive real integration. Offer "Best Use of [Sponsor API]" tracks
3. Brand visibility — logo on website, t-shirts, banners, social media mentions
4. Content — photos, videos, testimonials for their marketing

Sponsorship Tiers

Tier	Price Range	Includes
Title	$10k-50k+	Naming rights, keynote slot, premium booth, logo everywhere, recruiting session, custom prize track
Gold	$5k-15k	Large booth, logo on shirts/banners, workshop slot, prize track
Silver	$2k-7k	Small booth, logo on website/banners, swag in bags
Bronze	$500-2k	Logo on website, social media mention
In-kind	Varies	API credits, food, venue, prizes (counts as sponsorship)

Outreach Tips

• Personalize every email — reference something specific about the company
• Lead with their benefit, not your need — "We're offering your team access to 200+ developers" not "We need money"
• Follow up exactly once after 5-7 days if no response
• Make it easy to say yes — have a clear sponsorship deck PDF ready

Marketing & Registration

• Target 2-3x your capacity in registrations — expect 40-60% actual attendance
• Start promotion 6-8 weeks before — social media, university mailing lists, tech meetups, Discord/Slack communities
• Create urgency — early bird registration, limited spots, rolling acceptance
• Share teasers — announce sponsors, judges, prizes, and workshops progressively
• Leverage your sponsors' reach — ask sponsors to share on their channels

Day-Of Operations

Opening Ceremony (30-45 min)

• Welcome, schedule overview, WiFi password
• Sponsor lightning talks (2-3 min each, max 5 sponsors)
• Rules, judging criteria, submission instructions
• Team formation activity for solo attendees

During the Hackathon

• Mentors on rotation — have mentors available in shifts, not all at once
• Regular announcements — meal times, workshop reminders, submission deadline warnings
• Activities between hacking — cup stacking, trivia, lightning talks, yoga. Breaks prevent burnout
• Quiet hours — if overnight, designate a quiet zone for sleeping
• Food arrives on time — nothing derails a hackathon faster than late food

Submission Window (1-2 hours before judging)

• Give 30-minute and 15-minute warnings
• Have a team troubleshooting submission issues
• Close submissions on time — no exceptions builds trust

Common Mistakes

1. Underestimating food costs — always budget 15% more than you think
2. Too many sponsor talks — cap at 5 during opening. More = hackers tune out
3. Vague judging criteria — "most innovative" means nothing. Define what innovation looks like
4. Not enough power outlets — every seat needs power access. Bring extension cords
5. WiFi that can't handle the load — test with expected concurrent connections
6. Judging takes too long — expo-style judging (judges walk around) is faster than stage presentations for 20+ teams
7. No plan for solo attendees — facilitate team formation. Many first-timers come alone
8. Ignoring dietary restrictions — always have vegetarian, vegan, and allergy-safe options
9. Starting late — respect attendees' time. Start on schedule
10. No post-event follow-up — send a thank-you email with photos, project links, and a feedback survey within 48 hours

Post-Event

• Send thank-you emails within 48 hours — to participants, sponsors, judges, mentors, and volunteers
• Share a highlight reel — photos, videos, winning projects
• Collect feedback — short survey (5-10 questions max) sent the day after
• Publish results — use the Oatmeal platform to publish results publicly
• Write a retrospective — what worked, what didn't, what to change. Share with your team
• Maintain community — keep the Discord/Slack active. Announce the next event early

Virtual & Hybrid Considerations

• Streaming is non-negotiable for hybrid — invest in good cameras and microphones
• Virtual team formation is harder — use dedicated Discord channels or a matchmaking tool
• Time zones matter — schedule core activities in overlapping hours
• Engagement drops after 12 hours virtual — consider shorter formats (12-24h) for fully virtual events
• Submission should be platform-based — video demos + GitHub links work better than live presentations for virtual
• Have a dedicated "virtual experience" person — someone whose only job is making sure remote participants aren't forgotten

For detailed logistics checklists and judging setup guides, see the reference files.