Dates

Hackathon duration: 23 July 2025 - 15 September 2025, 1:00PM (SGT)

Milestone Check 1 (mandatory): 4 August 2025 - 8 August 2025 (subject to availability)

Milestone Check 2 (mandatory): 1 September 2025 - 5 September 2025 (subject to availability)

Judging Day: 15 September 2025, 9:00AM - 6:00PM (SGT)

Judging eligibility

1. You must pass all milestone checks. 

Milestone Check 1: 4 - 8 August

You will be required to present your selected problem statement, your planned solution and a plan for how your team will be implementing the solution (including what technologies your team will be using). 

Milestone Check 2: 1 - 5 September

You will be required to show significant progress in the development of your solution, including but not limited to designs or a partially working prototype.

2. All submissions must be done by Judging Day, 15 September 2025, 1:00PM (SGT)

3. You may choose to attend any of the upcoming workshops to gain more skills that will help you with your project. All hardware teams must attend at least one hardware workshop (either EIG 3D Modelling or EIG-Overflow IoT).

4. Each team must have at least one member physically present on Judging Day, 15 September 9:00AM – 6:00PM (SGT). More details on Judging Day will be released at a later date on our Telegram chat.

Project and Submission Requirements

All project submissions must be made via Devpost on this site.

  • Project Name
  • Project Description and details
  • 3-5 pictures or screenshots of your solution
  • GitHub Project Link (Must be open sourced)

You are prohibited from: 

  • Violating any applicable laws or regulations.
  • Encouraging or promoting illegal activity or violation of third-party rights.
  • Creating or operating any software or service that includes elements of pornography or online gambling.
  • Infringing upon the intellectual property rights of others.
  • Transmitting any harmful or malicious code.
  • Collecting or harvesting any information about your users without their consent. 

Prizes

Attractive tech-themed prizes will be given to the top team working on each problem statement.

Judging Criteria and Winner Selection

The winner will be the team with the highest points based on this judging criteria. All presentations are limited to 5 minutes followed by a 5 minutes Q&A.

Criteria Description Weightage
Innovation & Creativity Is the idea original or a fresh take on an existing problem? 25%
Technical Implementation Are the software and/or hardware components well-developed, functional, and technically sound? Does the solution demonstrate solid technical skills or engineering thinking? 25%
Value & Usability Does the solution provide real-world value and is it user-friendly? 20%
Problem-Solution Fit How well does the solution address the chosen problem statement? 20%
Pitch & Communication Was the idea clearly and confidently presented? Did the team explain it well? Were the judges able to resonate with the solution developed? 10%

Intellectual Property

Any intellectual property developed during the hackathon will belong to the team that developed it. The division of intellectual property between team members is the responsibility of the team, and the organisers will not be held responsible for any intellectual property disputes between team members. 

Plagiarism and Cheating

HackIT's organising team does not tolerate any cheating or plagiarism of other teams' projects as it is against both the HackIT and Ngee Ann Polytechnic's policies. If you are caught cheating or plagiarising another team’s project, your team will be disqualified immediately. 

If a team is suspected of cheating, they may be asked to provide:

  • Source code
  • Version control history (if applicable)
  • Any other supporting information deemed necessary by the organising team 

Code Reuse 

Using frameworks (e.g. React, Flutter), third-party packages, libraries and services (e.g. Firebase), and templates (e.g. create-next-app) are allowed for this competition. 

Further Actions 

The organisers reserve the right to determine what constitutes cheating in any given situation. 

We strongly encourage all participants to clarify doubts regarding code reuse early on. If you’re unsure whether your use of code is acceptable, please contact an organiserWe are more than happy to answer any such questions so that your efforts during the hackathon do not go to waste. Please provide any information that would help us along with email, such as the source code for software projects or the list of equipment used for hardware projects.