Your Boundaries
Wedding DJ do-not-play lists: what should you include?
Your do-not-play list does not need every song you have ever skipped. It should make the important boundaries clear.
The songs you cannot stand. The music that would change the feel of the reception. The choices that carry a personal reason. And anything you genuinely do not want played, even if a guest asks for it.
What actually deserves a place on your do-not-play list?
Start with the difference
"I would rather not hear it" and "do not play it" are different instructions.
Prefer less of
Music you do not especially enjoy and would prefer not to hear much of.
Avoid if possible
Music you generally do not want, where some discretion may be acceptable.
Do not play
Music you clearly do not want included.
Absolute no
Never played, regardless of a guest request or what is happening on the dance floor.
These are not industry-standard labels, just a useful way to plan. You do not need all four.
The clearer the boundary, the easier it is to respect.
Meaningful boundaries
Start with the music that would actually affect your experience.
This guide will not tell you which songs to dislike. These are the kinds of reasons something might belong on your list.
Specific songs
A song you genuinely do not want played.
Artists
An artist you do not want represented at the reception.
Genres or styles
A musical direction you do not want shaping the reception.
Wedding staples
Traditional or commonly played reception music you simply do not want at your wedding.
Line dances or participation songs
If you do not want those moments as part of the reception.
Personal associations
Music connected to a memory, relationship or experience you would rather not bring into the wedding.
Lyrical or content concerns
Music you do not feel fits your event or audience.
Cultural or family considerations
Music that needs more context, should only appear in a particular way or should not be used casually.
Do not overbuild it
You do not need to blacklist every song you would skip.
A list that tries to catalog every minor dislike can become less useful. Music may not need to be a hard prohibition just because:
If you genuinely do not want it played, that is different. There is no maximum length: a couple with many real boundaries can list them all.
Save the strongest instruction for the strongest preference.
How specific should you be?
Make the boundary as broad as you actually mean it.
Song level
"We do not want this specific song."
Artist level
"We do not want music from this artist."
Genre or style level
"We do not want this musical direction represented."
Context level
"This music is okay in one part of the reception but not another."
Request level
"This should not be played even if someone requests it."
Disliking one song does not necessarily mean disliking the artist. Disliking one artist does not necessarily mean excluding a whole genre. And if you genuinely do not want a genre, you can say that clearly too.
Make the rule match the reason.
Personal boundaries
"Please don't play this" can be enough.
You may have private reasons for avoiding a song or artist, and you do not owe anyone a detailed explanation. Your DJ may need to know how firm the boundary is, but not the story behind it. Reasons might include:
Your DJ needs to know the boundary.
They do not necessarily need the backstory.
Specificity matters
Do not let a broad label say more than you mean.
Terms like Latin music, Caribbean music, cultural music or international music can cover many different genres, traditions and styles. If you want to avoid one specific style, artist or tradition, name that rather than accidentally excluding a much broader category.
And if a broad category genuinely is outside your preferences, you can say so. For more on describing music precisely, see Wedding Reception Music Genres Explained.
Guest requests
Your boundaries should not disappear because someone asks.
Decide in advance how firmly your restrictions apply to requests. Three example policies, none better than the others:
Hard boundary
If it is on the do-not-play list, it is not played, even if requested.
DJ checks the context
Some lower-level preferences have flexibility, while hard boundaries stay protected.
Couple approval
For certain requests, the DJ checks with a point person you have chosen in advance, rather than interrupting you during the reception.
A guest request is a request.
It does not automatically override the couple's plan.
Boundaries + freedom
You can set hard limits and still give your DJ room to work.
Boundaries
Define what is outside the acceptable range.
Flexibility
Allows decisions inside the acceptable range.
You might give your DJ broad freedom during open dancing while several artists or songs stay completely off limits. For more on balancing the two, see How Much Input Should You Give Your Wedding DJ?
Freedom works inside the boundaries you set.
Not everything is binary
Sometimes the better instruction is "less," not "never."
There may be genres, eras or styles you do not want dominating the reception but would not mind hearing now and then. Useful language might sound like:
"We do not want this to become a major part of the night."
"A little is fine, but this should not drive the dance floor."
"We would rather prioritize these other genres."
"We are okay with this if it fits, but it is not something we need."
Expectations
Make sure "do not play" means the same thing to both of you.
How do you handle do-not-play songs?
Are those restrictions treated as absolute?
How are guest requests checked against the list?
Can we distinguish hard boundaries from softer preferences?
How should we communicate artist-level or genre-level restrictions?
How do you handle requests for something outside our music preferences?
Who should make a decision if an unexpected situation comes up?
How are important cultural or family music instructions handled?
The purpose is to avoid ambiguity. For the broader set of hiring questions, see Questions to Ask a Wedding DJ.
Put it into words
Give your DJ boundaries they can actually use.
Your Do-Not-Play Brief
Absolute do-not-plays:
[songs, artists, genres that are completely off limits]
Personal no's:
[music we do not want for personal reasons]
We would prefer less of:
[genres, eras, styles that should not dominate]
Context-specific boundaries:
[music that is acceptable only in certain situations]
Guest request rule:
[how restrictions apply to requests]
Important cultural or family notes:
[anything requiring specific handling]
If something unexpected comes up:
[who has discretion, whether a point person exists]
EXAMPLE 01
A few firm limits, broad flexibility otherwise
- Absolute do-not-plays
- Two specific songs and one artist
- Prefer less of
- Nothing in particular
- Guest request rule
- Requests welcome, except anything on the list
- If something unexpected comes up
- DJ's judgment
EXAMPLE 02
Skipping common traditions, flexible on the music
- Absolute do-not-plays
- Line dances, the garter and bouquet songs, and group participation songs
- Prefer less of
- Very slow songs once dancing starts
- Context-specific boundaries
- Explicit versions are fine after dinner, not before
- Guest request rule
- DJ can take requests that fit the vibe
EXAMPLE 03
Family music, personal boundaries and a clear request rule
- Personal no's
- A handful of songs and one artist, no explanation needed
- Cultural or family notes
- Our family songs only during the set after dinner, played in full and never as background music
- Guest request rule
- Nothing on our list is played, even if requested
- If something unexpected comes up
- Check with our planner, not with us
Three different lists, and none is better than the others.
Keep it useful
A few things can make your boundaries harder to understand.
Using "do not play" for every minor preference
It can make hard boundaries harder to tell apart from mild dislikes.
Being broader than you mean
Banning a genre when the issue is actually one artist or style can communicate the wrong thing.
Forgetting about guest requests
Clarify whether restrictions stay in place when someone requests the song.
Assuming the DJ knows why something matters
They do not need every story, but they should know whether a boundary is firm.
Creating rules without discussing them
Make sure the DJ understands how the list should actually be used.
Long list or short list, either is fine if the boundaries are clear.
What you don't want matters too
Your preferences include boundaries.
Understanding a celebration is not only about what you like. What you do not want can also clarify the atmosphere, music direction and experience you are trying to create, and what you are really looking for in a DJ.
VibeCraft Marketplace is being built around richer wedding context, including:
When it launches, that context is meant to help couples discover DJ companies that may align with their celebration.
Organic VibeCraft recommendations are not sold to the highest bidder.
Not more options. Better options.
Questions
Do-not-play list FAQ
Should I give my wedding DJ a do-not-play list?
If there is music you genuinely do not want at your wedding, a do-not-play list is one of the clearest ways to communicate it. If you have no real boundaries, you do not need to invent any.
What should be on a wedding do-not-play list?
Music that would actually affect your experience: specific songs, artists, genres or styles, wedding staples or participation songs you do not want, music with personal associations, content concerns and cultural or family music that needs particular handling.
How many songs should be on a wedding do-not-play list?
There is no right number. A list is useful when it clearly communicates genuine boundaries. A couple with many real boundaries can list them all; the point is clarity, not length.
Can I tell my wedding DJ not to play an entire genre?
Yes. If you genuinely do not want a genre represented, say so clearly. Just make sure the boundary is as broad as you actually mean, since the issue is sometimes one artist or style rather than the whole genre.
Can I tell my wedding DJ not to play a certain artist?
Yes. An artist-level boundary is a clear, common instruction. Say whether it applies to all of their music or only certain songs.
What happens if a guest requests a do-not-play song?
That depends on the policy you agree with your DJ in advance. Many couples treat hard boundaries as protected even when requested. A guest request does not automatically override your plan.
Should I include songs I simply do not like?
You can, but it helps to separate mild dislikes from real boundaries. Labeling something "play less of this" rather than "do not play" keeps your strongest instructions clear.
Can my do-not-play list include common wedding songs?
Yes. If a traditional or commonly played reception song does not fit your wedding, it can go on the list. You do not need to include music just because weddings often have it.
What if I have a personal reason for avoiding a song?
That is a perfectly valid reason. Add it to the list and make clear how firm the boundary is.
Should I explain why a song is on my do-not-play list?
Not necessarily. Your DJ needs to know the boundary and how firm it is, not the personal story behind it. Share context only if you want to.
Can I change my do-not-play list before the wedding?
Usually, yes. Ask your DJ how and when they like to receive final updates so the latest version is the one they use.
Will a do-not-play list make it harder for my DJ to read the room?
Not by itself. Clear boundaries define what is off limits, and your DJ can still respond to the room with everything inside those limits. Boundaries and flexibility can work together.
Keep Planning
Where to go next.
Know what belongs in your wedding.And what doesn't.
Clear preferences and clear boundaries make it easier to understand the DJ and reception experience that may fit you. VibeCraft Marketplace is being built to help couples turn that clarity into a more focused DJ search.