1. Team Formation

  • Each team must consist of 3 to 4 members.
  • Teams must be formed before the hackathon begins. No changes to team composition will be allowed once the event starts.

2. Project Scope & Theme

  • Teams must work on projects that align with the given theme or problem statements.
  • The project can be built using any technology or platform, as long as it adheres to the event’s guidelines.
  • The final submission must be in a debugged and ready-to-run state.

3. Time Frame

  • Teams must complete their project within the specified hackathon duration.
  • Late submissions will not be considered unless explicitly permitted by the organizers.

4. Originality & Use of Pre-Existing Code

  • The use of pre-existing code or previously developed projects is strictly prohibited, except for open-source libraries, APIs, or frameworks.
  • All submissions will be subject to plagiarism checks to detect copied.
  • Any team found violating this rule will be disqualified immediately.

5. Intellectual Property

  • Teams must ensure their work does not violate any copyright, patent, or intellectual property laws.
  • The ownership rights of the submitted projects will remain with the respective teams, but organizers reserve the right to showcase them for promotional purposes

6. Judging Criteria

  • Projects will be evaluated based on the following factors:
  • Technical Implementation – Code quality, efficiency, and functionality.
  • Design & User Experience – UI/UX aspects of the solution.
  • Creativity & Innovation – Uniqueness and originality of the idea.
  • Potential & Feasibility – Real-world applicability and impact.
  • Future Implications – Scalability and potential future developments.

7. Fair Play & Ethical Standards

  • Participants must maintain fairness and comply with all hackathon rules.
  • Any form of cheating, plagiarism, or unfair practices will result in immediate disqualification.
  • External help from non-team members is not allowed unless explicitly permitted.

8. Code Sharing & Open Source Contribution

  • Participants are encouraged to share their code with the wider community after the hackathon.
  • Open-sourcing the project on platforms like GitHub is appreciated but not mandatory.

9. Code of Conduct

  • All participants must follow a code of conduct promoting inclusivity, respect, and professionalism.
  • Any form of harassment, discrimination, or inappropriate behavior will not be tolerated and may lead to disqualification and removal from the event.

10. Prizes & Awards

  • Winning teams will receive prizes or awards based on the judging criteria.
  • Specific prize details will be announced before or during the hackathon.

11. Disputes & Arbitration

  • Any disputes or concerns will be resolved by the organizers and judging panel, whose decision is final and binding.
  • Any disagreements must be resolved through the arbitration process outlined by the organizers.

12. Changes to Rules

  • The organizers reserve the right to modify the rules, format, or prizes at any time.
  • Any changes will be communicated to participants in a clear and timely manner.

13. Submission Requirements

  •  Each team must submit a ZIP file containing the following elements:
  • Presentation PPT – Overview of the project, problem statement, and solution.
  • Team Video – A video of the team members explaining their project and its impact.
  • Demo Video – Demonstration of the implemented solution.
  • Source Code Folder – All relevant code files for the project.
  • ReadMe File – A text document explaining how to run the code, along with a deployment link if applicable.