Documenting a Season of Community Song

A community arts organisation documents its season by keeping three separate records: a rehearsal log, a teaching file and a performance file. The rehearsal log tracks dates, rooms, attendance and what was worked on. The teaching file holds warmups, section notes and arrangements. The performance file holds programmes, dates, venues and recordings. Kept apart, each record answers a different question later. Groups that document this way often trace their lineage back through named directors and founders, the kind of history that a choir such as the Capital City Voices ensemble preserves through its own faculty pages.

The reason to separate them is that a season is not one event. It is a run of Tuesdays, a set of skills being built and a handful of public nights. A single calendar entry flattens all three. Three files keep the shape.

What goes into a rehearsal log

The rehearsal log is the driest document and the most useful. One line per session: date, start and end time, room, who led, how many singers came, which pieces were touched.

A weekly ensemble that meets in the evening, say 7:30 to 9:30 on a fixed night, generates roughly forty lines a year. That is a small enough file to read in one sitting and detailed enough to spot patterns. A piece that appears in the log for six weeks running is either hard or unloved. The log will not say which, but it will tell you to ask.

Room notes matter more than they look. A church hall with a hard floor and a high ceiling behaves differently from a carpeted basement. If the group moves rooms mid-season, the log should say so, because the sound of the season changes with the room.

Attendance is worth logging as a number, not a list. Numbers show whether a section is thin. Names show who to call. Both belong, but in different columns.

How does a group document its teaching work?

Teaching leaves almost no trace unless someone writes it down. A warmup that worked in October is forgotten by February. A vowel fix that solved a blend problem in one section gets rediscovered three seasons later.

The teaching file should hold the warmup sequence in order, with a note on what each exercise is for. Breathing, resonance, range, blend, diction: five headings, a few exercises under each. When a guest clinician visits, their material goes in the same file with a date and a name attached.

Arrangements are teaching documents too. A chart with pencilled breath marks is a record of a decision. Keep the marked copy, not the clean one. The clean one is replaceable.

For groups that work with a music director, the file should note who led which session. A season can pass through several hands, and the teaching file is where that continuity lives. The point is not nostalgia. It is that a singer joining in year ten can see how the sound was built.

What belongs in a performance file

The performance file is the public face of the season, and it should be built as if a stranger will read it.

For each concert: date, venue, start time, programme order, personnel by section, and whether the event was recorded. If there was a printed programme, keep one copy flat. If there was a poster, photograph it before it comes down.

Programme order is more informative than it seems. It shows how the group paced an evening: what opened, what closed, where the slow piece sat. A season of programmes read together shows whether the group repeats itself or moves.

Recordings should be labelled with the date and the venue, not just the year. A rough phone recording of a live night is worth more than a clean studio take for one purpose: it shows what the room did.

Where should the records live?

One place, reachable by more than one person. A shared folder with three subfolders is enough. Paper is fine if it is scanned at the end of the season.

The failure mode is a single keeper. When that person steps back, the season disappears. Two people with edit access is the minimum. Three is better.

File names should lead with the date in year-month-day order, so the folder sorts itself. A rehearsal log named 2026-03-10-rehearsal.txt will sit in the right place forever. One named notes-final-v2.docx will not.

How does documentation help the next season?

It shortens the start. A group that opens its autumn planning with last year's log knows which pieces to revisit, which rooms to book and which weeks were thin.

It also protects the teaching. A new director inherits a warmup sequence and a set of marked charts instead of a blank page. That is the difference between a season that builds and a season that restarts.

And it gives the public record a spine. When a group is asked what it did, the answer is a folder, not a memory. For adult singers who move, or who return after years away, that folder is the handshake.

What a season record is not

It is not a scrapbook. Photographs and press clippings are welcome, but they do not replace dates, rooms and programmes.

It is not a private diary. Notes about individual singers belong elsewhere, or nowhere. The season record is about the work.

It is not finished. A log that stops in November is a log that lies. The last entry of the season should be written after the last concert, and it should say so.