Music requests and the no-go list: a practical guide

Two lists, not one

When planning music, most couples focus on a single wishlist — songs that absolutely must be played. Just as important, and often forgotten: the no-go list. Only together do the two give a DJ real guardrails for steering the evening confidently, even when spontaneous guest requests come in.

The wishlist: what actually matters

A good wishlist isn't a random collection of favourite songs — it's structured by moments in the evening:

Rather than listing 200 individual tracks, it's usually more useful to name a few reference artists or songs per moment and leave the DJ room to handle transitions.

The no-go list: specific, not vague

"Nothing too weird, please" isn't a usable no-go — it can't actually be applied. Specific no-gos, on the other hand, are immediately usable:

• Specific genres, e.g. "no schlager", "no metal".
• Specific artists or songs, often for personal reasons.
• Specific themes in the lyrics, e.g. breakup songs during the first dance.
• Volume or tempo limits at certain times, e.g. during dinner.

How spontaneous guest requests are handled

Guest requests on the night are normal and usually welcome — the deciding question is how they're checked against the pre-agreed list. A spontaneous request that fits the no-go list and the tone of the evening can usually be worked in. One that clearly contradicts the agreed frame should be politely but firmly declined by the DJ — that's exactly what the list is for.

A practical framework for building the lists

1. Start together as a couple: five to ten songs that must be played, and five to ten that definitely shouldn't.
2. Involve both families, especially for mixed or multicultural guest lists — musical taste often differs more between generations than between cultures.
3. Think in moments, not just songs, as in the table above.
4. Discuss the list with the DJ in good time, not on the wedding day itself.
5. Trust the list rather than rewriting it constantly during the night.

An example of a well-structured no-go list

Rather than a long, unspecific list, a short, concrete set of points the DJ can actually apply works better:

Who else should have input on the list?

Beyond the couple themselves, it's worth briefly considering whether specific family members have their own important no-gos — a song associated with a deceased relative that should be deliberately avoided, for example. These points can be quietly folded into the shared list, without anyone needing to explain on the night why a particular song isn't played.

The list isn't a sign of distrust

Some couples hesitate to build a detailed no-go list, worried it signals a lack of trust in the DJ. The opposite is true: a clear list creates security on both sides. The DJ doesn't have to guess or risk accidentally hitting a sensitive point, and the couple doesn't have to worry about anything on the wedding night itself, because the guardrails are already in place.

How often should the list be updated before the wedding?

A list built once isn't a fixed document. Months often pass between the first draft and the wedding day, during which preferences can shift or new songs come up. A short check two to three weeks before the celebration, where the couple goes through the list together once more, makes sense — not to reinvent it, but to confirm it's still current.

Conclusion

A well-thought-out wishlist and no-go list is one of the most effective, least time-consuming tools in wedding planning. With DJ Veys, a personal music wishlist including an explicit no-go list is a standard part of every booking, built together during the planning call.