Judging will take place after the hacking period ends at 12pm on Sunday, Jan 28th, 2024. Winners will be announced throughout the Closing Ceremonies from 3-5pm Sunday, Jan 28th, 2024.


If you applied to McHacks 11, received an acceptance and also confirmed your attendance, you are eligible to attend McHacks. If you attended and participated at McHacks 11, then you are eligible to make a submission. Each team must consist of up-to 4 participants.


  1. All submissions must be made by participants accepted to and physically at McHacks.
  2. All code written for a submission must be written by the submitting team at McHacks during the designated hacking time, with the exception of third-party libraries publicly available to every participant.
  3. All teams must not exceed 4 participants.
  4. Submitting the same project to multiple hackathons is strictly forbidden. Failure to do so results in immediate disqualification.
  5. You are strictly prohibited from starting your project prior to the hacking period. Failure to do so results in immediate disqualification.
  6. After the hacking period, you are allowed to edit your project only after Judging is completed. Failure to do so results in immediate disqualification.
  7. You are prohibited from outsourcing code or aid from non-McHacks 11-affiliated people, such as non-registered participants. Failure to do so results in immediate disqualification.
  8. All final judging decisions are at the discretion of the HackMcGill organising team.
  9. All teams must abide by the following requirements outlined under the section, “Main requirements”. This applies to the subsection, “Additional requirements”.
  10. In the event that any of these guidelines are not followed, McHacks reserves the right to revoke prizes and disqualify teams.

Our hackathon is dedicated to providing a harassment-free experience for everyone, regardless of the following:

  • gender
  • gender identity and expression
  • age
  • sexual orientation
  • disability
  • physical appearance
  • body size
  • race
  • ethnicity
  • nationality
  • religion
  • previous hackathon attendance or lack of
  • computing experience or lack of
  • chosen programming language or tech stack

Read the McHacks code of conduct at