How to host a student hackathon or build day: checklist and timeline
· buildtolaunch
This guide is for student organizers, club leads and lecturers who have been asked to "run something" and have a small budget. You get a six-week checklist, a day-of schedule and a follow-up plan, built around a build day rather than a 48-hour hackathon. Part of Build days and builder communities: how to join, host and grow one.
Short answer
To host a student hackathon or build day, pick one goal ("everyone leaves with a link someone can open"), choose the format and one build tool, and book a venue about six weeks out. Open approval-based registration four weeks out, recruit three to five helpers, test the tool yourself, run a tight schedule, and send a recap with every project link within 48 hours.
Hackathon or build day: choose first
The two formats look similar and need very different amounts of work.
| Hackathon | Build day | |
|---|---|---|
| Length | 24 to 48 hours | One afternoon, about 5 hours |
| Staff needed | 8 to 15 helpers, overnight cover | 3 to 5 helpers |
| Judges | Usually, plus a rubric | Optional; members can vote |
| Venue | Needs to stay open overnight | Any room with Wi-Fi and power |
| Coding needed | Often | No, if you use an AI app builder |
| Best for | Teams who want a challenge | First-timers and mixed majors |
If you have never hosted before, start with a build day. It costs less, fails more gently, and gives you a list of people who will come to the next one. Save the full hackathon for when you have members who already build. If you do want judges later, a judging rubric template saves you an argument.
Step 1: write your one-line goal
Write one sentence before you do anything else. Good examples:
- "Thirty students from any major each publish a working app link by 6 PM."
- "Ten teams of three ship a prototype for a real problem on campus."
Every later choice (venue, tool, schedule, prizes) is checked against that sentence. If a task does not help it, drop the task.
Step 2: the six-week timeline
| When | What to do |
|---|---|
| 6 weeks out | Fix the date, format and venue. Avoid exam weeks and public holidays. Write your goal sentence. |
| 5 weeks out | Choose one build tool. Ask its team or your lecturer about free credits (how organizers get sponsors and tool credits). Draft your code of conduct. |
| 4 weeks out | Open registration with approval turned on. Set a capacity and a waitlist. |
| 3 weeks out | Recruit helpers: a lead, a floor mentor, a registration person, a photographer. Share the plan in one document. |
| 2 weeks out | Build one example app yourself in 90 minutes with the same tool. Note every place you got stuck. |
| 1 week out | Message everyone: bring a laptop and charger, create the tool account beforehand, arrive 15 minutes early. |
| Day before | Walk the venue. Test Wi-Fi, projector and extension cords. Print a sign-in sheet as backup. |
| Event day | Run the schedule below. |
| Day after | Send the recap and links. Thank partners and the venue. Announce the next date. |
Step 3: set up registration
Student events are often run on Luma, a Google Form or a Facebook event. Whichever you choose, send people to one link only. If you use Luma, its help center describes the controls that matter most for a small room (help pages checked 18 Nov 2026):
- Capacity and waitlist. In the registration settings you set a maximum capacity and switch on the over-capacity waitlist. Only approved guests count toward capacity, and hosts approve or decline waitlisted guests by hand.
- Approval and questions. Ticket types can require approval, and you can add registration questions beyond name and email. Ask "What do you want to build?" and "Have you used an AI app builder before?" so you can balance the room.
- Messages. Event blasts let you send or schedule updates to guests, which replaces manual reminder emails.
- Check-in. You can check guests in at the door by scanning tickets.
Expect some no-shows. Free events often see a gap between sign-ups and arrivals, so approve a few more people than seats if your venue allows it, and keep the waitlist active. For a comparison of tools, see Luma vs Facebook Events.
Step 4: pick the tool and test it
One tool for everyone is the biggest time-saver. When all participants use the same AI app builder, one mentor can help anyone. Ask the tool's team in advance whether they can provide credits for a student event, and sign up yourself first to find the free-plan limits.
Your 90-minute test build tells you three things: how long a simple app really takes, what error messages beginners will hit, and whether your Wi-Fi can handle 40 people logging in at once.
Step 5: the day-of schedule
A schedule that works for a five-hour afternoon (our suggestion, adjust to your room):
| Time | Block |
|---|---|
| 0:00 to 0:20 | Doors, name tags, Wi-Fi, sign in to the tool |
| 0:20 to 0:35 | Welcome, the goal sentence, the rules, how voting or judging works |
| 0:35 to 1:00 | Pick a prompt or track; start building |
| 1:00 to 3:45 | Build time, mentors circulate. Short break at the halfway mark |
| 3:45 to 4:00 | Hard stop: everyone posts a link |
| 4:00 to 4:45 | Try each other's projects, leave feedback, vote |
| 4:45 to 5:00 | Results, thanks, date of the next session, group photo |
Rules that help:
- Define "shipped" as a live link. A slide or a screenshot is not shipped.
- Keep announcements under five minutes in total. People came to build.
- Give mentors a visible signal, such as a coloured sticker, so stuck people can find them.
- Do not add speakers. If a sponsor wants to talk, give them five minutes at the start.
Step 6: after the event
Most events lose their energy the next morning. Protect it:
- Post the recap with a link to every project within 48 hours (see the event recap template).
- Give every team somewhere to keep working. On buildtolaunch, builders can continue in project Spaces with an AI teammate and post updates to the weekly Launch League board.
- Put the next date in your recap.
- A month later, count return attendance and launches posted, not just the headcount (community metrics that matter, after the event: measuring whether your build day worked).
Where buildtolaunch can help
buildtolaunch is free for university students across Southeast Asia, with no coding needed to start. If you are hosting, its Events page lists upcoming events, and the Vibe-a-thon Saigon recap shows one afternoon format that worked. The Launch League can serve as a public board where participants post and vote. For a longer list of ideas, see 25 meetup ideas for university tech clubs.
Read the full guide: Build days and builder communities.
FAQ
How long does it take to organize a student hackathon or build day?
Plan on about six weeks for a build day with 30 to 80 people, and eight to ten weeks for a full hackathon with overnight cover. The long items are the venue, the helpers and the tool credits. If you already have a room and a club, you can compress a small build day to three or four weeks.
How many helpers do I need?
For an afternoon build day, three to five people are enough: a lead, a floor mentor, a registration person and a photographer. Add one mentor for every 10 to 15 participants if many are beginners. A hackathon needs more, plus someone responsible for the venue overnight.
Do I need sponsors to host one?
No. A build day can run with a free room, free-plan tools and snacks you ask people to bring or buy themselves. Sponsors help with food, prizes and tool credits, but a small event without them is better than a large one that never happens. See how student organizers get sponsors and tool credits.
Do I need judges?
Not for a build day. Letting participants try each other's projects and vote removes the need to recruit a panel and gets everyone testing real apps. For a hackathon with prizes, use judges and a written rubric so the results feel fair.
Can people with no coding experience take part?
Yes, if you choose an AI app builder where participants describe what they want in plain language. Make sure the prompt starts from something familiar, and have mentors who know the tool well. Beginners should finish with a live link, even a simple one.
What should I do the week after the event?
Send the recap with project links, thank the venue and partners, and invite attendees to the next session with a date. Ask each team what they will do next week in one line. The first week after decides whether people come back.