How to organize your worship team's song repertoire

The repertoire is the worship team’s invisible infrastructure: when it’s in order nobody notices, and when it isn’t, everybody notices every Sunday. The good news is that fixing it doesn’t require expensive tools or weeks of work — it requires picking a format and maintaining it.

Why do you need a master song list?

If these symptoms sound familiar, you don’t have a repertoire — you have an oral tradition:

• Charts arrive over WhatsApp as assorted PDFs, and nobody knows which version is the good one.
• The same song gets sung in a different key every time, depending on who leads and what they remember.
• Some songs only happen when one specific person leads, because only they know them.
• Preparing Sunday’s setlist always starts with hunting for files, not with choosing songs.

A master list — one single index with each song’s information — turns every one of those frictions into a ten-second lookup.

The minimum data card for each song

You don’t need a complex database; you need these fields, kept current:

Field	Why it matters
Title and author (and CCLI number if you report)	Identifies the song and simplifies licensing
Key per leader/lead voice	The same song lives in different keys depending on who leads
BPM and time signature	Click, tracks and transitions depend on it
Up-to-date chord chart	ONE good version, not five PDFs in a chat
Arrangement notes	“No bridge”, “a cappella ending”, “piano-only intro”
Last played date	The one datum that makes rotation possible

The rule that holds it all together: if it changes in rehearsal, it gets updated on the card. An outdated repertoire is worse than none, because it creates false confidence.

How do you rotate songs without burning them out?

Think of the active repertoire in three thirds, not as a flat list:

• Frequent (~15): the core that can be played any Sunday unannounced. This is where the house anthems live.
• Regular (~15-20): played once or twice a quarter; they keep variety without demanding extra rehearsal.
• Occasional: seasonal songs or specific moments (communion, baptisms) that don’t count against the core.

With last-played dates in sight, the quarterly review is almost mechanical: the overplayed rest, the dormant-with-potential return, and whatever hasn’t been played in a year gets archived without drama.

Where do you keep it?

Almost every team goes through the same evolution:

1. A Drive folder of PDFs — works for a season, until versions and keys drift out of sync.
2. A spreadsheet + folder — better: the sheet is the index with the card’s fields, files live alongside. Its limit: nothing transposes a chart for you or tells you which version is current.
3. A dedicated tool — songbook, keys and setlists in the same place. This is exactly the problem we’re building Muzin for: songs with transposable chords, a key per service and setlists shared with the whole team.

The jump from level 1 to level 2 takes one afternoon and is the one that hurts most not to make. Start today with the spreadsheet if you have nothing: migrating later is trivial compared to living without an index.

Common mistakes

1. The repertoire in the leader’s head. Works until the leader moves away, gets sick or simply takes a month off. Team information lives where the team can read it.
2. Charts in one key, voices in another. The classic: the PDF is in E, it’s sung in G, and every guitarist does the math their own way. The good chart is in the key you sing — which is why cheap transposition matters.
3. Not recording the last-played date. Without it, rotation runs on feelings — and feelings always favor the same five songs.
4. Duplicate versions. “Oceans”, “Oceans (acoustic)” and “Oceans v2 FINAL” living side by side in the folder. One song, one entry, one good version.
5. Starting with a full migration. Don’t load 200 historical songs on day one: load the 30-40 living ones, and add the rest only if they come back. The master list is a working tool, not a museum.