Why the agenda matters
A clear, published hackathon agenda does three things: it sets expectations, it protects the submission deadline, and it stops the day-of "wait, what's happening now?" chaos. Build it once, share it everywhere (registration page, dashboard, the room's projector), and the event runs itself.
Below is a template you can copy for a classic 48-hour hackathon, plus a tighter 24-hour version. If your event runs remotely over a week rather than a weekend, the shape changes — the online hackathon formats guide covers the async and staged alternatives.
48-hour hackathon agenda
| Time | What's happening |
|---|---|
| Day 1 — 17:00 | Doors open, check-in, food |
| 18:00 | Opening ceremony — rules, schedule, prizes |
| 18:30 | Theme reveal + Q&A |
| 19:00 | Teams form / finalize on the teambuilding board |
| 19:30 | Hacking begins ⏱️ |
| 22:00 | Mentor office hours (round 1) |
| Day 2 — 09:00 | Breakfast + standup |
| 11:00 | Mentor office hours (round 2) |
| 14:00 | Mid-point check-in / progress demos (optional) |
| 20:00 | Workshop or social break |
| Day 3 — 00:00 | Late-night push (snacks!) |
| 09:00 | Breakfast |
| 11:00 | Submission deadline — hard stop 🚩 |
| 11:30 | Setup for presentations |
| 12:00 | Team presentations (3–5 min each) |
| 14:30 | Judging & scoring |
| 15:30 | Awards ceremony + leaderboard reveal |
| 16:00 | Wrap-up, photos, certificates |
24-hour hackathon agenda
| Time | What's happening |
|---|---|
| 10:00 | Check-in + opening |
| 10:30 | Theme reveal, teams form |
| 11:00 | Hacking begins ⏱️ |
| 14:00 | Mentor hours |
| 19:00 | Dinner + check-in |
| Day 2 — 10:00 | Submission deadline 🚩 |
| 10:30 | Presentations |
| 12:00 | Judging |
| 13:00 | Awards + certificates |
Tips for a schedule that survives contact
- The submission deadline is the one immovable line. Put it in bold, announce it at the start, and send reminders at T-2h, T-30m and T-5m.
- Front-load mentor hours — teams need direction early, not at hour 40.
- Keep presentations short (3–5 minutes) and time them strictly, or judging runs into the night.
- Build in slack. Something always overruns; a 30-minute buffer before judging saves you.
In HackathonHost, your agenda lives on every participant's dashboard, the submission deadline is enforced automatically, and Live Control steps you through presentations with a timer. Pair this with our guides on running a game jam and judging criteria.
