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
- Where and when. The venue address, the room and its level, the date, and their own arrival time.
- Load-in details. Which dock or door, the route to the room, lift or stairs, where to park, and when the dock is available.
- Their times. Only the items they are part of: set-up complete by, sound check, service, their set, strike.
- One on-site contact. A name and mobile number for the person who can answer questions on the day.
- Venue rules that affect them. Access hours, power, noise limits, anything they must bring or may not bring.
- Load-out. When they can start, and when they must be clear.
By vendor type
| Vendor | Send them | Leave out |
|---|---|---|
| Catering | Service times, final headcount and dietary counts, room layout, when the program needs servers off the floor, kitchen and dock access | Technical cues, talent riders |
| Audio, lighting and video | The full program for their room, set-up and rehearsal times, power and rigging details, floor plan, slides and video files, talent technical riders | Client billing details, other vendors' contracts |
| Band or performer | Arrival, load-in route, sound check, set time and length, green room, parking, who meets them, what is supplied on stage | Other performers' fees and riders |
| Transport | Pick-up and drop-off times and places, passenger names and numbers, flight details for arrivals, the on-site contact | The program inside the room |
| Decor, florals and rentals | Room access time, floor plan, set-up complete by, when they can strike, dock and lift details | The running order, beyond doors and the end time |
| Photo and video | The moments that matter and when they happen, where they can stand, key people to capture, meal and break times | Load-in details for other vendors |
| Venue | The whole running order, every vendor's arrival time, and who is in charge on your side | Nothing. 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
- Date every version at the top, and say what changed.
- When a time moves, work out who it touches. Doors moving half an hour changes load-in for almost everyone.
- Send the new version to everyone who had the old one, not only the people you think are affected.
- A link that always shows the current version avoids the problem. A PDF is fixed the moment you send it.
A checklist before you send
- Is the address complete, with the room and level?
- Does it say which dock or door, and where to park?
- Is there one named contact with a mobile number?
- Are the times only the ones this vendor needs?
- Do the times match the current running order and the venue's order?
- Is anything private in there that this vendor should not see?
- Is the date on it?
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.