Every couple has one. Maybe it’s the song from a bad breakup. Maybe it’s “Cha Cha Slide” for the third wedding in a row. Maybe your uncle has already texted the DJ requesting a nine-minute Grateful Dead jam in the middle of dinner. Whatever the reason, a “do not play” list is one of the most useful tools you have for protecting the mood of your reception \u2014 and one of the most awkward things to put together if you don’t know where to start.<\/p>\n
At Sound Precision Entertainment, we ask every couple to build one during planning, because it saves us from guessing on the day of your wedding and saves you from an uncomfortable conversation on the dance floor. Here’s how to build yours without stepping on any toes.<\/p>\n
The easiest way to write a do-not-play list without sounding like you’re vetoing your guests’ taste is to frame every entry around your own story, not a judgment of the song. “This was our ex’s favorite band” lands very differently than “this band is bad.” Your DJ doesn’t need the backstory \u2014 just the title \u2014 but thinking about it this way keeps the list personal instead of preachy, which matters if a family member ever asks why a song didn’t get played.<\/p>\n
A good do-not-play list usually falls into three categories:<\/p>\n
Personal significance songs<\/strong> \u2014 anything tied to an ex, a breakup, or a chapter of your life you’re not looking to relive on your wedding day.<\/p>\n Overplayed wedding staples<\/strong> \u2014 songs you’ve heard at every wedding you’ve attended this year and have no interest in hearing at your own. There’s no shame in cutting a classic if you’re just tired of it.<\/p>\n Tone-breakers<\/strong> \u2014 anything that doesn’t match the vibe you’re going for, whether that’s a song that’s too aggressive for a formal reception or too slow for a high-energy one.<\/p>\n Most of the awkwardness around do-not-play lists doesn’t come from strangers \u2014 it comes from parents, in-laws, and wedding party members who have strong opinions about “their song” making the cut. The fix is to get ahead of it. If you know Dad is going to ask for a specific song during the father-daughter dance, or your mother-in-law always requests the same line-dance song at every family event, address it directly with them before the wedding rather than letting your DJ be the one to say no in the moment.<\/p>\n A simple script works well: “We’re keeping the reception music pretty specific to us, so we’re not doing requests that night, but we’d love to include your song during [cocktail hour \/ dinner] instead.” This gives people an alternative rather than a flat rejection, and it moves the “no” from the dance floor \u2014 where it’s most visible \u2014 to a conversation that happens weeks in advance.<\/p>\n A title and artist are enough for your DJ to avoid a song. But if there’s a song you’re cutting because a specific person is likely to request it live, tell your DJ that too. A do-not-play list works best paired with a short note on how to handle requests in the moment \u2014 something like “if anyone asks for X, feel free to say it’s already been arranged for later” rather than leaving your DJ to improvise an excuse on the spot. This is the difference between a DJ who protects your vision and one who gets cornered by a persistent guest at 9 p.m.<\/p>\n We’ve seen couples hand over do-not-play lists of 150 songs, which almost always backfires. A list that long usually means you’re trying to plan against every possible bad outcome instead of trusting your DJ to read the room. In our experience, a focused list of 10 to 20 songs \u2014 the ones that genuinely matter to you \u2014 is far more useful than an exhaustive one. It’s specific enough to protect what you care about, and short enough that your DJ can actually keep it in mind while working a live crowd.<\/p>\n It can feel uncomfortable to think about cutting a song that someone you love might request. But a do-not-play list isn’t a judgment of anyone’s taste \u2014 it’s a planning tool, the same as a seating chart or a menu choice. Not every guest gets their preferred entree either, and nobody takes that personally. Framing it this way, both for yourself and for anyone who asks, keeps the whole process low-stakes.<\/p>\n Every couple we work with fills out a music planning form that covers must-plays, do-not-plays, and everything in between \u2014 including guidance on how to handle live requests from guests. Our DJs use that form as a working guide throughout the night, not a rigid script, so your reception still feels spontaneous and alive while staying true to what you actually want to hear. If a tricky request does come up, we already know how you’d like it handled, so you’re never the one who has to say no.<\/p>\n Building your do-not-play list doesn’t have to be stressful. Keep it personal, keep it focused, and have the family conversations early \u2014 the rest is on us.<\/p>\nHandle Family Requests Before They Become Requests<\/h2>\n
Give Your DJ Context, Not Just a List<\/h2>\n
Don’t Overdo It<\/h2>\n
Remember: A “Do Not Play” List Isn’t a Reflection on Your Guests<\/h2>\n
How We Handle It at Sound Precision Entertainment<\/h2>\n