How to Organise Your Musical Ensemble's Repertoire in 2026

Google Drive, WhatsApp, shared folders, emails… Most musical ensembles juggle multiple tools to manage their sheet music, recordings and playlists. This patchwork that works at first quickly becomes unmanageable. Here is how to take back control.

The problem with general-purpose tools

The majority of ensembles — choirs, amateur orchestras, traditional music groups — use tools designed for something else. Google Drive is a storage tool, not a music repertoire system. WhatsApp is a messaging app, not a sheet music sharing platform.

The result? Scattered files, multiplying versions of scores, expired audio links, and rehearsals where no one has the right document.

The 3 classic mistakes

1. Putting everything in a single folder

A "Repertoire 2026" folder with 200 files inside — that's the most common pattern. Without structure by piece — score, audio, video, notes — finding anything becomes a chore.

2. Using WhatsApp as an archive

Messages disappear, files expire after a few months, and the history is buried in conversations. WhatsApp is perfect for real-time communication — not for storing a season's worth of work.

3. Not versioning scores

"Is this the corrected score or the old one?" That question comes up at every rehearsal when files are not named with intention. A system where each piece has its own centralised record eliminates this problem at the root.

The right structure

Whatever solution you choose, good organisation rests on the same principle: one record per piece, centralising everything related to it.

• Main score (PDF)
• Reference recording (audio/video)
• Working notes and structure
• Tempo, key, learning date
• Additional assets (arrangement, transposition, playback)

With this structure, any musician in the ensemble can find what they need in under 30 seconds — from their phone, before or during rehearsal.

Making the transition without losing everything

The move to an organised system feels daunting because it seems like starting from scratch. In reality, a well-planned migration takes 2 to 3 hours for a repertoire of 50 pieces.

1. List all your active pieces (those worked on this season)
2. For each piece, identify the primary "source" file
3. Import piece by piece, adding assets as you go
4. Archive dormant pieces — they stay accessible without cluttering things up

What matters is not immediate perfection, but having a clean starting point for the next season.