Cheerleading Software · School squads & all-star gyms · Early access · 2026

Built for the people legally responsible for every minor athlete on the floor — consent, safety, and media done right

Cheerleading Software is the operating platform for school cheer programs and all-star gyms that takes the consent layer seriously: who can pick up an athlete, who authorised their photo, what is deleted when a family leaves, and what the coach’s credential record shows when an incident is filed. The roster hub, consent flags, consent-gated gallery engine, and no-skim fundraiser split engine are built. Tryout blind scoring, stunt-group management, competition-division readiness, and the safety layer are early-access. No live payments today — no pricing commitment, no signup.

Book a conversation How it works

Consent-first rosterguardian directory, pickup/custody, eligibility, and media-release flags — built at the data layer

Exact centsno-skim fundraiser split engine — fee off gross first, largest-remainder reconciliation

Fail-closed mediano-release athlete appears in no gallery, no product, no share link — ever

Guardian-controlledconsent opt-in, withdrawal at any time, full data export in writing

Safety and compliance — the record that matters when something goes wrong

A coach’s credential, an incident report, a return-to-play gate — they should not live in a spreadsheet

A coach’s concussion-protocol certification expires in fourteen months. An athlete sprains a wrist at Tuesday practice. The AD needs to know before Saturday’s competition whether a clearance record was filed. These are not edge cases — they are the compliance reality of running a program with minor athletes. A sticky note, a shared spreadsheet, and a folder of scanned PDFs are not a defensible record.

The safety and compliance layer is being built to serve that reality: coach-credential expiry tracked with renewal alerts, incident and injury reports with timestamps and athlete-record links, return-to-play clearance tracking so a coach or AD can see at a glance whether a clearance record has been filed for an athlete, policy-acknowledgment collection from athletes and guardians, and an audit log that records every change to an incident record. The safety layer is early-access — the architecture is designed and the build is in progress. It is not yet production-ready.

Book a conversation Full platform

How it works

The cheer program year in four stages

Cheerleading Software runs on a season rhythm: tryout setup and consent collection before the season, opening practices and photo day, a competition and game season, and a clean year-end archive and handoff. Every stage is described as it is built today.

Step 1 · Pre-season — program setup, tryouts, roster, and consent collection

Coaches configure the program for the year: squad type (school JV, varsity, all-star competitive), season schedule, and any division or rulebook requirements. Tryout registration opens with the blind rubric configured. Once a squad is set, each athlete’s guardian directory is verified — who can pick up, emergency contacts, custody notes, authorized adults. Media-release and policy-acknowledgment collection runs before the first practice: an athlete is not cleared for any gallery delivery until the guardian has affirmatively opted in. The program owns its roster and consent data from day one.

Step 2 · Season opener — first practices, picture day, and fundraiser launch

Attendance and check-in open for the first practice. The check-in engine tracks which athletes are present, who authorised pickup, and staff ratios. Team photo day is configured in the scheduling engine and mapped to the consent-gated gallery workflow: only athletes with a current media release appear in any product ordered by any family. The opening fundraiser is configured in the split engine: fee off gross first, net to the squad treasury. The gallery delivery engine is ready; the live checkout interface is honest-off until the charge rail is enabled.

Step 3 · Competition and game season — sidelines, meets, media, and safety records

On game nights and competition days, check-in tracks who is present and records which staff member is accountable for each athlete. Any incident or injury during practice or competition is entered into the safety layer with a timestamp and linked to the athlete record. Return-to-play clearance status is tracked against the incident record so the AD can check it before the next event. Gallery assets from competitions are ingested and mapped to consent flags before any family link is generated — an athlete without a release does not appear in any product, regardless of what was captured. Mid-season fundraisers run through the split engine, each projecting exact-cent proceeds to the squad treasury.

Step 4 · Year-end — senior night, awards, media archive, and season handoff

