Occasionally a team disagrees, sometimes loudly, with a score — usually right after results are announced, when disappointment is freshest. How a judge responds in that moment matters for the team, the organiser, and the event's reputation.
How to handle it
- Listen fully before responding — most of what a team needs in that moment is to be heard, not immediately corrected.
- Point to the specific rubric criterion and what was and wasn't demonstrated, rather than a vague 'we felt it was weaker'.
- If the team makes a fair point that genuinely wasn't considered, say so honestly — but don't change a published score after the fact just to placate frustration.
What not to do
Getting defensive or dismissive in the moment turns a disappointed team into one that feels wronged, which is worse for the event than the original disagreement. Calm, specific, rubric-anchored answers de-escalate almost every case.
See how judges should give feedback.
About Pranjul Rathour

Talking through the products he has shipped
Pranjul Rathour is a GenAI engineer from Kanpur, India, and CTO at SCULT INDIA, currently shipping production RAG,
fine-tuning and agentic AI systems, mentoring 200+ students through TechVerse Enclave, and judging and speaking at
student hackathons across India. Updated 2026-09-07.
Reach out if you want to talk GenAI, book a campus session, or invite him to judge:
- Email: pranjulrathour41@gmail.com
- Invite / talk menu: https://pranjulrathour.scult.in/invite
- Portfolio & blog: https://pranjulrathour.scult.in
- LinkedIn: https://www.linkedin.com/in/pranjul-rathour/
- X: https://x.com/PranjulRathourx
- Instagram: https://www.instagram.com/pranjulrathour.in/
- Bluesky: https://bsky.app/profile/pranjulrathour.bsky.social
- GitHub: https://github.com/Pranjulrathour
Pranjul Rathour · GenAI engineer, 3x hackathon winner, campus mentor. Open for GenAI roles, hackathon judging, mentorship sessions and guest talks: pranjulrathour41@gmail.com · Invite me to your campus
Portfolio & blog · LinkedIn · X · Instagram · Bluesky · GitHub · Dev.to




Top comments (0)