<aside> βš–οΈ

How Projects Are Judged

All submissions scored 0-100 across five criteria. Focus on what you do bestβ€”you don't need perfection in every area.

🎯 Key: Working demo + cited sources + clear problem = strong foundation

</aside>

Projects will be evaluated based on:

Judging Criteria - 2026

Criterion Weight What Judges Look For Project Context Quick Self-Check
Clarity 25% Problem statement (card) is crisp, Success Test is observable, demo is clear and reproducible Presentation & Iteration: Clear communication of solution Technical Execution: Documentation quality βœ… Can I explain my problem in 10 seconds?
Proof 25% Demo passes from clean start, Evidence Log is linked, sources are cited Technical Execution: Functionality and code quality Real-World Feasibility: Evidence of working solution beyond theory βœ… Does my demo run without help? Do I cite claims?
Usability 20% 3-Line Pitch is clear, captions/alt text present, grade-8 readability Gender-Inclusive Innovation: Accessible design reduces systemic barriers & Presentation & Iteration: Communication to diverse audiences βœ… Can a non-technical friend understand my pitch?
Rigor 20% README & ethical considerations defined, decisions & next risks defined, at least one risk addressed, tradeoffs explained. SDG Impact: Documented alignment with measurable goals + Ethical Tech Development: Bias, privacy, exclusion mitigation & Real-World Feasibility: Deployment thinking βœ… Did I document WHY I made key choices?
Polish 10% Timeboxed scope, tidy repo/files, no broken links, clean file structure, ethical considerations documented Technical Execution: Code quality and professionalism Ethical Tech Development: Ethics integrated throughout βœ… Would I be proud to share this link publicly?



πŸš€ Ready to Build?

Next steps:

  1. Review Submission Requirements
  2. Download Evidence Log + Risk Log templates from the Hackathon page
  3. Book a mentor session for feedback before you submit

Questions? Ask in #support channel on Discord πŸ’œ