Hawkings Hack

Hackathon Rulebook: Event Name: Hawkings Hack Type of Event: Hackathon Venue: Seminar Hall Participation: Team of 1–3 members Mode: Offline (Presentation & Pitch Based) Round 1 Submission Deadline: 8th March Round 2 (Final Pitch): 12th February (In College) Reporting Time (Round 2): Event Format: Two-Round Evaluation System Competition Format: Round Structure Round 1 – Idea Submission & Internal Shortlisting Teams must submit a detailed PPT presentation before 8th March. The PPT must clearly explain: Problem Statement Proposed Solution Technical Architecture Feasibility & Implementation Strategy USP & Innovation Market/Societal Impact Based on internal evaluation, the Top 5 teams will be shortlisted. Round 2 – Final Pitch (Seminar Hall) Shortlisted teams will pitch their ideas before the judging panel on 12th February. Each team will be given: Fixed time for presentation Fixed time for Q&A by judges Winners will be decided based on final evaluation scores. The decision of the judges and organizers will be final. Hackathon Themes: 1. AI & Automation (Beyond Wrappers) Move beyond simple API calls. Focus on Agentic Workflows. Systems must demonstrate: Autonomous planning Execution capability Self-verification mechanisms 2. Web3 & Blockchain (Utility Over Hype) Build decentralized systems that: Improve transparency Establish trust in legacy industries Pure token-based speculation projects are discouraged. 3. FinTech (The Next Billion Users) Mobile-first financial systems. Emphasis on: Security Accessibility Scam prevention Financial inclusion 4. HealthTech (Care Beyond Clinics) Solutions for: Early diagnosis Remote monitoring Patient–doctor accessibility gap Must demonstrate practical applicability. 5. Open Innovation (The Wildcard) For unconventional ideas. Identify a neglected societal problem. Present a disruptive and technically sound solution. Rules & Regulations: 1. General Rules: The hackathon will be conducted as part of the Blitzkrieg coding event. Teams must have minimum 1 and maximum 3 members. All participants must be registered for the event. Participants must carry their ID cards. Only one submission per team is allowed. Plagiarism will lead to immediate disqualification. 2. Submission Rules (Round 1) PPT must be submitted before the deadline (8th March). Late submissions will not be accepted. PPT must include: Clear problem definition Technical explanation Architecture diagrams (if applicable) Scalability considerations Business/Impact model Teams must ensure originality of content. 3. Presentation Rules (Round 2) Only shortlisted teams will present in the Seminar Hall. All team members must be present during the pitch. Time limits must be strictly followed. Judges may interrupt to ask technical questions. 4. Evaluation Criteria Projects will be judged based on: Innovation & Originality Technical Depth Feasibility & Scalability Real-World Impact Clarity of Presentation Ability to defend the idea during Q&A 5. Prohibited Actions (Violations Lead to Disqualification) Plagiarism or copied ideas Misrepresentation of technical capabilities Use of AI-generated content without understanding or explanation Any form of misconduct or disruptive behavior 6. Tiebreaker Criteria Higher technical depth score Greater real-world feasibility Judges’ final discretion Important Notes: Teams are encouraged to think beyond superficial solutions. Mere UI prototypes without backend logic or system thinking will score lower. Working prototypes are encouraged but not mandatory. Judges’ decisions will be final and binding. Contact for Queries: Natya Vidhan Biswas - 9718413051 Ayushi Jain - 9582617263