How to Take Song Requests at School Dances
School dances live or die by the music. Get it right and students are on the floor all night. Get it wrong and you have a gym full of students standing against the wall staring at their phones. Taking song requests is one of the most effective ways to keep energy high and make every student feel like the night was made for them — but only if you handle it the right way.
Set expectations before the event
The worst time to figure out your request policy is when a student is already standing at your booth demanding you play something. Decide your rules in advance and communicate them clearly.
Work with student council or event organizers to agree on a content policy. Most schools require clean edits only and have specific artists or genres they want kept off the floor. Build a do not play list with staff or administrators before the night so there are no awkward conversations midevent. Make your request process visible from the start. If students know how to submit requests before they walk through the door, they will actually use the system instead of crowding your booth.
Use a digital request system instead of walkups
At a school dance, walkup requests are a recipe for chaos. Students cluster around the DJ booth, shout over each other, and your concentration breaks right when you need it most. A digital request system solves all of this.
A browserbased platform like Rekwest lets students scan a QR code and submit requests directly from their phones. No app download needed, no queue at the booth, and you get every submission in one organized place. You can review requests, approve what fits, and decline what does not — all without leaving your workflow.
Display the QR code in places students naturally look:
A large sign near the entrance so they see it before they even hit the dance floor. Projected on a screen or monitor near the DJ booth. On the refreshment table where students gather between songs.
Filter requests before they reach you
Not every request belongs at a school dance. A good request system lets you screen submissions before they affect your set, which means no awkward moments and no track playing that should not be there.
Use a platform that lets you approve or decline requests individually. Set up content filters in advance so explicit tracks never make it through to begin with. If a request does not fit the moment, decline it politely and move on. You do not need to explain every decision.
Let students vote on what gets played
One of the best things about a digital request system is that the crowd does some of the curation work for you. When students can vote on submitted requests, popular songs naturally rise to the top and you can be confident you are playing what the room actually wants.
Turn on voting so students can upvote each other’s requests. Use the vote count as a guide, but not a rule. A song with ten votes might not fit right now, but it might be perfect in twenty minutes. Popular voted requests also give you an easy way to build hype — when you finally drop the most requested song of the night, the reaction will show it.
Collect requests in advance
If the school promotes the event ahead of time, give students a way to submit requests before they even arrive. Preevent submissions let you build a starting playlist that already reflects the crowd’s taste and reduces the scramble to find tracks on the night.
Share the request link on the school’s social media, in morning announcements, or through student council. Review presubmitted requests and pull the tracks into your library ahead of time so there are no gaps. Use the preevent list to spot any recurring requests and make sure you have those songs ready to go.
Balance requests with your setlist
Requests should enhance your set, not control it. The energy of a school dance builds and falls in waves, and you are the one responsible for managing that arc. Do not let requests pull you off course at the wrong moment.
Play requests when they fit the current energy, not the moment they come in. Keep a handful of guaranteed floorfillers in reserve. When energy dips, play one of those rather than the next item in the queue. Mix requested songs between your planned tracks so the set stays cohesive and the floor stays full.
Handle the noplays gracefully
At some point you will have to decline a request, whether it is off the content policy, does not fit the vibe, or simply is not a song you have. How you handle it matters.
If you are using a digital platform, send a short, friendly decline message through the system so the student knows their request was seen. Never make a student feel embarrassed in front of their peers for what they requested. If the song would have been fine at a different moment, keep it in mind and come back to it later in the night.
Make it feel personal
The best school dances feel like they were designed for the specific group of students in the room, not a generic event playlist. Requests are your best tool for achieving that.
When you play a requested song, give it a quick shoutout on the mic. “This one goes out to everyone who asked for it” is enough to make a hundred people feel seen at once. Pay attention to which requests get the biggest reaction when played. That is realtime feedback about what is working with this particular crowd. By the end of the night, the students who submitted requests will feel like they were part of creating the experience, not just attending it.
A wellmanaged request system turns a school dance from a passive event into something students feel ownership over. With the right platform, a clear content policy, and a little crowd management, you can keep the floor packed and give every student a moment they will remember. Tools like Rekwest make it easy to collect, filter, and manage requests in real time so you can stay focused on the music and let the crowd do the rest.