The year-end season archive collects every practice, competition, gallery delivery, fundraiser split, and safety record under the season record. Senior-athlete recognitions are built from the roster. A season-handoff export delivers the full record to the incoming coach or AD in a portable format they can read without the platform. The organisation owns its data: a one-click export is available in writing — if the program ever leaves, the full roster, consent history, media-release ledger, fundraiser records, incident log, and check-in history leave with it. Consent withdrawal requests are processed within the stated window and logged.

The full platform

Five capabilities — honest about what is built and what is coming

Every feature is labelled honestly: Built means the underlying engine is production-ready. In development or Early-access means the surface, wire-up, or build is in active progress. We do not claim otherwise.

Consent-safe roster hub — guardians, pickup authorization, eligibility, and media-release flags

The roster hub is the consent record for every athlete on the squad. Each student entry carries its guardian directory — who can pick up, primary and emergency contacts, custody notes, and authorized-adults lists — alongside the athlete’s eligibility status and a per-athlete media-release flag. An athlete whose guardian has not granted media consent is locked out of every photo delivery, gallery share, and storefront product at the data layer — not by a manual filter, by the consent flag. Eligibility status ties to the school or gym’s own criteria and can be checked before a practice opens or a competition entry submits. Guardian-to-athlete links are explicit: a guardian account is never implied from an email address. The roster hub and consent flags are built and production-ready. The eligibility criteria engine is extensible — the rule set is configured per program, not hard-coded.

Roster hub built · consent flags built

Safety and compliance layer — coach credentials, incident reports, return-to-play, policy acknowledgments

The safety layer collects, tracks, and surfaces the compliance record that a coach, athletic director, or gym owner needs when something goes wrong: coach-credential expiry (first aid, concussion, safety-certification), incident and injury reports with timestamps, return-to-play clearance gating, and policy-acknowledgment collection from athletes and guardians. Policy acknowledgments are consent-adjacent: a guardian must check an acknowledgment before it is recorded — not implied by enrollment. An audit log captures every change to an incident record. The safety layer gives an AD or gym director a defensible paper trail, not just a checklist they remember to maintain. The safety and compliance layer is early-access — the architecture is designed, the build is in active progress, and it is not yet production-ready.

Safety layer early-access · in active build

Tryout tools — blind rubric scoring, judge-conflict disclosures, stunt-group and formation ops

Tryout tools serve two audiences who are not always aligned: the coach building a squad and the guardian wanting a fair process they can trust. Blind rubric scoring means judges score candidates on criteria — tumbling, jumps, motion technique, stunting, dance — without seeing the candidate name, only an anonymous identifier, reducing social bias from the scoring session itself. Judge-conflict disclosures record when a judge has a declared relationship with a candidate so the record shows it. Stunt-group and formation management are part of the same tryout module: once a squad is set, athletes can be assigned to groups and positions in the system. Competition-division readiness tracks the squad’s checklist against a division’s rulebook requirements. The tryout and formation tools are early-access — the design is complete, the build is not yet production-ready.

Tryout & formation tools early-access · in active build

No-skim fundraiser splits — exact-cent, fee-off-gross-first, per-squad treasury

The fundraiser split engine applies three rules in order. First, the platform fee is taken off gross first — deducted from gross proceeds before any split is calculated, so the platform’s share comes off the top, not out of the program’s cut. There is no platform skim. Second, splits are applied to the net remainder — the numbers a coach or booster treasurer sees in the projection are the numbers that land in the treasury. Third, a largest-remainder reconciliation pass assigns any residual penny to the party with the largest fractional remainder, so the total always equals exactly what came in, to the exact cent, minus the fee, with nothing silently absorbed into a platform margin. The split engine is built and production-ready. The charge rail that moves money is honest-off — present in the platform, not enabled for live transactions today. A treasurer can model a fundraiser split, see the exact projected distribution, and agree on the numbers before the charge rail is enabled.

Split engine built · charge rail honest-off

Who it serves

School squads and all-star gyms — distinct program paths, one platform

School cheer squads

