How to build a setlist that works on stage

A setlist is not the list of songs the band can play — it is the order they will be played in. The difference looks small on paper and is enormous on stage: good material in a bad order produces a lukewarm show, and everyone leaves unable to say what was missing.

Start with the end and the beginning

The two songs that matter most are the first and the last, and they have opposite requirements.

The firstis played with the sound not yet dialled in, cold hands and the room's attention scattered. It has to be familiar, comfortable to play and reasonably energetic. Never open with the hardest song in the set, however good it is — and never with the newest, the one the band has rehearsed twice.

The last is the one that stays in memory. It has to be the strongest, and strong here means recognisable, not complex. If you have a song the room sings along to, it closes the show.

A rule that solves half the problems: the first three songs should be the three the band plays most confidently. Warm-up and shop window happen at the same time, and it is the audience that decides whether to stay.

Energy in waves, not a ramp

The temptation is to order from calmest to most intense, climbing to the end. In practice that tires people out: an hour of rising intensity becomes constant noise, and the room loses any sense of what the peak is.

Waves work better — three or four songs pulling up, one breath, then up again, each cycle ending a little higher than the last. The ballad in the middle is not a drop in pace: it is what makes the next fast one feel faster.

A skeleton that tends to work for a one-hour show:

1. Familiar opener, medium-high energy
2. Two in a row pushing up
3. First breath — the most beautiful song, not the slowest
4. Middle block, where the less familiar material goes
5. Second breath, shorter than the first
6. Three to close, the most singable last

New or original material goes in the middle block on purpose: that is where attention has already been won and has not yet started saying goodbye.

Key and tempo between neighbouring songs

Two songs in a row in the same key and the same tempo sound like one long song — the listener does not notice the change. Two in distant keys sound like a stumble.

The middle path is to use neighbouring or relative keys: from G to D, or from C to Am. The change happens without drawing attention to itself.

When you do want to mark a turn — going into the closing block, say — a jump in key is a legitimate tool. It just has to be a choice, not what the order happened to leave you with.

The technical changes nobody plans and everybody suffers

This is the part that separates a setlist on paper from one that works. Between two songs you may need to:

• move the capo to another fret, or take it off
• change instrument
• change tuning
• have someone move position on stage

Each of those is five to twenty seconds of silence. One or two across a whole show go unnoticed; five scattered around turn the show into a sequence of pauses.

The fix is grouping. All the capo-2 songs together, all the alternate tunings in one block. If a change is unavoidable in the middle, it has to land where there would be talking anyway — introducing the band, thanking someone, the story behind the next song.

While building the order, write the capo position next to each song. The blocks appear on their own, and you save an entire rehearsal of discovering them.

Real duration, not the sum

Adding up the recorded track lengths underestimates the show every time. Live, you get longer intros, chorus repeats that were not in the plan, talking between songs and tuning.

A margin of 20% above the sum of the tracks usually lands close to reality. For a contracted hour, build about fifty minutes of music and keep two in reserve — it is far better to have material left over than to cut the ending short.

And make the reserves explicit. "We will see on the night" becomes an argument on stage with an open microphone.

The same list for everyone

Each musician with their own sheet, annotated by hand at different moments, is the classic origin of a mid-show collision. One person skips a song, another does not, and the band starts two songs at once.

What fixes it is not discipline, it is the list being one list and synced — when someone corrects the order, everyone sees the correction. Last-minute changes always happen; the problem is never the change, it is the change existing only in the head of whoever made it.

After the show

The most valuable information appears exactly when nobody wants to think about it any more. Still on the same day, mark on the list:

• where the room genuinely reacted
• where attention dropped
• which transition stalled
• whether time was left over or ran short

Three shows noted like that and the order adjusts itself. Without it, every show starts from zero and the same mistakes come back.