IRB Amendment Guide: Adding Recording/Transcription After Approval (Step-by-Step)

You need an IRB amendment when you want to add audio/video recording or transcription after your study is already approved because it changes what you collect, how you collect it, and how you protect it. Submit the change before you start recording, update all affected study documents, and tell participants in a clear, consistent way. This guide walks you through what to change, why it matters, and a step-by-step checklist, plus example amendment language you can adapt.

Primary keyword: IRB amendment guide

Key takeaways

• An amendment is usually required if you add recording, add a transcription vendor/tool, or change how you store/share audio or transcripts.
• Update the protocol, consent/assent, recruitment materials (if they mention recording), data management/security plan, and any scripts or interview guides.
• Explain what changed, why you need it, new risks (often privacy), and exactly how you will reduce those risks.
• Do not begin recording or sending files for transcription until the IRB approves the amendment.
• Plan how you will communicate the change to current participants (re-consent vs. notification) and document what you did.

When an IRB amendment is required (and when it might not be)

You generally need an IRB amendment any time you change approved procedures, data collection, or privacy protections. Adding recording or transcription almost always qualifies because it adds a new data type (audio/video) and often adds new handling steps (transfer, storage, transcription, access).

Common changes that require an amendment

• Adding audio recording to interviews, focus groups, or calls that were previously notes-only.
• Adding video recording (even if you only plan to transcribe audio) because video increases identifiability.
• Adding transcription, whether done by staff, an automated tool, or an external service.
• Changing data storage (new platform, cloud drive, new encryption method, longer retention, different access roles).
• Changing confidentiality language in consent forms, or adding new limits to confidentiality.
• Changing the study team (new personnel who will access recordings/transcripts).
• Changing how you de-identify (e.g., now you will remove names from transcripts, or you will keep a linkage file).

Changes that may be handled as a minor modification (IRB-specific)

Some IRBs treat low-impact edits as “administrative changes,” like fixing typos or clarifying wording without changing meaning. Even then, if the edit touches recording, transcription, or data security, most IRBs will still want it submitted as an amendment because it affects privacy.

Decision rule you can use

• If the change alters what data you collect, how you collect it, who can access it, where it lives, or how long you keep it, assume you need an amendment.
• If participants would reasonably want to know about it before agreeing, treat it as a consent-relevant change and submit an amendment.

What to include in the amendment: what changed and why it’s needed

Most IRB amendment forms ask for a summary of the change and a rationale. Keep it plain and specific so a reviewer can quickly see what is new, what stays the same, and what risks or burdens changed.

Describe “what changed” in concrete terms

• Old process: “Interviews were documented using handwritten notes only.”
• New process: “Interviews will be audio recorded and transcribed to text for analysis.”
• Scope: “All interviews” vs. “only a subset” vs. “only if participant agrees.”
• Tools/workflow: how you will record, transfer, transcribe, store, and delete.

Explain “why it’s needed” in participant-focused language

• Improve accuracy of quotes and reduce reliance on memory or incomplete notes.
• Support consistent coding and analysis across the research team.
• Reduce the time participants spend repeating or clarifying information.

Name the new or changed risks (often privacy) and how you reduce them

• Risk: Recording can contain identifiers (names, voices, locations, employers).
• Mitigation: Limit access, use secure storage, de-identify transcripts, and delete recordings on a schedule.
• Risk: A transcription step adds another “copy” of the data.
• Mitigation: Control file movement, track versions, and restrict who can download or share files.

Documents to update (and what to add to each)

When you add recording/transcription, you usually need to update more than the protocol. Make a list of every participant-facing and internal document that mentions data collection or confidentiality, then revise them to match the new workflow.

1) Protocol / research plan

• Add a recording section: what you record (audio/video), when, and who starts/stops recording.
• Describe transcription: who does it, what format you store, and quality checks (if any).
• Update data management: storage location(s), access controls, retention, and deletion.
• Update privacy protections: de-identification process and linkage file handling (if used).

2) Consent form (and assent, if applicable)

• State that recording will happen (or that it is optional) and what happens if someone declines.
• Explain transcription in simple terms: “We will turn the recording into a written transcript.”
• List who will hear/see recordings and who will read transcripts.
• Explain how long you will keep recordings and transcripts and when you will delete them.
• Explain how you will use direct quotes, if you plan to use them, and how you will protect identity.

3) Recruitment materials

