When a contributor asks for a break, everyone should understand whether the conversation is still being recorded. A microphone mute can affect one output while another device continues to store sound. Set a clear recording-state protocol before the session, particularly when the production uses local backups or several simultaneous recorders.
This is a practical expectations issue. It should be resolved in plain language rather than by asking contributors to recognise equipment indicators. The producer can describe how the agreed pause works and who confirms that the relevant recording paths have stopped.
Identify all the places speech can be stored
Ask whether audio is recorded in the camera, a separate recorder, a worn transmitter, a conferencing system or another authorised device. The answer should distinguish recording from monitoring and transmission. A person may no longer be heard through one destination while their microphone remains active elsewhere.
The RØDE Wireless PRO configuration guide provides a specific example: its transmitter mute can stop the receiver feed without affecting onboard recording. That behaviour is product-specific, but it demonstrates why the word muted needs an explicit meaning in the production brief.
Agree a clear pause request
Give contributors a simple way to request that recording stops. The response should identify when the agreed state has actually been reached, rather than treating the request itself as proof that every device changed state immediately. Discuss this before a sensitive or tightly scheduled interview, not after a private comment has already been made.
The protocol should also cover restarting. A participant who has just taken a break should know when the conversation is again being captured. Do not rely on a camera operator's visible action if a separate sound recorder has different behaviour.
Separate retained material from usable material
If a technical workflow creates material around a requested break, agree how it is flagged, restricted and handled. Ask who can identify the affected interval and whether any copy remains in a backup or cloud recording. Avoid making an absolute deletion promise without checking the actual storage process and the organisation's applicable requirements.
A hypothetical project director wears a locally recording transmitter during an interview. The camera feed is muted while the team discusses a sensitive internal detail. Because the crew has explained the separate local recording path beforehand, the director asks for a full recording pause rather than assuming the mute is enough. The team follows the agreed protocol and confirms the restart.
Test the protocol with harmless speech
A brief rehearsal can establish what the chosen controls actually do. The production team can use an ordinary test phrase, apply the agreed pause and inspect the relevant files. This checks the system without exposing private information or requiring the contributor to understand its routing.
Acceptance questions should include which devices store speech, who confirms a pause, how a restart is communicated and how any unintended interval is identified. The arrangement should be understandable to the participant and workable for the crew.
A clear recording-state agreement protects trust in the conversation. It also prevents a technical convenience, such as an always-running backup, from silently becoming a broader recording permission than the contributor and buyer intended.
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.