Wedding music brief: ceremony, entrances, first dance, drinks reception and dinner.

Your first contact with an event client goes wrong through poorly asked questions or questions nobody asked, rather than a lack of good taste. When the day arrives and the entrance needs a different song, the drinks reception sounds at dance-floor volume or three songs were forbidden, the problem began in the meeting that lacked a structure.

This guide covers the music brief, do-not-play list, first dance, entrances, ceremony music, drinks reception and dinner: the seven blocks turning a conversation into an executable plan.

The music brief as a reliability agreement

The music brief is the structured collection of everything played at the event. It is a document containing moments, songs, responsible people, levels and restrictions, rather than a song list. Close it with a written summary confirmed by the couple or person responsible; that writing protects you on event day.

At minimum, ask about:

• Moments and their songs: ceremony, entrances, first dance, parent dances and final waltz. Get exact title, performer and version—remix, original, instrumental.
• Styles by time slot: what is wanted for ceremony, drinks reception, dinner and dancing, and what is not.
• Restrictions: forbidden songs, uncomfortable subjects and the space’s volume limits.
• Audience profiles: predominant ages, family groups, culture or languages.
• Music logistics: who supplies ceremony audio, whether there are speeches, shows or performances, and who coordinates their cues.

A good brief also establishes the tone: the client understands they will give direction and trust your reading of the dance floor, rather than choose 150 songs. Making that clear avoids an awkward conversation halfway through the night.

Ceremony music, entrances and first dance

Ceremony music is the day’s most rigid block: just three or four pieces—prelude, the couple’s entrance and exit—playing at moments without a second chance. Prepare the exact version downloaded locally, check each file’s beginning and end—a forty-second intro ruins an entrance—and agree who presses play: you or the person responsible at the place of worship.

Reception entrances introduce each person or couple with a song. Confirm the order and, if there are many entrances, whether each has its own song or one shared song; the latter is much more robust when twelve people must arrive. Mark entry points in the file and prepare the transition to the next moment.

The first dance is the focal moment: chosen song, confirmed version, level set beforehand and a clean exit into the next block—parent dances or straight to dinner. If the song is long, agree in advance whether to play it in full or cut it towards the end.

The classic mistake in all three is improvising with streaming files that day. Download, analyse and test everything chosen on the actual equipment. The request-management guide explains how to negotiate requests arriving from the dance floor.

Drinks reception, dinner and background volume

The drinks reception and dinner use background music with a different mission from dancing: supporting conversation. That means low volume, continuity with few strong breaks and stable energy; a usual reference is being able to talk normally one metre from the speaker.

For the drinks reception, use the style defined in the brief, moderate tempo, unobtrusive lyrics and enough duration: an hour-and-a-half slot will play at least thirty pieces. If photos and the drinks reception are in different rooms, check whether a second sound position is needed or music moves with you.

For dinner, the same criterion applies with more restraint: nothing inviting people to get up too early, no sudden energy changes between songs and no party pulse. The transition to dancing is the day’s key moment: prepare it with a recognisable opening and progressive energy rise, rather than abruptly cutting to a dance track.

Must-play and do-not-play lists

The do-not-play list is as important as the essentials: songs associated with ex-partners, family drama or bad memories. Always request it in writing and load it into the software with its own tag, making it visible at a glance throughout the event.

Alongside it, keep a must-play list: between ten and twenty titles with priorities marked. More than thirty turns it into a cage: you can no longer read the dance floor because almost everything you want to play is already committed.

Manage dance-floor requests using a clear rule agreed beforehand: accept them if timing and energy allow and they do not conflict with the no list. Communicate the decision using public speaking and announcements, which explains how to do it without arguing in front of anyone.

From brief to set: preparation

With the brief closed, preparation is the usual work with direction: folders by moment—ceremony, entrances, drinks reception, dinner, dancing—BPM and key analysis of chosen pieces, cues at exact entry and exit points, and a running order for each slot that can be followed without watching the screen.

Plan set structure through energy arcs rather than individual songs: the drinks reception rises little, dinner holds steady, dancing opens with something recognisable, and later hours are read live. The set-programming guide develops that framework.

One specific precaution: leave space. A brief occupying 100% of the minutes has no room for speeches running long, delayed dinner or a dance floor suddenly asking for something else.

Confirming the running order with the couple and planner

Send the final summary a week before: moments and songs, entrance order, restrictions and timings, explicitly requesting confirmation. Copy the planner or wedding coordinator if present; copy the photographer or videographer too, because they need to know when the first dance happens to prepare lighting and framing.

On event day, the first conversation—five minutes—confirms nothing changed: a cancelled entrance, added speech or song no longer wanted. Afterwards, the written running order leads. It is the difference between improvising twice and not improvising at all.

Questions that build a good brief

The brief’s quality depends on the meeting’s quality. These questions distinguish a solid running order from an improvised list:

• Which moments are non-negotiable, and in what order? Fix the skeleton: ceremony, entrances, first dance, parent dances, speeches and ending. If order is unclear, it will be debated at the venue.
• Which song accompanies each moment, and which version? The same song exists as an original, radio edit, remix and live version; that difference can ruin an entrance prepared for weeks.
• What plays while people talk? Define drinks reception and dinner here: style, tempo and level. This question prevents the most complaints, because almost all volume problems begin in these slots.
• What must never play? Get the do-not-play list and its reasons, even if detailed explanations are unnecessary.
• Who supplies ceremony music and who is in charge? The answer determines extra equipment, whether to rehearse with the person responsible at the place of worship and whether another sound zone is needed.
• Are there specific family or cultural requests? Learn genres, languages and traditions beforehand to integrate them without improvising.
• Until when can music play, and how loud? The answer shapes the entire set’s pace and when dancing opens.

With those answers in writing, the rest—folders, analysis, cues and running order—is technical work. Without them, technical work is done twice: once for the meeting and again when everything changes.

Next step

With the running order resolved, support it: microphones, master of ceremonies and redundancy layers in Voice and redundancy at events.