School Band Network
Book a conversation

School Band Network · band directors, booster officers & activities offices · Early access · 2026

Every ensemble, the booster treasury, the instrument records, and the season calendar — one home for the band program.

School Band Network is the hub for a band program's full season: marching band, concert band, and jazz band on one roster, competitions and concerts on the shared scheduling core, a band-parent booster treasury with SEPARATE ENTITY governance and an exact-cent dues roster, instrument and uniform records tied to the roster, and director resources from a growing library of free engraved editions. Early access — no pricing commitment, no signup, no live charge today.

Book a conversation How it works
Every ensemblemarching, concert, and jazz band on one shared roster
Scheduling corecompetitions, concerts, and rehearsal blocks with conflict detection
SEPARATE ENTITY treasurythe booster club’s books, kept distinct from the school’s
Never publicthe band roster and dues status are never a public page

One program, five moving parts — on one address

A band program runs on five things at once. They usually live in five different places.

A band director runs marching band, concert band, and jazz band across a school year, each with its own roster of who plays what and in which section. A competition or a concert has to land on a calendar without colliding with the rest of the school's events. A booster club runs the fundraising and the dues that keep the program funded, and its books have to stay separate from the school's own accounts. Instruments and uniforms move between students every year and someone has to track who has what. And the music the ensemble performs has to come from somewhere the program can actually use without a license headache.

School Band Network puts all five on the same shared platform record. The ensemble roster, the scheduling core, the booster treasury, the instrument assignment records, and the engraved-editions library are built on the same student-record spine the rest of the platform reads from — not five separate tools a director has to keep in sync by hand.

Book a conversation Full platform

How it works

The band program's season in four stages

School Band Network runs on a season rhythm: pre-season setup of rosters, dues, and the calendar; the season opener; mid-season competitions and treasury tracking; and a year-end reconciliation and handoff. Every stage is 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.

The full platform

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

Every feature is labelled honestly: Built means the underlying engine is production-ready. In development means the surface or dedicated UI is in active build. We do not claim otherwise.

Every ensemble on one roster — marching band, concert band, and jazz band

A band program is not one ensemble. School Band Network keeps marching band, concert band, and jazz band on the same shared roster: a student's section assignment, their ensemble membership, and their eligibility all live on the one record the school already maintains, not a separate spreadsheet per ensemble. A student who plays in both concert band and jazz band appears correctly in each, tied to the same roster entry, so the director is not re-keying the same name twice. The roster and records substrate -- the shared student-record spine the rest of the platform reads from -- is built and production-ready. The ensemble roster substrate is built and production-ready today.

Ensemble roster substrate built

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

Band-parent booster treasury and dues — SEPARATE ENTITY governance, exact-cent split engine

The booster club's treasury is a SEPARATE ENTITY from the school's own administrative accounts, kept distinct at the data layer — not a manual spreadsheet an outgoing treasurer hands to the next one. The dues roster tracks who has paid, who owes, and who is waived, per season, summed to the exact cent; a financial-hardship waiver reason is held for the treasurer's own audit only and never appears in a public or family-facing view. The booster role itself is FERPA-walled: a treasurer's view is sums-only aggregates -- counts and cent totals per season -- never an individual student's row or a roster of names, enforced at the data layer, not a UI filter that a route could forget. The exact-cent fundraiser split engine applies the fee off gross first, then a largest-remainder reconciliation pass so the distribution totals to the cent. The treasury, the dues-roster engine, and the split engine are built and production-ready. The charge rail that actually moves money — dues checkout, fundraiser checkout, any live payment — is honest-off: present in the platform, not enabled for live transactions today.

Treasury & dues engine built · charge honest-off

Instrument and uniform records — assignment, condition, and checkout substrate

Every band director tracks which student has which instrument and which uniform. The platform has the substrate for that: an assignment record, a condition note, and a checkout-and-return lifecycle, all tied to the student's roster entry. That substrate is built and production-ready today. What is not yet claimed is a full dedicated inventory surface — the director-facing view that shows the whole uniform set by size and condition, flags an instrument out for repair, and generates an end-of-year return report. That surface is in progress on the built substrate. We name the distinction plainly: a director gets the assignment records and the checkout history on day one, and the dedicated reporting surface is the next step, not presented as finished before it is.

Assignment substrate built · dedicated inventory UI in progress

Director resources — free engraved editions, growing practice parts, and program designs

The freeschoolmusic engraved-editions approach is live: every score is engraved by us from a verified public-domain source, on our own infrastructure — not a copy of any copyrighted edition. The catalog grows as editions are completed and verified; the honest position on any given day is that the library has the titles that are finished, not a promise of full breadth. Practice parts — individual instrument parts extracted from the engraved score — are available for select titles today and grow as each edition is completed. Band-music merch and banner designs are in the platform's catalog for program banners and spirit apparel. The engraved-editions approach is live and the catalog grows incrementally.

