Onsite Technical Direction Checklist
When a corporate show starts slipping, it usually does not begin with a major failure. It starts with a missed cue, a bad confidence feed, a playback machine on the wrong output, or a presenter who was never properly checked on stage. That is why an onsite technical direction checklist matters. It gives the show caller, technical director, and department leads one shared operating picture before doors, before walk-in, and before the CEO steps into the light.
For conferences, product launches, executive webcasts, and hybrid events, onsite technical direction is not just about calling cues. It is about controlling risk in real time. The best technical direction keeps signal flow clear, keeps departments aligned, and catches small problems before they turn into visible failures.
What an onsite technical direction checklist should actually cover
A useful checklist is not a generic event template. For corporate production, it has to reflect the actual show system. That means screen management, playback, camera routing, graphics, streaming, audio handoffs, intercom structure, stage timing, and backup paths. If the checklist is too broad, nobody uses it. If it is too narrow, it misses the failure points that matter.
In practice, the checklist should follow the order of risk. Start with power, networking, and core system health. Then move through signal flow verification, operator readiness, presenter support, and cue execution. Leave room for show-specific notes, because a general session with Barco E2 switching and a breakout webcast have very different pressure points.
The pre-show technical direction checklist
Before anyone talks about creative polish, confirm the infrastructure. The technical director should know where primary and backup power are feeding critical systems, which UPS units are protecting show control, and what devices must never be power-cycled without coordination. If that is unclear on show day, the system is already exposed.
Signal flow comes next. Every source and destination should be verified end to end, not just at the rack. A laptop that resolves correctly at the switcher but fails at the confidence monitor is not tested. A camera feed that lands in multiview but not on stream is not tested. The point is to confirm the full path, including converters, processors, scalers, routers, and destination displays.
For larger corporate shows, that usually means checking presentation machines, show graphics, walk-in loops, stingers, camera shading, playback servers, remote callers, streaming encoders, confidence monitors, DSMs, teleprompter feeds, and records. If an LED wall is in play, verify canvas mapping, backup processing, and test content that reveals scaling or artifact issues. This is also where Barco E2 or E3 setups need close attention, especially destination management, layer logic, and preset confidence.
Audio should be checked from the technical direction perspective, not just the A1 perspective. Confirm what the TD needs to know: program feed source, mix-minus for remote guests, confidence return, playback handoffs, and how cues are affected if a wireless mic is swapped at the last minute. Many show issues are not audio failures. They are coordination failures between audio and show calling.
Comms deserve their own pass. Every key role should have a clear path: TD, show caller, video, A1, A2, playback, graphics, stream engineer, stage manager, and camera ops where needed. If there are separate channels, everybody should know what lives where. If there is a partyline backup or a wired backup for a wireless comms failure, confirm that before rehearsal. Quiet comms problems become loud show problems.
Onsite technical direction checklist for rehearsal
Rehearsal is where the checklist stops being theoretical. This is the time to validate timing, not just technology. Every show segment should be run far enough to expose cue density, presenter pace, and any confusion about ownership.
The most common rehearsal mistake is treating it like a content review instead of a systems test. A proper run should verify slide advances, video playback triggers, lower thirds, camera presets, lighting looks, comfort monitor timing, confidence return for remote speakers, and transitions between live and playback elements. If the opening video rolls but the lights do not move and the speaker enters before the IMAG cut is ready, the system is not ready.
Presenter management belongs on the technical direction checklist too. Confirm lav placement timing, walk paths, clicker operation, teleprompter expectations, and monitor positions from the stage sightline. Corporate presenters often make last-minute changes, and that is normal. The TD’s job is to reduce the number of surprises that land at T-minus 30 seconds.
It also helps to define what gets locked after rehearsal and what stays flexible. Playback file names, slide handoff procedures, cue numbering, and comms language should be stable. Speaker intros and timing adjustments may still move. That distinction keeps the crew from rechecking the wrong things while a real issue is developing somewhere else.
Show calling, cueing, and redundancy
Live execution depends on two things: clear calls and credible backup plans. If either one is weak, the show becomes reactive.
Cue language should be standardized before doors. There is a real difference between standby, warning, and go, and every operator should hear them the same way. The same goes for terminology like take, dissolve, fade to black, hold, abort, and reset. A technically strong crew can still miss cues if the language is inconsistent.
Redundancy has to be specific. Saying there is a backup is not enough. The checklist should identify what fails over automatically, what fails over manually, who owns the decision, and what the audience will notice. For example, a redundant stream encoder is helpful, but only if networking, platform authentication, and audio routing are also covered. A spare playback machine is useful, but only if content is mirrored and output mapping is correct.
This is where experienced onsite technical direction pays off. Redundancy is rarely all or nothing. Some shows justify full A/B playback, duplicate switching paths, backup records, and separate internet paths. Others need a more targeted plan built around the highest-impact failure points. It depends on audience size, executive visibility, streaming requirements, and how much tolerance the client has for interruption.
Department handoffs that usually cause trouble
Most show issues happen at the boundaries between teams. Video assumes audio has a return ready. Audio assumes playback has confirmed levels. Stage management assumes graphics has the final walk-up name. Nobody is wrong in isolation, but the show still breaks.
A strong onsite technical direction checklist forces those handoffs into the open. Confirm who owns final presentation ingest. Confirm who checks remote guest confidence and IFB. Confirm how last-minute content changes reach playback and graphics without bypassing version control. Confirm whether the stage manager or TD has final hold authority if a presenter is not in position.
Corporate productions with livestream elements add another layer. The room can look good while the stream is in trouble, or the stream can be clean while the room is seeing the wrong destination feed. That is why the streaming path needs dedicated verification, including platform login status, encoder health, record status, latency expectations, and return monitoring. For platform-specific checks, teams often reference Zoom or Microsoft Teams production requirements directly during prep.
If your event includes a complex general session, executive webcast, or hybrid program, this is usually the point where a full-service partner makes the difference. AV Land handles corporate event production and livestream systems in-house, which helps keep show control, routing, and support responsibility under one roof. See event services at https://av.land/event-services/ and livestream services at https://av.land/livestream-services/.
How the checklist changes by event type
A keynote with a wide-screen blend or LED wall needs more attention on destination management, presenter blocking, and cue precision. A panel discussion leans harder on microphones, camera coverage, lower thirds, and speaker coordination. An executive webcast may put less stress on room playback but more stress on streaming confidence, records, and remote guest reliability.
That is why a good checklist is modular. The core structure stays the same, but the detail changes with the show. AVIXA publishes useful standards and reference material that many production teams use to shape process, and Barco documentation is often part of the prep stack for image processing workflows.
The goal is not to create paperwork. The goal is to make the room easier to run.
What clients should expect from onsite technical direction
If you are hiring onsite technical direction for a high-stakes corporate event, expect more than someone calling cues on headset. Expect someone who understands signal flow, can pressure-test the show file, can coordinate departments without drama, and can make a fast decision when the plan changes. Expect rehearsals to be structured, not casual. Expect backup paths to be defined, not implied.
Most of all, expect someone who can see the whole system at once. That is the real value. Technical direction is not a layer added on top of production. It is the control point that keeps video, audio, lighting, streaming, staging, and presentation support moving as one show.
If your event has executive visibility, multiple content sources, live switching, or a public stream, the checklist should be built before show day and enforced on site. That is how complex corporate productions stay calm under pressure.
