← Back to Blog

Do-Not-Play List Tips for Utah Weddings: How to Share It Without Killing the Vibe

A do-not-play list is one of the easiest ways to make your wedding reception feel like you. It also helps your DJ avoid the songs that would make you cringe, annoy your parents, or pull the dance floor in the wrong direction.

The trick is keeping the list useful. If it turns into a 200-song spreadsheet with no context, your DJ has less room to read the room. If it is too vague, guests may request songs you thought were obvious no's.

For Utah weddings, I usually recommend a short, clear do-not-play list with a little context. That gives your DJ + MC enough direction without boxing the whole night in.

Start with the songs you truly hate

This sounds obvious, but it matters. A do-not-play list should not be every song you feel neutral about. It should be the songs that would genuinely bother you if they came on.

Good examples:

  • A song tied to an ex
  • A song your family overplays at every event
  • A line dance you absolutely do not want
  • A genre that does not fit your crowd
  • Explicit songs you do not want played, even as clean edits
  • Songs with inside jokes that would make the moment awkward

If you dislike a song but would not care if a guest danced to it, it probably does not need to be banned. The stronger your list is, the easier it is for the DJ to honor it.

Separate “hard no” from “only if the crowd really wants it”

This is the part most couples skip.

Not every song you are unsure about needs to be treated the same way. I like when couples use two categories:

Hard no: Do not play this under any circumstance.

Use judgment: We are not asking for this, but if the right crowd moment happens, you can decide.

That second category is helpful because weddings are live. Sometimes a song that feels cheesy on paper works because Grandma, cousins, and the whole wedding party are already on the floor. Sometimes a request looks good on paper but would clear the room.

Your DJ should be able to read that. A clear do-not-play list makes the call easier.

Be direct about line dances

Utah weddings can go either way with line dances. Some crowds love them. Some couples want none of them. Both are fine.

If you have strong feelings about the Cha Cha Slide, Cupid Shuffle, Wobble, Cotton Eye Joe, or any other group dance, say it clearly. Do not assume your DJ knows.

You can write it like this:

We are okay with one or two line dances if the dance floor needs help, but please skip Cotton Eye Joe.

Or:

No line dances at all, even if guests request them.

Or:

Line dances are fine early in open dancing, but we do not want them to take over the whole night.

That gives the DJ a real boundary. It also avoids the awkward moment where a guest asks for a song and the DJ is trying to guess what you would want.

Mention clean edits and explicit requests

A lot of Utah receptions are mixed-age and mostly dry, with kids, grandparents, church friends, and college friends all in the same room. That does not mean the music has to be boring. It does mean the request policy should be clear.

Tell your DJ how you want explicit songs handled:

  • Clean edits are okay
  • Clean edits only after a certain point in the night
  • No explicit songs and no clean edits of explicit songs
  • Guest requests are fine as long as they fit the vibe
  • Guest requests should be checked against the couple's do-not-play list first

I would rather know this before the reception than make that decision on the fly. My job is to keep the dance floor moving while still respecting the kind of night you want.

Do not use the list to micromanage the whole dance floor

There is a difference between protecting the vibe and trying to pre-plan every transition.

A helpful do-not-play list says, “Here are the songs and styles that do not fit us.” A stressful one says, “Only play these 74 songs in this exact order, and never change based on the room.”

The best receptions leave space for both: your taste and the crowd's energy.

Give your DJ must-plays. Give your DJ do-not-plays. Then let them connect the dots in real time. That is where mixing, quick transitions, and room-reading actually matter.

Tell your DJ why a song is banned if the reason matters

You do not need to explain every choice. If you hate a song, you can just say so.

But context helps when the reason changes how the DJ should handle requests. For example:

  • “Please do not play this artist because of a family situation.”
  • “No breakup songs during dinner or dancing.”
  • “Skip songs that mention alcohol heavily because our reception is dry.”
  • “Do not play this one even if the wedding party asks.”

That last line matters. Guests often request songs with confidence. A clear note lets the DJ politely say no without making it a big deal.

Send it early enough to actually use it

Try to send your do-not-play list with your timeline and song notes, not the morning of the wedding.

A week or two before the wedding is usually plenty. That gives your DJ time to look for clean edits, flag anything confusing, and understand the style you are going for.

If you are booking DJ Jake, this can be part of the planning conversation along with your must-play songs, special dances, timeline, MC cues, and request policy. You do not need a perfect music spreadsheet. A clear list is better than a long one.

Keep the final list simple

Here is the format I would use:

Hard no songs/artists

  • Song or artist name
  • Song or artist name
  • Song or artist name

Use judgment

  • Line dances are okay only if the floor needs help
  • Clean edits are okay after dinner
  • Guest requests are okay unless they are on the hard-no list

Extra notes

  • Keep things family-friendly until open dancing
  • Avoid songs that feel too club-heavy early in the night
  • No joke requests during special dances or sendoff

That is enough for a good DJ to work with.

My take

Your do-not-play list should make the reception feel safer, smoother, and more like you. It should not make the DJ scared to take a request or adjust when the room changes.

The sweet spot is simple: protect the songs you really do not want, explain the boundaries that matter, and leave room for the dance floor to breathe.

If you want help building a reception music plan that still feels flexible, check out my wedding DJ packages or reach out here. I can help you sort must-plays, do-not-plays, clean edits, and guest requests before the wedding day gets busy.

FAQ

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

Most couples only need a short list of true hard-no songs, artists, or styles. If the list gets too long, it can make it harder for your DJ to read the room and keep the dance floor moving.

Should we allow guest requests at our wedding?

Guest requests can work well if your DJ checks them against your do-not-play list and the overall vibe. If you do not want guest requests, say that clearly before the reception.

Can we ban explicit music at a Utah wedding reception?

Yes. Tell your DJ whether clean edits are okay, whether explicit songs are banned completely, and whether that rule changes later in the night.

When should we send our do-not-play list to the DJ?

Send it with your final timeline and music notes, usually one to two weeks before the wedding. That gives your DJ time to prep clean edits and ask clarifying questions.