Song requests at a party: the list that saves the night

There is a moment when every party loses its music. It usually arrives around half eleven: the dance floor is properly full for the first time, and precisely because of that somebody walks up to the booth and shouts a title at the DJ. Two songs later, the next one. From then on the DJ is no longer working the evening, but the queue in front of the booth.

The problem is not that guests want to hear songs. That is the best thing that can happen to a dance floor. The problem is how the requests arrive.

Why paper and shouting fail

Three reasons, and all three are independent of how good the DJ is:

• Shouted requests come at the wrong time. People ask when they feel like it, and that is rarely the moment the track fits. The DJ then either wrecks the build-up or stands in front of a disappointed face.
• Paper loses the majority. Eight people ask for the same song, but there are eight slips of paper, each with one vote. How is the DJ supposed to see that this is the song of the night?
• At two in the morning nobody can hear anything. The hours when requests arrive are exactly the loudest ones. Half the list is misheard, and then a different song by the same artist gets played.

Rule 1: collect earlier than you think

Requests collected before the party are better requests. Not because guests are more sober, but because they think it over. Someone tapping their phone during dinner names the song they actually want to hear. Someone walking to the booth at half past one names the song that just came to mind.

In practice that means the way to submit a request has to be open before the dance floor is. A QR code on the table is enough. Best of all is the same route the guests use for their photos anyway, because nobody memorises a second address.

Rule 2: count them together instead of piling them up

A request list only becomes useful once identical wishes turn into one line. That is the whole difference between “here are 60 slips of paper” and “two thirds of the room want these four songs”.

This holds even if you do it by hand: keep a list where you add a tally mark instead of writing a title down twice. At the end of the night the marks show which songs carried the room, and the DJ can see it long before that.

Rule 3: give no answer

This is the rule broken most often, and it is the most important one. The moment a guest learns their request was accepted, they start waiting for it. The moment they learn it was declined, they are offended. Neither state helps anyone at a party.

A request is a suggestion, not an order. Leave that open and it can be played on the mood, moved, or not played at all, and nobody keeps score. So a request list should show guests what has been asked for, but not what became of it.

What the DJ needs from you beforehand

Three things, in writing, not on the night:

• The first song of the dance floor. If you have an opening dance it is settled anyway. If you do not, it still decides who gets up first.
• The no-go list. Two to five titles or genres that have no business at this particular party. There is usually a reason only you know, and the DJ cannot guess it.
• The last song. It decides which feeling people take home. Do not leave it to chance, and do not leave it to the last shouted request.

How many requests actually turn up?

As a rough figure: at a party with 80 guests you get 25 to 50 requests if the route is easy enough. After merging, 15 to 30 different titles remain, and maybe 12 of them get played in one night. That sounds like a poor rate but it is not: the rest is still worth having, because it shows the DJ which way the room wants to go.

The list is worth something afterwards too

Keep it. A party is remembered in pictures, but the music is what comes back first. A year later the list of songs requested that night is a surprisingly precise record of who was there and how old everyone was.

How it works here

The gallery has a section of its own for this: your guests type in artist and title and get suggestions as they go, identical requests are merged into one line with a counter, and the DJ gets a link of their own to a console built for a tablet next to the decks. Guests deliberately get no answer back. At the end of the runtime the finished list sits in the closing archive as a text file.

How song requests work in detail