A decoration competition has no stage, so judging it is a logistics problem, not a scoring problem. Classroom decoration, pookalam spread across a whole campus, diya tables in a hundred booths, a float or tableau line parked along a route — in every one of these the judges have to go to the entries, not the other way round. Visiting order, how marks get compared across a panel that splits up to save time, and keeping a day-1 entry’s score fair against a day-2 entry are the real problems organisers hit. This guide covers that organiser-facing side; for the rubric itself (what to score on a single decorated item), see our diya decoration judging-criteria guide.
Why a no-stage competition breaks a normal judging plan
A stage item has one queue, one panel, one score within minutes. A decoration competition scatters entries across classrooms, hallways, a parking lot or a parade route, so the same panel cannot watch everything back-to-back. Organisers who skip this planning step end up with judges wandering the campus with a paper clipboard, no fixed order, and scores that drift as the day goes on because the first classroom they saw set an unspoken baseline the last one is unfairly measured against.
Route planning and published visiting slots
Treat each venue (a classroom, a pookalam site, a decorated booth, a parked float) as a stage with its own slot, the same way a stage-item schedule works in Time Management. Fix a visiting route in advance — shortest total walking distance, not the order entries were registered — and publish each venue’s visiting window to the entrants so a teacher or team captain knows when to be present. A published slot also stops entries from quietly adding finishing touches after the panel has already scored a neighbouring venue.
Splitting the panel without splitting the standard
With dozens or hundreds of venues, one panel walking together is too slow — most organisers split judges into two or three teams covering different zones in parallel. The risk: Team A’s “8/10” and Team B’s “8/10” are not the same 8 unless every judge is scoring from the identical rubric and has seen at least a few entries in common. Fix this with a short joint calibration round before the teams split (score 3-4 sample entries together, agree the line between bands), and a score-normalisation pass afterward — rank each team’s own list first, then merge, rather than comparing raw marks across teams directly.
Unscored reconnaissance to stop day-1 score drift
When judging is spread over more than a few hours — or across two days for a pookalam or float competition with a long build time — the earliest entries get scored against a baseline the judges haven’t fully formed yet, and later entries get scored against a baseline that has crept up or down. Run an unscored walkthrough of every venue first, with no marks given, purely so the panel has seen the full range before scoring anything. Only start awarding marks on the second pass. It costs one extra lap of the route and removes the single biggest source of disputed results in this format.
Entry numbers instead of names, and safety as a scored criterion
A decorated classroom or booth usually carries the class or house name in plain sight, which a stage item’s chest-number system is built to avoid. Where the venue itself can’t be anonymised, at minimum keep the score sheet keyed to an entry number rather than a name, and brief judges not to write the name on their sheet — it keeps the written record defensible even when the judge saw the label on the door. For float, decoration and pookalam entries involving flame, electrical wiring, raised platforms or crowd-adjacent structures, add a pass/fail safety inspection as its own scored line before the design marks are given — an unsafe entry should not be able to win on design alone.
Capturing marks on site and publishing results
Judges score from a phone or tablet at each venue rather than carrying paper sheets back for someone else to enter later — the same reason stage judging moved off paper. Marks for every venue land in one place as the panel finishes its route, so tabulation and results publishing don’t wait for the last zone to walk back in. Run the whole decoration competition inside the same event as your stage items so one chest-number/ID-card setup, one results screen and one set of certificates cover everything, rather than treating the decoration contest as a separate side-event.
FAQ
How many judges does a multi-venue decoration competition need?
Enough to split into 2-3 teams without any one team covering more than 20-25 venues in a day — beyond that, fatigue becomes its own source of drift even with calibration.
Can one team of judges decorate more than one venue?
Treat it as a different Participant Type setup in your rules, not a judging problem — decide and publish whether a house or class may enter multiple venues before registration opens, since it changes how entries are grouped for results.
What if the decoration competition spans two days?
Run the unscored reconnaissance lap at the start of each day, not just once at the very beginning — the baseline a panel formed on day 1 doesn’t automatically carry over cleanly to day 2 entries built under different conditions.
See it before you run one: open a eTalenter live demo and log in as a demo coordinator or judge — no sign-up needed. For a school arts fest or kalolsavam built around eTalenter, see the kalolsavam management software page. Questions on setting up your event: WhatsApp +91 96056 56508 or support@etalenter.com — we help with the software, not with judging your entries.
