Who's the Point of Contact When Vendors Share a Shoot Day

A shoot day with catering, AV, florists, and a photo or video crew on site only runs smoothly when one person is holding the whole schedule. We show up ready to plug into that role, not to fill it.

The point of contact on a multi-vendor shoot day is whoever the client has given scheduling and space authority to, usually the client, a hired planner, or a venue manager standing in for them. It is rarely any one of the vendors on site, including us.

Who Actually Holds the Point of Contact Role on a Multi-Vendor Day

On most shoot days with catering, AV, florists, and a photo or video crew all on site, the point of contact is the client or their hired planner, not any one vendor. That person holds scheduling authority and room access decisions. We report into that role; we don't compete for it.

The role usually sits with whoever has authority over the room and the day's plan: the client, a hired event producer, a venue manager standing in for the client, or occasionally a lead vendor asked to take it on. Before a shoot with several outside vendors on site, we ask directly who holds that seat. It shapes how we plan our own coverage, because our schedule has to sit inside theirs, not run parallel to it.

When a point of contact has been named clearly, the day tends to move the way it was planned. Vendors know who to flag a delay to, who approves a last-minute room change, and who has the final say if two setups compete for the same space. We build our shot list and call time around that person's plan, routing anything that could shift the room, the light, or the schedule through them.

When no one has been named, we still ask before the day starts. It removes a category of avoidable friction: two crews working the same corner of a room, a florist rearranging a background moments before a shot. Naming the point of contact early is a planning step, and it belongs to the client or planner to answer.

What the Point of Contact Role Actually Covers

The point of contact isn't a title on a call sheet, it's a specific set of decisions: who approves a schedule change, who has final say on room access, and who each vendor is meant to flag a problem to. On a shared shoot day, those three things matter more than anyone's job title.

Scheduling authority means the point of contact can move a load-in time or tell one vendor to hold while another finishes, and everyone else follows that call. Space authority means they decide which vendor gets which part of the room at which hour, especially when catering, florals, and camera all want the same clean corner at once. Being the flag point means every vendor has one named person to raise an issue with.

We treat those three things as the actual job, separate from who is physically standing in the room the longest. A planner working from a laptop in a side office can hold every bit of that authority; a vendor who arrives first and looks busiest cannot, unless the client has actually handed them the role.

This is why a shoot can have several capable, experienced vendors on site and still run into friction. Capability isn't the same as authority. A florist can be excellent at their craft and still not be the person who should decide whether the AV team gets another ten minutes before doors. That decision belongs to whoever the client put in the role, and naming it clearly is what keeps five separate schedules from becoming five separate guesses.

Why the Photo and Video Crew Doesn't Default Into the Role

Watching the whole room isn't the same as running it. Our crew often has the clearest view of a shoot day, because coverage means paying attention to every corner, but that visibility doesn't come with the authority to redirect another vendor's setup, and we don't assume it does.

It's an easy role to slide into by accident. A camera crew notices early when a florist's ladder is blocking a sightline, or when the AV cart is about to roll through a shot we need clean, and it's tempting to just start directing the room since we're already looking at it. We flag what we see instead, because a florist or AV tech has their own schedule and their own approvals to answer to.

Staying in that lane also protects the work we're actually there to do. A crew that spends the morning managing catering's table placement or the AV team's cable routing has less attention left for coverage, and coordinating other vendors was never part of the brief we were booked against. Documentation and day-of production management are genuinely different jobs, even in the same room on the same day.

So when something needs to change on someone else's timeline, we say what we're seeing to the point of contact and let them make the call. It is a small discipline, but it is the one that keeps a shoot day from turning into five vendors each quietly trying to run the room.

How We Raise an Issue Without Managing Someone Else's Vendor

When something on another vendor's side could affect our coverage, we describe what we're seeing to the point of contact rather than instructing that vendor directly. That keeps the decision with whoever actually has authority over the room, and it keeps our note factual instead of directive.

In practice, that looks like naming the specific thing and its specific effect: a rack of AV equipment sitting where a wide shot needs to be clean, a catering cart parked in a hallway we're told is our route between rooms, a florist still working a table we understood would be finished by a certain time. We describe the conflict and what we need resolved, and we leave the how to the point of contact, because they know that vendor's constraints better than we do.

We also try to raise it early enough that it's still an easy fix. A gear cart in frame five minutes before a shot is a scramble; the same note given during setup is a quiet adjustment nobody notices happened. Timing a request matters as much as the wording of it.

