How to build an office party playlist everyone actually likes
Every office party has a music problem, and it is almost never a taste problem. It is a collection problem.
Somebody posts “drop your song suggestions here” in a group chat. Eleven people answer. Nine of them are from the same three teams, four are jokes, and the person who builds the playlist ends up filling the gaps with whatever they personally like. Then a hundred people spend an evening listening to the musical taste of the two loudest employees.
The fix is not better taste. It is asking everyone, once, at the moment they are already answering you.
Ask with the RSVP
Put the song question next to the “are you coming” question. Same form, same minute.
The difference is dramatic, and it is not about enthusiasm — it is about friction. People will type one song title while they are already filling something in. Almost nobody will open a chat thread three days later to do it.
One box, one line of instruction:
One song you want to hear. First thing that comes to mind is fine.
Asking for one song rather than “some ideas” gets you more responses and better ones. People agonize over a list of five. They will give you one instantly.
If you want a second box, make it “anything you would rather not hear,” which is more useful than it sounds and catches the two or three songs that genuinely sour a room.
How many songs you actually need
This is arithmetic, and getting it right saves the night.
At roughly four minutes a song, an hour of music is about fifteen songs. So:
| Music runs for | Songs you need | With a buffer |
|---|---|---|
| 2 hours | ~30 | 40 |
| 3 hours | ~45 | 55 |
| 4 hours | ~60 | 75 |
Build about 25% more than the math says. You will cut some, the night may run long, and a playlist that ends while people are still dancing is a worse problem than one that never gets to the end.
In an office of any size you will usually collect more requests than you need, which is a good position to be in: you are choosing from real answers instead of padding with your own.
Build the night in three blocks
Do not shuffle. A single shuffled list treats the first hour and the last hour as the same room, and they are not.
Arrival and drinks. People are standing up, finding each other, talking. Music is background. It should be recognizable and it should not demand attention. This is about a third of your list.
Dinner or the sit-down part. Quieter still. If there are speeches or awards, the music goes off entirely — do not make a manager compete with a chorus.
After dinner. This is the part the requests were for. Front-load the songs that got requested more than once, because a song several people asked for is the closest thing you have to a guarantee.
If you are running a raffle or awards, put them at the start of the third block. The room is together, nobody has left yet, and the music picks up straight after.
Handle the requests you cannot play
Some requests you will not use, and it is easier if you decide the rules before you look at the list rather than after.
- Explicit lyrics. It is a work event. Find the clean version or cut it.
- Songs about a specific person. The joke will not read the way the requester thinks it will.
- Eleven minutes long. No.
- Anything that clears the floor. You will know.
You do not need to explain any of these publicly. The person who requested it will not follow up, and if they do, “we kept it work-appropriate” is a complete answer.
Give the DJ or the venue something usable
If someone else is running the music, hand over more than a list of titles.
- The songs, with artists — half of all song titles are ambiguous without them
- Which block each song belongs to
- The handful of songs requested by more than one person, marked
- The do-not-play list
- The exact time the music goes off for speeches, and when it comes back
- A phone number for the person on your side who can make a call mid-night
Send it a few days ahead, not on the night. A DJ who has seen your list in advance will build around it. A DJ handed a phone at 8pm will play their own set with three of your songs in it.
A detail worth stealing
When a requested song comes on, have whoever is on the microphone name who asked for it. It takes five seconds, it costs nothing, and it changes the character of the whole thing — the playlist stops being a background and starts being something the room built.
It also quietly makes the point that everyone was asked, including the people who do not usually get asked.
Keep the list
Save the playlist after the party. Next year’s committee starts from a list of songs this specific group of people actually asked for, which beats starting from a blank page and a group chat.
Collecting the requests without a group chat
Staff Party asks for song requests as part of the RSVP, so the person building the playlist gets one list with everyone on it instead of whoever was paying attention to the chat that afternoon. The same form collects dietary needs and the headcount.
Where this fits in the wider timeline is in the office holiday party checklist, and the features page covers what happens on the night — check-in, the raffle and the photo album.