Rules & Regulations

HACKATHON MENTOR GUIDELINES

Selection is based on availability, domain knowledge, and commitment to guiding student teams. Mentors will be assigned to two teams to ensure focused support without overburdening.

Provide guidance on problem-solving, technical implementation, and project management to assigned teams.
Facilitate sessions on ideation, prototyping, and debugging, while encouraging independent thinking among students.
Monitor team progress during the hackathon and offer feedback on prototypes, code quality, and presentation skills.
Promote adherence to team formation rules, including diversity in composition and equal contribution.

Availability: Mentors must be accessible during designated hackathon hours (e.g., via in-person sessions, virtual meetings, or messaging platforms like WhatsApp).
Team Assignment: Mentors will be paired with teams post-registration, considering alignment with problem statements (software or hardware editions).
Sessions: Conduct at least two structured mentoring sessions per team—one for initial planning and one for mid-event review—to align with the unique problem focus and first-come, first-served allotment.
Documentation: Maintain brief notes on team interactions and progress for organizer review, without sharing confidential team details.

Confidentiality: Respect team ideas and do not disclose proprietary solutions or strategies to other teams or external parties.
Fairness: Avoid favoritism; provide equitable guidance to all assigned teams, ensuring no influence on problem statement selections or participation editions.
Integrity: Report any observed plagiarism, unethical conduct, or rule violations (e.g., unauthorized team changes) to organizers immediately, which may lead to team disqualification.

Professionalism: Maintain a respectful, inclusive environment by supporting gender and departmental diversity in teams and fostering collaboration.
Conflict Resolution: Address team disputes impartially and escalate unresolved issues to organizers.
Adherence: Mentors violating these guidelines, such as engaging in biased mentoring or breaching confidentiality, may be removed from the event and barred from future participation.

Team Size: Exactly six (6) students per team.
Department Mix: Members must come from at least two departments.
AD, CSE and IT are counted as one department for this rule.
Gender Balance: If males form the majority, include a minimum of two (2) female members.
If females form the majority, include a minimum of two (2) male members.
Year Representation: Each team must include two (2) second-year, two (2) third-year and two (2) final-year students.

Unique Team Name: Each team must register with a unique team name.
Member Details: During registration, teams must provide details of each member, including their name, department, and year of study.
Team Leader: The team must nominate a team leader who will serve as the primary point of contact.
Students can download Presentation formats(.pptx) from our official site.

No Team Changes: Once registered, no changes in team composition are allowed.
Single Edition Participation: Each team can participate in only one edition of the hackathon, either Software or Hardware.
Unique Problem Focus: Teams must select and work on one problem statement only for the duration of the hackathon. Each problem statement is limited to a maximum of 2 to 3 teams.
Problem Allotment: Problem statements are allotted based on first-come, first-served. This ensures no more than three teams work on the same problem, enabling diverse approaches and solutions.

Internal Communication: Teams are responsible for managing their internal communication and task distribution.
Equal Contribution: All members should contribute equally to the project, with tasks distributed fairly among them.

Rule Adherence: Teams that do not adhere to the team composition rules or attempt to make changes without notifying the organizers will be disqualified.
Ethical Conduct: Plagiarism or any form of unethical behavior will lead to immediate disqualification.

Respect and Collaboration: All participants must adhere to the college's code of conduct, maintaining a respectful and collaborative environment throughout the hackathon.