Specifying Presentation Recording Deliverables

Start with the viewing situation. Will employees watch the complete session, search for a particular training topic or receive short excerpts? Does the viewer need to read detailed slides, see the presenter or understand audience questions? These answers help define the requested result without presuming a particular production configuration.

Write a plain-language deliverable description. For example, a hypothetical internal briefing might need one continuous presentation file with readable slides and intelligible presenter audio, excluding breaks. That is a request to evaluate and quote, not a promise of service. Specify whether questions, introductions and closing remarks belong in the deliverable so the boundaries are not decided after the event.

The team receiving the file should identify the destination platform and its accepted file requirements. Ask about container format, video encoding, resolution, aspect ratio and upload limits. A file extension alone does not describe all the characteristics that determine compatibility. Share the platform's requirements with the production provider for confirmation.

Also ask whether captions, a transcript, separate audio or separate presentation segments are needed. Each is a distinct deliverable to discuss, not an automatic companion to a video file. If editing is requested, define what it means: removing breaks is different from correcting slides or creating excerpts. Agree on the review process and acceptance criteria before work begins.

Assign someone within the organization to confirm permission to record and distribute presenter contributions, slides and included media. Permission to show an item during a meeting should not be treated as permission to publish it afterward. Ask the appropriate legal or organizational reviewer to resolve uncertain rights rather than asking the AV team to make that judgment.

Audience questions may introduce additional voices, personal information or confidential business details. Decide how participation will be communicated and which portions are intended for distribution. Establish who can flag material for exclusion and who approves the final release. A technically complete file is not necessarily cleared for circulation.

Name the delivery recipient and agree on a transfer method suitable for the organization's access controls. Ask when delivery is proposed, what review opportunities are included and who consolidates feedback. Do not assume a turnaround commitment or unlimited revisions. The exact deliverables and associated production configuration need a quote.

Define when the receiving team will check that files open, play through and match the agreed scope. Separately, ask what source material or working files, if any, will be retained, by whom and for what agreed period. Confirm deletion or transfer expectations in writing. Once delivery is accepted, assign internal responsibility for the organization's own archive rather than assuming the production provider maintains one.