How to tell participants a workshop is being captured (with the wording)

Written by the IdeaHone Editorial Team · · 5 min read

Silver studio microphone

The awkward version goes like this: the first idea is on the table, someone has just said something honest about the sales process, and the facilitator adds "oh, and this is being recorded". The room cools by two degrees and stays there. Telling people a workshop is captured is a legal need and a trust move, and timing is most of it: say it early, say it plainly, say it twice, in the invitation and in the room.

Why the notice matters

A captured workshop turns what people say into text that outlives the session. Contributions attributed to a person are personal data, so you need transparent information and a legal basis; check the details with your data protection officer. The notice in the invitation lets people ask or decline in private. The one in the room reaches the colleague who never reads invitations.

The three texts

Copy them, fill the brackets, cut what does not apply. They assume that speech becomes text and idea cards and that no audio file is kept.

1. The paragraph for the invitation e-mail

In this workshop we capture the discussion so that nothing gets lost. What is said is converted into text and sorted into idea cards during the session. No audio recording is stored. The text and the cards are kept for [twelve months] and can be seen by [the participants and the innovation team]. Contributions are attributed to the person who made them so that we can follow up on questions. If you prefer not to be named, tell [name] before or at the start, and your contributions stay anonymous. Questions go to [name, e-mail].

2. What the facilitator says in the room

Before we start: as mentioned in the invitation, we are capturing this session. What you say becomes text and idea cards, so you do not need to take notes. There is no audio recording, the text stays within [the team] and is deleted after [twelve months]. If you would rather not have your name on your contributions, say so now or in the break and I will switch it off for you. Any questions before we begin?

I agree that a voice profile is created from my voice so that my contributions in this and future workshops are attributed to me automatically. This is voluntary, I can withdraw it at any time with [name], and the profile will then be deleted.

Text 3 is only needed if your tool recognises speakers per person. Read it out loud, let each person decide alone, and note who agreed. Transcription and GDPR covers what the tool side has to do.

What to adapt

  • The retention period. Twelve months is a sensible default. Write down the real number and make sure someone deletes on that date.
  • Who can see the results. Name groups, not "the company". Participants and the innovation team is a clear answer; "management" is not.
  • Whether names are attached. If you only need the ideas, make contributions anonymous from the start. If you need to follow up, say why. Who said what helps you decide.
  • External guests. Customers and agency people have signed nothing with you. Send them the invitation text separately and let them opt out of being named without explanation.
  • The works council in Germany. Capturing what employees say in meetings is usually a matter for co-determination. Talk to the works council before the first workshop, not after a complaint.

These texts are templates, not legal advice. Show them to your data protection officer once, adapt them to your organisation, then reuse them.

If a tool stores audio, even temporarily, your invitation text must say so, including how long and where. These templates do not cover audio storage.

The sequence

  1. Text in the invitation. Paste paragraph 1 into the calendar invitation or e-mail, a few days before.
  2. Reminder on the agenda slide. One line on the first slide: "This session is captured as text, no audio is stored."
  3. Spoken notice before listening starts. Say text 2 before capture is switched on, never after the first idea. Tools like IdeaHone keep only the text, never the audio, so the sentence you just said stays true.
  4. Voice profiles only after the notice and only by choice. Read text 3, let people decide individually, and start without a profile for anyone who hesitates.
  5. The same sentence in the summary mail. Repeat what is kept, for how long and who sees it, so the notice survives in writing next to the results.

Three ways the notice costs you trust

  • Saying it after the first idea. A late notice feels like a trap. If you forgot, stop, say it, and offer to delete what was captured so far.
  • Burying it in the tool's terms. A link to a privacy policy is not a notice. People need two plain sentences they can repeat to a colleague.
  • Making a fuss about one opt-out. Switch names off for that person and move on without comment.

If you use speaker recognition, also explain how voice profiles work and what to tell your team.

Capture every idea while people talk

IdeaHone listens in your session and turns what people say into idea cards, questions and decisions, live on a shared board.

Request a demo

Do I have to tell participants a workshop is transcribed?

Yes. Converting speech into attributed text is processing of personal data, and participants have to be informed before it starts. Check the exact legal basis with your data protection officer.

What should a recording notice say?

What is captured, what is not, how long it is kept, who can see it, how to stay anonymous and whom to ask. The templates above cover all six points in a few plain sentences.

Is a transcript the same as a recording?

No, but it is still personal data. A transcript is searchable text attributed to people; an audio recording also keeps the voice itself. Both need a notice, and audio storage must be stated explicitly.

All resources