What we don't do is ask another vendor's crew to move their own equipment or change their own schedule. Those questions go through the point of contact, who can weigh our need against that vendor's plan and decide what actually shifts. It's a slower path than handling it ourselves, but it respects who was actually put in charge of the day.

What a Shoot Day Looks Like Without a Named Point of Contact

Without a named point of contact, small overlaps that would normally get resolved in a text message instead get worked out on the spot, in the room, in front of a client who is trying to enjoy their own event. It rarely looks like a single dramatic conflict; it looks like a string of small, avoidable ones.

A florist might still be adjusting centerpieces when catering wants to start plating at the same tables. An AV technician might be testing sound levels during the window the photo and video crew planned to capture a quiet establishing shot. Two vendors, each following the instructions they were individually given, end up wanting the same square footage of a room at the same time, and neither one is wrong. There just isn't anyone whose job it is to sort the order.

In that gap, whoever is most confident, most present, or loudest often ends up deciding by default, and that person isn't necessarily who the client would have chosen. It can also mean vendors quietly work around each other instead of raising a conflict at all, which avoids friction in the moment but can cost the shoot the exact shot, angle, or quiet window it needed.

None of this requires anyone to have done anything wrong. Every vendor can be professional, on time, and easy to work with, and a day can still drift without a named point of contact, simply because five separate schedules were never actually stitched into one. Naming the role is what turns five independent plans into a single day that holds together.

How a Pre-Shoot Conversation Prevents This

Naming the point of contact is usually a short conversation before the day, not a formal document. We ask the client directly who holds that role, get a specific name rather than a job title, and confirm it again in writing so every vendor on the shoot has received the exact same answer well before anyone arrives on site.

This is a different conversation than the physical walkthrough of the venue. A walkthrough settles the space itself: where the light is, where a crew can set up, what the room allows. Naming the point of contact settles the people, not the space, so both conversations matter and neither one substitutes for the other. A client can walk a beautiful, well-understood room and still not have named who is running the day inside it.

We usually ask a simple, direct version of the question: if two vendors need the same corner of the room at the same time, who makes that call? The answer doesn't need to be complicated. Sometimes it's the client, reachable by phone. Sometimes it's a planner with a full run of show, or a venue manager who knows the space best. What matters is that the answer exists before the first vendor walks in.

Once that answer is confirmed, we plan our own coverage around it, building slack into our schedule at the points where other vendors' timelines are most likely to shift. A pre-shoot conversation costs a few minutes; sorting out authority live, in the room, in front of a client, costs considerably more of everyone's attention on the day itself.

How Our Approach Changes Depending on Who the Point of Contact Is

The point of contact can be the client, a hired planner, or a venue manager, and each brings a different level of availability and detail. We adjust how much we lean on them accordingly, without changing who we treat as the actual authority.

When the client is their own point of contact, they are usually reachable but not always available in the moment, since they are also the one being celebrated, photographed, or presented that day. We keep questions for them short, specific, and timed for a natural gap, rather than routing every small logistics question their way throughout the day.

When a hired planner holds the role, they typically already have a detailed run of show and expect vendors to work from it. We ask for that document ahead of time and treat it as the shared reference point, flagging only genuine conflicts rather than re-asking questions the document already answers.

When a venue manager is standing in for the client, they usually know the space and the building's own rules better than the event's specific plan. We lean on them for anything about the room itself, access, load-in routes, restricted areas, and confirm with the client or planner for anything about the event's actual content and priorities. Knowing which kind of authority we're talking to changes what we ask, even when the underlying question stays the same: who decides this?

What We Do Day-Of to Stay Coordinated Without Overstepping

Once the day starts, staying coordinated mostly means checking in at natural breaks rather than narrating every move. We confirm our next block with the point of contact when a segment wraps, so our schedule stays visibly tied to theirs instead of drifting into a private timeline of our own.

We also keep a short, specific note of anything that could affect coverage later in the day: a room that will need to be reset before a particular shot, a vendor whose setup is running long, a window that closed earlier than planned. We pass that along at the next natural check in rather than interrupting someone mid-task, which keeps the point of contact informed without adding pressure to a moment that doesn't need it.

If a genuine conflict comes up, we describe it plainly, in one sentence if possible, and let the point of contact decide. We don't editorialize about another vendor's pace or process, since we don't know their full brief or their own constraints, and it isn't our role to judge it.

By the end of the day, the goal is that the point of contact could describe our part of the schedule accurately without having had to manage us. That is what staying coordinated actually looks like from the outside: a crew that fit cleanly into someone else's plan, asked good questions at the right moments, and never needed managing of its own.