How to Make an Event Run Sheet (Run of Show Guide + Example)

How do you make an event run sheet? List every moment of the event in time order, from load-in to venue clear. For each row, write the start time, what happens, who owns it, the technical cue (mic, slide, music, lights), and any notes. Put the key contacts at the top and the prep checklists before the timeline. Then walk through it with every owner before the day, and print it.

A run sheet (also called a run of show) is the one document everyone on your crew works from on the day. The AV lead reads it for cues. The caterer reads it for service times. The host reads it to know when to walk on stage. If it is clear, people act without asking you. If it is vague, your phone rings all day.

This guide covers what to put in a run sheet, how to lay it out, a worked example, and the mistakes that cause problems on the day. If you want a filled-in starting point, our event run sheet template has the full structure for a hybrid product launch.

Run sheet vs. run of show vs. agenda

People use these words loosely, so it helps to separate them:

Document	Who reads it	What it shows
Agenda	Guests	Session titles and rough times. No backstage detail.
Run of show	Stage and AV crew	Segment-by-segment cues: mics, slides, video, lights, music.
Run sheet	Whole event team	The full day: load-in, setup, the show, catering, teardown, owners, and contacts.

In practice, many teams use "run sheet" and "run of show" for the same thing. For a stage-heavy show with many technical cues, a separate run of show template keeps the AV detail in one place. For most corporate events, one run sheet that includes the cues is enough.

What to include in an event run sheet

A good run sheet has more than the timeline. These are the parts that do the most work.

1. Event overview

One block at the top with the event name, date, venue, expected headcount, and format (in person, virtual, or hybrid). Anyone who picks up the sheet should know what event it is in five seconds.

2. Key day-of contacts

The four or five people who make decisions on the day, with role and mobile number. Put this on the first page. When something breaks, nobody should have to search for a phone number.

3. Pre-event checklists

Group the prep tasks by time: one week out, the day before, and the morning of. Give each task an owner. Typical items are final headcount to catering, decks sent to AV, badges printed, a tech rehearsal, and a venue walk-through.

4. The master timeline

This is the core table. Use these columns:

• Time — the hard start time for the row.
• Item — what happens, with the speaker name and duration.
• Owner — one named person, not a team.
• Cue — the technical action: "mic 2 live", "play video", "music fade to 15%".
• Notes — backups, signals, and dependencies.

5. Vendor contacts

For each vendor: company, contact name, phone, email, arrival time, and exactly what they are responsible for. The scope line matters. It settles "is that your job or mine?" before the day.

6. Post-event checklist

Recording sent to attendees, thank-you emails, survey, final invoices, budget actuals, lost and found, and a debrief meeting. Without this list, the follow-up slips by a week.

Our run sheet layout includes all six parts, with owner tags on every checklist item and a highlighted row for critical moments such as a live demo.

How to make a run sheet, step by step

1. Fix the hard times first. Doors, the keynote, meal service, and venue close are usually set by contracts. Write them down before anything else.
2. Work backward to load-in. Ask each vendor how long setup takes. Add a buffer to their answer. Load-in is the first row of your timeline.
3. Fill the show segments. Add each talk, panel, or performance with its duration. Check that durations add up to the gaps between your hard times.
4. Add transitions as their own rows. Moving 150 people from a hall to a dining room takes time. Give changeovers, seating, and room moves their own rows.
5. Assign one owner per row. If two people share a row, write who leads. "Team" is not an owner.
6. Write the cues. Go through each row with your AV lead and add the exact technical action. Use the same words they use.
7. Add backups for the risky moments. Live demos, remote speakers, and outdoor segments need a written fallback in the notes column.
8. Review with every owner. Send the draft out at least a few days before, then walk through it in a short call. Owners will catch times that do not work.
9. Lock a version and print it. Put a version number or date in the footer. Print enough copies for every owner, plus spares at the registration desk.

Worked example: a 150-person charity dinner

This is an example only. The names and times are made up to show the format.

The Riverside Food Bank is holding an evening fundraiser at a hotel ballroom. Doors open at 6:00pm, and the hotel needs the room clear by 11:30pm. The event lead is Maya Chen. The AV lead is Sam Ortiz.

