Embedded Files
What constitutes a Valid Project Submission?
What constitutes a Valid Project Submission?
A Functional Prototype
Your primary deliverable should be a working prototype of your solution. This means it should be able to run and demonstrate the core functionalities you claim it possesses. It doesn't need to be a fully polished product, but it must be operational.
Participants Track
Participants Track
Track A: Non-Technical
Submission: Submit a link to a clickable UI/UX design prototype (e.g., Figma).
Include: A fully interactive flow that demonstrates the user journey and key features.
Demo: A video walkthrough or screen recording of the prototype is highly recommended to guide the judges.
Track B: Technical
Submission: Submit your code via a public GitHub repository.
Include: Source code for your front-end, back-end (minimal implementations are acceptable), APIs, database schemas, and configuration files.
Demo: If live deployment is not possible, please include a video demo of the code running locally.
Expected Deliverables
Expected Deliverables
All teams are required to submit the following by 13 March 2026, 11:59 pm GMT +8
Project Respitory Link (GitHub) / Figma Link
1. Non-Technical Track
Participants in this track must submit the following items:
Add your public Figma link to the GitHub Repository
README.md: A text file containing your project title, team members, and a brief summary.
Project Report: Submit your report in .pdf format
Prototype Link: A link to your interactive design
Video Demo:
Length: Maximum 8 minutes.
Format: Link to YouTube (please set your video to "Unlisted")
2. Technical Track
Participants in this track must submit the following items:
README.md: A text file containing project details, setup instructions, and the AI disclosure.
Project Report: Submit your report in .pdf format
Codebase: A link to your public GitHub repository containing all source code (Frontend, Backend, etc.).
Prototype Link: (Optional but recommended) A link to your design or flow if applicable.
Video Demo:
Length: Maximum 8 minutes.
Format: Link to YouTube (please set your video to "Unlisted")
Report
Introduction
Background of Case Study: Briefly introduce the context of your project.
Chosen SDG: Identify the specific Sustainable Development Goal your solution addresses.
Problem Statement: Clearly define the issue you are solving.
Objectives: List the specific goals of your solution.
Review of Existing Solutions
Analyze current solutions or competitors in the market.
Highlight gaps or limitations that your project aims to fix.
Methodology
Technical Track: Describe your tech stack, architecture, and implementation process.
Non-Technical Track: Describe your design thinking process, user research, and flow creation.
Results
Summarize the outcome of your work. Did you meet your objectives?
(Optional) Include any data or feedback gathered during development.
Prototype Showcase
Output / UI Screenshots: Include high-quality screenshots of your user interface or key features.
Note: Captions explaining the screenshots are recommended.
AI Acknowledgement (Mandatory)
Disclosure: You must disclose all AI tools used (e.g., ChatGPT, GitHub Copilot, Midjourney).
Usage: Briefly explain how these tools were used (e.g., "Used ChatGPT for debugging code," "Used Midjourney for asset generation").
Failure to disclose AI usage may result in disqualification.
Conclusion
Summarize your project and suggest potential future improvements.
Submission Form (Google Form)
A Google Form will be provided for official project submissions. Fill in your team details, project title, a brief description of your project, provide a link to your GitHub repository/Figma, report and video
Pitch + Demo Video (Preliminary Round)
Pre-record your video (consisting of your pitch and your solution demo) showcasing your prototype's functionality and explain your project. The duration is 8 minutes maximum.
Ps: The demo video consists of your pitching + the demo of your solution.
Our recommendations for version control
Our recommendations for version control
Extra tip: When collaborating on coding,
We highly recommend using GitHub for version control throughout the hackathon as it offers numerous benefits like:
Collaboration
Facilitates seamless collaboration among team members, allowing multiple people to work on the same codebase simultaneously.
Version History
Tracks all changes, allowing you to revert to previous versions if needed.
Showcase
Your GitHub repository serves as a professional portfolio of your work.
Submission
It is the required platform for your final code submission.
Page updated
Google Sites
Report abuse