A school cheer program has an athletic director as the institutional decision-maker, a school calendar, an academic-eligibility constraint on every athlete, and a booster or parent organisation on the fundraising side. The roster hub carries each athlete’s grade, eligibility status, and media-release flag alongside the guardian directory. Tryout blind rubric scoring helps coaches document the squad-selection process for a program with varsity and JV squads and stakeholders watching the outcome. The booster organisation’s fundraiser runs through the no-skim split engine, keeping the squad treasury separate from the school’s activity fund. Game-sideline and competition check-in tracks attendance and staff ratios.

All-star gyms

An all-star gym has an owner-director as the decision-maker, a competitive-season calendar, and a direct family billing relationship. Consent collection and guardian directory management are the same engine as school squads; the eligibility criteria are configured to the gym’s division and rulebook requirements rather than academic standing. Stunt-group and formation management track which athletes are in which group across a gym running multiple competitive routines simultaneously. Competition-division readiness tracks each team’s checklist against its division. Media from competitions and showcases flows through the consent-gated gallery engine — an athlete without a current release does not appear in any product delivered to any family.

Booster treasurers and team-admins

Booster treasurers and parent team-admins are first-class users, not afterthoughts. The fundraiser split engine shows the projected exact-cent distribution to the squad treasury before the charge rail is enabled — a treasurer can model the fundraiser, see the split, and agree on the numbers without waiting for a reconciliation after the fact. Volunteer coordination for picture day, competition travel, and game-night logistics is part of the same platform, so the parent-admin running the photo day schedule and the coach running the roster are working in one place.

Consent-gated media — the difference between a policy and an enforcement rule

An athlete without a media release appears in no delivery, no product, and no share link — enforced at the engine, not by a reminder

Most platforms handle photo consent as a flag a coordinator remembers to check before publishing. On this platform, the media-release flag is an enforcement rule: an athlete without a current release cannot appear in a gallery delivery, a team composite, a print product, or a shared link — the engine refuses to include them, not because a button is greyed out, but because the data layer blocks the operation. A guardian who withdraws consent sees the removal within the stated window, and the withdrawal is logged.

Galleries are private by default. A family accesses their athlete’s images through an authenticated link; there is no public-facing gallery of minor athletes anywhere on the platform. No face-search or AI-identification feature is presented as a headline capability. If it is ever used, it is consent-positive and opt-in. The gallery engine and storefront substrate are built and production-ready. The live checkout that accepts payment from families is honest-off — present in the platform, not enabled for live transactions today.

Athlete data & family consent

Your program’s data. Guardian-controlled. Consent-gated and never sold.

The roster, the guardian directory, the eligibility record, the media-release ledger, the fundraiser splits, the safety and incident log — all of it belongs to the organisation, not to the platform. No athlete or family data is sold to or shared with outside companies or advertisers. No behavioral tracking and no location tracking on minor athletes; no biometric data is collected on minor athletes, and face matching is not something this product can do — the consent machinery for it is off by default per athlete and the matching capability behind it is not wired. Minor athlete data is consent-gated: a guardian must affirmatively opt in before their child’s data enters any delivery, list, or product. Consent is not assumed. Consent can be withdrawn at any time.

The one-click full export is available in writing — if the program ever leaves the platform, every record leaves with it: the full roster, consent and media-release history, fundraiser ledger, safety and incident log, check-in history, and communication consent status. Minor athlete data is never visible to other families. This guarantee is part of the onboarding agreement, not a footnote.

What is built and what is coming — plainly

The roster, gallery, and split engines are built. The safety layer and tryout tools are coming. The charge rail is not live yet.

Built and production-ready today: the roster hub (guardian directory, pickup/custody, emergency contacts, eligibility flags, media-release flags); the consent-gated private gallery engine (athlete-level consent enforcement, private links, no public gallery of minor athletes); the branded storefront substrate and package/print fulfillment rail; the no-skim split engine (exact-cent, fee-off-gross-first, largest-remainder reconciliation); and check-in/attendance with authorized-pickup and ratio tracking.

