1. Event Schedule
| Date | Start | End | Activity | Location |
|---|---|---|---|---|
| Aug 8, 2026 | 8:00 | 8:30 | Registration and team formation | Mini Auditorium |
| Aug 8, 2026 | 8:30 | 10:00 | Opening briefing | Mini Auditorium |
| Aug 8, 2026 | 10:00 | 12:00 | Workshop by Generation Girl | Mini Auditorium |
| Aug 8, 2026 | 12:00 | 13:00 | Lunch (food is not provided) — participants may leave school | Canteen |
| Aug 8, 2026 | 13:00 | 16:00 | Hacking period — participants may leave school | Mini Auditorium |
| Aug 9, 2026 | 0:00 | 19:00 | Continuation of hacking period · Online submission deadline (19:00) | Outside school (school is closed) |
| Aug 10, 2026 | 8:00 | 8:30 | Briefing | Mini Auditorium |
| Aug 10, 2026 | 8:30 | 12:45 | Presentations and Q&A (10 minutes each) | Mini Auditorium |
| Aug 10, 2026 | 12:45 | 14:15 | Lunch (food is provided) | Canteen |
| Aug 10, 2026 | 14:15 | 15:00 | Winners announcement | Mini Auditorium |
Note: the event rundown is subject to change if needed.
2. Team Formation & Selection
Teams must consist of:
- Minimum: 3 members
- Maximum: 4 members
All participants must register individually through the registration form.
During registration, participants will have the option to indicate the names of individuals they would like to work with during the hackathon.
Participants who do not have preferred teammates may leave this section blank.
While the Event Committee will make every reasonable effort to accommodate teammate preferences, submitting preferred teammate requests does not guarantee placement on the same team.
3. What to Bring
- Laptop
- Charger
- Hardware (if needed for the hack)
- Any type of ID for verification
4. Requirements
Devpost
All participants should make an account on Devpost, which is the platform used for submissions. Only one team member should submit, and that submission must list the names of all team members. It is strongly recommended to sign up early to avoid any last-minute technical difficulties.
Devpost link: sispik-hacks-1-0.devpost.com
The Devpost submission is required to include the following:
-
Project Name and Tagline
A short, memorable name for your project along with a one-line summary of what it does.
-
Project Description
- What problem your solution addresses and who it affects
- How your solution works and why you approached it this way
- What makes your solution stand out
- Challenges faced and what you learned
-
Built With
List the languages, frameworks, APIs, tools, platforms, or hardware you used to build your project.
-
Pitch Deck
A brief, visual slide presentation that showcases your project – either as a link or an uploaded file.
-
Source code
A link to a public repository (e.g., GitHub) or a zipped folder of your code uploaded directly.
-
Video Demo Link
- 2 minutes maximum
- Hosted on YouTube, Vimeo, or a similar platform
- Walks though what your project does and the user experience
-
Teammates
List every member of your team.
Presentation and Q&A
- Each team presents for 5 minutes, followed by 5 minutes of Q&A (strictly 10 minutes total per team).
- The format of the presentation is entirely up to each team. However, it is encouraged to use the pitch deck alongside some sort of demo (live or recorded).
Workshop
- Updated browser (preferably Google Chrome)
- A Google account, for accessing the tools used during the workshop
5. Theme
Theme: Solutions to local environmental problems
Teams are expected to design and build a solution that addresses a real-world environmental problem affecting a local community. Use the guiding questions below to help shape your idea.
Guiding questions:
- What environmental issue affects your local community most directly, and who is impacted by it?
- How might your solution tackle the root of this environmental issue, rather than just its symptoms?
- Who are the primary beneficiaries of your solution, and how would you measure its impact?
These guiding questions are meant to inspire your thinking. Teams are not required to answer all of them directly in their submission.
6. Development Tracks
Code
Participants may use any programming language, framework, or development platform to build their solution. Examples include:
No-Code
Participants may develop their solution using no-code or low-code platforms without extensive programming. Examples include:
7. Judging Criteria
| Exceptional (9–10) | Proficient (7–8) | Average (5–6) | Underachieving (3–4) | Rudimentary (0–2) | |
|---|---|---|---|---|---|
| Creativity | The project answers a problem in a new or unexpected way. It is original and not taken from already existing code or ideas OR/AND The fresh use/conceptualization of a certain tool or gives a new user experience |
The project has some special features and puts a twist in already existing ideas and/or concepts, tools | The project does have little (1–2) special features but mainly uses concepts which are not new | The project is basic, there are little to no new ideas explored, little special features | The project, code or idea was directly copied from existing ideas without new interpretation or special features, too much use of AI |
| Relevance & Problem solving | The project effectively answers a problem, it creates an impact It is able to serve (benefit) the targeted audience/industry/users The solution is realistic in terms of timeline and resources |
The project answers a problem effectively Has the ability to benefit the target audience There is a few gaps in terms of a realistic timeline but otherwise reasonable |
The project answers a problem Has some ability to benefit the target audience Timeline and use of resources are not very realistic |
The project barely answers a problem Does not directly benefit the targeted audience Timeline and use of resources are not very realistic |
The project does not answer a problem It does not benefit the targeted audience at all Timeline and use of resources are not realistic |
| Technical Execution | The code or mechanism (if physical product) is able to conduct its intended purpose smoothly every time, good and easy user experience | The code or mechanism (if physical product) is able to conduct its intended purpose smoothly most of the time. Positive user experience | The code or mechanism (if physical product) is able to conduct its intended purpose smoothly sometimes. Minimal errors in user experience | The code or mechanism (if physical product) is not able to run smoothly, user experience is not satisfying | The code or mechanism (if physical product) is unable to conduct its intended purpose smoothly at all, unsatisfying user experience |
| Presentation (Pitch) | The presenters were all knowledgeable about their own product, showing enthusiasm The presentation is coherent, convincing, creative, easy to understand The presenters are able to answer any/all questions provided by the judges |
The presenters were all knowledgeable about their own product The presentation is coherent, convincing, easy to understand The presenters are able to answer most of the questions provided by the judges |
Some of the presenters were more knowledgeable of the product compared to others in the same team The presentation is convincing, easy to understand The presenters are able to answer some of the questions provided by the judges |
Some of the presenters were more knowledgeable of the product compared to others in the same team The presentation is easy to understand The presenters are able to answer little of the questions provided by the judges |
Presenters seemed underprepared, not knowing how to describe or pitch the product The presentation was not easy to understand, not creative, coherent or believable The presenters are unable to answer any of the questions provided by the judges |
| Transparency | If there is the use of AI at all, it is explained fully in the presentation. There should be no copying of designs from other existing code or physical product, has originality No plagiarism |
If there is the use of AI at all, it is explained fully in the presentation. There is minimal references to designs from other existing code or physical product, has originality No plagiarism |
Use of AI or inspiration from existing products is not fully explained in the presentation | Use of AI or the basis of inspiration is barely explained in the presentation | Use of AI is not disclosed in the presentation or fully copied from an existing software. In terms of hardware, product, the design and function is copied from an existing object There is plagiarism |
8. Food & Drink
- Day 1 (Aug 8): Drinks will be provided.
- Day 2 (Aug 9): No food or drink provided. The school is closed and teams work outside the venue.
- Day 3 (Aug 10): Lunch and drinks will be provided.