IRB Protocol Language for Recording + Transcription (Ready-to-Use Wording)

If your study includes audio or video recording, your IRB will usually want clear details on how you will record, transcribe, protect, and dispose of those files. The safest approach is to use plain, specific protocol language that explains what happens at each step, who can access the data, and when recordings will be deleted. This guide gives you ready-to-use wording researchers can adapt for the Methods or Procedures section, plus a checklist of common IRB attachments.

• Key takeaways
• IRB protocol language should explain recording, transcription, de-identification, storage, access, and destruction in simple terms.
• Your wording should match your actual workflow, tools, and study team roles.
• Consent materials and protocol text should say the same thing about recording and transcription.
• A short attachment checklist can help you avoid revision requests.

Why IRBs ask for detailed language about recording and transcription

Recording creates data that can directly identify participants through voice, image, name, or context. IRBs often ask for exact procedures so they can assess privacy risk, confirm that participants are informed, and see whether your safeguards fit the sensitivity of the study.

Good protocol language also helps your research team stay consistent. If your protocol, consent form, recruitment materials, and data security plan all use the same terms, review tends to go more smoothly.

What your IRB protocol should cover

Most protocols need to answer six practical questions. If you cover these clearly, you will usually address the main concerns tied to recording and transcription.

• How recording will occur.
• Whether audio, video, or both will be collected.
• How recordings will be transcribed.
• How identifiers will be removed or replaced.
• Where files will be stored and how they will be secured.
• Who can access the data and when files will be destroyed.

If your study includes health information, student records, or other regulated data, your institution may require extra wording. Check local policy and, when needed, align your protocol with rules such as the Common Rule.

Ready-to-use IRB protocol language for the Methods or Procedures section

Use the sample text below as a starting point, then replace bracketed text with your study details. Keep the wording accurate to your real process, since IRBs often compare this language with your consent form and security materials.

1) Recording procedures

Sample wording:

"With participant permission, the research team will audio-record [and/or video-record] study interviews, focus groups, or other research interactions using [device/platform]. Recordings are being made to support accurate data capture and analysis. Only research activities described in the consent process will be recorded. If a participant does not agree to recording, [describe alternative, if any, such as note-taking only or exclusion if recording is required for the study design]."

"At the start of each session, the researcher will confirm the participant's permission to record. Participants may request that the recording be paused or stopped at any time, to the extent described in the consent materials."

2) Transfer of recordings

Sample wording:

"After the session, recordings will be transferred as soon as feasible to [approved institutional storage location or encrypted system]. Recordings will not be stored on personal devices longer than necessary to complete secure transfer. Any temporary local copies will be deleted after transfer is confirmed."

"If remote conferencing software is used, recording settings will be configured to store files only in [approved location], when possible, and access will be limited to authorized study personnel."

3) Transcription method

Sample wording:

"Recordings will be transcribed using [manual transcription by study staff / a contracted transcription provider / automated transcription followed by human review / another method]. The purpose of transcription is to create a text record for coding, analysis, and audit of study procedures."

"If a third-party transcription provider is used, only the minimum necessary data will be shared for transcription. The provider will be instructed to handle study materials according to applicable confidentiality and data protection requirements, consistent with institutional policy and any required agreement."

Researchers who need a vendor workflow may also compare options such as transcription proofreading services when they need a reviewed text record rather than raw machine output.

4) De-identification procedures

Sample wording:

"Transcripts will be reviewed and de-identified by removing direct identifiers, such as names, contact details, student or employee numbers, medical record numbers, addresses, and other information that could directly identify a participant. When needed for analysis, participants will be assigned a study code or pseudonym. The key linking names to study codes will be stored separately from transcripts in a restricted-access location."

"If indirect identifiers or highly specific contextual details could reasonably reveal identity, the research team will redact or generalize that information in working copies used for analysis. Original source files will be retained only as described in the retention plan below."

5) Storage and security

Sample wording:

"Audio files, video files, transcripts, code keys, and related study documents will be stored on [institution-approved encrypted server / secure cloud environment / other approved system]. Access will require institutional login credentials [and multi-factor authentication, if applicable]. Study data will not be stored in unapproved personal accounts or shared through unapproved channels."

"Data will be protected using safeguards appropriate to the sensitivity of the study, such as encryption, password protection, role-based access, and separate storage of identifiers and research data. Security procedures will follow institutional requirements and any sponsor requirements that apply."

6) Access controls

Sample wording:

"Access to recordings, transcripts, and linkage files will be limited to authorized study personnel who need the information to perform study duties. This may include the principal investigator, co-investigators, approved research staff, and authorized compliance personnel if required for oversight."

"Team members will receive study-specific instructions on confidentiality, secure handling of files, and limitations on downloading, sharing, or copying data. Access permissions will be removed when a team member no longer requires access."

7) Retention and destruction plan

Sample wording:

"Recordings will be retained for [time period] and then permanently deleted, unless a longer retention period is required by law, sponsor terms, or institutional policy. De-identified transcripts will be retained for [time period] for analysis, verification, and any required recordkeeping."

"When destruction occurs, electronic files will be deleted from active systems and any other locations under the research team's control, consistent with institutional data disposal procedures. If a code key exists, it will be destroyed separately according to the same schedule or earlier, if permitted by the study design and recordkeeping requirements."