Early-access (designed, in active build, not yet production-ready): tryout blind rubric scoring, judge-conflict disclosures, stunt-group and formation management, competition-division readiness tracking, and the full safety and compliance layer (coach credentials, incident reports, return-to-play clearance gating, policy acknowledgments, audit logs).

Not yet enabled for live use: the payment rail (the part that moves money), live photo and product checkout, live carrier delivery for communications. These are honest-off — present in the platform, not enabled for live transactions. There is no live checkout here. No billing. No subscription. We say so directly because coaches and AD’s deserve to know what is production-ready and what is still being built.

Connected to the school platform

Cheerleading Software runs the squad. Assembly captures the game night. Seen puts every athlete on a page.

Cheerleading Software manages the roster, consent, safety, and media for the squad. Assembly is the moment layer: live school events — game nights, competitions, showcases — captured, ticketed, and archived. A cheer program’s biggest moments and Assembly’s event layer are the same night; wiring them is natural. Seen is the recognition layer: the programme that ensures every student athlete lands on a real page in the yearbook or programme — adviser-approved and consent-verified. School Booster Network is the booster club platform: gate-scan, concessions, and the same no-skim split engine, for the athletics booster organisation running the game-night operation while the cheer squad is on the sideline.

assembly.school seen.school homeroom.software schoolbooster.network

Early access · School cheer coaches, athletic directors, all-star gym owners

Book a conversation to see the current state honestly

Cheerleading Software is in active development. We do conversations that show the current state honestly: the roster hub with guardian directory and consent flags, how the consent-gated gallery engine gates a delivery to an athlete’s record, how the no-skim split engine projects a fundraiser, and how check-in tracks attendance and staff ratios for a practice. There is no pricing commitment and no signup. If it looks right for your program, we discuss what early access looks like.

To book: email [email protected].

FAQ

Common questions

What is built today vs. what is early-access?

Built and production-ready: the roster hub (guardian directory, pickup/custody, emergency contacts, eligibility flags, media-release flags), consent-gated private gallery engine, branded storefront substrate and package/print fulfillment rail, no-skim fundraiser split engine, and check-in/attendance with authorized-pickup and ratio tracking. Early-access (designed, in active build, not yet production-ready): tryout blind rubric scoring, judge-conflict disclosures, stunt-group and formation management, competition-division readiness, and the safety/compliance layer (coach credentials, incident reports, return-to-play, policy acknowledgments, audit logs). Honest-off (present in the platform, not enabled for live transactions): the payment rail, live photo and product checkout, and live carrier delivery for communications.

Is the payment rail live? Can we collect money from photo orders or fundraisers now?

Not yet. The gallery engine, the branded storefront substrate, the fulfillment rail, and the no-skim split engine are built and production-ready — the logic, the consent verification, and the distribution math are all there. The payment rail that moves money is honest-off: it exists in the platform but is not enabled for live transactions today. There is no live checkout, no billing, and no subscription. When the charge rail is enabled (a founder-gated decision), organisations will be notified. The CTA here is “book a conversation,” not “pay now.”

How does tryout blind scoring work, and why does it matter?

Tryout blind rubric scoring means judges evaluate candidates on criteria — tumbling progression, standing and running tumbling, jumps, motion technique, stunting, dance — against an anonymous identifier, not a name. A judge who knows a candidate by name has less influence over the raw score. Once scoring is complete, the anonymisation is lifted and scores are mapped back to candidates for the final record. Judge-conflict disclosures record when a judge has a declared relationship with a candidate — parent, sibling of a teammate, former private coach — so the record shows it. This is early-access: the design is complete, the build is in progress, and it is not yet production-ready.

How does media consent work for minor athletes? What happens if a guardian opts out?

Every athlete’s record carries a media-release flag. A guardian must affirmatively opt in before the flag is set — consent is not assumed by enrollment, not implied by signing a participation waiver. An athlete without a current media release does not appear in any gallery delivery, any shared link, any storefront product, or any team composite — enforced at the data layer, not by a manual post-publish filter. If a guardian withdraws consent, the flag is updated, and the athlete’s images are removed from any pending delivery within the stated window. The withdrawal is logged. No public-facing gallery of minor athletes exists on the platform by default.

