How to Plan a Hackathon: 6-Month Timeline

To plan a hackathon, start 4 to 6 months out: set the goal, format and length first, then book a venue with strong wifi and power, sign sponsors and API partners, write rules and prizes, open registration and recruit mentors and judges. In the last month, lock the schedule, test the network and brief your volunteers. On the day, run a clear 24- or 48-hour schedule with a kickoff, team formation, check-ins, a submission deadline, demos and judging. After the event, pay out prizes, share the winning projects and thank your sponsors with numbers. The sections below walk through each step with a sample 24-hour schedule you can copy.
Step 1: Decide the goal, audience and format
Every other decision follows from why you are running the hackathon and who it is for. Write one sentence that answers both before you book anything.
- Corporate internal hackathon. Employees build prototypes for the business or try new tools. Usually one or two working days, no overnight, held in your own office. The main costs are food, prizes and time away from normal work, and the IP question is usually settled by employment agreements.
- Public or community hackathon. Open to anyone, often themed around a cause, a city or an open data set. Expect a mix of experience levels, more registration no-shows and a bigger need for mentors and code of conduct enforcement.
- Student hackathon. Run by or for a university or school. Often 24 to 36 hours over a weekend, with travel reimbursement, sleeping areas and a strong focus on first-time hackers. Check campus rules for overnight events and minors.
- Sponsor or developer-relations hackathon. Built around a company's API or platform, with prizes for the best use of it. Clear technical docs and on-site engineers matter more than anything else.
- In-person, hybrid or online. In-person events create the most energy but cost the most. Hybrid adds a streaming setup and online judging. Fully online events can run longer but need a strong chat server and scheduled check-ins to keep teams engaged.
Then pick a length. 24 hours is the most common in-person format. 48 hours suits large public and student events over a weekend. Internal events usually run 8 to 16 working hours across one or two days. Set a target headcount too: a first hackathon of 50 to 150 people is very manageable for a small team.
Hackathon planning timeline
Use this as a hackathon planning checklist for a public or student event of around 100 to 300 people. Halve the lead times for an internal event.
4 to 6 months out
- Set the goal, theme, format, length and target headcount.
- Build a draft budget and decide whether registration is free or ticketed.
- Shortlist and book the venue, and confirm overnight access if you need it.
- Write a sponsor prospectus and start conversations with sponsors and API partners.
- Name an organizing lead for each area: venue and logistics, sponsors, participants, mentors and judges, food, and communications.
2 to 3 months out
- Publish the event page with dates, eligibility, the theme and the code of conduct.
- Open registration and plan to over-invite, since free events often see a large share of no-shows.
- Draft official rules, prize terms and IP terms, and send them for legal review.
- Recruit mentors and judges, and confirm prize categories with sponsors.
- Book catering, security, cleaning and any rentals such as tables, power strips and extra access points.
1 month out
- Lock the schedule and floor plan: team tables, quiet room, sponsor tables, stage, food, sleeping areas.
- Run a network test at the venue with the IT team.
- Publish API docs, starter kits and the submission process.
- Send judges the criteria and mentors their shift times.
- Recruit and assign volunteers for check-in, food, help desk and overnight shifts.
Week of
- Send a know-before-you-go email with arrival time, what to bring, wifi details and the schedule.
- Print signs, badges, judging sheets and the wifi network name.
- Confirm headcount with caterers and add 10 to 15 percent for overnight snacking.
- Brief volunteers, mentors and judges on the schedule and code of conduct.
Step 2: Book a venue that can handle the network and power
A hackathon venue lives or dies on two things people rarely check: internet and outlets. A conference hall that is fine for talks can collapse when 200 people each connect a laptop and a phone, then pull large packages and container images at the same time.
- Wifi. Ask the venue for the bandwidth, the number of access points in your rooms and the per-device limits. Plan for two to three devices per person, ask for a dedicated network for your event and get the name of the person on call overnight. Our event wifi guide covers the questions to ask.
- Power. Every seat needs an outlet. Budget for power strips at each team table and confirm which circuits they share, so you do not trip a breaker at 2 a.m.
- Space. Allow team tables with room to spread out, a quiet room, a stage or demo area with a projector, a food area away from laptops and, for overnight events, a sleeping room with lights off.
- Access and safety. Confirm 24-hour access, security staff, building rules for overnight stays and accessibility for every room you use.
Step 3: Build the budget and sign sponsors
Most public and student hackathons are free for participants and paid for by sponsors. The main budget lines are the venue, food for every meal and overnight snacks, prizes, wifi upgrades and rentals, swag, security and cleaning, AV for the kickoff and demos, insurance, and travel support if you offer it. Food is often the largest line for a 24-hour event, since you are feeding people four or five times.
Sponsors usually come in two kinds. Cash sponsors fund the event in exchange for logo placement, a table, a talk slot and access to participants who opt in to recruiting. API and platform partners provide credits, a sponsored prize for the best use of their product, and engineers who act as mentors. Offer clear tiers with a fixed number of slots at each level, and tell sponsors in writing what they get, including whether they receive any participant contact details and how consent works.
Step 4: Set prizes, rules and IP terms
Prizes give teams a target, but the rules are what keep the event fair. Common prize structures include an overall top three, category prizes tied to the theme, sponsor prizes for the best use of a specific API, a best first-time team award and a people's choice award.
Your official rules should cover eligibility, team size, what can be built before the event (usually nothing beyond public libraries and starter code), the submission deadline, what a submission must include, how judging works, how prizes are paid and taxed, and the code of conduct. Spell out intellectual property: many public events let participants keep ownership of what they build, while internal events usually follow employment agreements. Prize, contest and IP rules vary by country and state, so have a lawyer review the final rules. This guide is not legal advice.
Step 5: Plan team formation and mentors
Many participants arrive without a team. Let people register as a team of up to four or as solo hackers, then run a team-formation session right after kickoff: a short round of idea pitches, a wall or channel where people post the skills they have and need, and a cut-off time for registering teams. A volunteer should check in on anyone still without a team after the session.
Aim for roughly one mentor for every 10 to 15 participants, on scheduled shifts so someone is always available overnight. Mix sponsor engineers, designers and people who know the theme. Give mentors a help desk location, a way to be paged from team tables and a clear brief: help teams get unstuck, do not write their project for them.
Sample 24-hour hackathon schedule
This hackathon schedule starts on a Saturday morning. Shift every time to fit your venue, and keep the submission deadline firm.
- Saturday 9:00 a.m. Check-in, badges and breakfast.
- 10:00 a.m. Kickoff: welcome, theme, rules, code of conduct, wifi details, sponsor and API partner intros, prize categories.
- 10:45 a.m. Team formation and idea pitches.
- 11:30 a.m. Hacking starts.
- 12:30 p.m. Lunch.
- 2:00 p.m. Sponsor workshops and API demos, in a separate room so building continues.
- 6:00 p.m. First check-in: each team confirms its project name and members.
- 7:00 p.m. Dinner.
- Midnight. Late-night snack and a short break activity.
- 3:00 a.m. Overnight snack and mentor shift change.
- Sunday 8:00 a.m. Breakfast.
- 9:00 a.m. Hacking ends. Submissions due, with no exceptions.
- 9:15 a.m. Judging rounds or a science-fair style expo at team tables.
- 11:00 a.m. Finalist demos on stage, three to five minutes each.
- 12:00 p.m. Judges deliberate while attendees have lunch.
- 12:30 p.m. Awards, sponsor thanks and closing.
Step 6: Run judging and demos
Publish your judging criteria before the event so teams build toward them. Most hackathons score a handful of criteria such as technical difficulty, creativity, usefulness, design and presentation, plus sponsor criteria for API prizes. Our hackathon judging criteria page has a weighted rubric and a printable score sheet you can adapt.
With more than about 20 teams, run judging in two rounds: small judge groups visit team tables for a few minutes each, then the top teams demo on stage to the full panel. Time every demo, give judges a shared sheet to compare scores, and decide ahead of time how ties are broken and whether judges with a conflict of interest step out.
Step 7: After the hackathon
- Announce winners on your site and social channels with project links, if teams agree.
- Pay out prizes promptly and collect any tax forms your rules require.
- Send a short participant survey within 48 hours while memories are fresh.
- Send each sponsor a recap: attendance, submissions using their API, workshop turnout and photos.
- Hold a team debrief and write down what to change, then save the dates for next year.
Where Map D fits
Map D does not take project submissions, score entries or tally judges, so you will still use a submission platform and score sheets for that. It does help with the event around the build: a multi-track schedule of workshops, check-ins and demos that attendees can save to their own agenda in the app, a floor plan of team tables, stages, food and sponsor booths, live polls, and sponsor levels sold with add-ons in one checkout. See Map D for technology conferences for details. The floor plan editor is free for one event; publishing, the app and sponsor sales need a paid plan.
FAQ
How far in advance should you plan a hackathon?
Plan a public or student hackathon of 100 or more people about 4 to 6 months ahead, so you have time to book a venue, sign sponsors and API partners, and promote registration. A small internal corporate hackathon can come together in 6 to 8 weeks because the venue, wifi and participants are already in place.
How long should a hackathon be?
24 hours is the most common length for in-person events, because it gives teams one full build cycle and one night. 48 hours suits ambitious public or student events that run over a weekend. Internal corporate hackathons often run one or two working days with no overnight, and online or hybrid events sometimes stretch over a week of part-time work.
How many people should be on a hackathon team?
Two to five people per team is the usual range, with four as a common cap. Smaller teams move faster and keep demos focused. Allow solo hackers to join a team at a team-formation session, and set the cap in the rules so prize splits and judging are fair.
Who owns the code built at a hackathon?
It depends on your rules and, for internal events, on employment agreements. Many public hackathons state that participants keep ownership of what they build, while sponsors or the host get a limited right to showcase it. Write the intellectual property terms into your official rules and have a lawyer review them, since rules vary by country and state and this is not legal advice.

