“Powwow” covers two very different kinds of gathering. A traditional or social powwow is not judged at all — dancing, drumming and visiting happen on their own terms, with no placings. A contest powwow is a distinct, publicly advertised category: the host committee states up front that specific dance sessions are judged for points and prize money, dancers register in advance for a category, and results are posted. This article is about that second kind only, and about the organiser’s side of it — how the categories, divisions and scoring actually work — not about the cultural or spiritual meaning of the dances or regalia, which is not this article’s place to explain.
The source for the structure below is a major regional contest powwow in the United States that publishes its own dance categories and rules each year. It is a useful case study for the same reason the other judged festivals on this site are: a real, published rulebook, not a guess at how these events work.
It’s a point system across the whole weekend, not one judged score
If you have seen a school-competition-style grade band (an A/B/C scheme, say) attached to a powwow somewhere, that is not how a real contest powwow scores. The rules here describe a points-accumulated system: scoring starts from the first grand entry (Friday at 11am in this event’s schedule) and contestants carry a registrar-issued number that is recorded again at every grand entry across the weekend. The placing is built from points gathered across those sessions, not from a single performance score on one day. The rules name who selects the judges — the contest committee, together with the arena director and head judges — but do not state how many judges sit on each category, so that number is left unstated here rather than guessed.
For anyone building this in software, the lesson is to model the contest as a multi-session points ledger attached to one registered entry, not as a single scoresheet per category. Our judge scoring and tabulation guide covers setting up multi-round and multi-session scoring so points carry forward correctly to a final placing.
Three axes, not one list: style, gender and age — and the grid is ragged
The structural problem a contest powwow poses for software is this: a category is dance style × gender × age, but the three do not combine into a clean, evenly-filled grid. The style list that is offered actually changes by age band, and the gender split itself disappears at both ends of the age range. Generating “every style for every age for every gender” would invent categories the rules do not run. The real list has to be entered combination by combination, exactly as the rulebook states it.
| Age division | Ages | Gender split | Styles offered |
|---|---|---|---|
| Tiny Tot | 6 and under | Combined — no gender split | One single category, no style split |
| Junior | 7–12 | Girls / Boys | Girls: Jingle, Fancy, Traditional. Boys: Grass, Fancy, Traditional, Chicken |
| Teen | 13–17 | Girls / Boys | Same split as Junior |
| Adult | 18–39 | Women / Men | Women: Jingle, Fancy, Northern Buckskin/Cloth, Southern Buckskin/Cloth. Men: Grass, Fancy, Northern Traditional, Southern Straight, Chicken |
| Senior | 40–59 | Women / Men | Styles collapse: Women — No./So. Traditional, Fancy Shawl/Jingle. Men — No./So. Traditional, Grass/Fancy/Chicken |
| Golden Age | 60–69 | Women / Men | Same collapsed pattern as Senior |
| Living Treasure | 70 and over | Women / Men | All styles combined into one category per gender |
Read across the table and the shape becomes obvious: the youngest dancers compete in one combined category with no style or gender split at all; Junior and Teen keep the gender split but offer three or four styles each; Adult is where the style list is widest and most different between women and men; Senior and Golden Age quietly fold several named styles into combined style groups (“No./So. Traditional” and “Grass/Fancy/Chicken” are each a single category, not three); and Living Treasure drops the style split entirely and runs “all styles” as one category per gender. The source rulebook lists 34 named category rows to cover this (the published total is 33 because one source row spans two age bands that this model splits into two, since age groups here are per band).
Run this kind of event in a generic “age group × gender × item” generator and you will either under-build it (missing the style collapse at the older ages) or over-build it (offering styles to Senior dancers that the rulebook never lists). The correct approach is to set up each age group, then assign only the specific competition items that group actually runs — which is exactly how eTalenter’s “assign competitions to groups” step works, rather than assuming every item applies to every group by default.
Registration rules that double as scoring rules
A few registration rules in the source document directly shape how the contest is scored and run:
- One category only, no switching. A contestant registers into a single category and cannot move to a different one once registered — so the points ledger for that dancer never has to merge across categories.
- Full regalia required. Entry into the contest requires appearing in full regalia for the category entered; this is a participation rule the rulebook states, not a detail this article interprets further.
- Thin categories get combined. If fewer than five dancers register in a category, the contest committee may combine it with another. Small-field categories are a real operational problem for any points-based contest, and stating the combine threshold in advance avoids disputes later.
- Fixed windows. Online registration opens and closes on set dates ahead of the event, and onsite registration has its own cutoff (2pm on the Saturday in this event’s schedule).
Each of these is the kind of rule that is easy to skip when building a contest in software and then becomes a dispute on the day. Our online competition registration guide covers setting registration windows, locking a contestant to one category, and handling a combine-if-too-few rule before entries open.
The Drum Contest: a separate category, entered by a group
Alongside the dance categories, the source rulebook runs a Drum Contest as its own entry. It is judged separately from the dance categories, and critically, the entrant is a singing group, not an individual — the same “team as the unit of entry” pattern seen in couple and group events elsewhere on this site. Placement counts for a drum contest vary from one powwow to the next, so no fixed number of places is assumed here; set that per event rather than copying a figure from somewhere else.
What this means for organisers of any points-based, multi-session contest
Four things carry over from this one event to any contest that scores across more than one sitting. First, decide whether your contest is a single-score event or a points-across-sessions event, and build the ledger to match — they are not interchangeable. Second, build your category list from what the rules actually state for each age band, not from an automatic cross-product of every style, gender and age; a ragged structure is normal, not a mistake. Third, state your combine-if-too-few threshold and your one-category-only rule (if you want one) before registration opens, not after. Fourth, treat a group entry — a drum, a choir, a team — as a single row with named members, the same discipline used for the tango championship’s couples and the hula festival’s hālau.
Frequently asked questions
Is a contest powwow scored with grades, like a school competition?
No. The event this article is based on runs a points-accumulated system from the first grand entry onward, tracked against a registrar-issued number, not a single graded score per performance.
How many dance categories does a typical contest powwow run?
It varies by event. The one documented here runs 34 named age-and-style combinations across seven age divisions, but the style list differs by age band rather than repeating evenly, so a different powwow’s count will not match this one.
Can a dancer change category after registering?
Not in the event this article is based on — contestants register into one category only and cannot switch once registered. Build this as a lock in your registration step if you want to run the same rule.
Run a points-based or multi-session contest with eTalenter
eTalenter handles judged contests that don’t fit a simple single-score template: age groups with different items per group, points accumulated across multiple sessions, group entries with named members, registration windows, and a combine-if-too-few rule for thin categories. To see how the setup actually looks, open a live demo and log in as a demo coordinator or judge — there is no sign-up, and the demo is read-only, so nothing you click can change a real event.
Questions about setting up your own contest? Message us on WhatsApp or email support@etalenter.com.
Leave a Reply
You must be logged in to post a comment.