Recorded Interview Consent Forms: What to Include

A recorded-interview consent form should help a participant understand the complete data journey—not merely authorise a microphone. It should describe the real project, technology, people, uses, withdrawal limits and deletion process in plain language.

This guide explains what organisations and researchers should consider including. It is general information, not a universal legal template. Adapt the form to the project, lawful basis, ethics approval, participants and jurisdiction.

Use a participant information sheet and consent record together

The information sheet explains the project in enough detail for an informed choice. The consent form or recorded consent captures the participant’s decisions. A page of tick-box statements cannot repair inadequate information.

The Health Research Authority and Medical Research Council provide current guidance on designing proportionate participant information and consent materials rather than relying mechanically on a template. See the HRA guidance on informing participants and seeking consent.

1. Identify the project and responsible organisation

Include:

• Project title.
• Researcher or interviewer name.
• Sponsor, employer or institution.
• Data-controller identity where relevant.
• Contact details.
• Ethics or approval reference.
• Complaint or independent contact route.

2. Explain the purpose in plain language

State what the interview is trying to understand and how the information will be used. Avoid broad phrases such as “research and related purposes” unless the scope is explained.

3. Describe what will happen

• Interview format and expected duration.
• Location or online platform.
• Topics.
• Audio, video or both.
• Whether questions can be skipped.
• Whether the participant can pause or stop.
• Any foreseeable discomfort or risk.

4. Describe the recording technology

Explain:

• The recorder or approved platform.
• Whether audio is stored locally.
• Whether it is synced or uploaded.
• Whether AI transcription or summarisation is used.
• The supplier’s role.
• Whether human reviewers may access the file.
• Whether automated analysis or coding occurs.

Do not say “securely processed” without describing the meaningful safeguards.

Consent and lawful processing are not identical

In data protection, consent is one possible lawful basis, but some organisations rely on another basis while still obtaining ethical or contractual agreement to record. Use the form required by the relevant legal, research and organisational framework.

5. Explain who can access each record

6. Explain identity and quotation choices

State whether:

• Real names will be used.
• Pseudonyms will be assigned.
• Job title or location will be generalised.
• Direct quotations will appear.
• Participants can review quotations.
• Voice clips may be published.
• Complete anonymity can or cannot be guaranteed.

Distinctive quotations and contextual details may identify someone even after names are removed.

7. Separate the choices

Use distinct statements where appropriate:

• I agree to participate in the interview.
• I agree to audio recording.
• I agree to approved AI transcription.
• I agree to anonymised or pseudonymised quotation.
• I agree to identifiable quotation.
• I agree to public use of audio clips.
• I agree to deposit in a controlled archive.
• I agree to future research use.

Only include choices the project can genuinely administer. Do not hide optional public or future uses inside one broad checkbox.

8. Explain voluntariness and power imbalance

Participation should be free from pressure. Explain that declining optional recording or withdrawing should not affect employment, care, education, benefits or services where that assurance is true.

Where the interviewer is a manager, teacher, clinician, service provider or authority figure, add safeguards appropriate to the imbalance.

9. State withdrawal rights and limits honestly

Specify:

• How to withdraw.
• The contact route.
• The withdrawal deadline.
• Which files will be deleted.
• What cannot be withdrawn after anonymised aggregation, publication or archive deposit.
• Whether legal or safeguarding duties may require retention or disclosure.

Do not promise unlimited withdrawal when the project cannot deliver it.

10. Explain confidentiality and its limits

Describe who will receive identifiable information and circumstances that may require action, such as immediate danger, safeguarding concerns or a legal obligation. Avoid promising absolute secrecy.

11. Explain retention and destruction

Provide meaningful dates or events for:

• Raw audio.
• Draft transcript.
• Final transcript.
• Consent evidence.
• Re-identification key.
• Research archive.
• Exports and backups.

12. Explain sharing, international processing and future use

State whether data will be shared with collaborators, funders, clients, archive services or suppliers, and whether processing occurs outside the UK. Explain future use precisely enough for an informed choice.

13. Explain data-protection rights and complaints

Where applicable, include the right-to-information details, contact for access or correction requests, data-protection officer and route to complain to the ICO. Do not imply every right applies without qualification.

14. Make the form accessible

• Use short sentences and clear headings.
• Provide large print, Easy Read, audio or translated versions where needed.
• Allow time for questions.
• Use an interpreter or advocate appropriately.
• Check understanding rather than merely obtaining a signature.

Written, electronic and verbal consent

A signature is not the only method. UKRI notes that verbal consent may be ethically preferable in some contexts, including where written evidence could create risk. The method and justification should be approved and documented. See the UKRI research-consent guidance.

Where verbal agreement is permitted, use a clear script, capture the participant’s answers, record the information-sheet and consent-form versions and store the evidence with the interview metadata.

Example modular consent wording

“I have read or had explained to me the participant information dated [date/version]. I have had an opportunity to ask questions. I understand that the interview will be audio recorded for [specific purpose]. I understand that [approved service] will create a transcript and that [roles] may access the audio or text. I understand how quotations, withdrawal, retention and deletion will work. I voluntarily agree to the choices I have selected below.”

The wording must be adapted to the real project and reviewed through the required legal or ethics process.

Consent version control

Record:

• Information-sheet version.
• Consent-form version.
• Date provided.
• Date consent obtained.
• Method.
• Person obtaining consent.
• Participant’s selected options.
• Later withdrawals or changes.

When the technology, supplier, purpose or publication plan changes, assess whether participants need updated information or renewed consent.

How NERALVO Halo fits recorded interviews

Check Halo specifications before applying this guidance provides NOTE mode, supported CALL mode, 64GB local storage, up to 35 hours of recording and Bluetooth connection to DOWAY. DOWAY supports transcripts, summaries, templates, translation, mind maps and exports, with one year of DOWAY Max included.

Participant materials should describe the actual use selected by the project. Do not promise local-only processing when audio will be synced to DOWAY, and do not imply that every generated output is necessary.

Frequently asked questions

Is a signed form always enough?

No. Consent must be informed, specific and voluntary, and the project must operate as described.

Can one checkbox cover recording, publication and future use?

Bundling optional purposes can undermine genuine choice. Separate them where appropriate.

Can participants withdraw forever?

State realistic limits, especially after anonymisation, publication or archive deposit.

Should the participant receive a copy?

Providing the current information and a record of their choices supports transparency and accountability.

Must the form name the AI supplier?

Provide enough accurate information about the processing and recipients for an informed choice. The required detail depends on the context and privacy information.

Consent-form checklist

• Project and controller identified.
• Purpose and procedure clear.
• Recording and AI technology described.
• Access and suppliers explained.
• Identity and quotation plan stated.
• Optional uses separated.
• Voluntariness and power imbalance addressed.
• Withdrawal deadline and limits honest.
• Confidentiality limits explained.
• Retention and destruction specified.
• Sharing and future use described.
• Accessible format provided.
• Version and evidence recorded.

Bottom line: the strongest consent form is not the longest. It gives participants a clear, accessible and honest choice about what will happen from the first recorded word to final deletion or approved archive.