• Event: Friday, February 27 – Sunday, March 1 (CT)

• In-person check-in required: 3:00 PM CT on Friday, Feb 27

• Track / track path selection due: 11:00 PM CT on Saturday, Feb 28

• Final project submission: Submitted on Devpost by the posted deadline

• This is an in-person event — you must check in onsite to participate.

• You must comply with the event Code of Conduct and all posted hackathon rules.

• Teams are allowed. All majors and skill levels are welcome.

To be eligible for prizes and judging, your Devpost submission must include:

1. Track Path Selection (Required)

   • You must submit your track / track path by 11:00 PM CT on Saturday, Feb 28.

   • Multiple tracks are allowed, but your submission must clearly explain how your project fits each track entered.

2. Public GitHub Repository (Required)

   • You must provide a link to a public GitHub repository containing your project code and/or relevant build files.

   • Judges must be able to access your repo without requesting permissions.

3. 3-Minute Demo Video on Devpost (Required)

   • You must upload a ~3 minute demo video directly to Devpost.

   • Your video should clearly show: what the project does, how it works, and a working demo/prototype.

4. Project Description (Required)

   • Include a clear description of your project, what problem it solves, and how it relates to the theme/track(s).

   • Add setup/run instructions if applicable.

5. Build Window / Originality

   • Your project should be created during the hackathon window. You may use open-source tools/libraries/APIs, but credit external resources and clearly indicate what you built during the event.

• Prizes will be awarded by track and/or overall placement (as listed on Devpost and announced during the event).

• Only teams that meet all submission requirements are eligible for prizes.

• Organizers reserve the right to reassign awards if a submission violates rules or is incomplete.

Judges will score projects using the following:

Technical Ability

• The technology used is impressive and shows initiative beyond simply copying past creations and piecing them together.

• Hackers demonstrate a level of execution and problem-solving that exceeds what might be expected from a short build sprint.

Creativity

• The project explores a new technology or introduces unique ideas.

• The approach is fresh, exciting, or unexpectedly clever.

• It’s clear the team had fun building and is passionate about what they created.

Theme and Goal

• The project aligns with the hackathon theme and has a clear objective.

• The design and features reflect thoughtful consideration of the theme.

• The team communicates what they set out to achieve and why it matters.