Boilerplate text you can adapt quickly

Some researchers need a shorter block that fits directly into a protocol form. The examples below are concise versions you can paste and edit.

Short boilerplate: audio-recorded interviews

"With consent, interviews will be audio-recorded to support accurate transcription and analysis. Recordings will be transferred to institution-approved secure storage and removed from the recording device after transfer is verified. Recordings will be transcribed by [study staff/vendor/method], then reviewed for accuracy and de-identified. Only authorized study personnel will have access to recordings, transcripts, and code keys. Recordings will be deleted after [time period], and de-identified transcripts will be retained for [time period] in accordance with institutional policy."

Short boilerplate: focus groups

"With consent, focus groups will be audio-recorded [and/or video-recorded] for transcription and analysis. Because focus groups involve multiple participants, the research team will instruct participants to respect the privacy of others, but confidentiality among participants cannot be fully guaranteed. Recordings and transcripts will be stored in an approved secure system, access will be limited to authorized study personnel, and identifying information will be removed from analysis copies when feasible. Recordings will be destroyed after [time period] and transcripts retained as described in the data management plan."

Short boilerplate: remote interviews

"Remote interviews will be conducted using [platform]. With participant permission, sessions will be recorded using approved settings and stored in [approved location]. The research team will download or transfer recordings to secure study storage as soon as feasible and will delete temporary platform or device copies when permitted by institutional policy. Transcription, de-identification, access controls, and retention will follow the procedures described in this protocol."

Common mistakes that lead to IRB revisions

Many IRB comments come from gaps between what the protocol says and what the team plans to do. These are common problem areas to check before submission.

• Consent and protocol do not match. If the consent form says recordings will be destroyed in 30 days, the protocol should not say one year.
• The transcription method is vague. Name whether staff, automation, or a third party will create the transcript.
• Storage details are too broad. "Stored securely" is usually not enough without naming the approved system or controls.
• No plan for identifiers. State what you will remove, what you will keep, and where the linkage file will live.
• No backup plan for non-recorded participants. If recording is optional, explain whether you will take notes instead.
• No third-party documentation. If an outside vendor handles data, your IRB or institution may ask for contract or security documentation.
• Retention periods are missing. Give a clear timeline for recordings, transcripts, and code keys.

If you plan to compare manual and machine workflows, it can help to separate convenience from record quality. For example, some teams use automated transcription for speed, then apply review and de-identification before analysis.

Checklist of IRB attachments commonly needed

Attachment needs vary by institution, but this checklist covers items IRBs often request when a study involves recording and transcription. Use it as a pre-submission review tool.

• Updated consent form that clearly states whether sessions will be recorded.
• Script or consent language explaining why recording is needed and whether participants may refuse.
• Data security plan naming storage systems, encryption, access controls, and destruction timelines.
• Data management plan describing transcription, de-identification, and retention.
• Third-party agreement, confidentiality agreement, or service documentation if an outside transcription provider will access study data.
• Recruitment materials, if they mention recording or remote platforms.
• Interview guide or focus group guide, if required by your IRB.
• HIPAA authorization or related privacy documents, if applicable.
• Platform or software documentation if your institution requires review of remote tools.
• Amendment form, if you are adding recording or transcription to an already approved study.

If your project will create captions or subtitles from research recordings for education or dissemination, keep that use separate in the protocol and consent materials. Different outputs may need different review, especially when recordings could be identifiable.

Common questions

Do I need to name the transcription vendor in the IRB protocol?

Many IRBs do not require the vendor name in the main protocol, but they do expect you to describe whether a third party will access recordings or transcripts. Your institution may also require a separate agreement or review document.

Should I say that transcripts are fully anonymous?

Only if that is truly accurate. In many studies, transcripts are de-identified rather than anonymous because a linkage file may exist for part of the study.

Can I keep recordings forever for future research?

Only if your consent, protocol, and institutional rules allow it. If you plan future use, say so clearly and explain what form of the data will be retained.

What if a participant asks not to be recorded?

Your protocol should explain the alternative. You might use note-taking only, or you might state that recording is required if the study design depends on a verbatim record.

Do I need separate language for audio and video?

Yes, if the risks differ. Video often raises higher identification concerns, so your protocol should say when video is necessary and how you will protect it.

How specific should the destruction plan be?

Be as specific as your institution expects. Include what will be destroyed, when it will happen, and whether any de-identified transcripts or code keys will remain.

Can I use automated transcription for human subjects research?

That depends on your institution, data sensitivity, and approved safeguards. If you use it, say so in the protocol and explain the review, de-identification, and security steps that follow.

Final tip: make your protocol match your real workflow

The best IRB protocol language is not the most formal wording. It is the wording that clearly describes what your team will actually do, from the moment recording starts to the moment files are deleted.

Before you submit, compare your protocol, consent form, data security plan, and any vendor documents side by side. A simple consistency check can prevent avoidable revision requests and help your study team handle recordings and transcripts the right way.

If your research workflow includes outside transcription support, GoTranscript provides professional transcription services that researchers can review against their own IRB, consent, and data handling requirements.