What to Put in an Event AV Patch List

Ask the technical lead which signal paths the patch list will cover and whether audio, video and hybrid production need linked sheets. A useful list remains specific enough to follow a connection without becoming an unreadable substitute for every technical drawing. Detailed system design belongs with the production team.

Keep it distinct from the run of show. The run of show describes when a presentation or cue happens; the patch list identifies the signal path that makes it possible. Use shared source names across both documents so operators do not have to translate between competing labels.

Each source needs a unique ID and a plain-language description. A label such as Presentation Laptop A is more useful than Laptop when several computers are involved. Each destination also needs a specific identity, such as Main Display Program or Remote Audience Audio, rather than a vague instruction to send something to screens.

Keep IDs stable when a speaker or session changes. The content assignment can change without renaming the entire signal path. Ask technical staff to align document IDs with their working labels, allowing an operator's report and a planner's session note to refer to the same source.

For each entry, include the source ID, source output, receiving device or input, intended destination and signal type. Technical staff should supply relevant connection and format details. Where a path passes through processing or switching, the documentation should make that relationship traceable rather than implying a direct connection that does not exist.

In a hypothetical hybrid meeting, presentation video and presentation audio could follow different paths to room and remote audiences. Document those relationships explicitly. A visible slide on the main display does not establish that remote attendees receive the corresponding audio or that the correct content reaches every destination.

The person responsible for a deck is not necessarily responsible for its playback connection. Record a content owner for file questions and a technical owner for the source or signal handoff. If another party supplies a feed, identify who sends it, who receives it and who coordinates testing.

Define what the receiving team expects to get. Is it presentation content alone, a composed program image or a particular audio feed? These distinctions matter more than a generic note saying external feed. Production staff should resolve technical requirements directly, with planners tracking unanswered questions and approval responsibilities.

Add a verification field that distinguishes planned paths from tested ones. Testing should confirm the intended source at the intended destination, not merely that a connector is present. Let the technical lead define appropriate checks and record unresolved exceptions where operators can find them.

Assign one document owner and identify the current revision. If a backup source is included, document its path and who authorizes its use; its presence alone does not establish readiness. Exact corporate AV routing, processing and backup configurations require a quote based on the event design.