Wedding Do-Not-Play List: How To Build One (2026)

A wedding do-not-play list stops your reception from turning into an argument on the dance floor, and it takes ten minutes to build if you know what to include.

TL;DR

A wedding do-not-play list works best at 10-15 songs, not 50 — give your DJ boundaries, not a novel.
Split it into two categories: hard bans (exes, breakup songs) and soft bans (overplayed hits you’re tired of).
Hand your list to your DJ 2-4 weeks before the wedding, not the morning of, so they can plan around gaps.
DJ BrianC builds every Maine wedding around a do-not-play list plus a must-play list — both matter equally in 2026.

Why this matters

Guests remember the songs that ruined the mood more than the ones that made it. A drunk uncle requesting a song tied to your ex, or a DJ defaulting to a Cha Cha Slide you explicitly hate, turns your reception into damage control. Wedding DJs in 2026 field hundreds of requests a season — without a written do-not-play list, they're guessing at your taste under pressure, mid-event, with 150 people watching.

The fix isn't complicated. It's a document. But most couples either skip it entirely or write something so vague ("no country") that it doesn't actually protect them. A working wedding DJ needs specifics, not vibes.

What you'll need

A shared doc or spreadsheet (Google Docs works fine) both partners can edit
20-30 minutes together, ideally during your final DJ planning call
Your DJ's music request form or planning questionnaire, if they provide one
A rough sense of your reception timeline — cocktail hour, dinner, first dance, open dance floor
The must-play list started already, so the do-not-play list has context instead of standing alone

The steps

1. Separate hard bans from soft bans

A hard ban is non-negotiable: songs tied to a breakup, a deceased relative, an ex-partner, or anything genuinely upsetting to either of you. A soft ban is preference — songs you're just sick of hearing at every wedding.

Mixing these together confuses your DJ about how strictly to enforce each one. Label them clearly in two separate sections of your document. Expected outcome: your DJ knows which requests to politely decline versus which ones to skip without explanation if a guest asks.

Common mistake: treating every dislike as a hard ban, which leaves zero room for the DJ to read the room later in the night.

2. Name specific songs, not genres

"No country" bans George Strait and also bans a song a grandparent specifically requested for a slow dance. Genre-level bans are too broad and almost always get ignored or misapplied.

Write out actual titles: "Cotton Eye Joe," "Cupid Shuffle," "Chicken Dance." If there's a genre you truly want gone from the whole night, say so explicitly and separately from your song list, and expect your DJ to ask a follow-up question about it during planning.

Expected outcome: a list your DJ can cross-reference in real time without interpreting your intent on the fly.

3. Cover the reception timeline, not just the dance floor

Do-not-play requests aren't only about the open dance floor set. Cocktail hour, dinner, and the last song of the night each carry their own risk zones. If you hate a specific song that always shows up during cocktail hour sets, name it there too.

Many couples forget the last dance is a request minefield — a DJ closing out the night with a crowd-pleaser you specifically banned undoes hours of good planning in the final three minutes. Reference your last dance preferences alongside your bans so there's no gap.

4. Add context for family-sensitive songs

If a song is banned because of a family situation — an estranged parent, a recently deceased relative, a specific inside conflict — tell your DJ why, briefly. A one-line reason changes how firmly they enforce it when a well-meaning guest pushes back at 9 p.m.

DJ BrianC treats family-sensitive bans as absolute regardless of guest requests, but that only works if the DJ knows the stakes ahead of time. Expected outcome: zero awkward mid-reception conversations between you and your DJ about whether an exception applies.

5. Set a request-desk policy

Decide together how your DJ should handle guests who show up at the booth asking for a banned song. Options: a flat no, a redirect to a similar approved song, or a quiet check-in with you first.

Write this policy into the same document as your bans. A DJ without instructions here defaults to judgment calls, which is exactly what the list was supposed to prevent.

Common mistake: assuming "the DJ will just know" — professional DJs want the instruction in writing so they're not guessing under pressure in front of your guests.

6. Cross-check against your must-play and first-dance lists

Before finalizing, compare your do-not-play list against your first dance song choice and your must-play list. Conflicting instructions — banning an artist you also requested for a slow dance — create confusion your DJ has to sort out alone.

