Selection Criteria: The proposed solutions will be evaluated by experts on the basis of novelty of the idea, complexity, clarity, detailed document, feasibility, practicability, sustainability, the scale of impact, user experience, and potential for future work progression. General Overview ● Duration: 24 hours ● Format: Teams of 2-6 members (team sizes may vary) ● Registration Fees – Rs 599/- ● Categories: Various problem statements are provided across different categories. ● Registration: Usually requires online registration before the event starts. Teams often need to submit a brief on their ideas or tech stack ahead of time. ● Eligibility: Open to all college students (undergraduate and postgraduate) Key Stages of the Hackathon 1. Pre-Hackathon: Registration & Preparation ● Registration Process: o Teams will register in advance via the official Techfest website www.gyanotsav.com o Teams will need to create an account, register themselves and their members, and possibly submit an idea or project summary for approval. ● Pre-Hackathon Preparation: o Participants are encouraged to familiarize themselves with the tech stack and APIs that might be used. 2. The Hackathon Begins (Kick-off) ● Introduction Session: o On the day of the event, the organizers usually provide an orientation session where the rules, judging criteria, and technical resources are explained. 3. Development Phase ● Coding & Prototyping: o The core of the hackathon is the coding phase, which lasts around 18-20 hours. Teams develop their projects from scratch, using various tools, technologies. ● Collaborating: o Teams should maintain effective communication throughout the event, working together to tackle challenges, debug code, and integrate components. This is critical since time is extremely limited. 4. Progress Check-ins (Midway) ● Optional Check-ins: o Progress check-ins during the 24-hour period where teams share updates on their work, receive feedback, and ensure they are on track. o This helps teams re-align if they face technical blockers or need advice on improving their solution. 5. Final Stage (Presentation & Submission) ● Wrapping Up the Code: o As the 24-hour deadline approaches, teams begin wrapping up their projects. This includes ensuring that the project is functional, integrating all components, and preparing a working demo. ● Presentation Preparation (23-24 Hours): o Teams need to prepare their final pitch and presentation slides. Typically, teams have 5-10 minutes to present their project to the judges. o The presentation should include: ▪ Problem definition ▪ The solution they’ve built and how it solves the problem ▪ Demo of the working prototype ▪ Technologies and tools used ▪ The impact and scalability of the solution 6. Submission: ● Code Submission: o Teams usually need to submit their source code, project files, and any relevant documentation via an online portal (e.g., GitHub, Google Drive) by the end of the 24-hour period. ● Final Presentations (Judging): o Teams present their project in front of a panel of judges, which typically includes industry experts, professors, and experienced developers. The presentation is followed by a Q&A session where judges ask questions to evaluate the team’s problem-solving approach and understanding of the solution.