Editions approach live · catalog grows

Who uses it

Built for band directors, booster officers, and activities offices — one program, three views

Band directors

A director works from one roster across marching band, concert band, and jazz band, with section assignments and eligibility on the same record the school already keeps. Competitions, concerts, and rehearsal blocks go on the shared scheduling core, checked against the rest of the school's calendar. Repertoire comes from the growing freeschoolmusic engraved-editions library, with practice parts pulled for the titles that have them. Instrument and uniform assignments are logged against each student's roster entry as gear moves for the season.

Booster officers and treasurers

A booster treasurer runs the program's fundraising and dues under SEPARATE ENTITY governance: the club's books are kept distinct from the school's own accounts at the data layer. The dues roster shows who has paid, who owes, and who is waived, summed to the cent, with a hardship-waiver reason held for audit only. The treasurer's own view is sums-only — counts and cent totals, never an individual student's row — because the booster role is FERPA-walled by construction. The exact-cent split engine projects a fundraiser's distribution before any charge rail runs.

Activities offices

An activities office sees the band program the same way it sees the school's other activities: the ensemble counts, the event calendar, and the booster treasury summary, without a separate system to check. The office coordinates scheduling conflicts across programs using the same shared scheduling core the band program uses, and can see the instrument and uniform assignment history if a question comes up at the end of the year.

The booster treasury — SEPARATE ENTITY, sums-only, exact to the cent

The booster club's books stay the booster club's books. The treasurer sees sums, never a student's name.

A booster club's treasury is not the school's activity fund, and the platform treats it that way: the SEPARATE ENTITY flag keeps the club's single treasury distinct from the school's own administrative accounts at the data layer, not by a policy memo an outgoing treasurer hands to the next one. The dues roster tracks each member's obligation for the season — assessed, paid, waived — summed to the exact cent, with a fail-closed hardship-waiver gate for a family that needs one and the waiver reason held for the treasurer's own audit, never public.

The booster role itself is FERPA-walled: a treasurer's view is sums-only aggregates — counts and cent totals per season — never an individual student's row, enforced at the data layer before any application code runs. A treasurer running the annual report for the booster board sees the numbers the board needs, without ever holding a roster of student names or grades. The exact-cent fundraiser split engine runs the same way: fee off gross first, a largest-remainder reconciliation pass so the distribution totals to the cent, every leg stated before the charge rail runs.

The treasury, the dues-roster engine, and the split engine are built and production-ready. The charge rail that actually collects a dues payment or a fundraiser contribution is honest-off: present in the platform, not enabled for live transactions today.

Band students are minors — the roster is never a public page

Your program’s data. Never a public roster. Never sold.

A band program's roster, section assignments, and dues status belong to the school or the organisation running the program — not to the platform, and never to a public web page. A booster treasurer's own view is sums-only, described above; a booster session does not read an individual student's row at all. A family reaches its own student's information 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 roster page any visitor could browse. No family sees another family's student.

Program and family data is never sold to or shared with outside companies or advertisers. This page makes no claim about photos or biometric matching — that story belongs to schoolband.photos, the band program's dedicated photo home. A one-click export is available in writing: if the program ever leaves the platform, every record leaves with it.

What is built and what is coming — plainly

The program engines are built. The charge rail is not live yet.

Built and production-ready today: the ensemble roster substrate (marching band, concert band, jazz band, on one shared record); the performance and competition calendar on the shared schedule.software scheduling core; the SEPARATE ENTITY booster treasury with the dues-roster obligation engine (paid / owes / waived, fail-closed hardship-waiver gate, sums-only treasurer aggregate) and the exact-cent fundraiser split engine (fee-off-gross-first, largest-remainder reconciliation); the instrument and uniform assignment records (assignment, condition note, checkout-and-return lifecycle); and the freeschoolmusic engraved-editions approach, with practice parts available for select titles.

In progress: the dedicated director-facing instrument and uniform inventory surface. Not yet enabled for live use: the charge rail that moves money for dues checkout, fundraiser checkout, or any live payment. 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 a band director or booster treasurer deserves to know what is production-ready and what is still being wired.

Connected to the band-program platform

School Band Network is the program hub. Each sibling site has its own full depth.

School Band Network ties the whole band program together. For ensemble-specific operator depth, marchingband.software and concertband.software are the dedicated apex pages. For the free-music library itself, freeschoolmusic.com is the home for browsing and downloading engraved editions. For game-night and show-night box office and concessions, School Booster Network is the season/program-run operating platform. For the dues-roster engine on its own, dues.software is the sibling home. For band photo day and print ordering, schoolband.photos is the program's dedicated photo home, not re-pitched here. And the whole fleet lives under homeroom.software — the school publishing and management platform.

marchingband.software freeschoolmusic.com schoolbooster.network schoolband.photos homeroom.software

