Why Event Planners and DJs Need to Meet Before the Day

Email is good for paper trails. It's good for confirmations, contracts, and the kind of information that needs to exist in writing because someone might need to point to it later. What email is bad at is nuance, tone, and the things that are harder to put into words than most people realise.

By the time an event planner and a DJ sit down — or get on a call — two weeks before the event, something useful always happens. Not because either person has new information to deliver. Because talking is a different medium than writing, and different things come out.

What Gets Missed in Email

Timing assumptions. In writing, a timeline looks clean. "Doors open 19:00, dinner at 19:30, speeches 20:30, dancing from 21:30." Fine. But in a conversation, you find out that one of the speeches is a 15-minute slide presentation and someone in the room knows that it always runs longer. You find out the client's mother has asked to make a short speech that isn't on the formal program. These are things the planner knows but didn't think to include in the email, because they seem like details rather than factors.

In a conversation, those details come out. They always do, because talking invites it.

Tone of the evening. A brief can say "professional and upbeat." That phrase covers about a thousand different events. Talking for 20 minutes reveals whether "upbeat" means background Latin jazz during cocktails, or whether it means the CFO wants to open the dance floor with a surprise set to a specific song. These are not the same thing. Email collapses the distance between them. A conversation doesn't.

What the client is afraid of. Every event has something the organiser is privately worried about. Maybe a particular department head and his team are known to leave early, and the client is desperate to keep them engaged through dinner. Maybe last year's event ended badly and the client hasn't told anyone why but they're overcompensating on the music brief to make sure it doesn't happen again. These things don't appear in written briefs. In a conversation, they emerge — usually as a brief mention or a half-sentence that reveals much more than it says.

What Real Dialogue Produces That Email Cannot

Collaborative adjustments. In a real conversation, you can say "I'm thinking about approaching the last 45 minutes of the evening this way — does that align with what you're expecting?" And the planner can say, "Actually, the awards finish much later than we usually signal on the timeline — can we shift that by 20 minutes?" That exchange takes 90 seconds. In email, it takes four days and three misunderstandings.

Trust. This matters more than most planners admit. The DJ who called me last week to go over the timeline isn't someone I've met, but by the end of that call we had established a working relationship. I knew how she communicated. She knew I would flag problems early rather than absorb them quietly. That kind of calibration doesn't happen over email.

Actual creative input. When I understand the evening in enough depth — what the client is celebrating, who the audience really is, what the energy should feel like at 10 PM versus midnight — I can offer something beyond executing the brief. I might suggest a specific musical moment that fits the night better than anything the brief described. Or I might identify a structural problem in the timeline that nobody has noticed. But I can only do this if I've had a proper conversation, not just reviewed a PDF.

How to Structure a Useful Briefing Call

Keep it to 30 to 45 minutes. Anything longer usually means the brief wasn't thorough enough in the first place, and you're doing catch-up.

Start with the creative. What is this evening supposed to feel like? What's the best possible version of it? Let that conversation run before you get into logistics.

Then walk through the timeline, but not just the times — the texture of each segment. What's happening socially during dinner? Is the dancing guaranteed or does it need to be built from scratch? Are there non-music elements (awards, video, speaker) that require coordination?

End with risk. What could go wrong? What have previous events at this venue struggled with? What's the one thing the client is most anxious about?

Write notes during the call and send a summary within 24 hours. This does two things: it confirms what was discussed, and it reveals any discrepancy between what you heard and what the planner intended. Better to catch that on day minus-14 than day zero.

The Conversation That Changes the Event

Three months ago I did a gala for a pharmaceutical company. The brief was straightforward — typical corporate formats, conservative music preferences, standard timeline.

On the briefing call, the planner mentioned almost in passing that one of the senior directors was retiring that night. It wasn't in the brief. Nobody had flagged it as a focal point. But it explained why the client had been so precise about the musical programming for a particular 30-minute stretch of the evening — the one where dinner was transitioning to a more relaxed atmosphere.

I adjusted the playlist. I built that 30-minute stretch specifically around the era and genre that fit someone celebrating 35 years in the industry. It was subtle — the retiring director probably didn't consciously register it as being for him. But three different colleagues commented on the atmosphere during that moment.

That detail came out in a conversation. It would never have made it into an email.