Eligibility

Open to current post-secondary students aged 18+.
Teams of 1 to 5 people. You can form a team at the event.
Hackers must attend in person to demo and win prizes.
Organizers, judges and mentors can’t compete for prizes.

Building your project

All project work must start after hacking begins on Friday, November 13. You can plan ideas beforehand, but you can’t write code before the start.
You may use open-source libraries, frameworks, public APIs, templates and starter code. Say in your Devpost write-up what you used.
AI tools: AI coding assistants are allowed. Say how you used them on Devpost; judges score what your team built and understands.
Each team can submit only one project.
Pushing code to your repo after the submission deadline can make you ineligible. You can still update your Devpost page during judging.

Judging
Projects are scored 1 to 5 on each of five criteria, for a total out of 25:

Execution: Does it work?
Complexity: How much skill did it take?
Polish: Is it usable and presentable?
Originality: Have we seen this before?
Utility: Does it meet a real need?

Ties are broken by Execution, then Utility. Judges’ decisions are final. Organizers check eligibility (team rules, commit history) before announcing winners.

Ownership: Teams keep full ownership of their projects. By submitting, you let HackEd and the CompE Club show your project name, description and screenshots when promoting the event.

Prizes: Prizes go to the team members listed on the Devpost submission. Physical prizes are handed out at the closing ceremony; anything else is delivered within the week. Organizers can substitute a prize of equal value.

Code of Conduct
Everyone at HackEd Beta (hackers, mentors, judges, sponsors, volunteers) must follow the HackEd Code of Conduct, at DICE and on Discord. Harassment of any kind is not tolerated. Organizers may warn, remove or disqualify anyone who breaks it. To report a problem, talk to any organizer.
Full Code of Conduct: Code Of Conduct