Early access · Band directors, booster officers, treasurers, activities offices

Book a conversation to see the current state honestly

School Band Network is in active development. We do conversations that show the current state honestly: how the ensemble roster is organised across marching, concert, and jazz band, how the performance and competition calendar checks for conflicts, how the SEPARATE ENTITY booster treasury and the dues roster work, and what is built today for instrument and uniform records. 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 School Band Network?

School Band Network is the hub for a band program's full lifecycle: every ensemble — marching band, concert band, jazz band — on one roster, a performance and competition calendar on the shared scheduling core, a band-parent booster treasury with SEPARATE ENTITY governance and a dues roster, instrument and uniform records, and director resources from the free engraved-editions library. It is built for the band director, the booster officer or treasurer, and the activities office who need the whole program in one place rather than a separate tool for each piece.

Is dues collection or fundraiser checkout live? Can we collect money today?

Not yet. The dues-roster obligation engine, the SEPARATE ENTITY treasury, and the exact-cent fundraiser split engine are built and production-ready — the balance math, the hardship-waiver gate, and the distribution logic are all there. The charge rail that actually moves money — dues checkout, fundraiser checkout, any live payment — is honest-off: present in the platform, not enabled for live transactions today. There is no live checkout, no billing, and no subscription on this site. The CTA here is “book a conversation,” not “collect dues now.”

How does the SEPARATE ENTITY booster treasury work?

The booster club's treasury is kept distinct from the school's own administrative accounts at the data layer — a SEPARATE ENTITY, not a line item folded into the school's books. The booster role is FERPA-walled: a treasurer's own view is sums-only aggregates, counts and cent totals per season, never an individual student's row or a name list. A financial-hardship waiver reason on the dues roster is held for the treasurer's own audit only and never appears in any export or family-facing view. This is enforced at the data layer, not a policy memo or a UI filter a route could forget.

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.

What is built for instrument and uniform inventory?

The assignment record, the condition note, and the checkout-and-return lifecycle are built and tied to each student's roster entry — a director can log which student has which instrument and uniform today. The dedicated inventory surface — the full uniform set by size and condition, a repair-and-maintenance log, an end-of-year return report — is in progress on that built substrate. We name the distinction plainly because a director evaluating the platform should know exactly what is available on day one.

Where does the band music come from?

From freeschoolmusic: every score is engraved fresh from a verified public-domain source, on our own infrastructure — not a copy of any copyrighted edition. The engraved-editions approach is live; the catalog is the set of titles completed and verified, and it grows incrementally rather than promising comprehensive breadth on any given day. Practice parts are available for select titles today and grow as each edition is finished.

Is any band student data ever public? What about minors?

No. Band students are minors, and the band roster is never a public page. A booster treasurer's view is sums-only aggregates — never a student's name or row. A family reaches its own student's record 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 roster anyone can browse. No other family sees another family's student. Student and family data is never sold or shared with outside companies or advertisers.

How is this different from marchingband.software and concertband.software?

marchingband.software and concertband.software are the ensemble-specific deep-dive operator apex pages: the tools and detail for running that specific ensemble day to day. School Band Network is the program-level hub across every ensemble in the program at once, plus the booster treasury, instrument records, and the calendar in one address. Both surfaces read from the same underlying platform records; this hub cross-links the ensemble-specific apexes rather than duplicating their full depth.

How is this different from schoolbooster.network and dues.software?

schoolbooster.network is the season/program-run box-office and concessions operating platform — gate-scan, concessions POS, ticketing for game night and show night. dues.software is the dues-roster obligation engine itself, in its own right, for any booster, PTA, or club. School Band Network draws on both honestly — naming what each engine does — to give a band program a single home for its own dues, treasury, and season rhythm, and cross-links each site for its own full depth rather than re-pitching it here.

Does School Band Network handle band photo day?

No, and it does not re-pitch that story. Band photo day — the marching field show, section composites, and individual in-uniform portraits — is its own product at schoolband.photos. School Band Network cross-links it as the program's photo home rather than duplicating its ordering story here.

Who is School Band Network for?

The band director who runs the ensembles, schedules the season, and picks the repertoire. The booster officer or treasurer who runs the program's fundraising and dues under SEPARATE ENTITY governance, with a sums-only view that never sees individual student data. The activities office that sees the band program alongside the school's other activities. Families reach their own student's information through the platform's consent substrate, not a public page.

When is the platform available?

The platform is in active development. Built and production-ready today: the ensemble roster substrate, the performance and competition calendar on the shared scheduling core, the SEPARATE ENTITY booster treasury with the dues-roster engine and the exact-cent split engine, the instrument and uniform assignment records, and the freeschoolmusic engraved-editions approach. In progress: the dedicated instrument and uniform inventory surface. Honest-off: the charge rail that moves money for dues and fundraiser checkout. The best next step is a conversation where we show the current state honestly and discuss what early access looks like for your program.