Wrangling presenters and deadlines

Presenters don’t miss deadlines because they don’t care. They miss them because your deadline is the eleventh thing on their list, behind a forecast call and a customer escalation. Your job is to make the right thing easy and the late thing visible.

The presenter timeline

The presenter timeline template turns this into fill-in dates, owners, and a status column you can share with the exec sponsor.

T-60: topic and owner

Every session gets one owner. Co-presented sessions still have a lead, and that’s who you chase.

The session brief fits on one page: the kickoff narrative in one sentence, the audience (roles, tenure, how many), the slot and its length, what attendees should do differently afterward, and the deadlines. Send the deadlines as calendar invites the same day: the outline review, the draft review, the dry run, and the onsite rehearsal. An email with dates gets read once. A meeting on the calendar gets moved, which at least means someone looked at it.

If the presenter has an executive assistant, the EA is your real point of contact. Be nice to them. Be very organized with them.

The template deck

The template deck saves your production team hours and keeps the show looking like one event instead of fourteen. Build it before T-60 and send it with the brief.

• 16:9, with master layouts: title, section break, content, big number, full-bleed image, video placeholder.
• A minimum font size. Around 24 point is a reasonable floor for body text in a big room. If it doesn’t fit, it’s two slides.
• Video as separate files, not links to a streaming site. The show machine may not be online, and it shouldn’t need to be.
• No live demos without a recorded backup. Logging into a system on stage, on venue Wi-Fi, with 400 people watching, is a bold choice.
• Simple builds only. Complex animations break between machines.
• A file naming rule. Something like D1-0930-CRO-Keynote-v4, so the operator never has to guess which file is current.

The exec who sends slides at midnight

It will happen. Plan for it instead of being surprised by it.

Write it for them. For senior execs, swap “send me a draft” for “give me 20 minutes.” Interview them around T-45, build the outline and first draft yourself or with the comms team, and let them react. Most execs edit faster than they write.

Make the EA the deadline owner. Put the review sessions on the exec’s calendar, not just in their inbox.

Don’t argue at midnight. Acknowledge the file and triage it in the morning. Is it a fix (a number, a name, a typo) or a rewrite? Fixes go in under the freeze rules below. A rewrite goes to the exec sponsor with one question: is this change worth the risk of a new, unrehearsed deck in front of the whole revenue org? Sometimes the answer is yes. Then you take the new numbers and leave the rest.

One door for files. Every deck goes to one inbox or one shared folder, owned by one person. Nobody emails a file to the playback operator directly, and the version on the show machine is the version.

Field note: The exec who sends slides at midnight usually isn’t being difficult. They finally had time to think. Put that thinking time on their calendar at T-45, and the midnight email gets a lot rarer.

The slide freeze rule

At T-7, decks lock. Production needs that week to load files into playback, check fonts and video, build transitions, write cues into the run of show, and prepare confidence monitor notes. The run of show guide covers how those cues come together.

After lock, a change goes in only if it’s one of these:

1. A factual error. A wrong number, a wrong name, an old org chart.
2. Late data that was always going to be late. Final fiscal-year results, award winners, the quota number that’s still being approved. Build placeholder slides for these at T-30 so the late swap is one slide, not a new deck.
3. A legal or compliance change.

Everything else waits until next year. Every approved change goes through one person, usually the show producer or content lead, and gets logged with the time and the new version number. Even approved changes stop at a set time the night before each show day, so the operator isn’t loading files during walk-in.

Speaker notes and confidence monitors

Confidence monitors are the screens on the stage floor facing the presenter. They usually show the current slide, the next slide, the speaker notes, and a countdown clock.

• Notes are prompts, not a script. Short bullets in large type. A presenter who needs a full script should use a teleprompter and rehearse with it, because reading well from a prompter is its own skill.
• Agree on the clock. Presenters should know what the countdown means and what happens at zero. Usually that’s a “wrap” signal from the stage manager, and then their walk-off music.
• One clicker, tested. The presenter never touches the laptop. If the clicker fails, “next slide, please” is fine and nobody remembers it.
• Don’t read the slides. If it’s on the slide, they don’t need to say it. If they need to say it, it may not belong on the slide.

Rehearsal etiquette

Give each presenter a rehearsal slot about the length of their session plus ten minutes, and ask them to respect it:

• Show up on time. Rehearsal slots are back to back. A late CRO pushes every presenter after them.
• Run it at show speed, in full voice. Audio needs real levels, and the timer only means something if the pace is real.
• Dress for the mic. A lavalier pack needs a waistband or belt. Tell presenters that before they pick an outfit.
• Walk the stage. Where they enter, where they stand, where they exit, and who hands off to whom.
• Rehearsal is not a writing session. Edits get noted and triaged under the freeze rule, not typed in on the tech table.
• Thank the crew. They’re about to make everyone look good.

The CRO can help here by rehearsing first and on time. Nothing sets the tone for the other presenters faster. If you’re still building the agenda around these slots, the three-day kickoff agenda has the session lengths.

A good presenter on a locked deck beats a brilliant one still editing at walk-in.