• If you mention “interview” or “focus group,” add a short line that sessions may be recorded.
• Keep recruitment simple and save details for consent, but avoid surprises.

4) Interview/focus group scripts and moderator guides

• Add a script line: ask permission, confirm recording start, and remind participants they can pause.
• Add instructions for handling sensitive moments (pause recording, offer to go off-record).

5) Data security plan / confidentiality plan

• Where recordings will be uploaded and who has access.
• How files will be named (avoid using full names or identifiers in filenames).
• How transcripts will be stored and how you will remove identifiers.
• How you will share data within the team (no personal email, no unapproved drives).

6) HIPAA-related documents (only if your study involves PHI)

If your project involves protected health information, adding recording/transcription may affect your HIPAA authorization or waiver materials. Use your institution’s privacy office guidance, and follow the HIPAA Privacy Rule requirements in 45 CFR 164.

How to submit the amendment (step-by-step)

IRB systems vary, but the reviewer usually wants the same core items: a clear change summary, updated documents with tracked changes, and a plan for telling participants.

Step 1: Confirm the change details and scope

• What will be recorded (audio only vs. audio+video).
• Which study activities will be recorded (screening, consent, interview, follow-up).
• Whether recording is required or optional.
• Who will transcribe (study team, automated tool, or a service).

Step 2: Map the data flow end-to-end

• Capture → transfer → storage → transcription → de-identification → analysis → sharing → retention → deletion.
• List every person or role who touches the files at each step.

Step 3: Update documents (and keep them consistent)

• Revise the protocol first, then align consent, scripts, and security materials to match it.
• Use version dates on every document so the IRB can tell what changed.
• Use tracked changes or a redline if your IRB prefers it.

Step 4: Write the amendment summary like a reviewer checklist

• One paragraph: what changed.
• One paragraph: why you need it and what stays the same.
• Bullets: risks and mitigations.
• Bullets: documents updated (file names + version dates).

Step 5: Plan participant communication (re-consent vs. notification)

• New participants: use the revised consent going forward.
• Already enrolled participants: decide whether you need re-consent before recording or whether a written notification is enough.
• Key factor: whether the change affects what they agreed to in a meaningful way (recording often does).

Step 6: Submit through your IRB portal and respond to stipulations

• Upload the amendment form and every updated document.
• Answer reviewer questions with direct references to the exact document section you updated.
• Do not implement the change until you receive IRB approval, unless your IRB explicitly allows otherwise.

Checklist: adding recording/transcription to an approved study

• Define what you will record (audio/video) and when recording starts and stops.
• Decide whether recording is optional and how you will proceed if someone declines.
• Document the transcription method (team member vs. automated vs. service).
• Map the full data flow (capture → deletion), including access permissions.
• Update protocol sections: procedures, risks, benefits, confidentiality, data storage, retention.
• Update consent/assent: recording, transcription, quote use, retention, optionality.
• Update recruitment text if it could surprise people later.
• Update interview scripts to include recording permission and a pause/stop option.
• Update data security/confidentiality plan: storage, access, file naming, transfer method.
• Prepare participant communication plan for already-enrolled participants.
• Create a document list with version dates and upload everything in the amendment submission.
• Wait for approval before recording or transcribing.

Example amendment language: adding recording and transcription

Use these as starting points and adjust to match your IRB templates and your actual workflow. Keep language consistent across the protocol, consent, and scripts.

A) Amendment summary (for the IRB application)

• Change requested: “We request approval to audio record study interviews and to create written transcripts from those recordings for analysis.”
• Rationale: “Recording and transcription will improve accuracy of data capture and support consistent qualitative analysis.”
• Impact on participants: “Participants will be informed about the recording and transcription process during consent and may request that recording be paused or stopped.”
• Privacy protections: “Access to recordings and transcripts will be limited to the approved study team. We will remove direct identifiers from transcripts when feasible and store files in a secure, access-controlled location. We will delete recordings according to the retention schedule described in the protocol.”

B) Protocol language (procedures + data management)

• Recording procedure: “With participant permission, interviews will be audio recorded using [device/app]. Recording will start after consent and will stop at the end of the interview or at any time upon participant request.”
• Transcription: “Audio recordings will be transcribed into text for analysis. The transcript will be reviewed by the study team for completeness and to remove direct identifiers when feasible.”
• Storage and access: “Recordings and transcripts will be stored on [approved secure system] with access limited to [roles]. Files will be labeled using a study ID rather than participant names.”
• Retention and deletion: “Audio recordings will be deleted after transcription and verification, or by [timeframe], whichever occurs first. Transcripts will be retained until [timeframe] and then deleted/destroyed.”

