Product Launch Run Sheet: How to Coordinate Every Moving Part

A product launch is one of the highest-stakes events a company runs. The timeline is tight, the audience includes press and investors, and the moment the CEO steps on stage is not the time to discover your AV team doesn't have the right connector cable.

A product launch run sheet is what prevents that. It's the master document that coordinates every department — marketing, PR, production, logistics, and executive comms — around a single, agreed timeline. This guide covers what to put in yours, how to structure it, and the details that experienced launch coordinators swear by.

What Makes a Product Launch Run Sheet Different

Most event run sheets coordinate a venue and a program. A product launch run sheet coordinates an entire organisation.

Your launch might span a live venue event, a simultaneous livestream, a press embargo lifting at a specific time, social media posts going out in sequence, and a sales team activating the moment the product goes public. Each of those has its own timeline, its own lead, and its own set of dependencies.

The run sheet is the document that makes all of that happen at the right moment — or flags in advance when something is going to clash.

The Two Documents You Actually Need

Before building your run sheet, it helps to understand there are really two documents at play:

1. The Master Run Sheet — the full internal document covering everything from setup through to post-event. This is what your event coordinator and department leads use.

2. The Day-of Run Sheet — a condensed version of just the live event timeline. This is what goes to the venue crew, the MC, the AV team, and the security staff on the day.

Build the master first. Distil the day-of version from it.

What to Include in a Product Launch Run Sheet

Pre-Event: T-minus 4 Weeks to Launch Day

Your run sheet should capture key milestones leading into the event, not just the day-of timeline. Include:

Press embargo confirmation — date, time, and which outlets are under embargo
Asset delivery deadlines — when video, slide decks, product imagery, and demos need to be locked
Venue setup window — when your team has access and what needs to happen in that window
Speaker rehearsals — times, location, who needs to be there
Technical rehearsal — full run-through with AV, lighting, and livestream crew
Guest list finalisation — when RSVPs close, who manages the door list

These milestones don't need to be in the same format as your day-of timeline, but they should be in the same document so nothing slips through the cracks between planning and execution.

Venue Setup (Day Before or Morning Of)

Specify what needs to happen, in what order, and who owns each item:

AV and staging setup — display screens, microphones, camera positions, confidence monitors
Livestream and streaming platform setup — test stream, backup stream, stream key confirmed with platform
Product display and demo stations — physical product placement, demo devices charged and configured
Signage and branding — backdrop, directional signage, registration desk branding
Press check-in area — dedicated registration lane, press kits, embargo reminder cards
Catering setup — arrival time, layout, dietary requirements confirmed
Green room setup — for speakers and executives, with run of show and water

Guest and Press Arrival (T-minus 60 to 0 Minutes)

This window is often underplanned. Include:

Doors open time — and who confirms the venue is ready before doors open
Registration team briefing — who manages the list, what to do with walk-ins, VIP protocol
Press arrival window — when photography and video crews arrive, where they go
Embargo reminder — who communicates the embargo lift time to press on arrival
Executive pre-brief — final briefing with the CEO or keynote speaker (15 minutes before program)
AV final check — slides loaded, microphones tested, livestream active

Live Program

This is the most detailed section of your run sheet. For every segment, specify:

Start time and end time
Who is on stage
What is happening (speech, demo, video, Q&A)
AV cue (slide deck advance, video play, lighting change)
What happens immediately after (transition, next speaker intro, break)

Build in realistic durations. Applause, technical pauses, and speakers who go long are all predictable — plan for them.

Tip: Add a "hard stop" time to your run sheet. If you have media commitments, a venue curfew, or a livestream window, every speaker and MC needs to know the program cannot overrun.

Press Embargo Lift

If your launch involves a press embargo, the moment it lifts needs to be a named event in your run sheet:

Exact time — to the minute
Who notifies the PR team that the embargo has lifted
Who sends the notification to press (automated or manual)
Social media post scheduling — confirmed live at the same moment
Website product page going live — who confirms this is done and when

This is often a cross-team dependency that falls through the gaps if it's not explicitly owned.

Post-Announcement Segment

After the keynote or main reveal, most launches have a hands-on or networking period:

Demo station opening — who manages each station, how many staff per station
Press interview window — where do press interviews happen, who manages the queue, which executives are available
Product photography — when and where press photography is permitted
Social media team — where they're positioned, what they're capturing, when posts go out

Event Close and Pack-Down

Official close time — and who communicates it to guests
Equipment and product retrieval — demo devices, display units, branded materials
Press kit follow-up — who sends the press release and assets to any press who couldn't attend
Venue handover — who signs off with the venue manager
Internal debrief — even a 20-minute call the same day captures things while they're fresh

Sample Product Launch Run Sheet Timeline

