Analyst Day Run of Show: Roles, Timing, and Backup Plans

Why Analyst Days Fail on Execution, Not Content

Most post-mortems on a disappointing Analyst Day point to the wrong culprit. Teams blame the strategy slide, the guidance language, or a CFO who seemed flat. The actual failure usually happened three hours earlier, when the Q&A block ran long, the webcast froze during the CEO’s opening, or nobody knew who was supposed to cue the product demo video. A run of show is a minute-by-minute execution plan for the day, distinct from the high-level agenda investors see in the invite, and it is the document that determines whether your narrative lands or gets swallowed by chaos (Events.com, 2025; Guidebook).

IR teams spend months building the story: the strategic inflection point, the margin bridge, the roadmap. That work gets undone in real time by operational gaps that were entirely foreseeable. This article treats the run of show as an operations document with the same rigor as a financial model, complete with owners, timers, and pre-built contingencies for the failure points that show up on nearly every Analyst Day.

Setting Your Timing Norms: In-Person vs. Virtual vs. Hybrid

Industry benchmarks put in-person Analyst Days at roughly 3 to 3.5 hours (longer with a facility tour), traditional in-person investor days at 4 to 5 hours, and virtual formats at approximately 2.5 hours, since remote audiences disengage faster and attention drops off during longer streams (ICR, 2022; Q4/InvestorRelations.com, 2020; WeConvene, 2025).

The instinct to port an in-person agenda directly onto a webcast is the single most common timing mistake IR teams make. A 4-hour in-person day with a facility tour and networking reception has no virtual equivalent, and trying to force one produces exactly the drop-off WeConvene flags in its 2025 research. If your day is hybrid, build the virtual feed as its own shorter, tighter track rather than a webcast bolted onto the in-person run of show.

The Run-of-Show Backbone: A Proven Sequencing Model

A defensible narrative structure for the day moves the CEO’s strategic setup into CFO financials, then COO operational metrics, a product demo, customer or partner voice, a 12 to 24 month roadmap with trackable milestones, and finally extended Q&A that surfaces and addresses analyst skepticism directly (WeConvene, 2025). This sequence builds an argument rather than presenting a list of updates.

Each segment needs 20 to 30 minutes to build the narrative around its key message, and every agenda item should carry a specific time allocation and running order rather than a loose “morning session” label (OpenExchange, 2025). Convene’s planning guidance adds a practical constraint: limit slide counts and keep speeches tight, because slide-heavy segments are the most common source of overrun (Convene, 2018).

The sequencing matters because each segment sets up the next one’s credibility. If the CFO section runs 12 minutes over, the product demo gets rushed, and the customer panel, the part of the day analysts often find most persuasive, gets cut short or dropped entirely. Protecting the sequence protects the argument.

Assigning Roles: Who Owns What On (and Off) Stage

Every task on the day needs a named owner, not a department. Events.com’s run-of-show framework calls for a defined IR lead, MC, timekeeper, AV lead, webcast operator, and floor managers, each with a specific responsibility and a designated backup in case that person is unreachable when a decision needs to happen fast (Events.com, 2025).

Backstage roles matter as much as onstage ones. A timekeeper who can flash a two-minute warning card to a CFO mid-answer is often the difference between a Q&A block that ends on schedule and one that eats into the roadmap segment. ICR’s guidance also recommends using the day to showcase bench strength, non-typical investor-facing leaders who can field questions, and running Reg FD training for every presenter beforehand so nobody improvises language that creates disclosure risk (ICR, 2022).

The Pre-Event Timeline: Materials Lock, Rehearsals, and Sign-Off

Lock final materials 72 hours before the event. Any change after that point should require CFO and Legal sign-off plus an entry in a change log, and the master deck should live in a single restricted folder so nobody is presenting from an outdated version (WeConvene, 2025). This single rule eliminates the most common day-of scramble: a slide that was “fixed” the night before but never made it into the AV operator’s file.

Rehearsal cadence should be non-negotiable. Q4 recommends at least two full rehearsals for virtual events, including one on the actual live platform testing speaker transitions, slide control, and mock Q&A (Q4/InvestorRelations.com, 2020). WeConvene’s research points to a full dress rehearsal 48 hours out with every speaker, all AV, and full timing, recorded so presenters can get feedback on pacing and body language (WeConvene, 2025). OpenExchange similarly recommends a full-dress rehearsal the day before on the same AV and platform the team will use live, specifically to confirm timing and technical performance (OpenExchange, 2025).

Guidebook’s run-of-show framework adds a step teams often skip: read the entire run of show aloud, minute by minute, with all key players in the room, and hold a pre-event briefing 30 minutes before doors open with every backstage and onstage team present (Guidebook). That 30-minute huddle is where you catch the gaps a written document can’t surface, like two people both assuming the other owns the customer panel introduction.

Q&A Architecture: How Much, Where, and Who Fields What

Q&A should account for 30 to 40 percent of total event time, not get squeezed into whatever minutes remain at the end (Q4/InvestorRelations.com, 2020; OpenExchange, 2025). ICR’s model breaks the day into three or four content segments with roughly 10 minutes of Q&A after each, plus a dedicated 30 to 40 minute Q&A block at the close of the program (ICR, 2022).

Decide in advance who fields questions on which topics. OpenExchange recommends mapping specific executives to specific subject areas before the day starts, so a margin question doesn’t get fumbled to the product lead or a technical roadmap question doesn’t land on the CFO (OpenExchange, 2025). This mapping should live in the run of show itself, not in a separate briefing doc that the timekeeper and MC never see.

Distributed Q&A throughout the day, rather than one large block at the end, also protects against the scenario where a strong opening runs slightly over and the final Q&A gets cut to five minutes. Segment-level Q&A gives analysts multiple chances to engage and gives your team multiple recovery points if timing drifts.

Backup and Contingency Planning: Building the “If This, Then That” Playbook

The three highest-probability failure points on an Analyst Day are AV equipment, the webcast feed, and Q&A overrun. Each one has a specific, pre-wired response that should be written into the run of show, not improvised live.

For in-person events, that means backup projectors, backup microphones, and backup Wi-Fi hotspots on hand before doors open (WeConvene, 2025). For virtual and hybrid events, test every video link 60 minutes before start time and have a secondary Zoom, Teams, or Webex link ready to activate if the primary platform fails (WeConvene, 2025). Q4 also recommends pre-recording segments where feasible, since a pre-recorded product demo removes one live technical dependency from the riskiest part of the program (Q4/InvestorRelations.com, 2020).

None of these responses require debate in the moment. That’s the point: a contingency plan decided under pressure, in front of forty analysts, is a plan you’ve already lost control of.

From Static Agenda to Living Document: Building Your Run-of-Show Template

Build the run of show in layers: gather event details first (date, location or platform, segments, speakers, AV and tech needs), map the timeline in coarse blocks, then break those blocks into minute-by-minute detail including buffer periods and transitions, assign a named owner to every task, and integrate technical cues like slide-change prompts and video roll-in timing directly into the document (Events.com, 2025). A consistent template used across every Analyst Day lets your team read and execute it quickly instead of relearning a new format each cycle (Guidebook).

Treat this template as a living document that updates after every event, not a file you rebuild from scratch each year. Note where segments actually ran over, which contingency triggered, and who covered which role, then fold those notes into the next cycle’s template.