C) Consent form language (plain-language)

• Recording: “If you agree, we will audio record the interview so we do not miss anything you say.”
• Optionality (choose one):
  • Optional: “You can still be in the study if you do not want to be recorded. In that case, we will take written notes instead.”
  • Required: “You must agree to be recorded to take part in this interview.”
• Transcription: “We will make a written transcript from the recording. The transcript is a typed copy of what was said.”
• Confidentiality: “We will store recordings and transcripts in a secure location. Only the research team will have access.”
• Quotes: “We may use short quotes in reports or publications. We will not use your name in those quotes.”
• Stopping: “You can ask us to pause or stop the recording at any time.”

D) Participant notification / re-consent message (for already enrolled participants)

• “We are updating the study to include audio recording and transcription of interviews to improve accuracy.”
• “This does not change the topics we will discuss, but it changes how we capture what you say.”
• “If you choose to continue, we will review the updated consent information with you before any recording begins.”
• “You may decline recording (if optional) or withdraw at any time without penalty.”

Pitfalls to avoid (and how to prevent delays)

Most amendment delays happen when the IRB sees a mismatch between the protocol and the consent form, or when the privacy plan is vague. These are common issues you can fix before submission.

Mismatch across documents

• Pitfall: Protocol says “audio recorded,” but consent never mentions recording.
• Fix: Use a single source of truth (the protocol) and mirror it in consent and scripts.

Unclear data retention and deletion

• Pitfall: “We will store recordings securely” with no timeline.
• Fix: Specify when you delete recordings and how long you keep transcripts.

Overpromising confidentiality

• Pitfall: Saying “no one will ever hear the recording” when transcription requires access.
• Fix: Say who will access files and why, and describe safeguards.

Not addressing group settings

• Pitfall: Recording focus groups without addressing that other participants may repeat what was said.
• Fix: Add a clear confidentiality reminder and set expectations for group privacy limits.

Starting the change before approval

• Pitfall: Recording “just a few” sessions while the amendment is pending.
• Fix: Wait for approval and keep a written log of when the new procedure starts.

Common questions

• Do I need an amendment if I only want to record for note-taking and won’t keep the files?
  Usually yes, because recording still changes what you collect and may change risk, even if you delete it later.
• Can I make recording optional without an amendment?
  If recording was not in the approved materials, adding it as optional still changes the study procedures and typically needs an amendment.
• Do I need to re-consent participants who already completed interviews?
  If you will not record them retroactively, you may only need to document that the change applies going forward, but your IRB may still want a communication plan for active participants.
• What if a participant agrees to be recorded but later asks to stop?
  Build a clear process into your script: stop recording on request and explain what happens to the portion already recorded, consistent with your consent language and IRB approval.
• How should I handle identifiers in transcripts?
  State whether you will remove names/places during transcript cleaning, who will do it, and whether you will keep a linkage key, then keep that plan consistent across documents.
• Does adding transcription change my exemption status?
  It can, depending on what you record, identifiability, and how you store data, so confirm with your IRB before assuming your category stays the same.
• Are there federal rules I should reference?
  If you operate under U.S. human subjects rules, your IRB may reference the Common Rule at 45 CFR 46, but your institution’s policies and IRB guidance should drive your exact submission.

Choosing a transcription approach (team, automated, or professional)

When you add transcription, the IRB will want to know who creates the transcript and how you control access. Pick an approach that fits your timeline, sensitivity level, and internal policies.

• Study team transcription: Highest control, but it takes time and requires training for consistent formatting and de-identification.
• Automated transcription: Faster for drafts, but you still need a review plan, especially for names, technical terms, and sensitive content. See GoTranscript automated transcription options if your protocol allows it.
• Professional transcription: Helpful when you need clean, readable transcripts on a defined schedule, but you still need to describe how you will share files and limit access.

If you plan to send recordings outside your institution, confirm what your IRB and contracts office require (for example, confidentiality terms, secure transfer methods, and limits on reuse). Keep your amendment language aligned with what you will actually do.

When you are ready to implement recording and transcription in a way that matches your approved protocol, GoTranscript can support your workflow with professional transcription services that you can describe clearly in your IRB materials, along with your study’s data handling and participant communication plan.