Rules for Your Hackathon

Being extra clear ahead of time can prevent headaches down the road

Check out our full recommended rule list at https://github.com/MLH/mlh-hackathon-rules/blob/master/Rules.md

Making your rules clear will help you keep your hackathon fair for all attendees, and easily be able to point to specific rules if you have to disqualify hackers for cheating.

We know that some hackathons vary though, so are including some specific rules your team should decide on.

• How many people per team?

  • Can hackers participate solo?

  • Can the teams be as large as they want, and you might just have only 4 prizes?

  • We see hackers have the most success with teams of a maximum size of 4

• Can they crosspost to other hackathons on the same weekend?

  • If there is a digital event in the same timeframe of your event can they submit to both?

  • We generally recommend no but you should very clearly state this

• Do they have to submit code?

  • Is there a specific format?

    • GitHub link, repl.it, Google drive link, etc?

• Can they use publicly available frameworks?

  • Do they need to list said frameworks in a readme?

• Can they make multiple projects?

  • Recommend No

• Can they submit to multiple challenges?

  • Recommend Yes

• Deadline for submissions / time they can work on their projects

  • Make it very clear they cannot work on their project before the event.

• Will judging will be in person?

  • Will it be science fair style?

    • Recommended

  • Or will everyone demo to the larger group

    • Recommended only for very small events

• Who is allowed to participate

  • Students only?

  • Age Range?

  • No mentors/volunteers/organizers

• Are there any categories that require hackers to be a specific demographic?

  • Example: Beginners track where at least half the team must have this be their first hackathon.

  • Make sure to state how many of the team members must fit the category in your rules before the event.