This reference guide explains every field on the entry form and how they work together.
Section Selection Fields
These fields determine which competition section your entry belongs to:
| Field | Required | Description |
|---|---|---|
| Performance Type | Yes | Solo, Duo, Trio, Group, or Battle |
| Level | Yes | Skill/experience level (filtered by performance type) |
| Style | Yes | Performance category (filtered by performance type and level) |
| Age Group | Auto | Calculated automatically from dancer ages |
How Filtering Works:
- Select Performance Type first
- Available Levels filter based on what the event allows for that type
- Available Styles filter based on type and level
- Age Group is calculated, not selected
Performance Type Details
| Type | Min Dancers | Max Dancers | Notes |
|---|---|---|---|
| Solo | 1 | 1 | Single performer only |
| Duo | 2 | 2 | Exactly 2 performers |
| Trio | 3 | 3 | Exactly 3 performers |
| Group | 2 | 15 or more | Configurable per event |
| Battle | Varies | Varies | Special format per event |
Validation:
- Cannot save entry with wrong dancer count
- System shows error if count is invalid
- Some events may have custom limits for Groups
Age Calculation
How Age is Determined:
- The organiser sets the calculation method per event. The default is as of January 1 of the event year (the dance industry standard). The alternative is as of the first day of the event.
Solo Entries:
- Uses the dancer's individual age under the event's chosen method
Group Entries (Duo, Trio, Group):
- Uses the average age of all participating dancers, rounded to the nearest whole number
- Example: Dancers aged 12, 14, and 16 → Group age = 14 years (avg = 14)
Age Division Assignment:
- System automatically assigns the correct age division
- Based on calculated age and event's age division configuration
- No manual selection needed
Routine Detail Fields
| Field | Required | Visible | Description |
|---|---|---|---|
| Routine Name | Yes | Always | Name of your performance piece |
| Choreographer | No | Non-Battle | Who created the choreography |
| Music Title | No | Always | Name of the song |
| Music Artist | No | Always | Performer/band name |
| Duration (Minutes) | No | Non-Battle | Whole minutes portion |
| Duration (Seconds) | No | Non-Battle | Remaining seconds (0-59) |
| Special Requirements | No | Always | Props, lighting, staging needs |
| Notes | No | Always | Notes visible to studio and organiser |
Battle Entries Special Rules:
- Choreographer field is hidden (typically improvised)
- Duration field is hidden (varies by format)
- Other fields remain available
Field Details
Routine Name (Required)
- Appears on schedule and results
- Keep it clear and appropriate
- Examples: "Rise Up", "City Lights", "Warrior"
Choreographer
- Credit for the choreography
- Can list multiple names
- Examples: "Jane Smith", "Jane Smith and John Doe"
Music Title
- Song name for reference
- Helps organizers identify your music
- Example: "Unstoppable"
Music Artist
- Performer or band name
- Helps distinguish songs with same title
- Example: "Sia"
Duration
- Entered as minutes and seconds separately
- Used for schedule time calculations
- Events may set minimum and maximum time limits
Special Requirements
- Props you'll bring on stage
- Lighting requests (if available)
- Staging needs (placement, entrance side)
- Examples: "3 chairs", "Spotlight start", "Enter stage left"
Notes
- Private to your studio
- Not shared with organizers or judges
- Use for internal reminders
- Examples: "Quick change after this", "Backup dancer if needed"
Entry Number
What It Is:
- Unique identifier assigned to each entry
- Format: 3-digit number (#001, #002, etc.)
How It's Assigned:
- Automatically generated when entry is created
- Sequential based on creation order
- Cannot be changed after creation
Where It's Used:
- On the competition schedule
- For check-in at the event
- On results and certificates
- For announcements during competition
Saving Options
| Button | Action | Entry Status |
|---|---|---|
| Save as Draft | Saves without submitting | DRAFT |
| Save and Next | Saves, opens new form | DRAFT |
| Submit and Next | Submits, opens new form | SUBMITTED |
| Submit Entry | Submits and closes | SUBMITTED |
When to Use Each:
- Save as Draft: Need to confirm details later
- Save and Next: Creating multiple drafts quickly
- Submit and Next: Batch submitting entries
- Submit Entry: Final entry in your session
Validation Rules
Before Saving:
- Performance Type must be selected
- Level must be selected
- Style must be selected
- Routine Name must be entered
- Correct number of dancers must be assigned
Common Validation Errors:
| Error | Solution |
|---|---|
| "Routine name required" | Enter a name for the piece |
| "Please assign dancers" | Add dancers to the entry |
| "Invalid dancer count" | Adjust to match performance type |
| "Select a level" | Choose skill level from dropdown |
| "Select a style" | Choose style from dropdown |
Tips for Accurate Entries
- Double-check dancer birth dates - Wrong dates = wrong age division
- Verify dancer count - Must match performance type exactly
- Be specific with requirements - Helps organizers accommodate your needs
- Use notes for studio info - Track costume changes, music cues internally
- Save before navigating away - Unsaved changes will be lost