This final pass takes five minutes and catches most contradictions before they become a problem on the wedding day itself.

7. Send the list 2-4 weeks before the wedding

A do-not-play list handed over the morning of the wedding gives your DJ zero time to plan around it. Send it during your final planning meeting, 2-4 weeks out, so they can build a set that avoids the gaps entirely instead of scrambling in real time.

Expected outcome: your DJ arrives with a set already shaped around your bans, not a mental note they're trying to remember at midnight.

Book DJ BrianC for your wedding

Every Maine wedding package includes a do-not-play and must-play planning session.

Get a quote

Troubleshooting

A guest keeps requesting a banned song at the DJ booth. This is exactly what step 5's request-desk policy solves — a DJ with a written "decline and redirect" instruction handles this without pulling you away from your reception to weigh in.

Your partner and you disagree on a ban. Default to whichever partner has the stronger reaction. A song that's mildly annoying to one person but genuinely painful to the other should go on the hard-ban list, not get negotiated down to soft.

You forgot to send the list and the wedding is next week. Send it now anyway. A list arriving one week out still beats no list at all — your DJ can adjust a set faster than you think, especially with specific song titles instead of vague genre notes.

Your DJ plays a banned song anyway. This usually means the list wasn't specific enough (a genre ban instead of named titles) or arrived too close to the event. Confirm receipt of your list in writing during your planning call, not just by email.

A family member pressures the DJ to override a ban mid-reception. A professional DJ holds the line on family-sensitive bans regardless of pressure — this is why step 4's context notes matter, so the DJ isn't caught explaining a family situation to a pushy guest on the spot.

Tools and resources

A shared Google Doc split into hard-ban and soft-ban sections
Your DJ's planning questionnaire or intake form
Your must-play list and first dance song choice, for cross-checking
A reception timeline covering cocktail hour, dinner, and the final set
A garter and bouquet toss song reference, since traditional segments carry their own overplayed-song risks worth flagging early

What to do next

Once your do-not-play list is locked, build the flip side of it — the songs you're guaranteed to hear. Start with your best last dance songs guide to close the night on the right note instead of leaving it to chance.

FAQ

What is a wedding do-not-play list?

A wedding do-not-play list is a written document telling your DJ which songs, artists, or genres to avoid during your reception. It typically separates hard bans (songs tied to sensitive situations) from soft bans (songs you’re simply tired of hearing) so the DJ knows how strictly to enforce each one.

How many songs should be on a do-not-play list?

Most working lists run 10-15 songs across hard and soft bans combined. Longer lists become hard for a DJ to reference quickly during a live event, so specificity matters more than length.

When should I send my do-not-play list to my DJ?

Send it 2-4 weeks before the wedding during your final planning meeting. This gives your DJ time to build a set around your bans instead of adjusting on the fly during the reception.

Should I ban genres or specific songs?

Ban specific songs by title whenever possible. Genre-level bans like "no country" are too broad and often exclude songs a guest specifically wants that don’t actually bother you.

What happens if a guest requests a banned song anyway?

A professional DJ follows the request-desk policy you set in advance — decline outright, redirect to a similar approved song, or check with you first. Deciding this ahead of time avoids awkward mid-reception conversations.

Can I add songs to the do-not-play list after sending it?

Yes, but updates closer to the wedding date give your DJ less time to plan around the change. Send additions as soon as they come up rather than waiting until the final week.

Is a do-not-play list the same as a must-play list?

No, they’re opposite documents that work together. The must-play list guarantees certain songs get played, while the do-not-play list guarantees certain songs don’t — both should be cross-checked against each other before finalizing.

Do wedding DJs actually follow do-not-play lists?

Professional DJs treat a written do-not-play list as a contract term, not a suggestion. The list works best when it’s specific, arrives early, and includes a clear policy for handling guest requests at the booth.

One last thing

The most overlooked line item on a do-not-play list isn't a song — it's the last dance. Couples spend weeks agonizing over their first dance and forget that the final song of the night is the one everyone remembers walking out the door, so ban-check it with the same care in 2026 that you'd give your ceremony processional.

Wedding Do-Not-Play List: How to Build One (2026)

Why this matters

What you'll need