Loading...

Sistema Dance — Inscrição e Gerenciamento
PTESEN

Dance festival regulations: guide + ready-made template

What every set of regulations needs — explained clause by clause — and a ready-made template for you to copy and adapt.

A practical guide for organizers · Sistema Dance

The regulations are the most important document of a dance festival. They answer, in writing and before the event, every question that would otherwise come up in the middle of it: who can register, how long each performance lasts, how scoring works, who wins what. Well-written regulations prevent almost every argument on the day — because the rule was already there, clear, and everyone accepted it when they registered.

In this guide you'll find what each clause needs to say and why — and, at the end, a complete template to copy and fill in with your festival's details. Use it as a starting point and adjust it to the reality of your event; there's no generic set of regulations that fits everyone, but there is a backbone that every good one has.

The clauses you can't leave out

Before the template, it's worth understanding the role of each part. These are the sections that hold up the regulations of a dance festival:

Identification and purpose

Festival name, edition, who is organizing it, date and venue. It seems obvious, but it's what makes the document valid and orients whoever reads it. A short paragraph on the purpose of the event also helps give it an identity.

Genres and divisions

The list of what the festival accepts (classical ballet, jazz, contemporary, street dance, tap, rhythms…) and, where it makes sense, the subgenres within each. Make it clear whether there is a competitive division and a showcase division.

Categories by number of dancers

Solo, duo, trio, group — with the minimum and maximum for each. Define the boundary between trio and group so there's no room for doubt, because that's exactly where doubt appears.

Age brackets and tolerance

The brackets (baby, children, junior, adult, master…) with the cutoff age for each, the reference date for age (normally the age reached during the year of the event) and the tolerance: how much of the cast can be outside the bracket. This is the clause that generates the most appeals — write it precisely.

Performance time

The maximum duration per category (solos usually get less time than groups) and the tolerance accepted in seconds. Also say what happens if the music runs over time.

Registration, deadlines and fees

When registration opens and closes, the batches and prices, what defines the batch (generally the payment date), the payment method and the cancellation and refund policy. Without this in writing, every case becomes a negotiation.

Music

File format, submission deadline, how to label it (school name, routine, category) and what to do if something fails on the day. An organized festival asks for the music in advance, not at the theater door.

Judging and panel

How many judges, how the scores are combined (simple average or dropping the highest and lowest), the criteria judged and their weights, and how ties are broken. Transparency here is what gives the result credibility.

Awards

How ranking works (by score, by award tier, by placement), what the prizes are and whether there are special awards (best dancer, costume, choreography, best group of the festival). Make it clear when and how the result is announced.

Image and copyright rights

One clause authorizing the festival to record and publish images of the performances, and another passing to the participants the responsibility for the copyright of the music and choreography they use. It's basic protection for the organization.

Final provisions

The clause that closes the document: registration implies full acceptance of the regulations, and any cases not covered will be resolved by the organizers. Simple, but important.

Ready-made template to copy

Below is a complete template. Copy it, paste it into your text editor and replace everything [in brackets] with your festival's details. Adjust, cut and add whatever you need — it's a starting point, not a straitjacket.

Regulations Template

Regulations — [FESTIVAL NAME], [Nth] Edition

Organized by: [name of the organizing school/institution]. Date: [event dates]. Venue: [theater/gymnasium, city — state].

1. The festival and its objectives

1.1. [FESTIVAL NAME] is a [competitive / showcase / competitive and showcase] dance festival, hosted by [organizer], with the goal of [bringing together, connecting and celebrating dance in the region…].

2. Genres and divisions

2.1. Performances will be accepted in the following genres: [classical ballet, repertoire ballet, jazz, contemporary, street dance, tap, rhythms, …].

2.2. The festival will offer the [competitive and showcase] divisions, as chosen at the time of registration.

3. Categories (by number of dancers)

3.1. Solo: 1 dancer. Duo: 2. Trio: 3. Group: from [4] to [maximum number] dancers.

