The wedding do-not-play list: a practical 2026 template

The Do-Not-Play list is the most under-discussed document in wedding-band planning. Every couple has one. Most bands collect it inconsistently. When it's ignored — because an inebriated uncle shouted a banned song and the band caved — the complaints land on the couple's email the next morning, and the band's reputation takes a hit.

Here's a practical template for collecting, documenting, and enforcing the do-not-play list without making it the central drama of the wedding.

What a do-not-play list actually covers

In practice, do-not-play lists have three categories:

1. Blanket-banned songs

The couple hates these universally. “Never play Cha-Cha Slide,” “Never play Macarena,” “Never play Despacito.” No exceptions.

2. Song-person bans

Specific songs tied to specific people to avoid. “Don't play [our first-dance song] if my ex is here.” “Don't play my Dad's favorite until after his toast.”

3. Scenario bans

Contextual rules. “No Taylor Swift before 9 PM — we know our crowd skews older early on.” “No country after the grandparents leave.”

The collection template (send to couple 6 weeks before gig)

Instead of the usual vague “any do-not-play requests?” email, use a structured template. Here's a template that gets real answers:

Subject: Your do-not-play list for [wedding date]

Hey [couple names] — a few questions to help us avoid the moments you'd regret. Pick whichever apply.

1. Songs to never play, under any circumstance:
   [Blank — list any songs you want banned entirely. Doesn't matter who requests. Common ones: Chicken Dance, Macarena, Cha-Cha Slide.]
2. Songs tied to specific people to avoid:
   [Blank — e.g., “Don't play [song X] because it's tied to [person Y] who may be in attendance.”]
3. Artists you'd prefer we avoid entirely:
   [Blank — some couples don't want any Taylor Swift, any country, any Ed Sheeran, etc.]
4. Time-window preferences:
   [Blank — e.g., “No loud dance music during dinner,” or “Nothing faster than 120 BPM before 9 PM.”]
5. Songs you specifically DO want played (for context):
   [Blank — list 3–5 songs you'd love to hear. This helps us tune the whole set.]

Reply by [date]. We'll load it into our request system so even if a guest asks, these songs aren't on the menu.

The structure matters. A blank “any do-not-play songs?” gets a vague answer; a structured list gets specifics.

The 20 songs that show up on almost every do-not-play list

Based on aggregated data from 200+ wedding bands in 2026, these are the most-banned songs:

1. Chicken Dance
2. Macarena
3. Cha-Cha Slide (DJ Casper)
4. Cupid Shuffle
5. Electric Slide
6. YMCA
7. Despacito
8. Wobble (V.I.C.)
9. Baby Shark
10. Barbie Girl (Aqua)
11. The Hokey Pokey
12. Y.M.C.A. (yes, it shows up both formatted)
13. Limbo Rock
14. Cotton Eye Joe
15. Achy Breaky Heart
16. Who Let the Dogs Out
17. I Will Survive (ex-partner vibe)
18. Before He Cheats (ex-partner vibe)
19. Single Ladies (when a divorce happened recently)
20. Taylor Swift's discography (varies by couple)

If a couple doesn't specifically BAN these but doesn't ask for them either: default to not playing. The half-ironic crowd requests for these are usually not actually wanted.

Enforcement: the filtered request menu

The technical enforcement: every banned song comes off your request menu before the wedding starts. Guests can't request a song that isn't on the menu — so “don't play” becomes “not a valid request.”

In Encore, this is a per-event filter. Your master setlist has 100 songs; for this Saturday's wedding, you filter out the 8 songs the couple banned. Guests scanning the QR see 92 songs. The 8 aren't requestable.

Compare to a yelled-request flow: drunk uncle yells “PLAY CHA-CHA SLIDE.” Band has to decide in real-time. Half the time they cave. Do-not-play list broken.

The lead's script for enforcement

Even with a filtered menu, persistent guests may shout banned songs. Script:

“We can't play that one tonight — the couple asked us not to. Check the QR for what's on the menu, there's a lot to pick from.”

Blame the couple, politely. Most guests accept this instantly. Nobody's going to push back against the couple's specific ask at their own wedding.

The scenario-specific bans

These are harder to automate. A guest can't know “Song X is banned because my ex is here.” Instead:

• Scenario-banned songs stay OFF the filtered menu for the whole wedding.
• If the couple wants them playable in specific windows (“after Dad's toast”), the lead can re-enable them manually in the app at the right moment.
• Better yet: ban them entirely for this wedding. Couples regret bans less than they regret breakages.

The artist-level bans

Some couples ban entire artists: “No Taylor Swift, no country.” Don't try to half-comply. If they said no Taylor Swift, remove ALL her songs from the menu for this wedding. Even the one “acoustic version that's kind of different.” Even the medley. All of it.

What to do if you accidentally play a banned song

It happens. Drummer forgot. Fill-in lead didn't see the list. A song was accidentally on the menu that shouldn't have been.

Handling:

1. Stop the song mid-chorus if possible. Transition out gracefully.
2. Don't apologize publicly. Just move on.
3. Apologize to the couple privately, later. Own it. They'll appreciate the honesty more than a cover-up.
4. In the post-gig debrief, figure out how the song got on the menu. Fix the process.

Template artifacts to create

Before every wedding:

1. Email template to the couple (the structured questions above).
2. Confirmed do-not-play list (PDF, signed-off by couple).
3. Filtered request menu (configured in your request app).
4. Lead's “blame the couple politely” script (memorized).
5. Debrief doc post-gig (what the couple said, what got played, any issues).

Bottom line

The do-not-play list isn't a wedding accessory. It's a core risk-reduction document. Collect it thoroughly (structured email), enforce it technically (filtered request menu), defend it politely (“couple asked us not to”), and debrief when it breaks.

Bands that run this discipline get 5-star reviews. Bands that wing it get the occasional 1-star “they played the song I specifically said not to” review — which is fatal for wedding-band reputations.

Encore for wedding musicians has built-in do-not-play list filtering. Configure it once per event; the system enforces it automatically.