What is Team?
5 min read
Most class-management software genuinely doesn't have anything like this, and it's worth pausing on why. A regular class is casual by nature, someone can drop in, drop out, miss a week, no real consequences. A competitive team is a completely different kind of commitment, real contracts, real accountability, real stakes if someone stops showing up without a word. Team is Dancebase's answer to that side of a studio, built as its own genuine system, not a category with a stricter label slapped on it.

The shape of it, start to finish
- 1Auditions. A student applies to a specific team, often with a video submission, and you personally review it and accept or reject each application. Nobody joins a team by simply booking a slot the way they would a regular class.
- 2Eligibility (optional). A team can carry its own eligibility rules, the same condition-based gating a category uses, set on the builder's own Eligibility step.
- 3Contracts. Once accepted, a member goes through a real onboarding flow, a genuine agreement they read and accept, not just a checkout screen. This is where your studio's actual rules around commitment and consequences get spelled out plainly.
- 4Attendance. Tracked automatically, every single session, the moment a member taps their name in at the kiosk. No admin manually marking a roll sheet after the fact from memory.
- 5Strikes. Repeated no-shows without a genuinely valid reason become real grounds for removal, once a member's count hits the threshold you set for that team.

A student can genuinely be on more than one team
Up to a limit you set yourself, two teams by default, and multi-team membership comes with its own dedicated pricing tier, so a student on two teams doesn't just get charged double the first team's price by pure coincidence, you set that combined rate deliberately.
Each team runs on its own season, not the calendar year
- Duplicating an existing team is a genuinely fast way to set up a second one with the same base policies, then adjust just what's different.
- A team's absence reasons and multi-team pricing tiers are shared studio-wide settings, configured once, applying consistently across every team you run.