Why attendance data matters more than most teams realize

Most dance teams track attendance because they feel like they should, not because they're actively using the data. A check mark in a doc, a row in a spreadsheet — it accumulates, but it doesn't inform decisions.

The problem shows up at performance time. You have a dancer who's been to 60% of rehearsals — but which 60%? Were they there when you taught the second chorus? Did they miss the session where you finalized the transitions in the bridge? The aggregate number tells you something. The session-level detail tells you what to do about it.

What to track — and why session-level matters

Attendance tracking is only useful if it captures the right granularity.

At minimum: Present / absent / excused, per session, per dancer. This gives you the baseline pattern.

More useful: Which sessions each dancer missed. Because choreography is cumulative — each session builds on the last — knowing which sessions were missed tells you which material a dancer hasn't seen.

Most useful: Attendance connected to what was covered in each session. If you attach a rehearsal goal to each session ("learning the bridge formations, cleaning chorus 2 transitions"), you know not just who was absent but what they missed.

Coryo tracks attendance at the session level and lets you attach notes to each session — so absence data is meaningful, not just a count.

The pattern problem: why aggregates aren't enough

An attendance percentage — "Dancer 4 has been to 70% of rehearsals" — isn't actionable on its own.

70% could mean they've been consistently present for the last 8 sessions and missed the first 3 before the project was fully underway. That's fine.

70% could mean they've been present and absent in alternating sessions, missing every other session since the start. That means they've seen half the material from every section — and they're dangerously inconsistent heading into performance.

70% could mean they were present for the first 7 sessions and have missed the last 3 — during which you taught and cleaned the hardest section of the piece. That's a problem.

The pattern matters. Coryo shows attendance per session, per dancer, across the full project so you can see which version of "70%" you're actually dealing with.

Moving from tracking to acting

Attendance data is only valuable if you act on it. A few concrete uses:

Make-up sessions: If a dancer missed the session where you taught a key section, you know to schedule a make-up before performance. Without session-level data, you're relying on the dancer to tell you what they missed — which they may not accurately remember.

Positioning decisions: For high-visibility positions (center, front, solos), consistent attendance is a reasonable bar. If a dancer has missed a significant amount of rehearsal, you have documented evidence to reference when making placement decisions.

Early intervention: If someone misses 3 sessions in a row, that's a pattern worth addressing before it becomes a problem. Attendance tracking surfaces this automatically — you don't have to count in your head.

Team communication: Sharing attendance data with the team (done carefully) can create accountability. When everyone can see the attendance pattern, peer pressure does some of the work.

Why spreadsheets break down for attendance

Spreadsheet attendance tracking has real limits:

Manual aggregation. Calculating who has attended what percentage of sessions requires formulas. Segmenting by date range requires filtering. Cross-referencing with what was covered in each session requires notes in a separate doc.

Version control. Shared spreadsheets get edited by multiple people, versions diverge, and the "official" record gets murky.

No connection to context. A spreadsheet row has no inherent connection to what formation work was covered in that session, what video was filmed, or what notes were taken. The data exists in isolation.

Gets stale. People forget to update it. The record becomes unreliable. By performance time, you're not sure how current the data is.

Coryo tracks attendance as a native part of the rehearsal workflow — the record is part of the session, not a separate doc that depends on someone remembering to update it. See how Coryo's rehearsal tracker works →