Time	Item	Owner	Cue	Notes
2:00pm	Load-in: AV, stage, auction tables	Sam	House lights on	Loading dock only. Freight lift booked 2:00–4:00pm.
4:30pm	Sound check and slide check	Sam	All mics live	Host and speakers arrive by 4:45pm.
5:30pm	Registration desk ready	Maya	Background music 20%	Name cards alphabetical. Card reader charged.
6:00pm	Doors open, drinks reception	Maya	Music 30%	Silent auction opens.
7:00pm	Guests seated	Maya	Music fade to 10%	Signal to Sam when most seats are full.
7:10pm	Welcome from host, 8 min	Host: Leo Grant	Mic 1, title slide	—
7:20pm	Dinner service, first course	Hotel banquet captain	Music 20%	Dietary meals flagged on place cards.
8:15pm	Impact video, 3 min	Sam	Play video 1	Backup file on USB at AV desk.
8:20pm	Director's speech, 10 min	Ana Ruiz	Mic 2, slides 2–8	—
8:35pm	Live auction, 30 min	Auctioneer	Mic 3, lot slides	Spotter at each side of room.
9:10pm	Silent auction closes	Maya	Announcement on Mic 1	Volunteers collect bid sheets.
9:30pm	Dessert and dancing	Band	Band takes stage	Band contract ends 11:00pm.
11:00pm	Event ends	Maya	House lights up	Winners collect items at desk.
11:30pm	Room clear	Maya	—	Final walk with hotel manager.

Notice the details that make it useful. Every row has one owner. The video has a backup. The auction close has its own row, because volunteers need a fixed time to collect bid sheets. The last row is the venue deadline, not the end of the party.

Format and length

• Length. A small meeting may need one page. A full-day conference with breakouts can run to five or six pages. Length follows complexity. Keep the timeline itself as tight as you can.
• Orientation. Portrait works for most events. Use landscape if you have many columns, such as separate cues for lights, audio, and video.
• Type size. Use a size people can read while walking in a dim room. Bold the times.
• Highlight critical rows. Shade or mark the moments that cannot slip, such as a live stream start or a hard venue close.
• Footer. Add the event name, date, and version number on every page.
• Print and digital. Share a PDF so the layout does not change on phones, and bring paper copies. Wi-Fi at venues often fails.

Our guide on how to design a professional PDF covers type, spacing, and tables in more detail.

Common mistakes

• No buffer time. Speakers run long. Doors open late. Add a few minutes between segments, and more around meals and room changes.
• Shared ownership. "AV team" or "everyone" means nobody checks. Name one person.
• Cues written in your words, not the crew's. If the AV lead calls it "Mic 3", do not write "the handheld one".
• Only the show is listed. Load-in, catering service, and teardown cause as many problems as the stage does.
• No fallback for risky segments. Remote speakers and live demos fail. Write the backup plan into the row.
• Several versions in circulation. Number each version and tell owners when you change it.
• Missing contacts. A run sheet without phone numbers forces people to find you for every small issue.

Make your run sheet with BuildPDFs

BuildPDFs drafts the full document for you. Describe the event: date, venue, headcount, the segments, and who owns what. The AI document generator writes the run sheet on our template, with the contact block, checklists, timeline table, vendor list, and post-event tasks. You edit any row in plain language and export a print-ready PDF. For more event layouts, browse all planner and event templates.

FAQ

What is the difference between a run sheet and a timeline?

A timeline lists when things happen. A run sheet adds who owns each moment, the technical cues, and the notes needed to act. For weddings, a wedding day timeline is often shared with guests and family, while the run sheet stays with the vendors and coordinator.

Who should get a copy of the run sheet?

Everyone who owns a row: the event lead, AV, catering, venue staff, host, speakers, and key volunteers. Guests get the agenda, not the run sheet.

How early should I finish the run sheet?

Have a full draft ready a week or two before the event, so vendors can check it. Lock the final version a day or two before, after the last rehearsal or walk-through.

Should a run sheet include budget details?

Usually not. Keep costs in a separate budget or event proposal. The run sheet is for the people working on the day, and many of them do not need to see prices.