Dates
- Hackathon Launch (Briefing/Q&A): [Monday, 8 Dec 2025, 11:00am SGT]
- Online Workshops: [9–11 Dec 2025]
- Submission Deadline: [Thurs, 11 Mon 2025, 10:00am SGT (UTC+8)]
- Judging & Results: [11 Dec 2025]
- Live Showcase & Awards: [Fri, 12 Dec 2025]
Project and Submission Requirements
- Must be started and primarily built during the hackathon
- Must address the hackathon theme (Tech for the Community)
- You may use public APIs, AI tools, open-source libraries, and templates, but your project must show substantial original work from your team
- No harmful, unethical, or illegal solutions (e.g. privacy violations, harassment, discrimination, etc.)
Judging Criteria
|
Judging Criteria |
5 |
4 |
3 |
2 |
1 |
|
Impact and Relevance to Theme (20%) |
Solution has an excellent real-world impact, highly relevant to the problem statement, and aligns with hackathon goals. |
Solution has a good potential impact, mostly relevant to the theme and hackathon objectives. |
Solution has moderate impact and is somewhat relevant to the problem statement. |
Solution has low impact and is minimally relevant to the hackathon’s goals. |
Solution lacks a clear connection to the problem statement and has minimal or no impact. |
|
Technical Execution and Functionality (20%) |
Solution is technically impressive, stable, and fully functional, demonstrating effective use of AI/web technologies. |
Solution is functional with minor issues and demonstrates good technical use of AI/web development. |
Solution is partially functional with moderate technical implementation. |
Solution has major functionality gaps and limited technical execution. |
Solution lacks functionality and demonstrates minimal technical implementation. |
|
Innovation and Creativity (20%) |
Solution is highly innovative, presenting a unique and creative approach to the problem. |
Solution is creative and introduces some novel ideas or features. |
Solution has moderate creativity, building on existing ideas with slight variations. |
Solution shows limited innovation and lacks unique approaches. |
Solution is not innovative or creative, following standard solutions with no new ideas. |
|
User Experience and Usability (15%) |
Solution is highly user-friendly, intuitive, and well-designed. |
Solution is user-friendly with minor usability issues, demonstrating good attention to UX. |
Solution has a moderate level of usability but may require additional design refinement. |
Solution is difficult to use, lacking user-centered design. |
Solution is very difficult to use, with poor design and minimal focus on usability. |
|
Feasibility and Scalability (10%) |
Solution is highly feasible, with a clear plan for real-world application and scalability. |
Solution is feasible with minor adjustments and has potential to be scaled with moderate effort.
|
Solution is moderately feasible but requires significant adjustments for real-world application. |
Solution has low feasibility, with unclear paths to implementation and scalability. |
Solution is not feasible or scalable in its current form, lacking practicality for real-world use. |
|
Presentation and Communication (15%) |
Team delivers an outstanding, clear, and engaging presentation, effectively explaining their solution and impact. |
Team delivers a clear presentation with minor areas for improvement, effectively communicating the solution. |
Presentation is understandable but lacks clarity in key areas, impacting the solution’s communication. |
Presentation lacks coherence, making it difficult to understand the solution and its benefits. |
Presentation is unclear and unengaging, with minimal explanation of the solution and its impact. |
