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

If your study includes audio or video recording and transcription, your IRB protocol should explain exactly what you will record, who will access it, how you will de-identify it, and when you will destroy it. Clear protocol language helps reviewers assess privacy risk and helps your team follow the same process from consent to final deletion.

Below, you’ll find ready-to-use wording researchers can adapt for the Methods or Procedures section, plus practical decision points, common mistakes to avoid, and a checklist of attachments many IRBs ask for.

• Key takeaways
• State what you will record, why recording is needed, and whether recording is optional.
• Describe your transcription method in plain language, including any vendor or software used.
• Explain de-identification, storage, access controls, and the retention and destruction timeline.
• Make sure your consent form, data security plan, and any third-party agreements match the protocol.

What IRB reviewers usually want to see

Most IRBs look for a simple, complete description of the data lifecycle. That means collection, transcription, de-identification, storage, access, sharing, and final destruction or retention.

If you leave out one of those steps, reviewers often send the protocol back for clarification. The easiest fix is to write your process in the same order the data moves through your study.

Include these points in your protocol

• Whether you will record audio, video, or both.
• What device or platform you will use for recording.
• Why recording is necessary for the study.
• Whether participants can refuse recording and still participate.
• Who will create transcripts.
• Whether transcripts will be verbatim, edited, or summarized.
• How you will remove direct identifiers.
• Where files will be stored and whether storage is encrypted.
• Who will have access to recordings and transcripts.
• How long you will keep each file type.
• How recordings and transcripts will be destroyed.

Ready-to-use IRB protocol language for recording and transcription

Use the sample text below as boilerplate and adapt it to fit your institution’s rules, your study design, and your actual workflow. Replace bracketed text before you submit anything to your IRB.

1) Recording procedures

Sample wording: Interviews or focus groups will be audio-recorded [and/or video-recorded] to support accurate capture of participant responses. Recording will occur using [institution-approved recorder, encrypted device, secure videoconference platform, or other approved method] only after the participant has provided informed consent.

Participants will be informed that recording is for research documentation and transcription purposes. If a participant declines recording, [describe whether they may still participate and what alternative documentation method will be used].

2) Transcription method

Sample wording: Recordings will be transcribed into text for analysis. Transcription will be completed by [research team members / an institution-approved transcription provider / approved transcription software], and the transcript will be reviewed by the research team for accuracy and completeness.

If a third-party service is used, only the minimum necessary data will be shared to complete transcription. The protocol, consent materials, and any required institutional agreements will identify the use of the third party.

If you need outside support, some teams use professional transcription services and then review the transcript internally before analysis.

3) De-identification procedures

Sample wording: Following transcription, the research team will remove direct identifiers from the transcript, including names, contact details, locations, employer names, and other information that could reasonably identify a participant. Each participant will be assigned a unique study code, and the code key will be stored separately from the research data.

Any quotations used in reports, presentations, or publications will be reviewed to reduce the risk of indirect identification. If a quote contains unique details that could identify a participant, those details will be generalized, redacted, or not used.

4) Storage and security

Sample wording: Audio/video recordings, transcripts, and the code key will be stored on [institutionally managed encrypted storage / secure research drive / approved cloud environment]. Files will not be stored on personal devices or unencrypted removable media unless specifically approved by the institution and protected by encryption and access controls.

Data transmission, if needed, will occur only through institution-approved secure methods. Storage and handling procedures will follow applicable institutional data security requirements.

If your institution requires a specific security framework, align your wording with that standard. For example, U.S. teams often refer to their institutional requirements and, where health data is involved, the HIPAA Security Rule.

5) Access controls

Sample wording: Access to recordings, transcripts, and the code key will be limited to authorized study personnel listed on the protocol and trained in confidentiality procedures. Access permissions will be role-based and limited to the minimum necessary for study activities.

Third parties, if used for transcription or technical support, will receive access only to the files needed for their task and only under approved institutional terms. They will not be authorized to use the data for any purpose outside the study.

6) Retention and destruction plan

Sample wording: Identifiable recordings will be retained only as long as necessary to complete transcription, quality review, and any required research documentation, unless a longer retention period is required by law, sponsor terms, or institutional policy. After that point, recordings will be securely deleted or destroyed using institution-approved methods.

