Wedding band song request etiquette: a 2026 guide

Wedding gigs are a unique kind of minefield. The couple pre-paid a four-figure flat fee. The wedding party has opinions. Aunt Karen has stronger opinions. The drunk uncle wants to hear “Sweet Caroline” eleven times. Everyone thinks the band works for them specifically.

Handling song requests well at a wedding is a diplomatic skill. Handling them badly is the fastest way to get a bad review and lose referrals. Here's a framework that keeps the couple happy, the guests entertained, and your band out of the complaint email.

The three types of requests at a wedding

Type 1: Pre-approved by the couple

The couple gave you a list: “play these.” First dance. Father-daughter. Wedding party entrance. These are non-negotiable — play them at the planned moments, no deviation.

Type 2: The Do-Not-Play list

The couple gave you a list: “don't play these, no matter who asks.” Almost always includes the Chicken Dance, Macarena, Cha-Cha Slide, and often the bride's ex's favorite song. Treat this list as law.

The wedding industry has a running joke that every Do-Not-Play list has “Cha-Cha Slide” and yet 60% of receptions play it anyway by guest demand. Don't be that band.

Type 3: Guest requests during the reception

This is the messy middle. Guests want a song, the couple didn't specify, and the band has to decide in real-time whether playing it helps or hurts the event. This is where most wedding request awkwardness lives.

Why pay-to-request solves the Type-3 problem

Traditional wedding-guest-requests go like this:

• Guest walks up to the drummer mid-song.
• Says “Can you play [something]?”
• Drummer nods vaguely and forgets.
• Guest returns 20 minutes later, irritated.
• Band decides in real-time, usually under pressure, whether the request conflicts with the couple's flow.
• Everyone leaves the interaction slightly annoyed.

A pay-to-request flow converts that messy interaction into a clean transaction:

• Guest scans QR on their table.
• Picks a song from the band's pre-approved request menu (only songs the couple didn't veto).
• Pays (or doesn't — you can disable tipping for weddings, more on this below).
• Request lands in the band's hidden queue.
• Band plays it when it fits the flow. If it doesn't fit, auto-refund.

The guest self-serves. The band controls the flow. The couple's Do-Not-Play list is enforced at the system level (those songs aren't on the request menu). Nobody is arguing with the drummer.

The wedding-specific request flow

Step 1: Build a filtered setlist before the gig.

Start with your full 60–100 song setlist. Remove anything on the couple's Do-Not-Play list. Remove anything the couple didn't veto but that doesn't fit the vibe (the Death Metal Christmas medley is probably out).

What remains is your “guest-requestable menu.” This is what fans can pick from when they scan the QR.

Step 2: Decide whether tipping is enabled.

Weddings are awkward for tipping because the couple already paid your fee. A visible “TIP JAR” on every table implies the couple underpaid, which makes them look cheap.

Solution: requests-only mode. Disable the tip jar, show only the “request a song” button. Some couples love this. Some couples explicitly tell you to turn tipping on so their guests can show appreciation. Ask in advance.

Step 3: Place QR cards on every reception table.

Small cards, neutral design — no “TIP” language, no bright colors that clash with the couple's palette. The card should say something like “Song requests — scan” and nothing more. Elegance matters at weddings.

Step 4: Define the “dances” window.

Open requests during the dance-floor portion of the night, typically 9 PM to midnight. Don't accept requests during the ceremony, cocktail hour, or dinner — the flow is too tightly choreographed.

A platform like Encore lets you toggle request windows so the QR only accepts requests during the dance-floor portion.

Step 5: Announce it once.

When you transition from dinner to dance-floor mode, mention once: “Folks — if you want to request a song during the rest of the night, there's a QR on your table. Pick from what we know, and we'll work it in.” One sentence. Done.

The priority-tier etiquette

Priority tier at weddings is where the real money comes in — andwhere the etiquette gets tricky. Uncles with $100 to burn will try to jump every song they want to the front. The problem: every time they do, someone else's request gets pushed back.

Three rules for wedding priority tier:

1. Cap priority at $20–$25. Any higher and it feels like auction-y at a wedding. It also triggers guests thinking the band is extractive.
2. Disable priority during slow-dance windows.Slow dances are the couple's moment. If Uncle Jim pays $50 to play “Sweet Caroline” during the father-daughter dance, it's a disaster. Platform-level control: priority requests can't push a couple-chosen song.
3. Always refund if you can't get to it.A lot of late-night priority requests come in after the band's already decided to play three specific closers. Refund the stragglers automatically. The guest gets their money back; the band delivers the set they'd planned.

The most important rule: keep the couple in charge

The bride and groom are the clients. Everyone else is a guest. Every decision in your request flow should make the couple happier — not the guest with the biggest tip.

This means:

• If the couple gave you a Do-Not-Play list, enforce it even when a drunk guest pays $50 for a blocked song. Refund, apologize, move on.
• If the couple asked for a “no requests during first dance” rule, that rule stands no matter how much money comes in.
• If the couple is watching a specific song request come in that they'd find annoying (exes, work feuds, inside jokes from the bachelor party that don't land), skip it and refund.

The band that keeps the couple in control gets the five-star review. The band that lets the guests run the show gets the one-star review from the couple who felt like their own wedding wasn't theirs.

A quick pre-wedding checklist

1. Confirm Do-Not-Play list with the couple (in writing — email is fine).
2. Filter your request menu to exclude the Do-Not-Play list.
3. Decide with the couple: tipping enabled, requests-only mode, or both.
4. Set request window to dance-floor hours only.
5. Set priority cap to $20–$25.
6. Print elegant QR cards (neutral typography, no “TIP” signage).
7. Announce once at the transition from dinner to dance floor.
8. Refund anything you don't play by end of set.

The honest summary

Wedding pay-to-request works. It generates $100–$300 per wedding in guest requests, it reduces drummer-interrupting guest traffic, and it preserves the couple's flow better than shouted requests do. But it has to be designed differently than a bar gig: neutral signage, filtered setlist, capped priority, dance-floor-only windows, and strict Do-Not-Play enforcement.

Get those pieces right and the wedding request flow feels classy and modern. Get them wrong and you're the band that played “Cha-Cha Slide” at a no-kids black-tie reception.

See how Encore handles wedding requests — filtered setlists, tipping toggles, request windows, and a design that doesn't scream “tip jar” on the table.