Guides

What to send each vendor before an event

Vendors do not need your whole plan. They need their part of it, complete and current. Here is what that looks like for each kind of vendor, and how to keep it right when the schedule moves.

The short answer

Send each vendor five things: when and where they load in, the times that are theirs, who to call on site, what the venue expects of them, and the files they need. Leave out what is not theirs to see. Put a date on it, and send a new one whenever the schedule changes.

What every vendor needs

By vendor type

VendorSend themLeave out
CateringService times, final headcount and dietary counts, room layout, when the program needs servers off the floor, kitchen and dock accessTechnical cues, talent riders
Audio, lighting and videoThe full program for their room, set-up and rehearsal times, power and rigging details, floor plan, slides and video files, talent technical ridersClient billing details, other vendors' contracts
Band or performerArrival, load-in route, sound check, set time and length, green room, parking, who meets them, what is supplied on stageOther performers' fees and riders
TransportPick-up and drop-off times and places, passenger names and numbers, flight details for arrivals, the on-site contactThe program inside the room
Decor, florals and rentalsRoom access time, floor plan, set-up complete by, when they can strike, dock and lift detailsThe running order, beyond doors and the end time
Photo and videoThe moments that matter and when they happen, where they can stand, key people to capture, meal and break timesLoad-in details for other vendors
VenueThe whole running order, every vendor's arrival time, and who is in charge on your sideNothing. The venue should see all of it.

What to leave out, and why

A full copy of the master plan seems generous. It usually makes things worse. A caterer who gets forty rows has to find their six. And the master often carries things that should not travel: the client's personal mobile number, a performer's fee, another vendor's contract terms. Send people what they will act on.

When to send it

Send a first version once the times are firm enough to plan around, so vendors can book crew and trucks. Send again every time something of theirs changes. Send a final version shortly before the event. Teams differ on the exact timing. The rule that matters is that nobody is left holding an old version.

How to handle changes

A checklist before you send

The full set of sections is covered in what goes in a day-of packet.

Common questions

Should every vendor get the full run of show?

Usually not. The venue and the technical team need the whole program. Most other vendors need only their own times, their load-in details and one contact. A shorter document is more likely to be read.

What is a vendor timeline?

A vendor timeline is the event schedule cut down to one vendor's part: when they arrive, when they must be set, when they are needed during the event, and when they can leave.

When should I send vendors their information?

Send a first version once times are firm enough to plan crew and transport, again whenever something of theirs changes, and a final version shortly before the event. Exact timing varies by team and by vendor.

How do I stop vendors working from an old version?

Date every version, say what changed, and send the new one to everyone who had the old one. A single link that always shows the current version removes the problem.

Do vendors need to send me anything?

Often, yes. Many venues ask each vendor for a certificate of insurance before load-in, and some need vehicle or crew details for access. Ask the venue what it requires and by when, and pass that on early.

myROS is opening soon.Run of show software for event producers.
Join the waitlist