Choir and Ensemble

A choir or ensemble server: a channel per section, rehearsal notes, sheet music, attendance and concert logistics.

  • 5 categories
  • 21 channels
  • 11 roles
  • Medium
Download Discord JSON

Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.

No uses yetNo views yet

Server structure

Channels

NOTICEBOARD

  • noticeboard

    General ensemble chat.

  • how-we-rehearse

    When, where, what to bring, and what is expected between rehearsals.

  • your-section

    Self-Roles panel: pick your part.

  • announcements

    Schedule changes, concerts, everything urgent.

SECTIONS

  • sopranos

    Soprano questions and sectional coordination.

  • altos

    Alto questions and sectional coordination.

  • tenors

    Tenor questions and sectional coordination.

  • basses

    Bass questions and sectional coordination.

REHEARSAL

  • rehearsal-notes

    What was covered. Written after every rehearsal.

  • this-weeks-focus

    The bars to work on before next time.

  • attendance

    Say in advance whether you are coming. Two days ahead helps most.

  • Full Rehearsal
  • Sectional One
  • Sectional Two

LIBRARY

  • sheet-music

    One post per piece. The current edition.

  • recordings-and-references

    The versions the director wants you to listen to.

  • pronunciation-guides

    For the languages the ensemble does not speak.

CONCERTS

  • concert-dates

    What is booked.

  • logistics

    Call times, dress, transport.

  • ticket-and-programme

    Sales and the running order.

  • post-concert

    Photos, recordings and what to change.

Roles

  • DirectorAdministrator
  • CommitteeModerator
  • Section LeaderModerator
  • Accompanist
  • Singer
  • Soprano
  • Alto
  • Tenor
  • Bass
  • Muted

Overview

A choir runs on sections, and so does this server. Sections is one channel per voice part — #sopranos, #altos, #tenors, #basses — each visible to the whole ensemble but written in by its own singers, because the alto who is struggling with bar 43 wants to ask the other altos, not the room. Rehearsal is the weekly spine: #rehearsal-notes, written by the director after each session so anyone who missed it knows what was covered, #this-weeks-focus stating the bars to work on before next time, and #attendance where singers say in advance whether they will be there, which is the single most useful thing a small ensemble can track. The Library is read-only and staff-written: #sheet-music with a post per piece, #recordings-and-references for the versions the director wants the ensemble to listen to, and #pronunciation-guides, which any group singing in a language most members do not speak will need. Concerts covers the performance half: #concert-dates, #logistics for call times and what to wear, #ticket-and-programme, and #post-concert. Voice has a Sectional room per part for practising together between rehearsals and a Full Rehearsal room. The role list separates Director, Section Leader — the person who answers questions in their section channel — and Singer, with Accompanist and Committee as small functional roles rather than ranks.

When to use it

Ensembles usually run on a group chat plus an email attachment nobody can find again, so the sheet music is lost, half the group does not know which bars to practise, and the director has no idea who is coming on Thursday. This layout gives each section its own channel, keeps rehearsal notes and the week's focus where they can be read, holds the music in a read-only library, and turns attendance into something visible in advance.

What makes it different

  • A channel per voice part, so a section question reaches that section, not the room.
  • Rehearsal notes are written every week, so missing one rehearsal is not falling behind.
  • Attendance is stated in advance, which is what a director needs and rarely gets.
  • Pronunciation guides live with the music, for the languages the group does not speak.

Recommended Vetox setup

  • Self-Roles

    Post a Self-Roles panel in #your-section so singers pick their part and section pings reach only them.

  • Reminders

    Set a Reminder in #attendance two days before rehearsal, which is when people know whether they can come.

  • Welcomer

    Point Welcomer at #sheet-music so a new singer's first stop is the library rather than the chat.

  • Logs

    Enable Logs into the committee area so changes to the read-only library are visible to the director.

Questions

Why are section channels readable by everyone?

Because a tenor overhearing how the altos solved a tricky entry is useful, and hiding sections from each other creates four small choirs instead of one. Write access is limited to the section so questions land in front of the people who sing that part, but the whole ensemble can read, which is also how a director spots that three sections are stuck on the same bar.

Does this work for an orchestra rather than a choir?

Yes, with the section channels renamed to instrument families — strings, woodwind, brass, percussion — and Section Leader becoming principal. Everything else is unchanged: the rehearsal loop, the library and the concert logistics are the same problems. A very large orchestra may want a channel per instrument rather than per family.

Is a voice room per section actually used?

In ensembles that rehearse weekly, yes, more than most directors expect. Sectionals between rehearsals are hard to schedule in person and easy online, and a room that already exists gets used where one that has to be created does not. If a section never uses theirs after a term, delete it.

Common mistakes

  • Keeping sheet music in chat attachments, which are unfindable within three rehearsals.
  • Running one channel for all sections, so every part reads questions about parts they do not sing.
  • Taking attendance on the night, when the useful time to know is two days before.

Consider instead

Do you have any doubts?

Our team is there for you

0.0k

Servers

0+

Commands

0

Users

0

Languages