The Wedding Band Setlist Guide: Timeline, Songs, and Requests

A wedding setlist isn't just an order of songs. It's the schedule the whole evening runs on: the processional starts when the doors open, dinner music has to sit under conversation, the first dance happens at a time the photographer already knows, and the dance floor has to be full by the time the bar gets busy. Get the sequence right and the night runs itself. Get it wrong and you're the band that played a ballad while sixty people waited to eat.

Here's how working wedding bands build one.

Start with the timeline, not the songs

Before picking a single track, get the couple's run sheet and map your music onto it. A typical reception looks like this:

• Prelude (20-30 min): guests arriving and finding seats. Instrumental or low-key. Nobody is listening yet, and that's fine.
• Processional and recessional: specific songs, specific cues, usually non-negotiable. Know exactly how many bars you need and how to loop or cut cleanly, because people walk at unpredictable speeds.
• Cocktail hour (45-60 min): background energy. Think groove without volume.
• Dinner (60-90 min): the quietest music of the night. Anything that makes guests raise their voices is the wrong choice.
• First dance, then parent dances: the emotional centre of the night, and the songs most likely to arrive in an odd key or need a shortened arrangement.
• Party sets (2-3 x 45 min): where the actual gig happens. Build the floor, keep it, then peak.
• Last song: agreed with the couple in advance. Decide beforehand whether you're doing an encore and what it is.

Write the times next to each block. A wedding setlist with no times on it is a wish list.

How many songs you actually need

For a standard reception with three party sets, plan 30 to 40 songs including dinner and cocktail material, plus a handful of spares. The arithmetic behind that (and how it changes by set length) is in our guide to how many songs fit a 2-hour set. Weddings need more padding than bar gigs, because weddings run late: speeches overrun, the cake takes twenty minutes longer than planned, and you get asked to fill.

The three lists every couple should give you

Send this as a form rather than asking open questions, or you'll get a 90-song Spotify playlist and no guidance:

• Must-play: the songs that matter. Cap it - ten to fifteen is workable, forty is not a setlist, it's a jukebox.
• Do-not-play: the most valuable list of the three, and the one couples forget to write. Ex-partner songs, a track from a funeral, the one the family cannot hear. Ask explicitly.
• Requests-allowed?: decide in advance whether guests may request songs on the night, and whether requests go through you or the couple. "Ask the band" turns into chaos without a rule.

Guest singers and key changes

At some point the bride's aunt will want to sing. Say yes - it's usually the moment everyone films. Just find out the song and the key before the day, not on the night. Music Planner transposes a song for the whole band in one tap and the charts follow, so a last-minute key change doesn't mean five people scribbling on paper.

Same courtesy applies to the couple's own choices: a first-dance song in the original artist's key is often out of reach for your singer. Transpose it during rehearsal, not during the first dance.

Reading a wedding crowd

Weddings have the widest age range of any gig you'll play: children, twenty-somethings, and grandparents on the same floor. A few things that reliably work:

• Open the party set with something broadly known and mid-tempo rather than your hardest-hitting number. You're inviting people up, not blowing them back.
• Alternate decades. Three current pop songs in a row empties the floor of half the room.
• Watch the bar, not just the dance floor. A queue at the bar means you have thirty seconds before the floor thins.
• The couple dancing is worth ten other people. If they're up, keep the energy where it is.

Build it once, reuse it forever

The real efficiency in wedding work is that most of the set repeats. Your dinner block, cocktail block, and core party set are the same at nearly every wedding; only the must-plays and the first dance change. So build the set once as a template, then clone it per wedding and swap the five songs that differ. That turns a two-hour planning job into ten minutes.

It also makes the handover easy: export a clean PDF for the planner and the venue coordinator so everyone knows what happens when, and a version for the band with keys and cues on it.

Planning your next reception? Set up your wedding sets in Music Planner - clone last wedding's setlist, transpose for guest singers in one tap, and export a clean PDF for the planner.

Frequently asked questions

How long before the wedding should the setlist be final?

Two weeks is a good target: late enough that the couple has settled their must-plays, early enough that you can rehearse anything new and sort out keys. Expect one or two changes in the final week regardless.

Should we learn the couple's first-dance song even if it's obscure?

Yes, within reason - it's the one song they will remember in detail. If it genuinely doesn't work live, offer two alternatives (a different arrangement, or a track for that one dance) rather than saying no.

What do we play during dinner?

Low, warm, and familiar. Instrumental or lightly sung, tempos moderate, volume low enough that a table of eight can talk without shouting. This is not the moment for your best material.

How do we handle guest requests on the night?

Agree the rule with the couple first, then hold the line politely. A useful compromise: requests are welcome if they're already in your book, and anything else gets a friendly no. Keep two or three crowd-pleasers in reserve so a no still ends with a yes.