What goes in a day-of packet
A day-of packet is what you hand each crew member, vendor and performer so they can do their part on event day without calling you.
What a day-of packet is
On event day the producer is the person everyone calls. Where do I load in? What time am I on? Which door? Who has the room key? A day-of packet answers those before they are asked.
It is not one document. It is the same show, cut differently for each group of people. The crew's version, the caterer's version and the keynote speaker's version share a venue and a date and not much else.
You will hear it called other things depending on who you work with: a call sheet, a production book, a show packet, an event brief, a day sheet. Hotels and meeting planners may know a related document as the event specifications guide or resume. The names differ. The job is the same.
The pages everyone gets
Whatever the audience, the first page should carry these:
- Event, date, venue. With the client or host named.
- Version and time. When this copy was last updated, and who to ask about it.
- One show contact. A name and a mobile number that will be answered on the day. If people read nothing else, they read this.
- The exact way in. Street address, which entrance or dock, where to park, and the route to the room. Venues have many doors, and people go to the wrong one unless you name the right one.
- Key times. Load-in, doors, show start, show end, load-out, and any curfew.
- Safety. The nearest hospital, who the first aider is, the emergency meeting point, and anything specific such as protective equipment or work at height.
What each audience gets
Crew
- Their row on the call sheet: name, role, company, call time, where to report, and wrap.
- Department calls, if departments start at different times.
- The production schedule for the day, and the full run of show.
- Radio channels and who is on which.
- Meals: when, where, and whether they are provided.
- Dress.
A note on call time. On most crews it means in the room and ready to work, not pulling into the car park. Say which you mean.
Vendors
- Their dock or entrance, and their slot if the dock is booked by time.
- What the venue needs from them in advance, such as vehicle details or a certificate of insurance.
- The load path: dock height, freight elevator size, the distance to the room.
- Power, water or anything else they asked for, and where it is.
- Their part of the schedule: arrival, setup complete, service or performance times, and when they can strike.
- Venue rules that affect them.
- Who to call, by name.
Talent and speakers
- Arrival time and where to arrive. Who meets them.
- Green room or holding area.
- Rehearsal or sound check slot.
- Their time on stage, how they enter, and what microphone they will have.
- How their slides or tracks get to the crew, and by when.
- When they are free to leave.
The venue
Your venue contact generally wants everything, because they are the one who gets asked when you cannot be found. Send them the full schedule, and check it against their banquet event order line by line. Their kitchen and banquet staff work from the BEO, not from your packet.
The client
A shorter view: the guest-facing times, where they need to be and when, who to find on site, and nothing about dock heights.
What to leave out
The caterer's packet is not the AV team's packet. A vendor does not need the client's mobile number, the talent's contract rider or anyone's fee. A performer does not need the catering load-in.
Sending everyone everything feels safe, but it buries the one line each person needs, and it passes on details that were not yours to share. Start each version from what that reader has to do, then add only what helps them do it. Then read it once as that person and ask whether there is anything in it they should not see.
Where the information comes from: advancing
A packet is only as good as the answers in it, and those come from advancing the show. Advancing is the work of confirming every detail with the venue and each vendor before anyone arrives. Touring productions treat it as a job of its own and start weeks ahead. One-off events need the same conversation, even if nobody calls it that.
With the venue, confirm:
- Dock location, hours and how slots are booked.
- Freight elevator size and whether it is shared.
- Parking for trucks and crew.
- Power available in the room, and where.
- Rigging: who is allowed to do it, and how much notice they need.
- Sound limits and curfew.
- Access hours, and who opens the room.
With performers, ask for three things. The technical rider lists what the act needs. The stage plot is a drawing of where people, instruments and monitors go. The input list is the numbered list of what plugs into the sound system. Get the current versions. An old rider that is still in circulation is a classic source of a bad afternoon.
The venue's documents and rules
Your packet has to agree with paperwork you did not write.
The BEO. If your run of show says dinner is served at 6:55 and the BEO says 6:30, the kitchen will plate at 6:30.
Production guidelines. Many hotels and convention centres publish rules for outside production companies: how the dock is booked, which services only the in-house team may provide, how far ahead they need your schedule. Ask for them early. At a convention centre, trucks may have to report to a marshalling yard and wait to be called to the dock.
Labor rules. If the venue uses union stagehands, the working rules shape your schedule: minimum call lengths, when a meal break is due, what happens if it is missed, and when overtime starts. There is no single national rule. Terms are set by each local's agreement and each venue's rate card, and they differ from city to city and building to building. Many venues are not union at all. Do not copy another city's rule into your schedule. Ask the venue or the labor provider for the rules that apply to your dates, and build crew meals and call times around them.
When to send it, and how to reissue
- About a week out, send a preliminary version for anything large, so people can plan travel and flag problems.
- The day before, send the final. That is the usual minimum for crew. Some groups expect longer: wedding vendors often want the timeline a week or two ahead.
- One per day on a multi-day event.
- When something changes, say what changed in the first line. A new file with no note makes people compare two documents to find the difference, and most will not.
- For a change that matters, ask people to confirm they have seen it.
The classic failure is a second, unlabelled PDF in circulation. Keep one current version, say where it lives, and put the version time on page one so anyone can tell at a glance which copy they are holding.
Print or phone
People disagree about this, and both sides have a point. A shared live document means everyone sees the same version. Paper does not run out of battery, and ballrooms and loading docks are full of dead spots. Experienced stage managers often keep a printed copy for exactly that reason.
The safe answer is both: one live version that is the source of truth, and a printed copy of the pages each person cannot work without. If you print, the version time on page one is what stops an old printout from becoming a problem.
A quick check before you send
- Is there one phone number on page one that will be answered on event day?
- Does every time match the current run of show, and the BEO?
- Could this reader find the right door without calling anyone?
- Is the on-site contact the person who will really be on site?
- Is there anything in here this reader should not see?
How myROS builds it
In myROS the packet is built from the show. Contacts, site information, load-in, set times, talent and files come from what you already entered. You tick sections in or out for each audience, choose the exact people, times and files, and add your own notes. Because the packet is built from the run of show, a time you change there is the time the packet shows.
Common questions
What is an event call sheet?
A one-day document listing who is working, their role and company, when and where they report, and key contacts. It is usually part of the day-of packet for crew.
When should I send the day-of packet?
For crew, the day before at the latest, with a preliminary version about a week out for large events. Vendors and wedding suppliers often expect it earlier.
What is the difference between a call sheet and a run of show?
A call sheet says who reports where and when. A run of show says what happens during the event, item by item.
What does call time mean?
On most crews, the time you are in the room and ready to work, not the time you arrive at the venue. Say which you mean on the sheet.
What is a BEO and who writes it?
A banquet event order is the venue's document covering room setup and food and beverage service. The venue's catering or event manager writes it and both sides sign it.
What is a day sheet?
A touring term for one day's schedule and logistics for the travelling party: travel, venue, load-in, sound check, doors, set time and hotel.
What does advancing a show mean?
Confirming every detail with the venue and vendors before arrival: dock, power, rigging, schedule, hospitality and contacts.
Is a production book the same thing?
Close. A production book usually means the full binder for the whole event. A day-of packet is the part of it each person needs on the day.