A risk register is not a contingency line item buried in the AV budget. It is a shared document — owned by events, signed off by marketing, and built with your production partner — that names what can fail, who decides when it does, and what you funded to prevent it. Corporate shows fail in predictable ways: schedule drift, single-path switching, wireless gaps, stream delay, content capture that marketing cannot use. This guide shows how to build a register before you sign the PO, use it on show day, and update it after load-out so next year's budget reflects what actually broke — or almost did.
Why executives should require a register before the PO
Leadership does not need a technical runbook. They need proof that someone mapped failure modes against business outcomes and assigned owners before the ballroom fills. A register turns "we hope nothing goes wrong" into a decision log finance can follow: what you chose to mitigate, what you accepted, and who has authority when the CEO segment runs ten minutes long.
Without a register, risk conversations happen in hallways after the failure — when marketing is explaining why the internal broadcast looked amateur and procurement is asking why the backup path was a change order. With one, the same debates happen in planning, when mitigation still costs thousands instead of tens of thousands.
The business outcomes a register protects are straightforward. Schedule integrity — flagship segments start and end when leadership promised stakeholders they would. Message continuity — keynotes, product reveals, and awards run on the path you rehearsed, not the path you improvised. Brand exposure — live streams, hybrid feeds, and IMAG do not become tomorrow's internal meme because audio dropped or slides were unreadable on camera. Content leverage — footage and program audio are usable for the campaign marketing already sold to the CMO. Financial predictability — change orders and emergency rentals are exceptions you documented, not surprises that blow the quarter.
Events owns the register. Marketing owns the outcomes it protects. Production partners contribute the failure modes they have seen at your scale — union dock delays, matrix routing mistakes, RF coordination in a venue full of exhibitor Wi-Fi. Finance does not write it; finance should see it before the final budget lock.
What belongs on the register (and what does not)
Keep the register scannable. One row per material risk. Each row needs a plain-language description, a severity tier, a named owner, a mitigation plan, and a residual risk statement — what still might happen after you spend to reduce it.
Do not turn the register into a gear inventory. "We might need another speaker" is not a risk; "presenter wireless drops during CEO walk-on with no backup handheld staged" is. Do not list every vendor delay fantasy — focus on failures that change what the audience sees, hears, or records, or that force you to cut a segment leadership committed to.
Build the first draft around these categories. Require your production partner to add venue-specific and show-specific rows before load-in.
- 1.Schedule and run-of-show — Presenter overrun, late load-in compressing rehearsal, catering or union clocks that do not follow the script, segments that cannot flex when the general session runs long.
- 2.Show command and communication — No named show caller, unclear authority to hold or skip segments, broken comms between stage, video, audio, and show management.
- 3.Critical AV paths — Single-path switching on the product demo, no hot backup for the keynote, program audio not isolated for stream and post-production capture.
- 4.Wireless and RF — Frequency coordination gaps, insufficient backup mics, presenter habits that defeat the plan (pocketing the transmitter, turning off before the Q&A).
- 5.Hybrid and streaming — Encoder failure, audio delay between room and remote audience, failover sequence nobody rehearsed.
- 6.Content capture — Framing that kills vertical cuts, lighting that flatters the room but not IMAG, deliverable timeline not committed in writing.
- 7.Venue and logistics — Dock access, power, ceiling weight limits, freight elevator windows, weather for outdoor elements.
- 8.Third-party dependencies — Remote panelists, client-provided laptops, awards videos that arrive day-of, internet uplink shared with exhibitor traffic.
Each category should tie to an executive-visible outcome. If a row does not connect to schedule, message, brand, content, or budget predictability, cut it or merge it into a row that does.
Severity tiers and who decides
Not every risk gets the same investment. Severity tiers keep the register from becoming a wish list where everything is "critical" until nothing is funded.
Use four tiers and define them once, in writing, before vendors bid. Share the definitions with leadership so when you fund Tier 1 mitigation, nobody asks why you did not also duplicate every breakout.
- Tier 1 — Show stopper — Failure stops the flagship segment, forces a public restart, or sends leadership off-script on stage. Requires named mitigation, rehearsed failover, and a show-day owner with authority. Examples: CEO keynote on a single switcher path with no backup; product demo with live switching and no alternate source staged.
- Tier 2 — Visible degradation — The show continues but the audience or stream sees material quality loss. Requires mitigation plan and owner; rehearsal must prove the plan works. Examples: IMAG unreadable from side sections; stream audio drifting from room mix; awards montage codecs failing on the venue PC.
- Tier 3 — Recoverable friction — Backstage or near-miss issues the room may not notice if handled quickly. Document owner and response; fund mitigation when cost is low relative to stakeholder pressure. Examples: spare wireless not charged until morning; slide clicker battery; delayed graphics handoff from marketing.
- Tier 4 — Accepted — Known gap with executive sign-off. Residual risk is documented; no mitigation beyond standard practice. Examples: breakouts without full redundancy; VIP dinner not captured for post-show assets; weather plan for branded outdoor activation without tent budget.
When a risk escalates on show day, the owner does not debate severity in the hallway — they execute the tier response already agreed. Tier 1 gets the failover. Tier 4 gets logged for next year.
Building the register before the RFP
The register should inform the RFP, not replace it. Start six to eight weeks before you need signed scope — same window you use for venue hold and creative lock.
Events drafts the skeleton from prior shows: what broke, what almost broke, what cost a change order. Marketing adds rows tied to content capture and brand exposure — the segments that must record clean for the six-month campaign. Production partners you trust, or a shortlist in early conversation, add venue and technical rows you would not think to name.
Walk the draft with leadership once, before bids return. You are not asking for AV literacy. You are asking: "These are the Tier 1 failures we refuse to accept on the general session. This is what we propose to fund. Sign here or tell us what to downgrade."
That signature changes budget conversations. Finance sees redundancy and rehearsal as line items attached to named risks, not vague "production padding." Procurement compares bids against the same register — vendors who omit show calling or backup paths are non-compliant, not cheaper.
Bring these questions to every finalist. Written answers belong in the appendix of the signed scope.
- 1.Which register rows are you mitigating in base bid versus change order? Force specificity. "Redundancy included" is not enough — name the segment and the path.
- 2.Who is the show-day owner for Tier 1 failover decisions? One name, one comms channel, one authority to hold the stream or skip a segment.
- 3.What rehearsal time is allocated to prove Tier 1 and Tier 2 mitigations? If rehearsal is compressed by load-in, which rows move to residual risk — and who approved that?
- 4.How do you log near-misses during the show? The register updates from incident logs, not from memory at the bar.
- 5.What deliverable confirms mitigations were in place at doors? A pre-show checklist signed by production and events, cross-walked to Tier 1 rows.
Partners who answer with roles, hours, and paths belong on the shortlist. Partners who answer with brand names and "industry standard" do not.
Funding mitigation without blowing the budget
Executives cut redundancy first because it does not appear on the attendee survey. The register reverses that instinct by attaching dollars to outcomes.
Fund Tier 1 completely on flagship segments — keynote, product reveal, awards opener, any segment leadership promoted externally. Tier 2 gets funded where cameras and streams multiply exposure. Tier 3 gets funded when mitigation is cheap relative to embarrassment: spare handhelds, charged backup packs, a dedicated show caller on complex shows. Tier 4 gets explicit sign-off so nobody pretends you did not know.
The pattern that protects budget without gutting the show: tier production standards by segment importance, not by ballroom. General session earns failover and rehearsal; breakouts earn sensible defaults; VIP dinner earns what marketing committed to in the capture brief.
When finance pushes back, translate rows into avoided costs — reshoot days, emergency rental at show rates, executive time on a recovery call, campaign delay because footage is unusable. You do not need perfect attribution. You need leadership to see that the register is how you chose not to pay those invoices.
Cross-link the register to your production planning checklist so load-in, rehearsal, and show-day tasks map to Tier 1 rows. Checklists execute the plan; the register explains why those tasks exist.
Show day: activate the register, do not reinvent it
Show day is the wrong time to discover your backup path was value-engineered out of the winning bid. The register activates in three moments: pre-doors verification, rehearsal sign-off, and live incident response.
Pre-doors, events and production walk Tier 1 rows together — backup sources staged, wireless spares charged, show caller comms tested, stream path monitored. Anything not verified moves to residual risk with a name attached. No silent downgrades.
During rehearsal, log every near-miss against a register row. Slide animation choked the switcher? That is Tier 2 until proven fixed. Presenter wandered out of RF coverage? Tier 1 if it is the CEO segment. Rehearsal is where the register earns its keep; fixes belong on the tech table, not in the first five minutes of doors.
Live, the show-day owner executes tier responses. Comms stay on script: what failed, what path is live, whether marketing needs to adjust the stream or cut a segment. Marketing is not on headset, but marketing should know who owns the call when hybrid viewers see delay.
After strike, capture what activated, what nearly activated, and what was Tier 4 in hindsight but felt Tier 1 at the time. That log feeds the post-event update — and the next RFP.
After load-out: update the register or repeat the same failures
Within two weeks of strike, events and production should reconcile the register against reality. Rows that materialized get severity reviewed — was Tier 2 actually Tier 1? Mitigations that worked stay funded; mitigations that never got built become procurement findings, not anecdotes.
Share a one-page summary with marketing and finance: Tier 1 incidents (zero is the goal), Tier 2 degradations the room or stream noticed, near-miss count, change orders tied to undocumented risks. Marketing cares whether content rows failed — bad program audio, unusable presenter framing. Finance cares whether accepted Tier 4 gaps stayed accepted or became emergency spend.
Carry the updated register to the next show in the same program — annual meeting, roadshow, partner summit. Program-level risk is its own category: inconsistent crew quality across markets, touring show files that do not match venue resolution, hybrid standards that slip in market three because nobody updated the register after market one.
National programs benefit from one register template and market-specific appendices. Same Tier 1 definition everywhere; venue rows swap per room. That consistency is how you avoid the kickoff that looked polished in headquarters and "local" everywhere else.
From the floor: the register that stopped at the spreadsheet
A corporate leadership summit built a risk register in January — twelve rows, severity colors, owners named in the workbook. Events shared it once in a steering call. The production vendor of record was selected on price; nobody cross-walked the bid to Tier 1 rows before the PO.
Load-in hit a union dock window nobody had verified. Rehearsal lost two hours. The CEO segment stayed on a single switcher path because hot backup was listed optional in the bid. Mid-keynote, the clicker laptop slept; the slide deck froze on a financial chart while the CEO improvised and IMAG held the previous title slide. Hybrid viewers heard room audio eight seconds behind the stream because failover had never been rehearsed with the encoder path.
The spreadsheet still existed on someone's laptop. It had not been activated at doors, and nobody had signed Tier 1 mitigations into scope. The post-show summary took fifteen minutes to write — every row that failed had been named three months earlier.
Risk management is not the document. It is the signature, the bid cross-walk, and the pre-doors walk that proves you meant it.
Build your register before the RFP, fund Tier 1 like you mean it, and walk it at doors. Use our event production checklist to tie tasks to rows, and talk to our team if you want a production partner who plans failure modes before they happen — including nationwide programs where the same register travels market to market.
