Qualify AV Needs Before Bringing In a Production Partner

A planner asks you for AV and you make the introduction to your production partner the same afternoon. Three days later the partner calls you confused, the planner is annoyed that they have to answer the same questions twice, and you are stuck in the middle of a conversation that should never have needed a rescue. The fix is not a longer intro email. It is a short conversation you have with the planner before anyone else gets pulled in.

Why this conversation goes wrong

The word AV means almost nothing on its own. To one planner it means a microphone and a screen in a single room. To another it means two remote speakers feeding into a general session, three breakouts running at the same time, and a recording that legal needs to review before it goes anywhere. When you pass along a request without translating it first, the production partner has to start from zero and ask the planner everything you could have asked yourself. The planner gets frustrated because they already told somebody what they needed. The partner gets frustrated because the brief they received tells them nothing they can price or staff against. You end up as the messenger for two sides who are both irritated with you, and the event still does not have a scoped plan.

The deeper problem is that you are the only person in this chain who talks to both sides regularly. If you skip the qualifying step, nobody else is positioned to catch it. A vague request stays vague until somebody forces it to get specific, and that job falls to you before the introduction, not after.

How to prepare before you make the introduction

Before you call the production partner, get the shape of the program from the planner. Ask about the agenda, the rooms involved, and the attendee count for each session. Ask who presents and whether the content comes from the organizer, from outside speakers, or from both. Ask what needs to happen between sessions, since a fast turnaround between a general session and a breakout changes what equipment and crew the partner needs to plan for.

Ask directly whether there are remote presenters, whether recording is required, and who inside the planner's organization can confirm those answers if they change. Find out where the group is in its budget process, since a partner conversation before budget approval is a different conversation than one after. Write all of this down in plain language. You are not writing a technical spec. You are writing the story of the event so the partner can see where a technical failure would actually hurt the program.

What to say

Mel, a meeting planner, opened with a request that sounded simple. "We need AV for a group of 180 and we would like to talk to your production partner directly."

Grant, the group sales manager, did not forward the request as is. "I can set that up. Before I do, help me understand the program they will be supporting. Is this one general session, several breakouts, remote speakers, or some combination."

Mel explained that the morning opened with a general session that included two remote speakers, followed by three concurrent breakouts in the afternoon.

Grant asked whether recordings were part of the plan. Mel said the board had not decided yet and would revisit it once they saw the scope and options. Grant answered plainly. "I will send the partner a brief with your dates, the agenda, the room plan, the remote speaker setup, and a note that the board still needs to decide on recording. They will come back to you with a scoped estimate and confirm what equipment and staffing that covers. I am not going to describe a setup as available until they confirm it themselves."

That last line matters. Grant did not guess at capacity or promise a configuration on the partner's behalf. He set the planner's expectations at the same time he set the partner's brief.

Mistakes to avoid

Do not treat a planner's calm tone as proof that the request is well defined. A planner can sound completely confident about a plan that is missing half the details a partner needs. Ask the questions anyway.

Do not promise specific equipment, staffing levels, or turnaround times before the partner has confirmed them. If you tell a planner a hybrid feed is no problem and the partner later says it needs another week of lead time, the planner remembers that you said no problem, not that the partner corrected it later.

Do not send the partner a brief stuffed with details that have nothing to do with the event, like unrelated contact information or internal notes about the planner's organization. Send the dates, the agenda, the room plan, the attendee range, the open questions, and the date a decision is expected.

Do not wait until the week of the event to have this conversation. AV planning tied to breakouts and remote speakers takes time to staff and test. The earlier you qualify the request, the more options the partner can actually offer.

How to practice and score it

Set up three vague AV requests and have your team turn each one into six specific questions before they would make any introduction. Score the questions on whether they reveal the actual flow of the event, whether they identify who can confirm details later, and whether they avoid handing the partner a request that is really just a copy of what the planner said.

This is the kind of scenario that works well as a rehearsed conversation rather than a checklist review, since the skill is in how you ask, not just what you ask. DealSpeak's Hospitality and Travel practice conversations include this exact scenario along with related ones, so a group sales manager can run through the planner exchange, get scored on question quality, and try it again with a tougher planner who pushes back on the delay. If your team also handles bookings made on behalf of other travelers, it is worth having them Check the Approved Process Before Booking for Another Traveler as a companion scenario, since both conversations depend on the same habit of confirming details before you act on them. Managers reviewing pace data with owners run into a similar trap, which is why it helps to Separate Booking Pace From a Forecast in an Owner Review rather than blending the two.

Where this leaves you

An AV introduction is only useful when the partner receives a brief they can actually price and staff against. Get the agenda, the room plan, and the open decisions from the planner first, and write them down in plain language before anyone else joins the conversation. The five minutes you spend asking questions saves everyone the week they would otherwise spend untangling a vague request after the fact.