> 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/run-your-event/project-submissions.md).

# Project Submissions and Judging

Open submissions, collect every presenting project, and judge each eligible challenge consistently.

*Last reviewed: August 2026.*

Every presenting project must be submitted through the event's **Challenges** page. Teams must also select each eligible partner challenge they are entering. Devpost, a form, or another platform does not replace this flow.

## Set the Submission Window

An organizer controls when teams can submit:

1. Open the public event page while signed in as an organizer.
2. Select **Manage Submissions**.
3. Under **Submission Deadline**, set the **Submissions open** and **Submissions close** date and time.
4. Select **Save deadline**.
5. Check the status at the right of the section. It shows **OPEN** while submissions are available.

Open submissions during build time and close them at the project deadline, before demos begin. If the deadline changes, update it here and communicate the same change to every team.

<figure><img src="https://3055709124-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJmh9SgoamU1I7ykefuED%2Fuploads%2Fgit-blob-084b17d24e70dc160ad128530d5952896774a2d5%2Fmanage-submissions-empty.png?alt=media" alt="Manage Submissions page with controls for submission open and close times"><figcaption><p>Set and save the submission window from Manage Submissions.</p></figcaption></figure>

## Before Building Begins

Tell hackers:

* The exact submission deadline
* Which partner and local challenges are available
* The required project information
* The demo format and time limit
* The judging criteria
* That every presenting project must be submitted, even if it is not entering a partner challenge

Open the **Challenges** page yourself and confirm that every challenge assigned by MLH appears correctly. The **Add Submission** button becomes available only during the saved submission window.

Use the [MLH Standard Hackathon Rules](https://github.com/MLH/mlh-policies/blob/main/standard-hackathon-rules.md) as the default: project-specific work happens during the Hack Day. Organizers may use a different approach when it suits their event, but must communicate it clearly before building begins.

## How Teams Submit Projects

One team member should submit the project on behalf of the team:

1. Sign in using the account used to register for the event.
2. Select **Challenges** in the “View and submit challenges for this event” banner.
3. Select **Add Submission**.
4. Enter the project link, project name, description, and technologies used.
5. Add a demo URL if the team has one.
6. Under **Which challenge(s) are you submitting to?**, select every partner and local challenge the project is eligible to enter.
7. Select **Submit Project** before the deadline.

<figure><img src="https://3055709124-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJmh9SgoamU1I7ykefuED%2Fuploads%2Fgit-blob-1d2babe7f603fda698656b60ad35d3d39ffa5b66%2Fchallenges-submissions-open.png?alt=media" alt="Hack Day Challenges page with assigned and local challenges and an active Add Submission button"><figcaption><p>Teams start from the event's Challenges page while submissions are open.</p></figcaption></figure>

<figure><img src="https://3055709124-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJmh9SgoamU1I7ykefuED%2Fuploads%2Fgit-blob-7b0e7e54a0fcf84fd350119434de4aaa498b13d5%2Fproject-submission-form.png?alt=media" alt="Project submission form with project link, name, demo URL, description, technologies, and challenge selections"><figcaption><p>Complete the required project fields and select every eligible challenge before submitting.</p></figcaption></figure>

{% hint style="info" %}
The same project can appear once for every challenge it selected, and the total shown in Manage Submissions may count those challenge entries. This is expected; do not treat them as duplicate project forms.
{% endhint %}

## Verify Every Project Before Demos

Return to **Manage Submissions** before demos begin:

1. Identify each unique project in the **All** view and compare it with the teams scheduled to present. Do not rely on the headline total when projects entered more than one challenge.
2. Use the challenge tabs to confirm that each assigned partner category has the expected entries.
3. Search by project, hacker, or technology when you need to find a specific submission.
4. Ask a missing team to submit while the window remains open. Apply the same deadline policy to every team.
5. Confirm that the submission window is closed when demos begin, then refresh the list.

<figure><img src="https://3055709124-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJmh9SgoamU1I7ykefuED%2Fuploads%2Fgit-blob-180b4493b920fbec8e9a115f4c2dd655e619d3be%2Fmanage-submissions-projects.png?alt=media" alt="Manage Submissions page with project cards, challenge filters, search, and Mark Winner buttons"><figcaption><p>Review unique projects and use each challenge filter to confirm coverage before judging.</p></figcaption></figure>

## Use a Simple Judging Rubric

Score every eligible project using the same criteria. A lightweight rubric works well for short events:

| Criterion                | What judges should consider                                                   |
| ------------------------ | ----------------------------------------------------------------------------- |
| Technical implementation | Does the project work, and how effectively does it use the chosen technology? |
| Creativity               | Is the idea or implementation distinctive?                                    |
| Learning and ambition    | What did the team learn or attempt during the Hack Day?                       |
| Demo and clarity         | Can the team clearly explain the problem, solution, and implementation?       |
| Partner eligibility      | Does the project satisfy the assigned partner's specific requirements?        |

Tell judges how to handle ties before judging starts. A judge should disclose a close relationship with a team and recuse themselves when that relationship could affect the result.

## Select Proposed Winners

For each MLH partner category:

1. Filter Manage Submissions to the relevant challenge.
2. Confirm that the project appears under that challenge.
3. Verify the partner-specific evidence described on the relevant partner page.
4. Select the strongest eligible project using the published rubric.
5. Record the proposed result in the judges' notes.

Do not announce a winner yet. Continue to [Closing Ceremony and Winner Declaration](/run-your-event/closing-ceremony-and-winner-declaration.md) to mark each winner, verify the saved result, and make the project gallery public.