How to get a sub up to speed before a gig

What the sub actually needs

When a sub asks "can you send me the set?", what they are really asking for is four things, and most bands only send one.

• The song list. Titles, yes. But a list of titles tells the sub what to learn, not how to play it with your band. It is a starting point, not a handoff.
• The keys. This is the critical one. A sub will default to the original key unless you tell them otherwise. If your singer does "Isn't She Lovely" in F instead of E, and the sub learned E, you will hear about it on the first chord. Every song needs the key your band does it in, not the key on the record.
• The arrangements. The parts where your version differs from the recorded version. You skip the second verse. The ending is a hard stop, not a fade. The bridge repeats. The sax takes the first solo, then guitar, then out. These are the details that separate a sub who is faking it from a sub who sounds like they have been in the band for a year.
• The set order. What songs, in what order, for how long. If the sub knows the set as well as the band does, they are not just following along - they are anticipating what comes next, which is the difference between a good night and a stressful one.

The text-thread approach (and why it falls short)

The most common handoff goes like this. The bandleader texts the sub a list of songs, maybe with keys. The sub asks a few questions. The bandleader answers some of them, misses others, and says "we will figure it out at soundcheck." At soundcheck, there is no time, and the gig begins with both sides hoping for the best.

This works often enough that bands keep doing it. But it puts the burden on the sub to piece together the truth from fragments, and it puts the burden on the bandleader to remember and communicate every detail manually. Both of those burdens grow with the size of the repertoire. A sub for a four-song jazz combo is a different handoff than a sub for a sixty-song wedding band.

The deeper problem is that the text-thread handoff is disposable. Next time you need a sub, you start from scratch. The information does not accumulate anywhere.

A better handoff, any format

Whether you use an app, a spreadsheet, or a well-organized document, the principle is the same: the handoff should be one thing, not a thread.

Build a single reference that has the song title, key, tempo, structure, solos, and any notes that matter for each song. If you already have an organized repertoire, the sub handoff is just giving them access to it. If you do not, building one for the sub is the forcing function that makes you build one for the band.

Include the set order for the specific gig, not just the song list. The sub wants to know what is first, what is the opener for the second set, where the slow section is, and what the closer is. Context helps a player prepare in a way a flat list does not.

Mark the songs that have non-obvious arrangements. Not every song needs a note. But the ones where the band does something different from the record - a key change, a cut section, an extended outro - should be flagged so the sub pays attention to those.

How Setlist handles it

In Setlist, the band’s entire book is shared. When you invite a sub, they see the repertoire on their phone instantly - every song, with the key, tempo, structure, and solos, current as of right now. They also see the set for the gig, in order, with all the same detail.

There is no text to compose, no file to attach, and no version to go stale. The sub gets the same library the band uses, and when the bandleader changes the set order or updates a key, the sub’s copy updates too.

After the gig, if the sub is not continuing, nothing changes for the band. If they are sticking around, they already have the book. Either way, the handoff was the invitation, and the information did not have to be assembled from memory.

What it will not cover

No tool replaces the conversation. If the band has unwritten rules - the singer likes a long intro on the third song, the drummer always pushes the tempo on the closer, the client wants no songs with explicit lyrics - those are things a human has to communicate. Setlist handles the factual repertoire, the keys and arrangements and set order. The bandleader still has to tell the sub what the vibe is and what the client expects.

It also does not help with learning the material. A sub who has never heard half the songs still needs to practice them. What Setlist does is make sure they are practicing the right versions, in the right keys, with the right arrangements, instead of learning something that does not match what the band actually plays.

The gig is Saturday

If you have a sub coming in this weekend, the fastest thing you can do right now is get your song list into one place with the correct keys and send it over. A spreadsheet works. Setlist is faster because the sub gets it on their phone with the set order and it stays current if anything changes before the gig.

Try it. Invite the sub, build the set, and see whether the handoff took five minutes instead of an hour of texts. Then reply and tell me what your sub needed that the app did not cover.