HACK312 — Official Hackathon Rules 1. Dates

HACK312 is a fully remote, 48-hour hackathon hosted by Machine Learning at Illinois Tech (ML@IIT).

All times are in Central Standard Time (CST).

  • Friday, 4:00 PM: Hackathon begins and project development opens.

  • Saturday, 5:00 PM: Devpost submissions open.

  • Sunday, 4:00 PM: Hackathon ends and all final submissions are due.

All projects must be submitted through the official HACK312 Devpost page before the deadline.

2. Eligibility
  • HACK312 is open to students, developers, designers, and technology enthusiasts of all experience levels.

  • Participants do not need to be Illinois Tech students.

  • Participants may compete individually or as part of a team.

  • No prior hackathon experience is required.

  • Participants must comply with applicable laws, Devpost's terms of service, and event rules.

  • Participation is free.

Additional eligibility restrictions, if any, will be announced by the organizers before the competition begins.

3. Team Requirements
  • Participants may work individually or collaborate in teams of up to 5 members.

  • Each participant may belong to only one competing team.

  • Each team may submit only one project for judging.

  • All listed team members must have meaningfully contributed to the submitted project.

  • Teams are responsible for coordinating their work and ensuring their submission is completed on time.

4. Project and Submission Requirements Project Tracks

Every submission must address at least one of the following tracks:

Hack Chicago: Develop a technology-driven solution addressing a challenge or opportunity affecting Chicago, its communities, infrastructure, or residents.

Hack Illinois Tech: Develop a technology-driven solution that improves the Illinois Tech student experience, campus services, academic resources, or university community.

Project Development
  • Projects must be developed primarily during the official hackathon period.

  • Participants may use existing libraries, frameworks, APIs, datasets, templates, and open-source tools.

  • Pre-existing projects may not be submitted as entirely new hackathon work.

  • Any reused code, templates, or existing project components must be clearly disclosed.

  • Projects must be original, or participants must have the necessary rights to use included third-party materials.

  • Any programming language, framework, or technology is permitted.

  • Projects should include a functional prototype or proof of concept demonstrating their main functionality.

Required Submission Materials

Each project submission must include:

  1. Project Name: A clear and recognizable title.

  2. Project Description: The problem, proposed solution, functionality, and potential impact.

  3. Selected Track: Hack Chicago or Hack Illinois Tech.

  4. Demo Video: A video demonstrating the project's functionality (recommended length: 2–3 minutes).

  5. Source Code: An accessible GitHub repository or equivalent source code link with documentation.

  6. Technologies Used: A list of major programming languages, tools, APIs, frameworks, and platforms used.

  7. Screenshots or Visuals: Images demonstrating the project and its main features.

A live application or deployed demonstration is encouraged but not required.

All submission materials must be accessible to the judges.

5. Artificial Intelligence and External Tools

The use of AI-powered development tools is permitted, including coding assistants, generative AI models, and automated development platforms.

However:

  • Participants must understand and be able to explain their submitted projects.

  • AI-generated code and content must be reviewed and tested.

  • Participants must disclose substantial use of AI-generated components.

  • Projects should demonstrate meaningful participant contributions, creative problem-solving, and technical implementation.

  • Using AI does not automatically improve or reduce a project's judging score.

6. Judging Criteria

Eligible submissions will be evaluated using the following criteria:

  • Innovation & Creativity (25%): How original or creative is the idea or implementation?

  • Technical Implementation (25%): How effectively was the project developed? Does the prototype demonstrate meaningful functionality?

  • Impact & Relevance (25%): How well does the solution address the selected challenge?

  • Presentation & Demonstration (15%): How clearly is the project explained and demonstrated?

  • User Experience & Design (10%): How intuitive, accessible, and usable is the solution?

Judges will consider the project's scope, complexity, and demonstrated achievements within the hackathon timeframe.

Projects are not required to be production-ready.

7. Prizes and Recognition

Participants may be eligible for:

  • LinkedIn participation badges.

  • Surprise prizes for selected projects.

  • Recognition for outstanding innovation, technical implementation, and community impact.

Specific prize categories, eligibility requirements, and award details will be communicated by the organizers.

Prizes have no guaranteed cash value unless explicitly announced.

8. Code of Conduct

HACK312 is committed to providing a respectful, inclusive, and welcoming environment for all participants.

All participants must:

  • Treat fellow hackers, mentors, organizers, and judges with respect.

  • Refrain from harassment, discrimination, bullying, or abusive behavior.

  • Respect the intellectual property and privacy of others.

  • Avoid plagiarism, intentional misrepresentation, or fraudulent submissions.

  • Refrain from unauthorized access to systems, accounts, networks, or data.

  • Use event communication channels responsibly.

  • Follow the instructions of event organizers and moderators.

Violations may result in warnings, removal from event communication channels, disqualification, or other appropriate actions.

Participants should report concerns directly to the event organizers through official event communication channels.

9. Intellectual Property

Participants retain ownership of the original intellectual property they create during HACK312.

By submitting a project, participants confirm that they have the necessary rights to the materials included in their submission.

Participants also agree that event organizers may display publicly submitted project information, screenshots, descriptions, and demonstrations for hackathon judging, announcements, and event promotion, subject to applicable permissions and platform terms.

HACK312 organizers do not claim ownership of participants' original projects.

10. Fairness and Disqualification

The organizers reserve the right to review submissions for compliance with the published rules.

Projects may be disqualified for:

  • Plagiarism or misrepresentation of work.

  • Failure to meet submission requirements.

  • Submission after the stated deadline.

  • Violations of the code of conduct.

  • Fraudulent or intentionally misleading demonstrations.

  • Other material violations of published competition rules.

Disqualification decisions will be based on reasonable review of the relevant circumstances.

11. Event Changes and Technical Issues

Organizers may make reasonable changes to the event schedule or procedures when necessary due to technical difficulties, platform outages, or circumstances beyond their control.

Material changes affecting participation, deadlines, judging, or prizes will be communicated to participants through official event channels.

Participants are encouraged to submit early to avoid last-minute technical difficulties.

12. Final Agreement

By participating in HACK312, participants acknowledge and agree to follow the official event rules, submission requirements, code of conduct, and applicable Devpost terms.

HACK312 is about innovation, learning, and turning ideas into reality. Build responsibly, collaborate respectfully, and have fun!