SUDO // BUILD - Official Rules and Regulations
Introduction
This document outlines the official rules, regulations, and procedures for the SUDO // BUILD. The event
is designed to foster innovation, collaboration, and technical creativity among participants. As this is a
fully online event, all participants are required to read, understand, and adhere to these guidelines to
ensure a fair and productive competition for all.
I. General Regulations
A. Eligibility: Participation is open to everyone (College Students).
B. Team Formation:
1. Teams must consist of a minimum of 1 and a maximum of 4 members.
2. Participants may register as a pre-formed team or as individuals to be assigned to a team. All
collaboration will occur remotely.
3. Changes to team composition are not permitted after registration.
C. Code of Conduct:
1. All participants must maintain a high standard of professionalism and respect towards fellow
participants, mentors, judges, and organizers within all online communication channels.
2. All work submitted must be original and created during the hackathon.
3. The committee will not provide any API access.
4. Participants cannot use any existing repository from GitHub.
5. There are no restrictions in using any AI tools (any GPTs, Gemini etc).
6. Participants can use any dataset either synthetic data, online sources, or any third party.
D. Online Event Logistics:
1. Format: This hackathon will be conducted entirely online. All activities, will take place in a virtual
environment. Round 1 will be conducted through Google Meet for participants.
2. Communication Platform: The official platform for all announcements, will be done through a
common WhatsApp group for all teams. All participants are required to join this group.
3. Presentation Platform: All presentations and pitches (Round 3) will be conducted via Google Meet.
Links will be provided to the teams in advance on common WhatsApp group.
4. Technical Requirements: Participants are responsible for ensuring they have a stable internet
connection, a functional webcam(if required), and a microphone to participate effectively in the
virtual presentations.
II. Competition Structure
The hackathon is structured into three distinct rounds, each with specific objectives and deliverables.
Round 1: Ideation, Domain Selection, and Conceptual Pitch
This initial round is focused on brainstorming, conceptualizing a project, and presenting the idea for
approval. Participants will be judged based on the document submitted.
1. Ideation Phase :
● Teams will collaborate remotely during a strict 45-minute window for intensive brainstorming.
● The objective is to identify a significant problem and formulate an innovative technological solution
on the given domain.
2. Domain Selection:
● Following the ideation phase, each team must select a primary domain for their project.
Domains:
● Child safety and protection
● Digital wellbeing and mental health
● Financial Inclusion
● Smart city and sustainability
3. Idea Documentation:
● Teams are required to produce a concise concept document. This document must include:
○ Project Title: A working title for the project.
○ Domain: The selected domain for the project.
○ Problem Statement: A clear description of the problem the project aims to solve.
○ Proposed Solution: A detailed explanation of the proposed technical solution.
○ Key Features: A list of the core functionalities and features.
○ Technology Stack: An outline of the technologies, languages, and frameworks the team plans
to use.
○ External Sources: If the teams are using any external datasets and repository.
Round 2: Project Development and Technical Documentation
This round is the core development phase of the competition.
1. Development Phase:
● Teams will have an uninterrupted period to build a functional prototype or a minimum viable
product (MVP) of the idea approved in Round 1.
2. Technical Documentation :
● Following the 24-hour development period, teams will have to create comprehensive project
documentation. This documentation must include:
○ A setup and installation guide.
○ An overview of the project architecture.
○ A description of the code and its functionalities.
○ A link to the source code repository (e.g., GitHub).
3. Submission:
● All project files, source code, and technical documentation must be submitted digitally through the
official submission portal before the final deadline. Submit a video demo showing the working of
the project and it's use cases.
● Please Note: The submission deadline is absolute. No extensions will be granted under any
circumstances. Failure to submit within the specified time will lead to disqualification.
● Judges will review the submitted projects and documentation to evaluate technical
implementation, completeness, and adherence to the proposed concept.
4. Advancement:
● The top 72 teams will advance to the next round, subject to judges decisions.
Round 3: Final Presentation and Evaluation
The final round involves demonstrating the completed project to the judging panel and a wider
audience.
1. Final Presentation:
● Each team will be allocated a specific time slot to present their project virtually. Presentations
should include:
○ A brief introduction to the problem and solution.
○ A live demonstration of the working prototype (screen sharing will be required).
○ A discussion of the technical challenges faced and overcome.
○ An outline of potential future developments for the project.
2. Question & Answer Session:
● Following the presentation, the judging panel will engage in a virtual Q&A session with the team to
gain deeper insights into the project's technical and conceptual aspects.
3. Final Judging:
● The winners will be determined based on a comprehensive evaluation of their performance across
all rounds, with a primary focus on the final project and presentation. Judging criteria will include
technical complexity, innovation, design, completeness, and presentation quality.
Note: The exact duration allocated for presentations in Round 3 may be adjusted based on the final
number of participating teams.