Event recording release workflow
The committee wants to record every session for members, and the registration form says nothing about it.
The short answer
Decide what will be captured, for what use and for how long before anyone writes a notice or buys a camera. Then take that decision, the draft notice and the speaker release to your data protection contact and legal adviser, and only start recording when their answers are filed.
Where someone says no, the plan needs a way to honour it on the day, such as a no-camera area or a pause in recording.
Decide the purpose first
Recording for member-only replay, public marketing, training material and archive are different purposes and may need different answers. Write the purpose, who can view, and how long it stays available.
Capture only what the purpose needs. Audio of a session is a smaller decision than video of the audience.
The workflow
- Write the recording plan: what (audio, video, stills, livestream), where, who records, purpose, viewers and retention.
- Send the plan and the draft notice to the data protection contact and legal adviser with the question pack below.
- Prepare the speaker release and attach it to the speaker invitation, then record answers in the presentation permission register.
- Add the attendee notice to registration and confirm with the registration form field minimiser that no extra personal data is collected for recording.
- Plan on-site signs, camera positions and a way to honour those who decline.
- After the event, store the recordings where the plan says, release only files with filed permissions and keep the takedown path from content takedown request ready.
Who is covered and how
| Group | What to arrange | Confirm with |
|---|---|---|
| Speakers and moderators | Written release per session; separate from slides | Legal adviser |
| Delegates | Notice at registration and on site; a way to opt out of being filmed | Data protection contact |
| Panel and Q&A participants | Say at the start that the session is recorded; give an alternative for questions | Legal adviser and data protection contact |
| Recording supplier | Contract on who holds the files, who may edit and how they are returned or deleted | Legal adviser |
Question pack for the data protection contact and legal adviser
- Does recording audio or video of delegates involve personal data under our data protection obligations, and what must the notice say?
- Is consent, notice or another basis the right approach for each group, and who decides?
- How should a delegate decline being filmed, and how will staff and camera operators know?
- How long may recordings be kept, who may view them and where are they stored?
- What happens if a delegate or speaker asks for removal after publication?
- Does the recording supplier's contract cover storage, return and deletion?
- These answers come from the competent party. The event team records them and does not decide what is lawful.
Worked example · Fictional example
A fictional one-day member forum
Fictional organisation and figures, illustrative only.
A fictional professional body wanted to record eight sessions for a member portal. The plan covered audio and stage video only, with no audience shots, and the draft notice and release went to the data protection contact and legal adviser.
Two speakers declined video, so their sessions were recorded as audio. The question-and-answer segments were announced as recorded, and delegates who preferred not to be on record could send questions by card.
Use this yourself
Recording plan and release checklist
Fill this in before writing the notice, and keep it with the answers from your advisers.
- Purpose, viewers and retention period written down:
- What is captured (audio, video, stills, livestream) and what is not:
- Speaker and moderator release sent, answers logged per session:
- Attendee notice drafted, reviewed by the data protection contact and legal adviser:
- Registration form checked so no extra personal data is collected:
- On-site signs, no-camera area and opt-out handling briefed to staff and operators:
- Recording supplier contract covers files, storage, return and deletion:
- Music in recorded content checked against the music licensing questions:
- Takedown contact and process ready before anything is published:
Open the tool: Conference materials and translation-version checker
Handle it in-house, or bring in help?
Your team can usually handle this when
- Audio-only recording for an internal audience.
- Few speakers who all answer the release promptly.
- Advisers already have a standard notice.
Outside planning help earns its fee when
- Video and livestream for a public or member audience.
- Multiple parties hold part of the plan: supplier, venue, sponsor and association.
- Speakers or delegates are asking not to be filmed and nobody owns the response.
Need the recording permissions coordinated?
A conference project lead can write the recording plan with you, take the question pack to your data protection contact and legal adviser, collect speaker releases and brief the recording supplier on the answers. The legal and privacy conclusions remain theirs.
Questions organisers ask
Is a sign at the door enough?
Ask your data protection contact and legal adviser. A sign may be part of the plan, but whether it is enough for your event is their call, not the event team's.
Can we record first and ask later?
Treat recording as something to confirm in advance. Once captured, you may hold files you are not sure you can use.
Where do press and photographers fit?
Press photography has its own steps in the press accreditation workflow. Keep one plan so notices to delegates cover both.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.