> For the complete documentation index, see [llms.txt](https://hackdays-guide.mlh.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hackdays-guide.mlh.com/plan-your-event/sample-schedules.md).

# Recommended Hack Day Schedule

Copy and adapt one recommended run of show for a focused Hack Day.

We suggest aiming for an event of around six hours. That gives teams meaningful time to build while leaving enough time for submissions, demos, judging, and closing.

The format works for workplace programs, professional meetups, community events, and student-led groups.

## Build Your Schedule

Set your event length, start time, and expected number of teams. The generator adjusts build and demo time while always including time for project submission, judging, marking winners, publishing the project gallery, and closing.

Review [Project Submissions and Judging](/run-your-event/project-submissions.md) before finalizing the schedule so the submission window and demo format match the required workflow.

{% @mlh-hack-day-schedule/schedule-generator content="" %}

## Recommended Starting Point

The generator starts with this six-hour run of show. It assumes approximately six teams, food served during build time, no workshop, and a small enough event to complete check-in promptly. Open doors early if your venue expects a queue. Use the generator above to apply real clock times or add optional program blocks.

Make food available during building rather than stopping the whole event for a meal or snack break. Teams can take a break when it suits them while the build space and mentor support remain available.

| Elapsed time | Activity                                                                         | Organizer checkpoint                                                                                                                            |
| ------------ | -------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| 0:00–0:15    | Doors open and OrganizerHQ check-in                                              | Confirm every attendee is checked in; open doors earlier if your venue expects a queue                                                          |
| 0:15–0:30    | Welcome, MLH opening material, Code of Conduct, schedule, and partner categories | Show the submission URL and deadline                                                                                                            |
| 0:30–5:15    | **Build time**                                                                   | Includes team formation and idea alignment; help teams define a realistic scope, then remind them at 60 and 30 minutes before submissions close |
| 2:45–3:15    | **Food available during build time**                                             | Offer a meal or snacks while keeping the build space open so teams can eat without stopping work                                                |
| 4:45–5:15    | **Project submissions during build time**                                        | Teams keep building while one member submits in OrganizerHQ and selects each eligible partner challenge                                         |
| 5:15–5:45    | Project demos for approximately six teams                                        | Use a visible timer and a consistent demo format                                                                                                |
| 5:15–5:45    | **Judging and winner declaration during project demos**                          | Score projects as they are presented, mark every MLH partner winner, and make the project gallery public before closing                         |
| 5:45–6:00    | Closing ceremony and group photo                                                 | Announce winners after the saved results and public gallery have been checked                                                                   |

## Make It Shorter or Longer

For a shorter event, give teams more time to build by asking participants to arrive with ideas or teams where practical. Reduce the number or length of demos before compressing submissions, judging, recording winners, or closing; those are the steps most likely to fail when an event runs late.

For a longer event, add building time, mentor support, a focused workshop, or more demo time. For events of seven hours or more, the generator may reserve up to 90 minutes for project demos when the team count requires it. A Hack Day must run for at least 3 hours and may not exceed 12 hours.

## Adjust for Attendance

The simplest format is for every team to give one short demo to the whole room; use that approach whenever it fits. If you expect more teams than the demo block can reasonably support, shorten each demo first. If whole-room demos are still impractical, use [science-fair-style judging](https://guide.mlh.com/general-information/judging-and-submissions/judging-plan) as a fallback: teams remain with their projects while judges move between them. This format requires more coordination, so avoid it unless the team count makes it necessary.

For broader scheduling advice for full-scale or more complex events, see the [MLH Hackathon Organizer Guide](https://guide.mlh.com/general-information/hackathon-scheduling/detailed-run-of-show).