Twelve questions your production team should be asking twelve weeks before your energy summit, and what it costs you when they don't.

Energy-sector flagships are the hardest corporate events to produce cleanly, and it's not close. Vendor badging through Avetta- or ISN-class portals. Rigging that intersects controlled areas. Multi-site broadcast to terminals where the uplink is whatever the plant gave you. A C-suite that expects a TV-caliber keynote and a board that expects MNPI handled like MNPI. Twelve weeks out, here's what a production team that's actually run an energy summit should already be asking. If your team is hearing any of these for the first time on the scoping call, that's the signal.

Security & compliance

1. Vendor-portal badging, when does it actually start? Avetta, ISN, Veriforce, your major's bespoke portal: every one of them takes longer than your team thinks. Start day one of contract, not day one of load-in. Crew that shows up unbadged on a plant-adjacent venue is a crew that doesn't get on site, and the cost of that miss is rebooking day-rates inside two weeks of the show.

2. What's adjacent to the venue, and is any of it controlled or hazardous? This is the question that drives rigging inspection routing, load-in path, and the line item nobody budgets for: incremental insurance. Walk it on the advance, not on a floor plan.

3. Will the venue need a third-party rigging engineering stamp? On or near plant sites, the answer is usually yes, and "usually" here means "assume yes, get the exception in writing if not." The stamp is two to three weeks of lead time. Find out on week twelve, not week four.

Broadcast topology

4. How many terminal or plant sites need to receive live, and how many of them have IT teams that have done this before? The site count drives encoder fleet and licensing. The IT-readiness count drives whether your production team is also doing onsite uplink ops at three terminals on show day. Those are different scopes. Price the second one before you sign.

5. What's the primary uplink at each receive site, and what's the failover when it browns out? Plant networks are not corporate networks. We've engineered failover into bonded cellular through a Peplink stack across fourteen Gulf Coast terminals, zero downtime. If your team can't tell you the failover, the failover is hope.

6. Is Q&A bidirectional, does the plant floor need to speak back into the keynote? This is the question that quietly redesigns your entire comms plan. One-way broadcast is a streaming engagement. Bidirectional is a multi-site show with return audio, IFB to the keynote stage, and a moderator workflow that gets rehearsed. The cost difference between the two is roughly an order of magnitude. Decide on week twelve, not week three.

Content and IP

7. Is any of the content MNPI, and who on the production team needs to know that before the recording starts? MNPI determines recording access controls, who holds master files between show and earnings call, and the destruction protocol post-event. It also determines who on crew gets briefed and who doesn't. If your production team has never had this conversation with your IR or legal counterpart, that's a fixable gap. If they don't know what the question means, that's a different problem.

8. Who signs off on sponsor content, and by what date? Sponsor content is the load-in-day fire drill that nobody schedules. Define the approval chain and the deadlines on week twelve. Get them in writing. Get the alternate approver in writing. The sponsor whose decision-maker is unreachable in show week is the sponsor whose package will not clear, and somebody on your team will be re-cutting an opener at 11 PM Tuesday. Engineer it out.

9. Does any content go to IR or comms the day of? If yes, your production team needs an edit bay onsite, a same-day cut workflow, and an IR review window built into the show flow, not bolted onto it after wrap. Day-of IR delivery is not a deliverable you add late. It's a scope decision made now.

Execution risk

10. What's the weather contingency, and have you priced the redundancy you actually need? Houston in September is not Houston in March, and the Gulf Coast in hurricane season is a different planning regime entirely. Wind-rated LED, generator redundancy, an indoor backup room held on a no-show fee, a tent rated for the actual wind load, pick the four that match your date and your venue. The cost of the wrong four is the cost of the show.

11. Who's calling the show, your person or ours? If it's your show caller, the rehearsal schedule expands and the production team builds around their cadence. If it's ours, we need agenda lock four weeks out and a script that's been red-lined twice. Either model works. Both models fail when nobody decides until production week.

12. What's the one outcome the C-suite will judge this summit by? Every production decision downstream gets engineered around the answer to that question. Engagement metric? The room build and the broadcast routing change. Investor signal? The keynote stage and the IR cut workflow change. Internal alignment? The Q&A architecture and the show-flow pacing change. If your team can't answer this on the scoping call, the entire scope is provisional, and provisional scopes are how budgets blow up in week ten.

If the team across the table can't run you through these twelve in a scoping call, you're not looking at a production partner. You're looking at a rental desk in a nicer jacket. The difference shows up on show day, but the bill for it shows up in week ten.