School Band Network
Book a conversation

School Band Network · Performance & competition calendar · Early access

The performance and competition calendar, explained — the model, not a live event list.

This page describes how a competition, a concert, or a rehearsal block becomes a scheduled slot on School Band Network's shared scheduling core — the same schedule.software engine that already runs eight K-12 booking surfaces on the platform. It is a model page, not a live calendar: no event, date, or school named or implied here is real. To see your own program's actual calendar, book a conversation.

Book a conversation What this page shows

Reused verbatim from the platform pillars

The scheduling core, in the platform's own words

Performance and competition calendar — built on the shared scheduling core

Competitions, concerts, and the rehearsal blocks that lead up to them run on the shared schedule.software slot engine — the same canonical slot, booking, and availability primitive that already runs eight K-12 booking surfaces on the platform. A director puts a regional competition on the calendar, blocks the rehearsal windows before it, and the engine checks the date against the school's other events for conflicts. A rehearsal block is a slot with a room, a time window, and a participant set drawn from the ensemble roster -- not a separate scheduling tool the band program has to maintain on its own. The scheduling core is built and production-ready today.

Scheduling core built

The season, reused verbatim from School Band Network

Where the calendar sits across a season's four stages

Every stage of a band program's season touches the scheduling core somewhere -- from the first competition and concert dates going on the calendar pre-season, through mid-season conflict checks, to the year-end record. Described as it is built today.

Step 1 · Pre-season — rosters, dues assessment, and the season calendar

The program's ensembles are configured for the year — marching band, concert band, jazz band — and students are placed on the shared roster with their section assignment. The booster treasury opens the season's dues roster: an obligation assessed per member, per season, with a fail-closed hardship-waiver gate for a family that needs one. The SEPARATE ENTITY flag keeps the booster treasury distinct from the school's own accounts from day one. Competition and concert dates go on the shared scheduling core before the first rehearsal. Instrument and uniform assignments are checked out against the roster as the season opens.

Step 2 · Season opener — first rehearsals, dues collection begins, repertoire selected

The first rehearsal blocks and the opening concert or competition are on the calendar, checked for conflicts against the school's other events. The dues roster starts tracking who has paid, who owes, and who is waived for the season. The director selects the season's repertoire from the growing engraved-editions library, with practice parts pulled for the titles that have them. The booster treasury's opening fundraiser, if the program runs one, is configured in the split engine: fee off gross first, split calculated on the net.

Step 3 · Mid-season — competitions, concerts, and treasury tracking

Competitions and concerts run on the scheduling core, with rehearsal blocks filled in around them and conflicts checked automatically. The booster treasury's split engine projects the exact-cent distribution for any mid-season fundraiser before the charge rail runs, and the dues roster shows the current paid/owed/waived status for every member, summed to the cent. Instrument and uniform condition notes and checkout status stay current on the assignment record as gear moves between students.

Step 4 · Year-end — instruments returned, treasury reconciled, program archived

Instruments and uniforms are checked back in against the assignment record, closing out the season's checkout history. The booster treasury reconciles to the cent and the dues roster closes out for the season. A portable export hands the incoming director and the incoming booster treasurer the full record — the roster, the calendar, the dues status, and the treasury — in a format they can read without the platform. If the program ever leaves the platform, every record leaves with it.

What this page shows — and what it does not

This is a model page. No live calendar is embedded here, and no event on this page is real.

The performance and competition calendar engine itself is built and production-ready: a competition, a concert, or a rehearsal block is a slot on the shared schedule.software scheduling core, and the engine checks a new date against the school's other events for conflicts automatically. What is honest-off is what appears on THIS page: schoolband.network does not embed a live, browsable calendar of any program's actual competitions or concerts here, and nothing below names a real event, a real date, or a real school.

If a competition, a concert title, or a rehearsal window appears anywhere near this page, treat it as illustrative language describing how the engine behaves, never as a real entry on any program's actual schedule. A director or booster officer sees their own program's real calendar inside the platform itself, not on this public marketing page.

There is no signup and no pricing commitment on this page. The way to see the real thing is a conversation: we walk through how the scheduling core actually behaves for a program like yours, against the current, honest state of the build.

Program data only — never a public roster

A scheduled event names a date and an ensemble. It never names a student.

Everything the scheduling core tracks for an event — the date, the location, the ensembles involved, the rehearsal blocks leading up to it — is program data: headcounts, dates, and director or staff assignments. Band students are minors, and the ensemble roster behind any scheduled event is never a public page. No student name appears anywhere on this site.

A family reaches its own student's information only through the platform's consent substrate — the single-school wall and the do-not-publish kill-switch that back the whole platform — not a public schedule or roster page any visitor could browse. No other family sees another family's student.

Early access · Band directors, booster officers, activities offices

Book a conversation to see your program's real calendar

This page is the model, described honestly. There is no pricing commitment and no signup. A conversation shows how the scheduling core actually behaves for a program like yours -- against the current, real state of the build, not a canned demo built on fabricated events.

To book: email [email protected].

FAQ

Common questions

Does this page show our program's actual competition and concert calendar?

No. This page describes the scheduling core's model — how a competition, a concert, or a rehearsal block becomes a slot with conflict detection — honestly and in the abstract. No event, date, or school shown or implied here is real. A director or booster officer sees their own program's real calendar inside the platform itself, not on this page.

Is there a live, embedded calendar widget anywhere on this page?

No. Nothing on this page renders live calendar or event data. That is a deliberate honest-off boundary: a marketing page does not get to show, imply, or preview any real program's schedule.

What is schedule.software, and why does School Band Network use it instead of building its own calendar tool?

schedule.software is the platform's own shared scheduling core — the canonical slot, booking, and availability engine already running eight K-12 booking surfaces. School Band Network builds the performance and competition calendar on that same core rather than maintaining a second, separate scheduling engine just for band.

How do we see our program's real calendar?

Book a conversation. We walk through how the scheduling core behaves for a program like yours — honestly, against the current, real state of the build — rather than a canned demo built on fabricated events.

How does the performance and competition calendar work?

A competition, a concert, or a rehearsal block is a slot on the shared schedule.software scheduling core — the same engine that already runs eight K-12 booking surfaces on the platform. A director adds the event, sets the date and location, and the engine checks it against the school's other events for conflicts. Rehearsal blocks leading up to a competition are added the same way, with the ensemble roster as the participant set. The scheduling core is built and production-ready.