Committee meetings, hidden from the band

A committee meeting is not a rehearsal. It should not sit on the same calendar the whole band sees, and it should not send a notification to every euphonium player asking if they are coming.

BandHQ has a dedicated event type for this: Committee meeting. It behaves like any other event for the people who need it, and does not exist as far as everyone else is concerned.

Create one

Events → New event → set the type to Committee meeting. Fill in the details as normal. Save.

That is the whole difference from creating a rehearsal.

Who sees it

Members of the committee — anyone whose role in the band is admin, or who holds a position that grants admin (Musical Director, Chairperson, Treasurer, Secretary, and so on).

Everyone else sees nothing:

• The event is not on their calendar
• They do not get a notification when it goes up
• They cannot see it in the Events list
• If they subscribed to the band's calendar feed, it does not appear there either
• The RSVP-chase reminder does not go out to them

This is enforced at the database, not in the interface — a bug in the app cannot leak a committee meeting to the wider band because the query itself is not allowed to return it.

What the committee sees

The full event page, with a Committee only badge on it so it is obvious this is a private one rather than a normal event the app happens to be showing you. The RSVP row asks Going / Maybe / Can't the same way, and the responses list only shows committee members.

What this is not

• Not a chat channel. A committee meeting is an event, with a date, time and RSVP list. If you want an ongoing back-and-forth, use a section-restricted chat channel.
• Not encrypted end-to-end. The database can read the row (it has to, to enforce who sees it). BandHQ staff have contractual access to production systems — see the Trust page. A meeting title should not carry information you would not put in a company email.