Chapter 14: Schedule Design
Pacing, energy, and the art of not over-programming
Your schedule is the rhythm of your event. Get it right and participants flow naturally from kickoff to demos. Get it wrong — too packed, too loose, or badly paced — and you lose people.
This chapter covers how to design schedules that maintain energy, respect focus time, and work for different event durations.
The core principle: protect hacking time
Here's the thing most first-time organisers get wrong: they over-programme. They fill the schedule with speakers, activities, workshops, and "energisers" because they're worried participants will get bored.
Participants don't get bored during hackathons. They get bored during interruptions.
Once teams are working on their projects, the room's focus is precious. Mid-day speakers, surprise video calls, and non-essential announcements break flow and frustrate people who are deep in problem-solving. What feels "fun" to an organiser often feels like an interruption to someone in the zone.
Your job as a scheduler: Create clear start and end bookends, provide structure around meals and deadlines, and then get out of the way.
Schedule templates
One-day hackathon (8–10 hours)
A compact format that works well for beginners and community events.
8:30 AM — Doors open, registration, coffee, networking
9:00 AM — Opening ceremony (30 min): welcome, theme, challenges, logistics, team formation
9:30 AM — Team formation and project scoping (30 min)
10:00 AM — Hacking begins
10:00–12:00 — Hacking (workshops available in a separate room, optional)
12:00 PM — Lunch (45 min)
12:45–4:30 PM — Hacking continues
3:00 PM — Checkpoint announcement: "2 hours left. Start thinking about your demo."
4:30 PM — Submissions due
4:45 PM — Demos and judging (45–60 min)
5:45 PM — Winners announced, closing remarks
6:00 PM — Wrap-up, networking, optional after-event drinks
24-hour hackathon (Friday evening to Saturday evening)
The classic overnight format.
Friday:
6:00 PM — Doors open, registration, dinner, networking
7:00 PM — Opening ceremony (45 min)
7:45 PM — Team formation (30 min)
8:15 PM — Hacking begins
11:00 PM — Late-night snacks available
Saturday:
8:00 AM — Breakfast available
12:00 PM — Lunch
1:00 PM — Checkpoint: "Halfway there. Scope down. Focus on what you can finish."
3:00 PM — Afternoon snacks
4:00 PM — "2 hours left. Focus on your demo."
5:30 PM — Submissions due
5:45 PM — Demos and judging (60–90 min)
7:00 PM — Winners announced, closing ceremony
7:30 PM — Event ends, optional social
A note on overnight hacking: You can allow overnight work, but don't glorify or encourage it. Set up a quiet rest area. Remind people that sleep makes them more productive, not less. The all-nighter hackathon culture is unhealthy and we should move away from it.
48-hour hackathon (Friday evening to Sunday afternoon)
The full weekend experience.
Friday:
6:00 PM — Doors open, registration, dinner
7:00 PM — Opening ceremony (45 min)
7:45 PM — Team formation
8:30 PM — Hacking begins
11:00 PM — Late snacks
Saturday:
8:00 AM — Breakfast
9:00 AM–12:00 PM — Hacking (optional workshops in a separate room)
12:00 PM — Lunch
1:00–6:00 PM — Hacking continues
3:00 PM — Afternoon snacks, checkpoint announcement
6:00 PM — Dinner
7:00–10:00 PM — Hacking continues
10:00 PM — Late snacks, encourage rest
Sunday:
8:00 AM — Breakfast
9:00 AM–12:00 PM — Final hacking push
10:00 AM — "3 hours left. Start wrapping up."
11:00 AM — "2 hours. Focus on demos."
12:00 PM — Submissions due, lunch
1:00 PM — Demos and judging (90–120 min)
3:00 PM — Winners announced, closing ceremony
3:30 PM — Group photo, networking, event ends
The opening ceremony
Your opening sets the tone for the entire event. Keep it tight — 30–45 minutes max. People are itching to start building.
Structure:
Welcome & introductions (5 min) — Introduce the organising team, thank sponsors by name (show logos), acknowledge partners.
Event overview (5 min) — Theme, objectives, schedule with key milestones, Code of Conduct reference.
Logistics (5 min) — How to access resources (BuilderBase, APIs, docs), where to get help (mentors, Slack channels), food schedule, submission deadline and format, social media hashtag.
Judging & prizes (3 min) — Criteria explained, prizes announced, demo format clarified.
Newcomer welcome (3 min) — This is critical. Ask first-timers to identify themselves (raise hands, type in chat). Celebrate them. Applause, shoutouts, genuine welcome. Reassure them they have value to contribute. This single moment resets the room from "competitive veterans" to "inclusive community."
Project pitches (1 min per pitch, hard cap) — Format: problem, proposed solution, skills needed. Only people who will actually work on the project get to pitch — no "I have an idea but won't be here" slots. Coach pitchers to frame as "here's why my day is going to be awesome" not "I need people." Keep strict time limits.
Team formation (facilitated immediately after pitches).
Kickoff — "Let's build!"
The closing ceremony
Bookend the event with the same energy you started with. 30–60 minutes.
Structure:
Project showcase — For small events (under 20 teams): each team presents 1–2 minutes. For large events: showcase finalists or play demo videos.
Winner announcements — Build anticipation. Announce category winners first, then 3rd → 2nd → 1st. Celebrate every winner.
Thank yous — Participants, sponsors (by name, again), judges, mentors, speakers, volunteers, organising team.
Closing remarks — Feedback survey link, post-event community info, any next steps, tease next event if planned.
Group photo — Get everyone together. This becomes your best marketing asset for next time.
Workshops: when and how
If you're running workshops alongside hacking:
Always in a separate room. Never interrupt the main hacking space.
Schedule them early. Workshops in the first few hours give newcomers something to do before they're ready to hack. After lunch, most people are deep in their projects and won't leave for a workshop.
Keep them interactive. Lectures don't work at hackathons. Follow-along, hands-on workshops where participants build something work.
45–90 minutes is the sweet spot.
Record everything. Someone will miss the workshop and want to catch up later.
Energy management
Over the course of an event, energy follows a predictable curve:
High energy: Opening ceremony, first hour of hacking, demo presentations
Low energy: Mid-afternoon (especially after lunch), overnight (24hr+ events), the hour before submissions are due (stress, not low energy)
To manage the curve:
Serve lighter lunches (avoid heavy carbs that cause afternoon crashes)
Keep coffee and water continuously available
Make mid-afternoon checkpoint announcements encouraging and practical, not just nagging about deadlines
For overnight events: designate a quiet rest area, actively encourage breaks
The final countdown warnings create natural energy — use them
Key takeaways:
Protect hacking time above all else — don't over-programme
Opening ceremony: 30–45 min max, include a newcomer welcome moment
Project pitches: 1 min each, hard cap, only people working on the project
Schedule workshops in the first few hours, in a separate room, always interactive
The countdown sequence (3hr → 1hr → 30min → 10min) creates natural structure and urgency
Don't glorify all-nighters — encourage breaks and rest