Meeting participants should understand why an AI voice recorder is being used, what it will capture, how AI processing works, who can access the files and what choices they have. A vague statement such as “this is being recorded for notes” may not explain the real workflow. Clear communication should happen before recording and remain available throughout the meeting.
Provide written information in advance
Where practical, include a short notice with the invitation or agenda. It should state:
- the purpose of recording;
- the meeting or sections covered;
- whether audio, transcript, summary or structured outputs will be created;
- the approved users and storage location;
- the expected retention period;
- how participants can ask questions or object;
- the alternative available when recording is not suitable.
Use an accessible format and provide translation, plain-language or other support where needed. Do not rely solely on a link that participants may not be able to open.
Use a concise verbal opening
A practical opening script can be:
“I plan to record this meeting to create a draft transcript and action summary. The recording will be stored in our approved system and accessed only by the people responsible for the meeting record. The AI output will be checked by a person. We expect to delete the raw recording according to our retention process. Please tell me now or at any time if you have a concern or want the recording paused. We can use an alternative note-taking method.”
Adapt the script to the actual workflow. Do not promise deletion, access limits or processing arrangements that the organisation cannot deliver.
Explain the purpose and limits
State the specific work purpose, such as preparing action notes, supporting an authorised interview record or reducing duplicate note-taking. Explain that the AI output is a draft and may contain mistakes.
Make clear what the system will not do. It should not be described as judging emotion, attention, honesty, agreement or job performance unless a separately authorised and appropriate process genuinely exists. Do not imply that the recording replaces the official decision or human review.
Describe what will and will not be captured
Explain whether the full meeting or only selected sections will be recorded. Identify breaks, private side discussions or sensitive topics that will be excluded. Tell participants how they will know when recording starts, pauses and stops.
If a screen, chat, presentation or remote platform creates a separate recording or transcript, explain that separately. Avoid accidental duplicate records with different access and deletion rules.
Explain AI processing plainly
Participants should know whether audio will be transcribed, summarised, translated or converted into templates, mind maps or action lists. Explain that automated processing can mishear names, numbers, specialist terms and negative statements and that a responsible person will verify important details.
Where third-party or cloud processing is used, provide the organisation’s approved description rather than making assumptions about technical or legal arrangements.
State access, sharing and retention
Name the role or team that can access the raw audio and the people who may receive the final note. Explain whether a more widely shared summary will be redacted.
Give the intended retention period or the rule used to determine it. Distinguish the raw recording, draft transcript and approved meeting record because they may have different lifecycles.
Give participants real choices
Explain the available options without pressure:
- ask a question before recording starts;
- request a pause for a particular contribution;
- decline to be recorded where the process permits;
- provide information in writing;
- join a non-recorded follow-up;
- use a designated human note-taker;
- request clarification about access, correction or deletion procedures.
Do not treat silence, attendance or failure to leave the meeting as automatic agreement when the applicable process requires something more.
Handle hybrid meetings and late arrivals
Display a visible recording indicator in the remote platform where available. The chair should announce the recording to both in-room and remote participants and confirm that remote chat or platform transcripts are covered by the explanation.
When someone joins late, pause if necessary and give the same essential explanation before capturing their contribution. Record that the notice was repeated without collecting unnecessary personal detail.
Use an accessible participant notice
Keep sentences direct and avoid legal or technical jargon. Provide sufficient time for questions. Consider captions, translated information, large print, plain language or an individual explanation where needed.
For meetings involving children, vulnerable people, sensitive personal matters or people whose participation may not be fully voluntary, use the organisation’s specialist procedure and escalation route. A generic script is not a substitute for an appropriate safeguard.
Record what participants were told
The meeting record can note:
- notice version and date;
- when and how it was provided;
- the purpose and scope explained;
- the chair or responsible person;
- questions, objections or agreed alternatives;
- late-arrival notices;
- any approved exception.
Do not record speculative reasons for a participant’s concern. Capture only what is necessary to show the process followed.
Keep a pause and stop procedure
The chair should know how to pause the device immediately. When recording resumes, state that it has restarted and confirm the authorised scope. At the end, announce that recording has stopped before informal conversation begins.
If recording continues accidentally, protect the file, report the incident where required and follow instructions on deletion, retention and participant communication.
The NERALVO Halo AI Voice Recorder can support audio capture and DOWAY-generated transcripts, summaries and other structured outputs. The participant explanation should accurately describe the organisation’s chosen features, controls and retention—not every function the product can provide.
Participant-transparency checklist
- Was written notice provided in advance where practical?
- Was a truthful verbal explanation given before recording?
- Are purpose, scope and AI processing clear?
- Are access, sharing and retention described?
- Are choices and alternatives genuine?
- Are accessibility and language needs addressed?
- Are late arrivals covered?
- Is the notice version and any objection documented?
Ready to capture meetings properly?
View the NERALVO Halo AI voice recorder with 64GB local storage, meeting capture, compatible phone-call recording workflows and one year of DOWAY Max included.
View NERALVO Halo