> 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/start-here/requirements-and-eligibility.md).

# Requirements and Eligibility

Confirm the required event format, organizer responsibilities, and partner eligibility before applying.

*Last reviewed: August 2026.*

Use this page as the source of truth for Hack Day program requirements. Your event approval and onboarding materials may add partner-specific conditions.

## Required

Every Hack Day must meet all of these requirements:

* **Receive MLH approval.** Submit a Hack Day application and wait for approval before advertising MLH or an MLH partner.
* **Remain free.** Do not charge an entry, ticket, membership, or required participation fee.
* **Take place entirely in person.** Registration and event communications may happen online, but virtual rounds and hybrid participation are not permitted.
* **Run for 3 to 12 hours.** Four to six hours is ideal.
* **Use OrganizerHQ as the event system of record.** Use it for registrations, day-of check-ins, project submissions, and MLH partner prize winners.
* **Collect every presenting team's project in OrganizerHQ.** Every team presenting a project must submit it through OrganizerHQ. Teams must additionally select each eligible partner challenge they are entering.
* **Present the MLH opening material.** Show the short prerecorded presentation and the partner information assigned to your event.
* **Follow the MLH Code of Conduct.** Share the [MLH Code of Conduct](https://github.com/MLH/mlh-policies/blob/main/code-of-conduct.md) and make its reporting information available during the event.
* **Complete event closeout.** Submit the required event summary, photos, winner records, and eligible receipts.

{% hint style="warning" %}
Do not substitute Devpost, a form, or another project platform for OrganizerHQ. You may use another tool as an optional judging aid, but the required projects and winners must still be recorded in OrganizerHQ.
{% endhint %}

## Recommended

MLH strongly recommends that organizers:

* Plan a focused 4–6 hour event using the [recommended Hack Day schedule](/plan-your-event/sample-schedules.md).
* Use an accessible venue with reliable Wi-Fi, power, seating, and presentation equipment.
* Identify an event lead, a check-in lead, and at least one person responsible for submissions and judging.
* Tell attendees the submission deadline and judging criteria before building begins.
* Keep enough time at the end for demos, judging, recording winners, and the closing ceremony.

## Optional

Depending on the size and format of your event, you may add:

* Workshops or mentor office hours
* Locally created prize categories
* Team-formation activities
* A theme chosen for your community
* An external spreadsheet or judging tool, provided OrganizerHQ remains the system of record

## General Eligibility

Hack Days may be organized for workplaces, professional communities, civic groups, clubs, schools, and other local organizations. Participants may include professionals, students, and community members unless your event approval or assigned partner program specifies a narrower audience.

Partner assignment is not guaranteed. MLH will confirm the eligible audience, geography, partner categories, and prize format in your approval or onboarding materials.

## Partner Eligibility

| Program        | Organizer and event eligibility             | Participant eligibility                       | Status |
| -------------- | ------------------------------------------- | --------------------------------------------- | ------ |
| Google Gemini  | Assigned by MLH to approved events          | Participants must be at least 18 years old    | Active |
| Google Gemma   | Assigned by MLH to approved events          | Follow the eligibility in your event approval | Active |
| GitHub Copilot | High-school organizers in the United States | Follow the eligibility in your event approval | Active |
| Snowflake      | Assigned by MLH to approved events          | Follow the eligibility in your event approval | Active |
| Cloudflare     | Assigned by MLH to approved events          | Follow the eligibility in your event approval | Active |
| Solana         | Assigned by MLH to approved events          | Follow the eligibility in your event approval | Active |

If your approval and this table disagree, follow your approval and email <hackdays@mlh.io> so the guide can be corrected.

## Definition of Done

Your Hack Day is program-complete when you can answer **yes** to every item:

* [ ] Was the full event free and entirely in person?
* [ ] Did every attendee check in through OrganizerHQ?
* [ ] Did every presenting team submit its project through OrganizerHQ?
* [ ] Did each team select every eligible partner challenge it entered?
* [ ] Did you mark every MLH partner prize winner and publish the project gallery before announcing results?
* [ ] Did you present the required MLH and partner material?
* [ ] Did you submit the event summary and required photos?
* [ ] Did you submit itemized receipts for any requested reimbursement?