Guide · Updated
How to host a hackathon
To host a hackathon, pick a format you can actually run, book a venue with solid Wi-Fi and power, open registration with host approval, line up sponsors for tools and food, publish a judging rubric before anyone starts building, and end with timed demos. Everything else is detail, and the details are below.
This guide comes from running devkick build nights and game jams in Toronto and Waterloo, including devkick 005, a one-day game jam at the University of Toronto. Looking for an event to join instead? See hackathons in Toronto and hackathons in Waterloo.
1. Choose the format
The format decides everything downstream: venue hours, food, how much sponsors need to give, and how ambitious projects can be. If this is your first event, run the smallest format that still produces demos. A tight five-hour jam that ends on time beats a weekend event that runs out of energy on Saturday night.
| Format | Length | Typical size | Best for |
|---|---|---|---|
| Build night | 3 to 4 hours | 20 to 60 people | A first event, a recurring community, or a demo night where people bring work in progress. |
| One-day jam | 5 to 10 hours | 30 to 150 people | A themed build with sponsor tools and a single judging block. devkick 005 ran this way in five hours. |
| Weekend hackathon | 24 to 36 hours | 100 to 1,000+ people | Student and flagship events with travel, overnight space, workshops, and prize tracks. |
Then write the goal in one sentence. devkick 005's was: build a playable game in one day and submit it to the Chroma Awards. A clear goal tells people whether to come, tells sponsors what they are paying for, and tells judges what to reward.
2. Plan the timeline
Eight to twelve weeks is enough for a one-day event. Weekend events with travel need longer.
8 to 12 weeks out
- Write the one-sentence goal: who should come, and what they should leave having built.
- Pick the format and a date that does not collide with exams, holidays, or a larger event in your city.
- Book the venue and confirm Wi-Fi capacity, power at every table, room hours, and access rules.
- Start sponsor conversations. Credits and tools take weeks of internal approval at most companies.
4 to 6 weeks out
- Open registration with host approval so you can balance roles and cap the room.
- Lock the schedule, theme, judging rubric, and judges.
- Collect sponsor logos, credit codes, redemption steps, and anyone they are sending on site.
- Write the code of conduct and decide who handles a report on the day.
The final week
- Publish a single event page with the schedule, credits, Wi-Fi, rules, and judging criteria.
- Send approved attendees the address, room number, arrival time, and what to bring.
- Order food for the confirmed count, plus dietary options asked for at registration.
- Test the projector, the demo laptop, the adapters, and the venue network yourself.
On the day
- Arrive an hour before doors. Set up check-in, signage, power strips, and the demo station.
- Run a ten-minute kickoff: goal, schedule, credits, rules, judging, and where to get help.
- Walk the room every 30 minutes. Unblock teams and note who is close to a demo.
- Close submissions on time, run demos on a timer, judge, and announce before people leave.
3. Venue and logistics
Universities, coworking spaces, and company offices are the usual venues, and many will host for free in exchange for visibility or student access. devkick 005 ran in room BA1220 at the Bahen Centre at the University of Toronto. Whatever the space, confirm these in writing:
- Network. Ask how many devices the Wi-Fi supports and get a guest login in advance. Print the credentials.
- Power. Every seat needs an outlet. Bring power bars if the room does not have them.
- Hours and access. When can you set up, and when does the building lock? Leave a buffer after demos.
- Demo setup. A projector, an HDMI and USB-C adapter kit, and one laptop that teams can present from.
- Food. One meal or substantial snack per four hours, water, and options for the dietary needs you collected.
4. Registration
Keep registration free and turn on host approval. devkick uses Luma for this: approval lets you cap the room, balance roles, and see who is coming before the day. Ask one question that helps teams form, such as role (developer, designer, artist, audio) and experience level. Free events see no-shows, so approve somewhat more people than the room holds, adjusted by your own attendance history.
Say plainly who the event is for. "No game development experience is required" on the devkick 005 page brought in designers and audio people, not only programmers, and mixed teams built better games.
5. Sponsors and sponsorship
Sponsors want builders using their product, honest feedback, and content from the day. Offer that directly instead of a generic logo package. For a one-day event, ask for:
- Tool credits that teams can redeem in minutes. devkick 005 had credits from Devin, ElevenLabs, Meshy and Rosebud AI.
- Food and drinks, which is the easiest line item for a sponsor to approve.
- Prizes or a pathway. The devkick 005 winner was fast-tracked to the semi-finals of a Chroma Awards category, which mattered more to teams than swag.
- A person on site to help with their tool, judge, or give a short talk.
Put every credit's redemption steps on one page that attendees can open on their phones. Codes that need a card at checkout, only work for new accounts, or renew automatically should say so up front. It saves an hour of questions during build time.
6. Run of show
Most of the event is building. Protect that block: no talks in the middle, and announcements only on a schedule. This was the devkick 005 run of show:
Open with a ten-minute kickoff covering the goal, schedule, credits, rules, and judging. Give a 30-minute and a 10-minute warning before building ends, and close submissions on time.
7. Hackathon judging criteria
Publish the rubric before building starts so teams can aim at it. Use four to six criteria, weight the ones that match your goal, and score every team the same way, whether they show a finished build or a pitch. This is the rubric devkick used for its game jam: score each criterion 1 to 5, multiply by the weight, and add up for a total out of 100.
| Criterion | Weight | What earns points |
|---|---|---|
| Core idea | ×4 | One sentence, and it sounds fun. |
| Sound and voice | ×4 | Audio is core to the experience, not decoration. |
| Visuals and 3D | ×4 | The look brings the world, characters or mood to life. |
| Creativity | ×3 | A fresh concept, or a familiar genre with a real twist. |
| Player experience | ×3 | You understand what the player does and feels. |
| Path to finished | ×2 | Realistic scope and a clear next step. |
Swap the theme-specific rows for your event. A developer-tools hackathon might replace sound and visuals with technical execution and use of sponsor APIs. Keep a row like "path to finished" so judges reward realistic scope over a slide deck.
Make scores consistent
Tell judges that specific beats vague: a clear plan can score a 4, and a 5 needs something built. Give them the same few questions to ask every team, and write tie-breakers down in order before the event, for example: which project would we most want to use, which used the sponsor tools most ambitiously, and who made the most progress for their team size.
8. Demos and what comes after
Run demos on a visible timer, two to three minutes each, from one laptop if you can. Announce winners before people leave. Within a week, post a recap with photos, winners, and links to projects, with each builder's consent. devkick publishes demoed projects on its builds page and keeps a record of past events on the events page.
The recap is also your pitch for the next event. Send it to sponsors with attendance, number of demos, and what was built with their tools.
Hackathon checklist
- Venue booked, with Wi-Fi, power, capacity and hours confirmed in writing
- Registration open with host approval and a role question
- Schedule, theme, rules and code of conduct published
- Judging rubric with weights, judges confirmed, tie-breakers written down
- Sponsor credits, codes and redemption steps on one page
- Food and drinks ordered for the confirmed count
- Projector, demo laptop, adapters and microphone tested
- Recap plan: photos, a winners post, and project links with builder consent
Hackathons in Toronto and Waterloo
devkick curates hackathons in the Toronto-Waterloo corridor, with a take on each event and squad status for teams forming in Discord.