How to handle song requests at a wedding without losing your set

What are the four ways to collect song requests?

In practice there are only four, and each one comes at a different cost. It helps to know which one you are paying.

The guest who walks up to the booth. This is the default, meaning it is what you get when you have not picked anything else. It happens at the worst possible moment (you are cueing the next track with a full floor), and it usually comes a couple of drinks in and in a hurry. The interruption is not even the worst part. It is that you are negotiating on your feet, in front of people, and everyone nearby hears your answer.

A notepad or request cards on the tables. Better than the booth, because it keeps requests off your back during the dancing. But you end up with thirty slips in illegible handwriting, duplicates everywhere and no way of knowing which ones really matter. And only the guests who notice the cards take part, which is usually a handful.

The song line on the RSVP card or wedding website. Well meant and almost always useless. Only a small share of guests fill it in, cold, thinking about the song that represents them rather than the one they want to dance to. And it arrives so early that by the wedding nobody remembers what they wrote.

A QR code on the tables during dinner. Guests request and vote from their phone while they eat, and you get a list ranked by votes before the dance floor opens. It is the only one of the four that gives you what you actually need: not a stray request, but a picture of what this particular room wants.

Why dinner and not the dance floor?

This is the most misunderstood point, so it is worth slowing down. The reasonable objection is: “I don’t want two hundred people on their phones in the middle of my set.” And it is right. That is why the dance floor is the wrong place.

During dinner, people already have their phone out. They are seated, between courses, deep in table conversation. It is the one moment of the reception when requesting a song costs nobody anything. They also think better: they remember the song from their college days, vote for the one someone else added, argue about it a little. The list that comes out is a lot more honest than one made in a rush at the booth.

Then there is the effect almost nobody expects: when the dance floor opens, the phones go away. Guests have already asked for their song, and all that is left is to wait and see if it plays. It is the exact opposite of what everyone fears.

Does the request list decide what you play?

No. It sorts, it does not command. Be clear on this before you pitch it to anyone, because it is the first question the couple will ask, and the one you will ask yourself. A request list ranked by votes is not a work order. It is information about a crowd you just met.

You still decide what goes in, in what order and what it mixes into. If the top song is a slow ballad and it is 11 p.m. with the floor at its peak, the ballad waits, or does not make it at all. The difference from having no list is that you stop guessing your first three songs and correcting on the fly: you open the dance floor already knowing where the room is headed.

And there is a part no advance list will give you: two or three heavily voted songs that neither the couple nor you would have picked, often a hometown favorite, the anthem of one friend group or the inside joke of an entire table. Those tend to become the songs of the night.

How do you say no without looking bad?

You will turn requests down either way, so it pays to have your answer ready. Three things that work:

Never a flat no. “I’ve got it, I’m saving it for later” ends the conversation without embarrassing anyone. But if you say it, deliver when you can: people remember.

If the couple blocked it, say so. Many couples hand over a do-not-play list (the song tied to an ex, the one that upsets the family), and it is the perfect answer because it is true. “The couple asked me not to play that one” leaves no room for argument and does not make you the bad guy.

Let the no stop being yours. This is the big shift. When requests come through a list with votes, the guest can see their song sitting at number sixteen with fifteen songs ahead of it that have more support. The rejection is no longer the DJ who will not play it; it is the rest of the room voting for something else. That alone saves you half your booth conversations.

What do you keep after the wedding?

One more thing, and you start to notice it around your tenth wedding. If you collect requests in an organized way, every wedding leaves you a record of what was requested and voted. After a full season you have real data on what works by type of wedding, by average age and by area.

The notepad of paper slips will never give you that, and it is what separates a DJ with ten years of playing from a DJ with ten years of getting better. If you want to see how that works in practice, here is how TuParty works as a DJ song request app, and the seven things to check before choosing one.