A group dance item takes up more of your schedule, your stage and your judging panel’s attention than any solo item on the programme. One team can be eight to twenty dancers, several props, a backing track that has to cue correctly, and — at a school or club fest — often more than one team from the same house or unit competing in the same item. Get the logistics wrong and the symptom isn’t a bad performance, it’s a programme running forty minutes late by the third group item. This guide is the organiser’s side of running group dance well: scheduling realistic slots, handling several teams per unit, managing props and music safely, and scoring fairly across a large field. If you’re looking for the marking scheme itself, see our group dance judging criteria guide; if you’re coaching a team to prepare, see how to prepare for a group dance competition.
Why group items break a programme that a solo item wouldn’t
A solo item is one performer, one entry, one cue. A group item multiplies almost every risk: more dancers means more time walking on and off stage, more props means more setup and clearance time, a shared backing track means more that can go wrong technically, and — because group items are often capped per unit rather than per dancer — the same house or unit may enter two or three separate teams under different team names in the same item. None of this is a reason to avoid group items; it’s a reason to schedule them differently from solo items rather than giving every item on the programme the same flat time slot.
- Stage footprint is bigger. A dancer alone needs a few seconds to walk to position; a team of fifteen with a formation entry needs real walk-on time, and a team that sets props on the floor needs clearance time before the next team can enter.
- Changeover, not performance time, is what overruns a schedule. The piece itself might run the same 4–6 minutes as a solo, but the gap between one team leaving the stage and the next starting is where minutes quietly disappear across a long programme.
- One item can mean several entries from the same unit. Unlike most solo items, where a unit sends one candidate per age group, group items are commonly capped by number of teams per unit rather than one entry only — so the running order for a single item can be longer than it looks on paper.
Scheduling realistic stage slots
The single most common scheduling mistake is timing a group item by its performance length alone. Build the slot from three numbers instead: walk-on time, performance time and clearance time.
- Add a fixed changeover buffer per entry — commonly 1–2 minutes for a group item versus 30–45 seconds for a solo — and hold to it; teams that use props or a floor-level formation need the higher end of that range.
- Stagger backstage calls so the next team is already in the wings before the current team finishes, rather than calling a team only once the stage is clear. A team that has to be found backstage after their cue is the most common cause of a stalled programme.
- Group all entries of the same item back to back rather than scattering them across the day — judges calibrate to each other’s scoring as they watch a run of comparable entries, which is harder to do if a group item is interrupted by three solo items in between.
- Build in one buffer slot per 8–10 entries for the inevitable run-over, rather than discovering the overrun only at the end of the session.
Handling several teams per unit in the same item
Where the rules allow more than one team per unit in a group item, each team registers and competes as its own entry with its own name — “Green A” and “Green – Vasantham” from the same house are two separate entries, not one house entry split in half. Plan for this explicitly rather than assuming one team per unit:
- Confirm the per-unit team cap before registration opens, and state it on the item’s rules sheet — a cap discovered after teams have already formed causes disputes that are hard to resolve fairly.
- Give every team its own chest-number block or team code, never a shared number, so the draw, the call sheet and the judges’ sheets can tell “Green A” apart from “Green – Vasantham” at a glance.
- Draw the running order across all teams in the item together, not grouped by unit, so two teams from the same house aren’t forced to perform back to back — that reduces the chance of a props or costume mix-up between them.
- Keep team rosters locked once the draw is published. Group items are usually built during registration, with named candidates assigned to a named team — allowing late roster swaps after the draw invites disputes about eligibility.
Props, backing tracks and the backstage handoff
Most delays and disputes in group items trace back to the handoff moment — the thirty seconds between one team clearing the stage and the next team’s music starting.
- Collect music files well before the event, in one format, from one point of contact per team — not from individual dancers on the day. A missing or corrupted track found minutes before a team’s slot is avoidable with an advance collection deadline.
- Publish the prohibited-prop list before registration (commonly fire, water, items that can damage the stage surface, and anything that could injure another performer) so teams don’t build choreography around something that will be refused at the door.
- Assign one person to each wing to clear abandoned props immediately after a team exits — a prop left on stage is both a safety hazard for the next team and a common, avoidable deduction for the team that left it.
- Have a backup playback device and a saved copy of every track cued and ready, and agree in advance how a team restarts if the music genuinely fails mid-performance, rather than deciding it live in front of the audience.
Scoring group items fairly across a large field
A group item often draws more entries than any solo item in the same category, which makes judge fatigue and drift a real risk by the tenth or twelfth team. The organiser’s job is to protect the panel’s consistency, not just collect their scores.
- Brief judges on the published rubric before the session starts, not between entries — see our guide to designing a fair scoring rubric for how the criteria should be weighted and published in advance.
- Use the same panel for every entry in the item where possible, rather than rotating judges mid-item, so scores stay comparable across the full field.
- Average or normalise across multiple judges rather than relying on one judge’s total — see how judges score fairly with multi-judge tabulation for the method, including dropping an outlier score where the rules allow it.
- Let the system tabulate as scores come in rather than totalling on paper after the session — with ten or more group entries, each with several judges and criteria, manual tabulation is where arithmetic errors creep in unnoticed.
A printable stage-slot planning checklist
| Step | What to confirm | Done |
|---|---|---|
| Before registration | Per-unit team cap, prohibited props list, music file format and submission deadline published on the rules sheet. | |
| After registration closes | Every team has its own chest-number block/team code; rosters locked; music files collected from one contact per team. | |
| Building the draw | Running order drawn across all teams in the item together; teams from the same unit not scheduled back to back; all item entries grouped in one block on the day. | |
| Scheduling the slot | Walk-on + performance + clearance time added per entry (not performance time alone); one buffer slot built in per 8–10 entries. | |
| Backstage on the day | Next team called to the wings before the current team finishes; one person per wing assigned to clear props immediately on exit; backup playback device ready. | |
| Judging the item | Panel briefed on the published rubric before the session; same panel held for the full item; scores tabulated as they come in, not totalled afterwards on paper. |
Frequently asked questions
How much time should I schedule for a group dance item?
Schedule the item’s performance time limit plus a fixed changeover buffer per entry — commonly 1–2 minutes for a group item with props or a floor formation, versus 30–45 seconds for a solo item. If the item allows several teams per unit, multiply the buffer by the total number of teams expected, not the number of units, since each team is a separate entry with its own walk-on and clearance time.
Can the same house or unit enter more than one team in a group item?
Yes, where the item’s rules allow a per-unit team cap above one — each team registers and performs as its own named entry (for example “Green A” and “Green – Vasantham” from the same house), not as one combined entry. Publish the cap before registration opens and give each team its own chest-number block so the draw, call sheet and judges’ sheets never confuse one team for another.
How do we keep judging consistent across a large number of group entries?
Brief the full panel on the published rubric before the session starts, keep the same judges on the item from first entry to last, and group all of that item’s entries into one continuous block rather than spreading them through the day — judges calibrate against each other by watching comparable entries in sequence. Average or normalise scores across judges rather than relying on any single judge’s total, and tabulate as scores come in so a data-entry slip is caught immediately rather than at the end of a long session.
Running group dance at your event?
eTalenter handles the parts of a group item that paper and spreadsheets struggle with: team registration with named rosters, a chest-number block per team, a published scoring rubric for the judging panel, live multi-judge tabulation as scores come in, and a draw and call sheet your backstage team can actually run from. See it for yourself with a live kalolsavam demo — log in as a demo coordinator or judge, no sign-up needed, and nothing you click can change the event. For the full event-day backstage flow, see our guide to token and call sheet management, and for the organiser side generally, explore eTalenter’s competition management software, message us on WhatsApp, or email support@etalenter.com.
Leave a Reply
You must be logged in to post a comment.