The phrase local recording can describe different things. It may mean a file captured directly on the contributor's device, or a file saved on another computer from the transmitted call. Before commissioning a remote interview, ask exactly where the intended speech master is created and how it reaches the editor.
This distinction matters because a successful conversation does not establish that the preferred production file has been secured. The recording plan needs to cover capture, upload, identification and a listening check, not merely the call itself.
Draw the boundary in plain language
Ask whether the source is recorded before or after the contributor's audio travels through the conferencing connection. Identify the fallback if that source is missing. A call recording can be a useful alternative, but it should be described as such rather than presented as equivalent without inspection.
Zoom's Recording Studio documentation distinguishes local recordings from cloud fallback and describes storage and upload dependencies. Its feature conditions are specific and can change. Confirm the actual account, application and participant setup rather than assuming every remote platform offers the same path.
Make completion more than ending the call
If a recording needs to upload after the session, allow time and assign support. Tell the contributor what must remain available and who confirms receipt. The supplier should handle the technical instructions appropriate to the selected platform; the buyer's brief should make the completion condition explicit.
A progress indicator is useful but not final evidence that the editor has a complete, readable file. Ask for confirmation that the required source has been opened, contains the expected duration and can be matched to the picture or other participants.
Plan for unequal source availability
In a multi-person remote discussion, one participant may supply a local recording while another contributes only a transmitted stream. Decide how that difference affects the finished film. It may be acceptable, may require additional treatment or may justify a limited rerecording of an essential passage.
A hypothetical company interviews two regional project leads. One joins from a supported desktop setup; the other switches to a phone shortly before recording. The producer identifies that the intended source path has changed and revises the plan. The client does not discover the mismatch only when the two voices sound markedly different in the first edit.
Keep the fallback honest
Specify when a fallback can be used without further approval and when an audible compromise needs discussion. A technically complete file may still contain interruptions or processing that affect an important sentence. The check should therefore include representative speech, not just a file-size comparison.
Ask which source was used in the final edit and whether any passages came from the fallback. Retain that information with the project so later revisions do not accidentally revert to a different recording.
The commissioning outcome is a verified path from the contributor's voice to an identified editorial source. Once capture location, upload responsibility and fallback treatment are explicit, remote recording becomes a defined production workflow rather than a hopeful assumption that the call platform will supply everything afterwards.
Discuss the production
Contact Live Images to discuss the proposed film, intended audience and audio requirements. Confirm suitability, scope and availability for your particular brief.
Editorial note
Original commissioning guidance prepared with AI assistance. Examples are hypothetical, not completed Live Images projects. Search intent is an editorial hypothesis, not measured demand. This draft remains unpublished.