Most scoring inconsistency between judges traces back to skipping a fifteen-minute briefing before the first pitch. It is the cheapest fix in the entire judging process.
What to actually cover
- Walk through the rubric line by line — what does a 3 vs a 4 on 'execution' actually mean, concretely.
- Score one sample team together, out loud, and discuss any disagreement before real scoring starts.
- Agree on the conflict-of-interest process and the tiebreak process, so nobody improvises either mid-event.
- Confirm logistics: how long each team gets, whether Q&A time counts against the five minutes, where scores get submitted.
Do this even for a panel of two
Judges assume calibration only matters for large panels. Two judges scoring independently without a shared reference point can disagree just as sharply as ten.
See panel judging vs solo judging.
GenAI engineer and AI product builder with 2+ years shipping production-grade AI systems: RAG pipelines, fine-tuned LLMs, hybrid retrieval and multi-modal apps across vision, speech and OCR, architected end to end from ingestion to deployment. Leads engineering for SCULT INDIA's 14-member team, founded the 500+ member TechVerse Enclave community and has mentored 200+ students. Three hackathon first prizes: Changethon 2025 (IIT Roorkee), Product Genesis at Vividhotsava 2025 (CSJMU Kanpur) and BYTEBATTLE (MeetKats).
Open to GenAI roles, hackathon judging, mentorship sessions and guest talks at colleges. Email pranjulrathour41@gmail.com.
