Dance Software · for dance programs and studios
Privacy
Costume-and-photo day: the full picture-day operation
A dance studio that runs a costume photo session is running picture day. The same infrastructure applies: roster-bound galleries, per-subject consent gates, and a branded store where parents review and order photos. None of this requires a separate photo-management system — it runs on the same picture-day substrate as the school-photography platform.
Scheduling: fixed-slot on the shared engine
Costume photo sessions are scheduled on the fixed-slot engine. A class or company is assigned a block; individual dancers can be assigned specific positions within the block (useful when the photographer needs to move through a planned sequence of setups). The scheduling surface reads the roster to determine who is in scope for the session. Changes to the roster — a dancer moving from one class to another — update the session manifest without a manual re-entry pass.
Capture and gallery: roster-bound, consent-gated
Photos from the costume session are ingested on the platform’s own private system and associated to the dancer’s roster record. A dancer’s costume photo is not displayed in any gallery and is not offered for sale unless consent is on file. The consent gate is fail-closed: an absent consent record is treated as no consent, not as implied consent. A parent or guardian who has not yet consented sees a gallery that tells them their dancer’s photos are on file and available to the studio but not currently displayed or purchasable.
Studio store: early access on the built substrate
The branded studio store for parents — where a parent browses their dancer’s costume photos and places a print or digital order — is built on the picture-day substrate and available in early access. Orders settle on the platform’s own system; the studio receives its revenue leg on every order through the earnings ledger. The ledger routes the studio leg today; the physical payout to a studio bank account is being wired. No dollars reach a studio bank account yet and we say so rather than presenting payout as live.
What is built, what is in early access, and what is honest-off
Recital scheduling on both the fixed-slot and window-overlap engines, costume-and-photo day on the built picture-day substrate, recital programs as publications with fail-closed print preflight, team and roster management for classes and companies, and the music-licensing posture tied to freeschoolmusic.com are built on the shared platform substrate. The dance-operator command center console is in early access — available to partner studios and programs, not yet open for general use. The branded studio store for parent photo orders is in early access; the studio-leg payout to a bank account is the fast-follow being wired. Ticket sales and a public recital storefront are planned, honest-off: the seam exists; the wire is not connected; no ticket revenue flows today. Parent communication dispatch is built on the routing side; the outbound provider is not yet connected. We say all of this plainly rather than presenting in-progress work as finished.
Dance Software is part of the Stanley Studios K-12 platform: one consented student record underneath, one print pipeline, one scheduling core — purpose-matched to the dance vertical.