Recording a video call, interview, webinar or livestream can make valuable content easier to review and reuse, but the workflow should be planned before anyone presses Record. This UK-focused checklist covers consent, privacy notices, transcription, storage, access, deletion and public reuse so creators and businesses can make a reasonable, documented decision for each recording.
Overview
There is no single “recording consent” button that makes every call lawful. The right approach depends on who is involved, why the recording is being made, what information it contains, how it will be used and whether it will be shared publicly. A private internal meeting, a paid webinar with registered attendees and a guest interview for YouTube may require different notices and controls.
Before recording, identify the purpose in plain language. For example: “We will record this interview to edit short clips for our website and social channels,” or “We will record this training session so registered attendees can watch the replay.” Avoid collecting or retaining more material than that purpose requires.
Consent may be appropriate in many creator and event workflows, particularly where participation is voluntary and publication is part of the plan. It should be informed, specific and capable of being withdrawn where consent is the chosen basis. In other situations, an organisation may consider another lawful basis under UK data protection requirements. That decision should be documented and, where the situation is sensitive or high-risk, checked with a suitably qualified privacy professional.
Recording is only one stage. Automatic captions, call transcription tools, meeting summarizers, cloud storage, editing platforms and public video hosts can all create additional copies or uses of the conversation. Treat each hand-off as part of the privacy workflow.
Checklist by scenario
Private business meeting
- Tell participants before the meeting that recording is planned, why it is needed and who will receive it.
- Explain whether transcription or automated summarisation will also be enabled.
- Give participants a practical way to ask questions or raise an objection, where applicable.
- Restrict access to the people who need the recording for the stated purpose.
- Set a review or deletion date instead of keeping the file indefinitely.
Guest interview or creator livestream
- Agree the recording and intended channels with every guest before the session.
- Cover live broadcast, replay, edited clips, thumbnails, captions, transcripts and promotional extracts separately if they are possible uses.
- Confirm how a guest can request a correction or raise a concern about a proposed edit.
- Do not assume that an informal verbal “yes” covers every future use. Keep a written confirmation, release or consent record suited to the project.
- Check that music, images, screenshares and comments appearing in the recording can also be used as planned.
Webinar, workshop or online event
- Put the recording notice in the registration flow, event email and opening announcement.
- Tell attendees whether questions submitted in chat, names, profile images or audience video may appear in the replay.
- Offer a route for asking questions privately if attendees do not want to speak on the recording.
- Decide whether the replay will be restricted to registrants, shared with a customer group or published publicly.
- Brief hosts and moderators on how to pause recording or remove sensitive material before publication.
Practical disclosure script
A clear opening statement is better than a vague warning: “Before we begin, this session is being recorded for [purpose]. It may be transcribed and [shared with / published for] [audience]. Please avoid sharing information you do not want included. If you have a question about the recording or need an alternative way to participate, contact [name or channel].” Adapt this wording to the actual workflow. Do not promise limited access if the file may later be repurposed publicly.
What to double-check
Platform settings
Review the recording controls before each event because names and defaults can change between platforms and plan levels. Check whether recording starts automatically, whether local and cloud copies are both created, who can download the file, whether chat and captions are saved, and where recordings are stored. Also inspect guest permissions, waiting rooms, screen-sharing controls and the setting that determines whether participants receive an on-screen or audible recording notice.
If you use transcription or a meeting summarizer tool, identify the provider, the data it receives, the account where output is stored and the people who can access it. Treat a transcript as a searchable copy of the conversation, not as harmless metadata.
Storage and access
Use named folders, sensible permissions and a clear owner. Avoid leaving recordings in a personal downloads folder, an open shared drive or a platform account that former team members can still access. Protect particularly sensitive material with stronger access controls and avoid downloading it to devices that are not managed or secured.
Retention decision table
| Recording type | Possible retention approach | Review question |
|---|---|---|
| Routine internal meeting | Keep until notes, actions or an approved summary are complete. | Is the original still needed? |
| Training or webinar replay | Keep while the material is accurate and the replay is offered. | Has the content, consent or access audience changed? |
| Guest interview | Keep the master and published edits only as long as the agreed project requires. | Does the planned use still match the guest’s agreement? |
| Complaint, dispute or regulated record | Follow the organisation’s documented legal, contractual or records policy. | Is a hold required before deletion? |
These are planning prompts, not universal retention periods. Set a documented schedule based on purpose, business need and applicable legal obligations. Delete or anonymise copies when they are no longer required, including obsolete transcripts, exports and editing-project files.
Common mistakes
- Announcing the recording after it starts: give notice early enough for people to make an informed choice.
- Using one notice for every purpose: distinguish internal review, replay access, public publication and promotional clips.
- Forgetting the transcript: captions and summaries may contain names, opinions, contact details and sensitive disclosures.
- Publishing the raw file automatically: review chat, private screenshares, waiting-room content and accidental disclosures first.
- Keeping everything forever: an archive should have an owner, access rules and a review date.
- Relying on platform defaults: confirm settings in the actual account and event, then record the decision in your run of show.
- Ignoring withdrawal or correction requests: have a clear process for evaluating requests and identifying every published copy.
When to revisit
Use this checklist before each recorded call, guest interview, webinar or content-repurposing project. Revisit it sooner when the audience changes, a guest is added, the purpose expands, a new transcription or storage tool is introduced, or a private recording is being made public.
Schedule a formal workflow review before major seasonal planning cycles and at least when your platforms, account permissions or privacy documentation change. Recheck current guidance from the UK Information Commissioner’s Office and other relevant UK requirements rather than relying on an old template. Platform recording, transcription and storage controls can change independently of your internal policy.
For the next recording, write down five decisions before sending the invite: the purpose, the notice wording, the intended audience, the retention or deletion date and the person responsible for reviewing the final file. Then test the platform with a colleague, confirm that the recording notice appears, and keep the consent or notice record with the project. For a wider webinar workflow, pair this checklist with the Live Webinar Run of Show Template and review the guidance on recording, transcription and meeting summaries.
This article provides practical information, not legal advice. If a recording involves sensitive information, children, vulnerable participants, employment issues, international disclosure or a disputed legal basis, obtain tailored advice before proceeding.
