IPSC IT Fest 26

Events

08–10 December 2026 · The Doon School

Events / Hackathon

The Doon School · 08–10 December 2026

Hackathon

Participants are combined with students from other schools into cross-school Companies. Each Company appoints a CEO, CTO and CMO by chit-picking after the Opening Ceremony, and only then are the Problem Statements released.

Cross-school venture build

You will not be competing as your own school.

Plan view · schematic

Rules

How it runs

  1. The Hackathon tests a team’s ability to carry a conceptual challenge through to a market-oriented solution: a functional prototype, sound business and marketing thinking, and the ability to communicate and defend the result under questioning. It runs as a single continuous stage, with no elimination rounds unless the Organising Committee announces otherwise.
  2. Each school nominates three students. They do not necessarily compete together as a school team: they are combined with students from other schools to form cross-school Companies. The number of Companies, schools per Company and members per Company are set by the Organising Committee on final participation strength. For example, if 15 schools take part, five Companies of three schools each may be formed, giving approximately 15 members per Company. Allocation cannot be requested or altered.
  3. After the Opening Ceremony and Company formation, and before the Problem Statements are released, each Company appoints a Chief Executive Officer, a Chief Technology Officer and a Chief Marketing Officer through the prescribed chit-picking process. Judges may question any Company Member, whatever their role.
  4. Companies then receive a set of Problem Statements organised under multiple Sustainable Development Goals, and each selects one. The Problem Statements are confidential until their official release.
  5. The Development Period runs from the release of the Problem Statements to the submission deadline set by the Organising Committee. Every Company must produce three interconnected outputs: a Functional Prototype (hardware, software or a combination), a Business/Financial Strategy, and a Marketing Strategy. Concept art, static slides, wireframes or mock-ups alone are not a functioning prototype, and any simulated functionality must be disclosed.
  6. The solution must be substantially developed by the Company during the Development Period. Pre-built solutions, outside development assistance and outsourcing of any technical, marketing or financial work are not permitted.
  7. AI tools are permitted. Each Company must disclose the AI tools used, the purpose of each, and the significant components that were AI-assisted, and every Company Member must be able to explain the final output, including AI-assisted components.
  8. Participants bring their own laptops; internet access is provided by the host school. Mobile phones and personal hotspots are prohibited during the competition unless the Organising Committee permits them for a specific purpose, and any group chat used within or between Companies must include a member of the Organising Team.
  9. The event concludes with a 15-minute Corporate Pitch to the Judging Panel, in which all Company Members should take part, followed by a Question-and-Answer session whose duration will be specified before the event.

Fabrication. Hardware is optional. Campus fabrication facilities, including 3D printing, may be made available for approved hardware development. A hardware solution earns no extra credit for containing physical components, and a software-only solution is not disadvantaged.

Company structure. To be announced · TBC

Event details

Discipline
Team event
Participants
3 per school
Control
Cross-school Companies
Event head
Vir Sandhu

Judging

  • Scored out of 100 across three pillars and eighteen criteria
  • Judges assess the evidence a Company presents through its Prototype, Submission, Corporate Pitch and Q&A
  • Hardware integration and AI transparency are not marked criteria: hardware is optional, and AI use must be declared and understood
  • Ties go to the higher Programming, Technology & Product Development score, then Core Functionality & Working Prototype, then Financial & Business Viability, then Marketing & Market Strategy, then Judging Panel deliberation

Can you build it? Can you sell it? Can you sustain it?

Judging rubric

How the marks fall

CriterionWeightMarks
A. Programming, Technology & Product Development 40
A1. Understanding of Problem & Technical Approach 6
A2. Core Functionality & Working Prototype 14
A3. Technical Complexity & Quality of Implementation 6
A4. UI/UX & Product Design 5
A5. Innovation & Technical Creativity 5
A6. Testing, Reliability & Performance 4
B. Marketing & Market Strategy 35
B1. Target Market & Customer Understanding 7
B2. Value Proposition & Product Positioning 7
B3. Marketing Strategy & Customer Acquisition 7
B4. Competitive Differentiation 4
B5. Branding, Communication & Promotional Strategy 4
B6. Marketing Feasibility & Product Integration 6
C. Financial & Business Viability 25
C1. Business Model & Revenue Generation 5
C2. Costing & Budgeting 5
C3. Pricing Strategy 4
C4. Financial Viability & Sustainability 5
C5. Resource & Operational Planning 3
C6. Financial Assumptions, Risk & Scalability 3
Total100

Weights are those in the event’s published documents. Scoring levels, tie-break order and who scores what are set out in full in the document pack below.

Documents

The Hackathon pack

5 of 5 documents available

These are the documents your team will receive for Hackathon. Between them they set out everything a team needs in order to prepare.

1

Rulebook

Description and objective, team composition, format and progression, run structure and timings, permitted and prohibited actions, penalties, appeals, and definitions.

Open PDF

2

Platform & Environment Specification

Languages and libraries permitted, devices brought versus provided, internet access, policy on AI tools, provided datasets and platforms, submission format.

Open PDF

4

Judging Rubric

Criteria with point values summing to a stated total, scoring levels, tie-break order, who scores what, and when scores are published.

Open PDF

5

Inspection & Safety

Pre-competition inspection checklist and schedule, consequences of failed inspection, safety requirements during runs, spectator boundaries, and the emergency stop procedure.

Open PDF

6

Support Material

A worked example, a starter guide to core techniques, the concepts a team should learn, common mistakes, and an FAQ.

Open PDF

Flow

How Hackathon works, step by step

The event from start to finish, as the rules above set it out. The detailed documents for Hackathon will appear here once they are released to registered schools.

  1. Registration

  2. Opening Ceremony

  3. Cross-school Company formation

    Participants are combined with students from other schools.

  4. CEO, CTO and CMO appointed

    By the prescribed chit-picking process, before the Problem Statements are released.

  5. Problem Statements released

    Organised under multiple Sustainable Development Goals. Each Company selects one.

  6. Development Period

    Problem analysis, prototype development, testing and iteration, business and financial planning, and marketing strategy, until the submission deadline.

  7. Final submission

    Including the AI-use declaration.

  8. 15-minute Corporate Pitch

  9. Question & Answer session with the Judging Panel

  10. Scored out of 100; results at the Closing Ceremony

Who runs it

The people behind Hackathon

Vir Sandhu

Vir Sandhu

Event Head

To be announced · TBC

Next

IT Quiz

A team-based technology quiz with an MCQ preliminary round followed by a live final with rapid-fire and buzzer rounds.

Questions

The Hackathon documents above are the definitive reference for the event. If anything in them is unclear, do write to us.