How to Organize a Hackathon: Step-by-Step Guide + Free Checklist (2026)
Running a hackathon is one of the best things you can do for your community. It turns a group chat into a room full of people building real things, and it's the fastest way to grow a club, a campus community or a city meetup.
It's also a lot of moving parts. This guide walks you through how to organize a hackathon step by step, from eight weeks out to the winners post, with a free checklist you can copy at the end.
Last checked: October 2026.
TL;DR
- Start 8 weeks out for a build night, and 3–4 months out for a 24-hour hackathon with sponsors.
- Decide the format first: in-person or online, a 2–3 hour build night or a 24-hour hackathon, open innovation or set tracks.
- Your biggest costs are usually food and venue, so lock in free rooms and sponsors early.
- Judge on clear criteria (real problem, it works, uses the tools well, clear demo) and announce winners within 24 hours.
- Want help? Request support for your hackathon on TinyBounties.
Step-by-Step Guide to Planning Your Hackathon
Planning a hackathon gets much easier when you break it into clear stages. The steps below cover the key decisions to make before, during, and after the event, from choosing the format and timeline to sponsors, judging, prizes, and follow-up.
Step 1: Pick your format
Before anything else, decide what kind of hackathon you're running. Everything else follows from this.
| Format | Best for | Typical size | Planning time |
|---|---|---|---|
| Build night (2–3 hours) | First event, campus clubs, weeknights | 30–120 people | 4–8 weeks |
| One-day hackathon (8–12 hours) | Clubs with a bit of experience | 50–200 people | 6–10 weeks |
| 24-hour hackathon | Big campus or city events with sponsors | 100–700+ people | 3–4 months |
| Online hackathon (1–2 weeks) | Global or remote communities | Any size | 4–8 weeks |
Open innovation or set tracks? Open innovation lets teams build anything, which brings creative ideas but makes judging harder. Set tracks (for example "best use of AI agents" or "best climate project") make judging fairer and are easier to sell to sponsors. Many hackathons do both: one open category plus 2–4 sponsor tracks.
A real example: at UCL Build Night, students built 30 working AI agents in 90 minutes, judged live the same evening. A short format like that is a great first event.
Step 2: Build your team
You can't run a hackathon alone. Even a small build night needs a few people with clear jobs:
- Lead organizer: owns the timeline and makes the final calls.
- Sponsorships: finds sponsors and manages what you promised them.
- Logistics: venue, food, Wi-Fi, power strips, check-in.
- Marketing: event page, posters, social posts and the recap.
- Participant experience: mentors, judges, schedule and the Discord or group chat.
For a build night, two or three people can cover all five. For a 24-hour hackathon, give each its own owner.
Step 3: Plan your timeline
Here's a simple timeline that works for most student and community hackathons. For big events, start the sponsor work even earlier: Major League Hacking's organizer guide suggests starting sponsor outreach about four months before.
8 weeks out
- Pick the date, format and size.
- Book the venue.
- Set the budget and start sponsor outreach.
- Put up a simple event page (Luma works well).
6 weeks out
- Open registrations.
- Choose your tracks or problem statements.
- Line up judges and mentors.
4 weeks out
- Order swag, stickers and posters (allow at least a week to print).
- Write the run of show: a minute-by-minute plan for the day.
- Confirm food for your expected headcount.
1–2 weeks out
- Shortlist or confirm participants.
- Send reminders with the schedule, what to bring and how to submit.
- Brief judges on the criteria.
Day of
- Arrive early to test Wi-Fi, power and the projector.
- Run check-in, kickoff, workshops, building time, demos and judging.
After
- Post the winners within 24 hours.
- Send a thank-you and recap to participants and sponsors.
Step 4: Venue and budget
Free venues come first. Campus rooms, library spaces, coworking spaces and sponsor offices are often free for student clubs. Check the Wi-Fi capacity and the number of power outlets before you book.
Food is usually your biggest cost. Plan for at least one meal and snacks, and more for anything longer than four hours.
| Item | Build night | 24-hour hackathon |
|---|---|---|
| Venue | Free (campus room) | Free–paid hall |
| Food and drinks | One meal + snacks | 3–4 meals + snacks + coffee |
| Swag and stickers | Optional | Shirts, stickers, winner merch |
| Prizes | Small gift cards | Cash or larger prizes |
| Printing and standees | Posters | Posters, standees, ID cards, lanyards |
| Photography | Phone photos | A photographer for the recap |
Most hackathons are funded by sponsors. We wrote a full guide on how to get sponsors for your event, including an email template.
Step 5: Registrations and shortlisting
Free events always lose some people on the day, so it's normal to accept more registrations than seats.
For big hackathons, shortlisting keeps the quality high. Ask for a short form: name, school or company, skills, team, and one line on what they want to build. For example, the Hack IIIT Delhi team expects around 3,000 registrations, shortlisted to 80–90 teams based on their proposals.
Send clear confirmation emails with the date, venue, schedule and what to bring (laptop, charger, ID).
Step 6: Problem statements and tracks
Good problem statements are specific enough to inspire, but open enough that teams can be creative. A useful format:
- The problem: one or two sentences on a real pain point.
- Who it's for: students, small businesses, a city, a community.
- What a great solution looks like: for example "an agent that works on the live web, not a fixed dataset".
- Resources: docs, credits and example projects.
If a sponsor provides a track, ask them for the problem statement, resources and a judge.
Step 7: Mentors, workshops and judging
Mentors unblock teams. Aim for roughly one mentor per 8–10 teams, and give them a shared channel so teams can ask for help.
Workshops at the start get everyone building faster. A 30-minute intro to the main tools is usually enough. Ask sponsors to run these.
Judging criteria should be shared before building starts. A simple scorecard:
| Criterion | What judges look for |
|---|---|
| Real problem | Does it solve something people actually have? |
| It works | Is there a working demo, not just slides? |
| Use of tools | Does it use the sponsor or track tools well? |
| Demo and pitch | Is it clear and convincing in 2–3 minutes? |
Live judging (judges walk around or watch quick demos and score on the spot) keeps the energy high, and winners can be announced the same night. That's how UCL Build Night judged all 30 builds in one evening.
Step 8: Submissions and prizes
Make submitting simple:
- A link to the working project (repo or live demo)
- A short demo video
- A LinkedIn post about the build tagging the hackathon and sponsors (this also spreads the word for free)
Prizes don't have to be big. Gift cards, swag, credits and a shout-out on the organizer's and sponsors' pages all work well. For a first build night, some clubs skip prizes and put the budget into better food.
Step 9: After the hackathon
The days after the event decide whether people come back:
- Post the winners within 24 hours on LinkedIn, X and Instagram, tagging the teams and sponsors.
- Send a recap to participants: winners, photos and what's next.
- Report back to sponsors: how many attended, how many used their product, photos and posts.
- Ask for feedback with a short form.
- Announce the next event while people are still excited.
The free hackathon checklist
Copy this into your notes or task tracker.
8 weeks out
- Pick date, format, size and tracks.
- Book the venue (Wi-Fi, power, room for food).
- Set the budget.
- Start sponsor outreach.
- Publish the event page.
4–6 weeks out
- Open registrations.
- Confirm judges and mentors.
- Write the problem statements and judging criteria.
- Order swag and printing.
- Write the run of show.
1–2 weeks out
- Shortlist and confirm participants.
- Send reminders and the schedule.
- Brief judges and mentors.
- Confirm food, deliveries and the volunteer schedule.
Day of
- Test Wi-Fi, power, projector and mic.
- Check-in, kickoff and workshops.
- Building time with mentors on hand.
- Demos, live judging and winners.
- Photos throughout.
After
- Winners post within 24 hours.
- Recap email to participants.
- Sponsor report.
- Feedback form.
- Announce the next event.
Want TinyFish at your hackathon?
TinyFish is one API that lets AI agents search, read and act on real websites, which makes it a great track for any AI hackathon. Teams can build agents that work on the live web, and students get $35 in their TinyFish wallet to build with at tinyfish.ai/students.
- Running a hackathon? Request TinyFish support for your event on TinyBounties: workshops, problem statements, judging criteria and more.
- Organizing events in your community? Join the TinyFish Ambassador Program.
- Building at one? Read how to win a hackathon with AI.
Keep reading
- How to Get Sponsors for Your Event or Hackathon (+ Email Template)
- How to Win a Hackathon with AI: Use TinyFish to Supercharge Your Project
- 12 Community Ambassador Programs to Lead in Your City
- How to Host a Tech Meetup: Step-by-Step Guide + 20 Event Ideas (2026)
Follow TinyFish for events, bounties and community spotlights: X (@Tiny_Fish) · LinkedIn (TinyFish) · Instagram (@tinyfish_ai)
AI disclosure
Content on this website may be created or refined with the assistance of AI tools and is subject to human editorial review.