Time	Activity	Lead	Notes
8:00 AM	Venue access — setup begins	Production Manager	AV crew on-site
9:00 AM	Livestream test stream	AV Lead	Confirm with streaming platform
10:00 AM	Demo stations configured and tested	Product Team	All devices charged, accounts logged in
11:00 AM	Speaker rehearsal — full run-through	Event Coordinator	All AV cues rehearsed
12:00 PM	Lunch break — crew	Event Coordinator	Stagger so venue is never unattended
1:00 PM	Press kit and registration desk ready	PR Lead	Embargo reminder cards at desk
1:30 PM	Doors open — guest registration begins	Registration Team	VIP lane active
1:30 PM	Press arrives — dedicated check-in	PR Lead	Confirm embargo lift time with all press
2:15 PM	Executive pre-brief	CEO + Event Coordinator	Green room, 15 minutes
2:25 PM	AV final check — slides, mics, livestream	AV Lead
2:30 PM	Program begins — MC opens	MC	Welcome, housekeeping
2:35 PM	CEO keynote	CEO	20 mins. Slides deck A. Hard stop 2:55 PM
2:55 PM	Product reveal segment	Product Lead	Video plays, then live demo
3:10 PM	Guest Q&A	MC + CEO	10 mins max
3:20 PM	Press embargo lifts	PR Lead	Social posts live, website page live
3:20 PM	Program close — MC outro	MC	Direct guests to demo stations
3:25 PM	Demo stations open	Product Team	Press photography permitted
3:25 PM	Press interviews begin	PR Lead	Green room interviews, 10 mins each
4:30 PM	Official event close	Event Coordinator	Thank guests, venue pack-down begins
5:30 PM	Venue handover	Production Manager	All equipment and product retrieved
6:00 PM	Internal debrief call	Event Coordinator	20 mins — all department leads

Roles to Name in Your Run Sheet

For a product launch, the run sheet needs a named person against every role below. If a role is unmanned, the task doesn't happen:

Event Coordinator — owns the run sheet, makes real-time calls
MC — runs the stage program, keeps time
AV Lead — manages all technical cues, livestream, and on-site tech
PR Lead — manages press arrival, embargo, interviews, and follow-up
Product Team Lead — manages demo stations and product handling
Executive Liaison — the person whose job it is to look after the CEO or keynote speaker
Social Media Lead — captures and publishes content from the event
Registration Manager — owns the door list and guest experience on arrival
Production Manager — venue, logistics, catering, and pack-down

Common Product Launch Run Sheet Mistakes

Forgetting the embargo in the timeline. The embargo lift is one of the most time-sensitive moments in a product launch, and it often lives in a separate PR document rather than the main run sheet. Put it in both.

Not assigning an executive handler. Executives are focused on their presentation, not the clock. Someone needs to be responsible for getting them to the right place at the right time — and that role needs to be in the run sheet.

No hard stop on the keynote. Speakers run long. Without a hard stop time written into the run sheet and communicated in the rehearsal, your Q&A gets cut, your demo window shrinks, and your press embargo might lift before the keynote is done.

Treating the livestream as an afterthought. If you're streaming, the livestream audience is part of your event. They need to be in the run sheet — from stream start time, to what happens if the feed drops, to who monitors the comments or live chat.

No plan for the demo station period. The post-announcement period often runs on vibes. Plan how many staff are at each station, what the demo script is, and how press interviews are queued.

Pre-Launch Checklist to Include in Your Run Sheet

Add a pre-event checklist section that your team works through in the 48 hours before the event:

Building Your Run Sheet: Format Tips

Product launch run sheets tend to be longer and more cross-functional than most event run sheets. A few formatting choices make them easier to use:

Use colour coding by department. AV cues in one colour, PR in another, product team in another. At a glance, each lead can spot their moments without reading every line.

Include a "dependencies" column. Some moments require a prior action to be complete. Make those dependencies visible: "Livestream goes live — requires tech rehearsal sign-off from AV Lead."

Keep a short front-page summary. The full run sheet might be 4–5 pages. A one-page summary of key times (doors open, program start, embargo lift, close) means everyone can quickly answer the basic questions without scrolling.

Version control it. A product launch run sheet gets updated constantly in the week before the event. Put a version number and date at the top of every copy, and send a "final" version explicitly named as such.

Wrapping Up

A product launch is too important — and too cross-functional — to coordinate through scattered emails and Slack messages. Your run sheet is the document that brings every department onto the same page, with the same timeline, and the same understanding of who owns what.

Build it early, rehearse against it, and update it relentlessly. The version you use on launch day should be the result of dozens of small improvements, not something assembled the night before.

Need a run sheet that's built for complex, multi-team events? Run Sheets gives you a shareable, real-time run sheet that your whole team can work from — whether they're backstage, at the demo stations, or on the livestream. Get started free →