Most competitions don’t fail because the performances were bad — they fail because of something nobody decided in advance: a tie-break rule that didn’t exist, a rubric judges saw for the first time on stage, a results sheet with one wrong name on it. These mistakes organizers make running a competition repeat across school kalolsavams, church talent tests and club kalotsavams alike, because the underlying problem is always the same: a decision got made on the day instead of in the setup. Here are the 10 that cause the most disputes, late nights and reruns — and how to fix each one before your next event.
1. No published rubric until the morning of the competition
If judges only see the scoring criteria right before the item starts, every judge improvises their own weightage in their head — one favours technique, another favours stage presence, and the scores don’t agree. Parents notice the inconsistency even when they can’t name it. Fix: decide the criteria and marks per criterion weeks ahead, print it, and hand every judge the same rubric before the panel sits down. A library of ready weightages (competition scoring rubric templates) or a guide to building your own fair rubric gets this settled in an afternoon.
2. Paper scorecards and manual tabulation
Five judges, a stack of paper scorecards, and someone adding it all up by hand at 9pm — this is where arithmetic errors creep in, and it’s why results get announced hours after the last performance ends. Fix: move scoring onto a judging and tabulation system that totals the moment the last judge submits, so results are minutes away instead of hours.
3. No tie-break rule decided in advance
A dead-even score between two candidates is common, and arguing out a tie-break rule in front of both families is the worst possible moment to invent one. Fix: agree the tie-break method — highest single criterion, judge count, re-performance, or a shared rank — before the competition starts, and publish it with the rules. See how to break a tie in a competition for the standard options.
4. Judges who were briefed five minutes before the panel
A judge who doesn’t know the rubric, the time limit or the deduction rules will score on instinct — and instinct varies wildly from one panel to the next, especially across multiple stages running at once. Fix: brief every judge on the same rubric, time limits and deductions beforehand, and where bias is a concern, hide candidate names from the scoring screen with blind judging by chest number.
5. No call sheet or running order published
Without a clear running order posted where candidates and coordinators can see it, items start late, candidates miss their turn, and the whole schedule drifts by the afternoon. Fix: publish the running order and chest numbers ahead of time and work from a printed event-day checklist — see our arts fest event day checklist.
6. Skipping chest-number anonymity
When a judge can see or hear a candidate’s name, school or unit, unconscious bias creeps into the score — especially in a small community where judges often know the families. Fix: assign chest numbers and keep the judging screen name-blind, so the scoring panel sees “Candidate 214”, not a name they recognise.
7. Treating every event level the same
A school-level kalolsavam with Houses, a district festival with Schools as the units, and a single-city club event are three different hierarchies — reusing one level structure for all of them forces a bad fit, like squeezing houses into a district event that actually has sub-districts and schools. Fix: build the age groups and event levels to match your actual hierarchy before registration opens, not after. The system should flex to your structure, not the other way round.
8. No deduction or disqualification rules written down
“Did they go over time?” “Was that prop allowed?” — without deduction rules settled in advance, every one of these becomes a judgement call made on the spot, and whichever way it goes, someone will feel it was unfair. Fix: write the deduction table (time overrun, disallowed props or material, identifying marks on a written entry) into the rules before the event, the same way our sample competition rules template does.
9. Collecting entries on paper or Excel until the week before
Hand-collected entry forms mean someone is re-typing names, age groups and item choices into a spreadsheet days before the event — exactly when mistakes are most likely and least fixable. Fix: open online registration early so candidates or guardians submit directly and a coordinator reviews and approves each entry, instead of re-keying a stack of paper forms.
10. Publishing results without a review step
The moment totals are calculated is not the moment to publish them — a wrong chest number, a missed score, or a late correction needs a human check first, and once a result is on the podium or the projector, undoing it is public and awkward. Fix: build in a review-and-confirm step before anything goes public, so a coordinator signs off on winners before results publish online, on the podium, or on social media.
How these mistakes compound
None of these ten happen in isolation — a late rubric usually travels with unbriefed judges, and paper tabulation usually travels with a missing review step. That’s why organizers who fix even three or four of them (a published rubric, a tie-break rule, online registration, and a review step before publishing) see most of the complaints disappear, long before they get to the rest of the list. eTalenter keeps the whole chain — registration, rubric, judging, tabulation, review and publishing — in one system precisely so these decisions get made once, in the setup, rather than improvised on the day.
Frequently asked questions
What is the single biggest mistake in running a judged competition?
Not publishing the scoring rubric before the event. Every other scoring problem — inconsistent judges, disputed results, long tabulation delays — traces back to criteria and weightage that weren’t agreed and shared in advance.
How do we stop results disputes after the event?
Settle the rubric, deduction rules and tie-break method before the competition, keep judging blind by chest number, and add a review step before results publish. Most disputes come from a rule that was decided — or changed — after the fact.
Do small single-level events need all of this, or just big multi-level festivals?
A single-city club event or a one-school competition needs the same rubric, tie-break and review discipline as a multi-level festival — it just needs less of the level-structure planning in mistake #7. The scoring mistakes don’t scale down with event size.
Run your next competition without these ten mistakes. See the platform, open a live demo and log in as a demo coordinator or judge to see rubrics, tabulation and review in action (no sign-up), WhatsApp us, or email support@etalenter.com.
Leave a Reply
You must be logged in to post a comment.