Community band management software that replaces the six-spreadsheet system

Community band management software earns its keep when it kills the six-spreadsheet system. EnsembleBase keeps one roster and generates the rest from it.

Every band that has been around more than a few seasons accumulates this system by accident. A trombonist who moved away in March is still on the email list in June, marked active on the roster, and absent from the dues sheet entirely — because those are three different files maintained by three different volunteers.

Where the six-spreadsheet system breaks

Any one of those errors is survivable. What wears people down is that every question — who is playing Saturday, who owes dues, how many tickets have sold — starts with working out which file to open and which volunteer to ask.

Summer season: parades, festivals, and who can actually make it

Concert bands have a scheduling problem orchestras mostly don't: the summer run of parades, park concerts, and festival gigs, each with its own call time and its own subset of the band. Availability polling in EnsembleBase works per event. Post the whole summer schedule, let members respond date by date, and see for each gig who's in, who's out, and who hasn't answered. When the Memorial Day parade shows three trumpets, you know two weeks out, while there's still time to call a sub from the roster.

Scheduling, reminders, and follow-ups run off the same data. The reminder email for the festival gig goes to the people playing it, and the nudge about the availability poll goes only to the people who haven't responded.

One roster that shows your instrumentation balance

In EnsembleBase, the roster is organized by section, with chairs, principal status, and substitute status on each member. Your instrumentation balance is visible the moment you open it: eighteen flutes and two tubas is a familiar community band problem, and when each section's headcount is on screen, recruiting stops being a vague "we need more low brass" and becomes a specific target.

A gig-based player who covers the July 4th concert but skips the fall season is one roster record with a sub status, instead of a name added to and removed from five files.

Seating charts filled from the roster

The seating chart builder hands you a starting template to reshape into band rows, with your roster beside it: filter by section or by who's unplaced, and drag players onto seats. When a clarinetist switches chairs, that's a drag and a swap prompt, not a redrawn chart. Publish, and the chart is on every player's portal page.

Dues and tickets in the same place as everything else

Dues tracking sits on the member record: set the season's dues, collect payment online, and see who has paid without reconciling a bank export against a spreadsheet. Ticketing lives here too, on the Pro and Scale plans: every concert can have a public event page with online sales, plus door sales and scanning on the day. The flat $1.00 service fee is added at checkout, buyers can choose to cover the card processing, and with both passed along the band keeps full face value.

One gig, start to finish

Take the September festival slot. You post the date, and the availability poll goes out to the current roster. The results show you're short a bass clarinet, so you message the one sub with bass clarinet on her record. The seating chart takes four drags from the roster panel, the reminder email goes only to the people playing the gig, and by the time the trailer is unloaded that night, door sales have already landed in the same dashboard as everything else. The six spreadsheets never came out.

Who owns the account when the treasurer retires?

Every long-running band has a version of this story: the ticketing login belonged to Debbie, Debbie retired to Arizona, and now the spring concert's sales report lives behind a password reset sent to an email nobody checks. Personal accounts on outside platforms leave with the person who created them.

EnsembleBase is the band's workspace, with multiple administrators and four access levels (owner, admin, manager, member). A handover is an invitation and a revocation: the new treasurer gets admin access, the old access is turned off, and every record stays exactly where it was. And your data exports — roster, dues, buyers, finances, all CSV — so the band is never hostage to the tool, this one included. Getting in is covered the same way: if your records are scattered across those six spreadsheets today, the EnsembleBase team will migrate them for you.