De-identified transcripts will be retained for [insert time period] in accordance with institutional policy and the study recordkeeping plan. The file linking participant identities to study codes will be retained separately and destroyed when it is no longer needed for study administration, follow-up, or audit requirements.

How to adapt the wording for your study

The best protocol language is specific enough to be real, but flexible enough to match what your team will actually do. If your workflow changes after approval, you may need an amendment.

Choose the right level of detail

• Name the recording method if you already know it.
• Name the transcription approach only if you expect to use that exact approach.
• Avoid promising immediate deletion if your team needs time for quality review.
• Avoid saying data is anonymous if you record identifiable voices or faces at collection.

Adjust for common study types

• Interviews: Explain who records, where files upload, and when transcripts are checked.
• Focus groups: State that confidentiality among participants cannot be fully guaranteed.
• Remote sessions: Name the approved platform and say whether cloud recording is enabled.
• Video studies: Explain why video, not just audio, is necessary.
• Multilingual studies: State whether recordings will be transcribed in the source language and whether translation will follow. If needed, some teams also use audio translation service support as a separate step.

Keep protocol and consent aligned

Your consent form should match your protocol on recording, optional participation, third-party use, storage, and retention. Mismatched wording is a common reason for revision requests.

If your study also needs accessible outputs for video-based research materials, separate services such as closed caption services may need their own review under your institution’s process.

Common pitfalls that slow IRB approval

Many delays come from vague language, not from the study itself. Reviewers want to know exactly how you will protect participants when recordings and transcripts are involved.

• Saying files will be kept in a “secure location” without naming the approved system.
• Not explaining whether recording is required or optional.
• Using “anonymous” when data starts as identifiable.
• Forgetting to mention third-party transcription or AI tools.
• Not separating the code key from de-identified transcripts.
• Missing a retention period or destruction method.
• Leaving the consent form inconsistent with the protocol.
• Promising confidentiality without noting the limits in focus groups or online platforms.

IRB attachment checklist for recording and transcription studies

Many IRBs ask for supporting documents beyond the protocol narrative. Use this checklist before you submit or amend your study.

• Updated consent form that clearly states recording details.
• Recruitment materials that match the consent and protocol.
• Interview guide or focus group script, if required by your IRB.
• Data security plan.
• Data flow summary showing collection, transcription, storage, access, and deletion.
• Third-party agreement, service agreement, or institutional review document for outside transcription providers.
• Business associate or data processing agreement, if required by your institution or law.
• List of study team members with roles and access levels.
• Confidentiality training documentation, if your institution requests it.
• Amendment summary if you are adding recording or transcription after initial approval.

Quick pre-submission check

• Does the protocol say what will be recorded and why?
• Does it identify who will transcribe and how?
• Does it explain de-identification in concrete terms?
• Does it name the approved storage location?
• Does it limit access to listed study staff?
• Does it include a clear retention and destruction plan?
• Do the consent form and protocol say the same thing?

Common questions

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

That depends on your institution. If you already know the vendor and your IRB expects third-party disclosure, include it and make sure your consent materials match.

Can I call my transcripts anonymous if I remove names later?

No. If you collect identifiable voices, faces, or direct identifiers at the start, the data is identifiable at collection even if you later de-identify it.

Should recordings be deleted right after transcription?

Only if that matches your real process and institutional rules. Many teams need a short review period to check transcript accuracy and complete documentation.

What if participants do not want to be recorded?

Your protocol should state whether they can still participate and how the researcher will document responses instead. Your consent form should say the same thing.

Do I need separate language for video recording?

Yes, if you collect video. Video increases identifiability, so explain why it is necessary, how it will be stored, and who will see it.

What should I say about AI transcription tools?

Say whether you will use them, what data will be uploaded, who will review outputs, and what security and access rules apply. Do not leave AI use implied or unstated.

What if my institution has its own template language?

Use it as your starting point. Then add the operational details reviewers need for your specific workflow, especially for transcription, de-identification, and deletion.

Final tip

Good IRB protocol language for recording and transcription is plain, specific, and consistent across every study document. If a reviewer can follow your data from recording to destruction without guessing, your submission is in much better shape.

If your study needs transcripts as part of that workflow, GoTranscript provides the right solutions, including professional transcription services that teams can fit into their documented research process.