Skip to main content

Submission & Judging Guide

Team Registration​

Your team needs to be registered by 11:00pm on Saturday. YOU MUST HIT SUBMIT ON THE FINAL SCREEN OR YOU WILL NOT BE REGISTERED. Don’t worry, you do not have to have your whole project done by this time. This is just to make sure your team is registered on Devpost. You will have until 12:00pm on Sunday to fully submit your project.

Follow this guide on how to register your team: Devpost Guide

👥 Team Formation

The maximum number of members in a team is 4. Don’t worry if you don’t have a team — a hackathon is a great place to meet new people! After the opening ceremony, we will have a teambuilding session where you can find people to hack with. Additionally, we will provide a teambuilding channel in Discord where you can find teammates.

Your project needs to be finalized by 12:00pm (noon) on Sunday! No edits should be made to your project after that time. Make sure you have at least the following:

  • Project Title and Description
  • Challenges/Tracks you are submitting to
  • Code Repo (i.e GitHub) or Zip file
  • Demo Video (should ONLY be a demo - not your entire presentation, maximum of 2 minutes)

Devpost

You will submit your project here

If you need help using Devpost, please refer to the Devpost Guide for step-by-step instructions.

Submission Rules​

Any violation of these rules will result in immediate disqualification of your team and project

  • 1 hacker minimum and 4 hackers maximum per team
  • Only submit to HackUTD — projects that submit to other hackathons will be disqualified
  • You should add a link to your code on Devpost — project demos with a working product yet have no code uploaded will be disqualified. No changing uploaded code after the deadline.
  • Public frameworks and libraries are allowed, but submitting only copied code will result in disqualification
  • Each hacker is only allowed to be a part of and create one project during this hackathon
  • You may only submit to two sponsor challenges but are free to submit to as many general tracks as you’d like (design, hardware, beginner)
  • To be eligible for the beginner track 3/4 of your team must be first time hackers
  • Anything presented at judging should only be worked on from noon on Saturday to noon on Sunday
    • There should be no coding or building before noon on Saturday
    • However, you can ideate beforehand with your team!

Important Timings​

  • Nov 8th, 11:00 PM (Saturday Night) - Devpost Team Registration Due
  • Nov 9th, 12:00 PM (Sunday at Noon) - Final Project Due on Devpost

Judging

Projects need to submitted on Devpost. A few important things to note:

  • Judging is done in-person.
  • All teams will be given a table to set up their presentation below (see sheet below, will be linked on Sunday).
  • You’ll be judged multiple times over the course of 3 hours and should stay for the entire time

Judging Tips​

  • Have a compelling 30 second pitch that clearly explains why your solution is useful to grab the attention of judges.
  • A functional live demo of your project is the best way to show what you have accomplished.
  • Support your demo with a brief presentation that explains the problem you're solving, the tech stack you used, and the project's future steps.
  • Presenting with enthusiasm and positive body language (despite the possible lack of sleep) shows the judges you are passionate and proud of your work, which leaves a good impression.

Judging Maps​