//// Official Rulebook & Participant Guidelines
IEEE IGNITE Hackathon 2026
24-Hour Software & Hardware Hackathon · 14 - 15 October 2026 · SKIT Jaipur
- Event
- IEEE IGNITE - 24-Hour Software & Hardware Hackathon
- Dates
- 14 - 15 October 2026
- Venue
- Indoor Sports Complex, SKIT Jaipur
- Registration fee
- ₹500 per team (non-refundable)
- Prize pool
- ₹5 Lakh
- Mode
- Offline only (no online participation)
- Duration
- 24 hours, continuous
- Team size
- 1 to 4 members
- Open to
- Currently enrolled UG, PG, diploma and PhD students
About
IEEE IGNITE is a 24-hour, fully offline software and hardware hackathon held at Swami Keshvanand Institute of Technology, Management & Gramothan (SKIT), Jaipur. It is open to eligible student teams from SKIT and from other institutions, subject to the rules in this rulebook.
By registering, every participant agrees to follow this rulebook and all instructions issued by the organizing committee.
Eligibility
The hackathon is open to students currently enrolled at a recognized college or institute.
- Undergraduate, postgraduate, diploma and PhD students are eligible. Final-year students may participate.
- School students and full-time working professionals are not eligible.
- Teams may include members from different years and departments.
- Teams from institutions other than SKIT are welcome to register.
Team Formation
Each team must have between 1 and 4 members, all from the same institution and campus.
- Team size: Minimum 1, maximum 4 members.
- Same institution: All members must belong to the same college/institute and study at the same campus. Inter-college and inter-institution teams are strictly prohibited.
- One team per person: A participant may register with only one team. Duplicate registrations or membership in multiple teams may lead to cancellation of candidature or disqualification.
- Team Leader: Every team must nominate one Team Leader, who is the primary point of contact and must be physically present throughout the event.
- Gender composition: There is no requirement for female members.
- Member changes: Routine changes are not permitted after registration. In an emergency or unavoidable circumstance, organizers may allow a team to continue with fewer members.
- No online participation: All members must participate in person.
- Absences: Any member who will be absent must be reported to the organizing team in advance.
Registration & Verification
Seats are limited and allotted on a first-come, first-served basis; every member must be verified in person before the hackathon begins.
- Registration fee: As specified in the official registration form. The fee is non-refundable once registration is complete.
- In-person verification: All registered members must be physically present for verification before the start of the event.
- Identity documents: Each participant must carry both an original college ID card and a government-issued photo ID.
- Identity mismatch: Any mismatch in name or photograph between the submitted IDs may lead to immediate disqualification of the participant and the entire team on grounds of cheating and unfair practice.
- Exceptions: Late arrival and other exceptional verification cases are handled at the organizers' discretion.
Problem Statements & Participation
The problem statements are live on the official website, and a team's selection is final.
- Problem statements and tracks are published on the official IEEE IGNITE website/portal: 25 problem statements across 4 themes.
- Teams must select their problem statement through the designated portal.
- Once selected, a problem statement cannot be changed.
Development & Originality
The core solution must be built during the official 24-hour window, and the team alone is responsible for what it submits.
Permitted
- Standard programming languages, frameworks, open-source libraries, development tools and templates
- Third-party APIs and pre-trained AI/ML models, where relevant
- Generative-AI tools such as ChatGPT, Gemini, Claude, Copilot and similar
Not permitted
- Submitting a completely pre-built project as the team's hackathon solution
- Developing the core solution outside the official 24-hour period
- Obtaining substantial implementation work from anyone outside the registered team
Accountability: Every team member must understand the submitted implementation and be able to explain the code and technical decisions to the judges. Using AI or external tools does not shift responsibility for the correctness, originality or explainability of the work away from the participating team.
Hardware & Infrastructure
IEEE IGNITE covers both software and hardware builds; teams bring their own equipment and must keep it safe.
- Teams may bring and use their own hardware and components, and are responsible for everything their solution requires.
- Each team is advised to bring one extension cord or power strip.
- Prohibited items include unsafe equipment, exposed high-voltage systems, hazardous substances, weapons and any other dangerous equipment.
- Venue infrastructure must be used responsibly. Damaging or tampering with event facilities is not allowed.
Team checklist
0/4 packedCode of Conduct & Fair Play
Participants must behave professionally and respectfully at all times; the following are strictly prohibited.
- Academic dishonesty: Plagiarism, cheating, code theft, deliberate sabotage and misrepresentation of work.
- Misconduct: Harassment, discrimination, threatening behaviour and any other inappropriate conduct.
- Security violations: Unauthorized access to event systems, attacks on the event network or another team's systems, malware deployment and infrastructure tampering.
- Outside help: Obtaining substantial implementation work from people outside the registered team.
Teams may discuss ideas with mentors and seek general technical guidance from them.
Submission & Demonstration
Teams must submit a working, demonstrable solution through the official mechanism before the announced deadline.
- Submit the completed solution through the submission mechanism specified by the organizers. A GitHub repository may be required for source code.
- Maintain a clear README with setup and usage instructions, where requested.
- The solution should be demonstrable as a working prototype or functional implementation.
- All submissions must meet the deadline and format announced by the organizing team.
Judging & Final Authority
Projects are judged on six criteria, and the panel's decision is final and binding.
Criterion 01
Problem understanding
Clarity on the problem and who it affects
Criterion 02
Innovation
Originality of the idea and approach
Criterion 03
Technical implementation
Quality of architecture, code and engineering
Criterion 04
Functionality
How well the prototype works in the demo
Criterion 05
Feasibility / impact
Practicality and potential real-world value
Criterion 06
Presentation / Q&A
Clarity of the pitch and answers to judges
- Judges may ask any team member to explain the project's architecture, implementation, code or technical decisions.
- Failure to demonstrate or explain substantial parts of the solution may affect evaluation and may lead to disqualification where applicable.
- The decision of the judging panel and organizing committee is final and binding.
Organizer Rights
The organizing committee may adjust arrangements when necessary and act on any situation this rulebook does not expressly cover.
- The committee may make reasonable changes to the schedule or operational arrangements and will announce updates through official channels.
- The organizers reserve the right to take appropriate action in cases of rule violations, safety concerns, unfair practices, or circumstances not expressly covered here.
- Participants should follow the official IEEE IGNITE communication channels and event portal for the latest instructions and announcements.