3.2. [Specific rules, if any — e.g., large group above X dancers.]

4. Age brackets

4.1. The age brackets are: [Baby (up to 6 years), Children (7 to 9), Pre-junior (10 to 12), Junior (13 to 15), Adult (16 to 29), Master (30+)].

4.2. The age considered is the age [reached during the year of the event].

4.3. Tolerance: up to [e.g., 30%] of the cast may be outside the registered bracket. The category is determined by the [average age / age of the oldest dancer].

5. Performance time

5.1. Solo, duo and trio: up to [3] minutes. Group: up to [5] minutes.

5.2. Tolerance of [10] seconds. If the limit is exceeded, [the performance may be stopped / a score deduction will apply / warning only].

6. Registration, deadlines and fees

6.1. Registration runs from [date] to [date], exclusively through [website/system/form].

6.2. Fees: [Batch 1 — $X per routine until DATE; Batch 2 — $Y; per-dancer fee, if any]. The batch is determined by the [payment date].

6.3. Cancellation and refund: [policy — e.g., X% refund until DATE; after that, no refund].

7. Music

7.1. Music must be submitted by [date], in [MP3] format, labeled with [school, routine and category].

7.2. We recommend that each group bring a backup copy on the day of the event.

8. Judging and the panel

8.1. The panel will consist of [number] judges of recognized expertise, with no ties to the participants.

8.2. The final score will be [the average of the scores / the average after dropping the highest and lowest], judging the criteria of [technique, interpretation, choreography, costume].

8.3. In case of a tie, the tiebreaker will be [highest technique score / panel decision]. The judges' decisions are final and not subject to appeal.

9. Awards

9.1. Awards will go to [the top three of each category/bracket / by score tier: gold, silver, bronze].

9.2. Special awards: [best dancer, best choreography, best costume, best group of the festival].

9.3. Results will be announced [at the end of each session / at the end of the event / on the festival website].

10. Image and copyright rights

10.1. By registering, participants authorize the festival to record and publish, free of charge, images and videos of the performances for promotional purposes.

10.2. Responsibility for the copyright of the music and choreography used rests solely with each participating group.

11. Final provisions

11.1. Registration implies full acceptance of these regulations.

11.2. Any cases not covered will be resolved by the festival organizers.

11.3. Organizer contact: [phone / email / person in charge].

Generic template, for adaptation. It does not replace legal advice when your event calls for it.

How to adapt the template to your festival

Be specific. Every bracket you leave vague becomes a question on event day. Round numbers and deadlines with an exact date are worth more than "at the organizers' discretion".

Write with the "what if?" question in mind. What if two groups tie? What if the music runs over time? What if a dancer registers through two schools? Every "what if?" answered on paper is one less problem later.

Align the regulations with registration. It does no good for the regulations to say one thing and the entry form to allow another. Ideally, the registration system already enforces the regulations' rules automatically — age within the bracket, number of dancers per category, music length within the limit. That way the regulations stop being a text nobody reads and become a rule the system enforces on its own. That's exactly what Sistema Dance does: you set up your regulations' rules once, and every registration is validated against them on the spot.

Common mistakes in regulations

Leaving age vague. Not saying which date counts for age, or forgetting the tolerance, is the #1 cause of appeals. Close that door.

Not defining what a batch is. If the regulations don't say the batch is determined by the payment date, every school will want the previous batch's price. Write it down.

Forgetting image rights. Without that clause, you don't have clear authorization to use the event's photos and videos in your promotion.

Regulations nobody can follow. Too many rules, too many exceptions, and the festival grinds to a halt. Write enough to leave no doubt — and let the registration system take care of enforcing the rule.

Your regulations, turned into a rule the system enforces on its own

In Sistema Dance you set up genres, categories, age brackets, age tolerance and music length once — and every registration is automatically validated against your regulations. Talk to us and see how it works.

Talk to us Read the complete guide →