What does the safety and compliance layer track?

The safety layer is designed to give coaches, ADs, and gym owners the documentation record they need when something goes wrong: coach-credential expiry (concussion-protocol certification, first-aid, safety-certification renewal dates), injury and incident reports with timestamps and athlete-record links, return-to-play clearance gating (an athlete is not cleared for the next event until a clearance record is filed), policy-acknowledgment collection from athletes and guardians (not implied by enrollment), and an audit log for every change to an incident record. The safety layer is early-access — the architecture is designed, the build is in active progress, and it is not yet production-ready.

Does the platform serve school squads and all-star gyms differently?

The platform serves both as distinct configuration paths, not two separate products. A school cheer program has an athletic director as the institutional decision-maker, a school calendar, an academic-eligibility constraint on every athlete, and a booster or parent organisation on the fundraising side. An all-star gym has an owner-director as the decision-maker, a competitive-season calendar, a division and rulebook constraint rather than an academic one, and a direct family billing relationship. The consent architecture, roster hub, gallery engine, and fundraiser split engine are shared. The eligibility criteria, the season schedule type, the fundraiser split configuration, and the safety-layer credential types are configurable per program type.

How does the no-skim fundraiser split engine work?

The split engine applies three rules in order: fee off gross first (the platform’s fee is deducted from total proceeds before any split, so the program always sees the net); splits applied to the net remainder (the percentage the program sees in the projection is the percentage it actually receives, not a percentage of gross that the fee then erodes); and a largest-remainder reconciliation pass (any residual penny after integer division is assigned to the party with the largest fractional remainder, so the distribution totals exactly to the cent). There is no platform skim: the engine inserts nothing between what a supporter contributes and what the program receives. The split engine is built and production-ready. The charge rail that moves money is honest-off.

How does stunt-group and formation management work?

Once a squad roster is set, athletes can be assigned to stunt groups (base, flyer, back-spot, front-spot) and to formation positions. Group and position assignments are stored per routine, not just per season, so a program with multiple competition routines can maintain distinct assignments for each. Formation changes are tracked with a history record, so a coach can see what the formation was at last week’s practice. Stunt-group and formation management are early-access — the design is complete, the build is in active progress, and these are not yet production-ready.

What family and athlete data is collected? Is any of it sold?

The program owns its roster and family data. No athlete or family data is sold to or shared with outside companies or advertisers. No behavioral tracking or location tracking on minor athletes, and no biometric data is collected on minor athletes. Face matching is not something this product can do: the consent and deletion machinery for it exists and is off by default per athlete, but the matching capability behind it is not wired and cannot be switched on. Athlete data that involves minors is consent-gated: a guardian must affirmatively opt in before their contact or their child’s data enters any list or delivery. Consent can be withdrawn at any time. Minor athlete data is never visible to other families. A one-click full export is available in writing — if the program ever leaves the platform, every record leaves with it.

What can our program actually use right now?

The platform is in active development. In a conversation we walk through the current state honestly: the roster hub with guardian directory and consent flags, the consent-gated gallery engine with a demonstration delivery, the no-skim split engine modelling a fundraiser projection, and the check-in engine for a practice. None of those involve live payments today. A conversation is the honest next step — we show what is built, what the early-access timeline looks like for tryout tools and the safety layer, and what early access means for your program.

When is the full platform available?

The roster hub, consent flags, gallery engine, storefront substrate, fulfillment rail, and split engine are built and production-ready today. The tryout tools, stunt-group/formation management, competition-division readiness, and safety/compliance layer are early-access — in active build, not yet production-ready. The payment rail, live photo checkout, and live carrier delivery for communications are honest-off — present in the platform, not enabled for live use. The best next step is a conversation where we show the current state honestly and discuss what early access looks like for your program.