Judges don’t score your code. They score your product, your pitch, and your potential. Understanding the rubric is the difference between “good project” and “winning project.” Here’s what they actually evaluate.
The Standard Hackathon Rubric
Most hackathons in India (SIH, corporate, platform-hosted) use a variation of these 5 criteria:
| Criteria | Weight | What Judges Actually Check |
|---|---|---|
| Innovation/Novelty | 20-25% | Is this different from what exists? Did they think creatively? |
| Technical Implementation | 20-25% | Does it work? Is the architecture sound? Did they use tech well? |
| Impact/Usefulness | 20-25% | Would real people use this? Does it solve a real problem? |
| Demo/Presentation | 15-20% | Can they communicate clearly? Does the demo work live? |
| Completeness | 10-15% | Is it a finished product or just a mockup? |
Innovation/Novelty (20-25%)
What gets high scores:
- Solving a problem nobody else thought of
- Using technology in an unexpected way
- Combining two existing ideas into something new
- Addressing an underserved audience
What gets low scores:
- “Another todo app” or “another chatbot”
- Direct copies of existing products
- Just wrapping an API without adding value
Technical Implementation (20-25%)
What gets high scores:
- It WORKS. Live demo doesn’t crash.
- Multiple systems integrated (frontend + backend + AI + external API)
- Error handling (what happens with wrong input?)
- Good architecture (even if simple)
What gets low scores:
- Only mockups/slides with no working code
- Hardcoded everything (only works with pre-loaded data)
- Crashes during demo
Impact/Usefulness (20-25%)
What gets high scores:
- Clear target user (“ASHA workers in rural Bihar” not “everyone”)
- Quantifiable impact (“saves 2 hours/day” or “reduces cost by 40%”)
- Works for India specifically (regional languages, low internet, affordable)
What gets low scores:
- “It would be useful for society” (vague)
- No clear user research
- Solution looking for a problem
Demo/Presentation (15-20%)
What gets high scores:
- Confident, clear, under time limit
- Live demo works first try
- Shows real data, not Lorem ipsum
- Answers judge questions directly
Read: Complete demo and pitch guide
Completeness (10-15%)
What gets high scores:
- End-to-end flow works (not just one screen)
- Deployed and accessible via URL
- Has user auth, proper navigation, error states
Secret Criteria (Unwritten)
Judges also unconsciously evaluate:
- Team energy – do they seem excited about their own project?
- Story – is there a narrative? (“We faced this problem ourselves…”)
- Polish – consistent design, proper fonts, no broken layouts
- Mobile-ready – many judges check on their phone while listening