Biweekly classes — the quiet scheduling feature studios actually want

May 17, 2026 · 5 min read · by James, half-owner of a dance studio

Most class schedules are weekly and look the same week after week. But almost every competitive studio has a quiet exception: a set of solos, duets, or small-group classes that meet every other week. The 30-minute solo coaching that's once a week is way too much one-on-one time for the studio (and the family's wallet); once every other week is the sweet spot.

Until recently, almost every dance studio software we'd looked at handled this badly. Either they didn't support biweekly at all (so studios faked it by entering "every Monday" and remembering not to hold the class half the time), or they supported it in a way that made attendance and billing weird.

Why "fake it as weekly" doesn't work

The studios that hacked around the limitation by entering biweekly classes as weekly classes lived with three persistent annoyances:

Attendance gets noisy. The instructor opens the attendance roster every Monday and has to remember whether this Monday is a "real" class day or an "off" day. Half the time the instructor takes attendance on a day the class didn't actually meet, and now there's an attendance record that doesn't reflect reality.

The schedule lies to parents. The family portal shows the class meeting every week. Parents show up on off-weeks, or worse, miss the on-week because they assumed it was an off-week. Now the front desk is fielding "wait, is there class today?" texts every Monday morning.

Billing is off by half. A weekly class at a weekly rate charges full price. Studios that wanted to charge half had to either (a) eat the difference and over-charge their families, (b) issue manual credits each month, or (c) create a duplicate "biweekly" rate group with half the prices and remember to assign the class to it. Option C works, but it's invisible — there's no on-screen reminder that this class is biweekly, so the rate-group assignment is a single point of failure.

What "real" biweekly support looks like

The shape of the feature, once you build it properly:

1. Cadence is a property of the class meeting, not a fake weekly pattern. When the instructor sets up the class, they pick weekly or biweekly. If biweekly, they pick which set of weeks — A or B (or whatever the studio calls them).

2. The schedule grid honors the cadence. The dashboard, the room-availability view, the instructor's "today's classes" list — none of them show the class on the wrong week. An A-week solo doesn't appear on a B-week Monday. Off-week Mondays are quiet for that class.

3. Attendance follows. The instructor opening the attendance roster on a B-week Monday sees the B-week students, not the A-week ones. No accidental absent marks, no phantom rosters.

4. Conflict detection is cadence-aware. A studio with two biweekly classes in the same room at the same time on opposite weeks isn't actually conflicting — they're alternating. The software shouldn't flag them as a problem.

5. Billing stays the studio's call. This one's controversial. Some software wants to auto-half the price for biweekly classes. We think that's a mistake. Studios price biweekly classes differently than half a weekly class for all kinds of reasons — costume costs are the same, choreography time is the same, the instructor still has to prep. The right model is: cadence handles scheduling. Rate group assignment handles billing. If you want to charge half, you make a half-priced "Biweekly Solo" rate group and assign it to those classes. The software can nudge you ("hey, this class is biweekly but uses the regular Solo rate group — did you mean to use Biweekly Solo?") but it shouldn't make the decision for you.

The "but some students come every week" wrinkle

One question that almost always comes up: what if you have a biweekly class but a couple of students attend every week? Maybe they want extra coaching, maybe they're prepping for a competition.

The temptation is to build "per-student cadence within a class." We thought hard about this and decided against it. It splits the rate-group model in confusing ways, makes attendance harder to explain ("why does this student appear on this date but not this one?"), and bloats the data model for a relatively rare case.

The cleaner pattern: set up two biweekly classes. One for the A week, one for the B week. They can share a room and instructor (the software shouldn't complain). Students who want every week enroll in both. Students who want every other week enroll in one. Attendance is clean, billing is clean, the family portal shows it accurately. It's an extra step at class-setup time, but it cascades naturally everywhere else.

We'd rather make the studio's life easier downstream than save them five minutes during setup.

The studio-defined labels thing

The two alternating weeks need names. We call ours A and B — that's the default. But some studios call them 1 and 2, some call them Comp Week and Drill Week, and one studio I know calls them Vanilla and Chocolate (don't ask).

Software that hardcodes "A / B" creates a tiny friction every time the front desk has to translate ("which one's A again?"). Studio-defined labels mean the front desk uses the words they're already using. It's a small touch but it adds up over a season.

What this lets you actually do

With real biweekly support in place, a few things suddenly become possible:

Competition solo coaching — the canonical biweekly use case. 30-minute private at $40, alternating Mondays.
Adult workshops — most adult students don't have the time commitment for a weekly class. Biweekly hits the sweet spot.
Faculty meetings or office hours — yes, you can run a non-student "class" on a biweekly schedule and have the software just track when the room is reserved.
Specialty technique sessions — pointe technique, partnering, masterclasses — things that don't justify a weekly slot but want regular cadence.

The unifying theme: studios have always done these things. They've just been managing them in side notes and shared mental models because their software couldn't represent them. Once the software does, the studio finally has a single source of truth.

The pragmatic version of "do less"

Building this took us a couple of days. Building billing magic on top of it (auto-half-price, per-student cadence, etc.) would have taken a week or two and introduced a real risk of subtle billing bugs that wouldn't surface for months.

We chose to do less. Cadence is purely scheduling. Billing stays the studio's job, via rate groups they already understand. The software just makes sure nothing accidentally trips up — by showing a quiet warning if a biweekly schedule is paired with a non-biweekly rate group, and by letting the existing manual override system handle the edge cases.

That's the boring version. It's also the version that doesn't surprise you with a wrong invoice three months later.