Dates and Event Format
  1. The Main Hackathon will take place from 29 to 30 August 2026.
  2. The event will be held in person at COM3 MPH, NUS School of Computing.
  3. Teams will have approximately 24 hours to design and build their projects.
  4. Exact check-in, briefing, submission, judging, and closing times will be announced separately.
  5. Official challenge statements will be released at the start of the hackathon.
Eligibility
  1. LifeHack 2026 is open to university students studying at institutions in Singapore.
  2. Participants from any academic discipline are welcome.
  3. Main Hackathon teams must contain 2–4 participants.
  4. Every team member must complete an individual LifeHack registration.
  5. Participants without a team may register individually and request to be matched with other participants.
  6. A participant may only belong to one Main Hackathon team.
  7. Participants may also join the Algorithmic Hackathon because the two tracks are scheduled separately.
Project Requirements
  1. Each team must address one of the official LifeHack 2026 challenge statements.
  2. Project development must take place primarily during the official hackathon period.
  3. Teams may use open-source libraries, frameworks, APIs, datasets, starter templates, and existing development tools.
  4. Any significant pre-existing code, assets, datasets, or templates must be clearly disclosed.
  5. Submitting an existing completed project as a new LifeHack project is not permitted.
  6. Projects must be the team’s own work and must not plagiarise another person’s work.
  7. Teams are responsible for ensuring that they have permission to use all code, data, media, and other materials included in their project.
  8. Projects must comply with applicable laws and must not contain harmful, discriminatory, abusive, or unlawful material.
  9. Participants may use any suitable technology stack unless a challenge statement specifies additional requirements.
  10. Policies concerning generative AI, sponsor-provided APIs, intellectual property, and confidential data will be clarified before the event.
Submission Requirements
  1. Teams must submit their project before the announced deadline.
  2. Each team should make only one Devpost submission.
  3. Every participating team member must be listed on the submission.
  4. The submission must include a working prototype, project description, source-code repository, and demonstration materials.
  5. The submitted repository should contain instructions explaining how to run or evaluate the project.
  6. Projects must be sufficiently functional for judges to evaluate during the live demonstration.
  7. Teams must clearly acknowledge third-party tools, datasets, APIs, libraries, and assets.
  8. Late or incomplete submissions may be excluded from judging.
  9. Final submission fields and requirements will be updated before the hackathon.
  10. The organisers reserve the right to clarify these rules and resolve unforeseen situations fairly.