Rules for LETS HACK

Hackathon Spirit

Hackathons are like marathons: Some people go to compete but most people take part to better themselves and have fun. Whatever the reason is you’re at a hackathon, make sure you’re upholding the spirit of the hackathon by collaborating with other teams, helping beginners, coding for silly/funny to advanced projects, and having fun.

Rules of the Hackathon -

  1. You must treat all team members, competitors, judges, coaches, mentors, volunteers, etc, with respect and courtesy.
  2. Hackathon teams will be a maximum of 4 people and also can particiapte individually.
  3. All prizes are to be shared between all team members.
  4. Teams should be made up exclusively of students (School Students and College Students both can participate) or people who are not organizers, volunteers, judges, sponsors, or in any other privileged position at the event.
  5. All team members should be present during the hackathon and at the time of the presentation. (If it'll require)
  6. Teams can of course gain advice and support from organizers, volunteers, mentors sponsors, and others.
  7. All work on a project should be done during the hackathon.
  8. Teams can use an idea they had before the event but it doesn't include code and development part. It's just an idea.
  9. Teams can work on ideas that have already been done or already present in the market but we suggest building projects with improvement. Hacks do not have to be “innovative”. If somebody wants to work on a common idea they should be allowed to do so and should be judged on the quality of their hack.
    1. Open Innovation - Anything which you’re building and proud to show but it doesn’t relate to any given themes then you can submit your project under the “Open Innovation” category
    2. Early Hack - Are you an Elon Musk fan? Or someone who started coding at an early age while being in school then this track is especially for you. Judging criteria would be different for this category and we can ask you to verify your school identity. You can participate all alone and in a team also. Our EarlyHack Team will be there to help you out if you get stuck in something. 

  10. Teams can use libraries, frameworks, or open-source code in their projects. Working on a project before the event and open-sourcing it for the sole purpose of using the code during the event is against the spirit of the rules and is not allowed.
  11. Teams must stop hacking once the time is up.
  12. Teams can be disqualified from the competition at the organizers’ discretion. Reasons might include but are not limited to breaking the Competition Rules, behaving in a way that violates the hackathon spirit, or other unsporting behavior.
  13. All projects should be submitted to the hackathon GitHub account (TBA) before judging begins. Failure to submit will result in disqualification. should commit regularly throughout the hackathon to the team repository. Team repositories that are committed in the entirety near the close of the hackathon, will be examined and the team could be disqualified for a rules violation. A single GitHub commit made near the end of the hackathon will draw the suspicion that the work was not completed at the hackathon.
  14. All project submissions will be randomly code-reviewed. Applications will be spot-checked by code reviewers. All the projects selected by the judges as finalists will be code reviewed to confirm that the code is original work created at the hackathon and all components and assets conform to the licenses allowed in these rules.

Innovative and Scalable Projects

Innovative and Scalable Projects will get a chance to display their projects and business plan to the investors and incubators. If you’ll get selected you’ll get mentoring support and other opportunities to take your idea from project to startup.


  • At the time of submission team/participants have to submit a video of their project.
  • Videos should be less than 3 minutes in length and uploaded to YouTube/Vimeo etc. (set on unlisted) with the link emailed to the judges at the contest close.
  • You are encouraged to present what you have done even if your hack is broken or you weren’t able to finish. It’s okay if you didn’t finish your hack—that happens all the time!

Judging Criteria

Teams will be judged on these four criteria. Judges will weigh the criteria equally. During judging, participants should try to describe what they did for each criterion in their project.

  • Technology: How technically impressive was the hack? Was the technical problem the team tackled difficult? Did it use a particularly clever technique or did it use many different components?
  • Design: Did the team put thought into the user experience? How well designed is the interface?
  • Completion: Does the hack work? Did the team achieve everything they wanted?
  • Innovation: What problems did they solve and how innovative the idea is for solving the problem?
  • Presentation of the Project: How much of the project is well represented along with the Video, GitHub READme and description of the project.
  • Scalability: A project scalable and can be implemented in real life on a large scale with a feasible cost to solve the specific problem for which it has been created.
  • Extra Points: Extra Points for using any specific technology/platform/problem statement/tech stack of our sponsors.

These criteria will guide judges but ultimately judges are free to make decisions based on their gut feeling of which projects are the most impressive and most deserving.

So don’t worry about coming up with the next big idea or building the next Facebook/Amazon/Google/Twitter/Tinder or TikTok. You’ll have plenty of time for that outside the hackathon, just focus on learning, having fun, and making new friends. At the end of the day the skills you learn and the friends you make might lead to the next big thing—but you don’t have to do that to win a hackathon.


The competition is just a part of the hackathon. To make the most out of the event, try something new, teach other people, and make new friends!