Retention Schedule Template for Audio, Transcripts, and Consent Forms

A retention schedule tells your team how long to keep research audio, transcripts, consent forms, and analysis files, and when to delete or archive them. Use it to match your IRB approval, consent language, funder rules, and institutional policy before you collect or transcribe data.

• Set retention periods before data collection starts.
• Separate raw audio, identifiable transcripts, anonymized transcripts, consent forms, and analysis files.
• Match every date to your IRB approval and institutional policy.
• Document deletion, archiving, and exceptions for audit trails.

Key takeaways

• A retention schedule template should name each data type, owner, storage place, retention period, and disposal method.
• Audio often carries more identity risk than a cleaned transcript, so it may need a shorter retention period.
• Consent forms may need a different retention rule because they prove participant permission.
• IRB approval, consent forms, grants, contracts, and institutional policy must agree.
• A disposal checklist helps you delete files fully and record what happened.

What a research retention schedule should include

A research retention schedule is a simple control document. It explains what data exists, where it lives, who owns it, and what happens to it after the approved retention period ends.

For studies with interviews, focus groups, oral histories, or recorded sessions, the schedule should cover more than transcripts. Audio, consent forms, field notes, codebooks, exports, and analysis files can all carry risk.

Use this core structure

• Data category: Audio, video, transcript, consent form, analysis file, or related document.
• Identifiability: Identifiable, coded, de-identified, or anonymized.
• Storage location: Approved server, encrypted drive, research platform, or archive.
• Access owner: Principal investigator, project manager, data steward, or records office.
• Access group: Named team members or approved roles.
• Retention period: Exact time period or event-based trigger.
• Retention trigger: Study closeout, publication, last participant contact, grant end, or IRB closure.
• Disposal action: Secure deletion, shredding, transfer to archive, or long-term preservation.
• Documentation: Deletion log, archive receipt, approval note, or records ticket.

Define your terms before you set dates

Teams often confuse de-identified and anonymized data. A coded file can still link back to a person if a key exists.

An anonymized file should not contain direct identifiers or a practical way to re-identify the participant. If your institution uses strict definitions, use those exact terms in the schedule.

Retention schedule template for audio, transcripts, and consent forms

The template below gives common categories and decision points. Replace every bracketed item with your IRB-approved wording, institutional rule, or project-specific date.

Do not copy the sample retention periods without checking your local policy. Some institutions, sponsors, journals, and laws require longer or shorter periods.

Template table

Copy-ready retention schedule fields

• Project title: [Insert project title]
• IRB protocol number: [Insert number]
• Principal investigator: [Insert name]
• Data steward: [Insert role or name]
• Schedule approved by: [Insert IRB, records office, sponsor, or PI approval]
• Effective date: [Insert date]
• Review date: [Insert date]
• Retention trigger: [Study closeout / publication / grant end / last data collection / other]
• Exceptions: [Legal hold / participant withdrawal / sponsor request / archive deposit / other]

How to align the schedule with IRB approval and institutional policy

Your retention schedule should not create new promises after the study starts. It should reflect what your IRB, consent materials, contracts, and institution already allow.

If these sources conflict, pause before deleting or keeping data longer. Ask your IRB office, records office, data protection officer, or sponsor contact for written guidance.

Step 1: Pull the controlling documents

• IRB application and approval letter.
• Consent forms, assent forms, and recruitment materials.
• Data management plan.
• Grant or sponsor agreement.
• Institutional records retention policy.
• Data security and acceptable-use policy.
• Repository or archive terms, if you plan to share data.

Use the most specific rule first when it clearly applies. For example, a study consent form may promise that audio will be destroyed after transcription.

Step 2: Compare promises and requirements

Create a short crosswalk with one row for each data category. Note what each source says about storage, access, sharing, withdrawal, retention, and destruction.

• If consent says “audio will be deleted after transcription,” your schedule should not keep raw audio for future analysis unless you amend approval and consent if needed.
• If policy says consent forms must be kept for a set records period, do not delete them just because audio files are deleted.
• If a sponsor requires data retention, check whether that includes identifiable data or only final research records.
• If participants can withdraw data, keep the linking key only as long as needed and approved to honor that right.

Step 3: Use the stricter safe option when unsure

Sometimes one document says “at least” a certain period, while another says “until transcription is complete.” These may apply to different file types.

Do not solve this by guessing. Keep a written decision note and get approval from the right office before changing retention periods.

Step 4: Update the IRB when the schedule changes

A change in retention can affect participant risk. Many IRBs expect an amendment when researchers keep identifiable data longer, share it differently, or add future use.

The U.S. Office for Human Research Protections explains federal human subjects protections under the 45 CFR 46 regulations. Your institution can add stricter local rules.

Practical disposal checklist

Disposal is not just pressing delete. You need to remove approved files from active storage, backups when policy allows, shared folders, devices, and vendor workspaces.

Use this checklist at the end of transcription, study closeout, archive transfer, or the approved retention period.

Before disposal

• Confirm the retention trigger has happened.
• Check the IRB protocol, consent form, and institutional policy one more time.
• Confirm no legal hold, audit, complaint, publication review, or sponsor request applies.
• Confirm no pending participant withdrawal or correction request depends on the file.
• Identify the final approved version to keep, if any.
• List all copies, drafts, exports, downloads, and backup locations you can control.

During disposal

• Delete raw audio or video files from approved storage when the schedule requires it.
• Delete temporary transcription drafts, notes, and duplicate exports.
• Delete identifiable transcripts after approved de-identification, if the schedule says so.
• Remove files from shared drives, local computers, sync folders, email attachments, and portable media.
• Ask approved vendors or service providers to confirm deletion when your agreement requires it.
• Shred paper consent forms only after their required retention period ends.
• Transfer files to an approved archive only when consent, IRB approval, and policy allow it.

After disposal

• Record what was deleted, archived, or retained.
• Record who approved the action and who completed it.
• Record the date, method, storage location, and file category.
• Keep the disposal log in the project records location.
• Update the data inventory and access list.
• Notify the PI, data steward, or records office if your policy requires it.

Documentation steps for audit trails

An audit trail should show that your team followed the approved plan. It should also explain exceptions without exposing more participant data than needed.

Keep the audit trail separate from sensitive data when possible. Give access only to people who need it for study oversight, records management, or compliance.

Keep these records

• Data inventory: A list of file categories, locations, owners, and versions.
• Retention schedule: The approved version and any later revisions.
• Crosswalk: Notes showing how the schedule matches IRB approval, consent language, sponsor terms, and policy.
• Access log: Names or roles with access to restricted files.
• Version log: Dates for raw, draft, cleaned, de-identified, and final files.
• De-identification checklist: Steps used to remove or reduce identifiers.
• Disposal log: Date, file category, method, approver, and person completing disposal.
• Exception log: Legal holds, IRB amendments, sponsor instructions, or archive transfers.

Use clear file naming

File names can leak identity if they include participant names. Use study IDs, dates, and version labels instead.

• Avoid: Maria_Garcia_interview_sensitive_topic_audio.mp3
• Use: P014_interview_audio_2025-03-12_raw.mp3
• Use: P014_transcript_2025-03-15_deidentified_v2.docx
• Use: StudyA_disposal_log_2025-Q2.xlsx

Protect the audit trail too

Audit records can still contain sensitive clues. A disposal log that lists participant names, diagnoses, locations, or case details can create new risk.

Use participant IDs where possible. Store the ID key separately and delete it when the retention schedule allows.

Common pitfalls when keeping or deleting research files

Most retention problems come from vague plans, duplicate files, or missed promises in the consent form. You can avoid these issues with early planning and simple controls.

Pitfall 1: Treating all files the same

Raw audio, identifiable transcripts, anonymized transcripts, and consent forms do not carry the same risk. They also may not have the same retention rule.

Separate the categories in your template. Give each one its own owner, storage location, and disposal action.

Pitfall 2: Keeping audio “just in case”

Audio can reveal voice, emotion, names, background sounds, and other details. If you do not need it after transcription and quality review, your schedule may call for deletion.

If you want to keep audio for future use, include that plan in the IRB materials and consent language before collection when possible.

Pitfall 3: Forgetting transcription drafts

Draft transcripts, exports, and proofreading files can contain the same identifiers as final transcripts. Do not leave them in downloads folders or email threads.

If you use outside support, choose a process that fits your data handling needs. GoTranscript offers human transcription services for teams that need transcripts as part of a controlled workflow.

Pitfall 4: Deleting consent forms too early

Consent forms prove what participants agreed to. Many projects need to keep them longer than raw recordings or draft files.

Store them separately from the data when possible. This limits the chance that a person can connect identity to responses.

Pitfall 5: Ignoring backups and synced folders

Files may copy themselves into cloud sync folders, device backups, analysis tools, or email systems. Your disposal checklist should cover each location your team can control.

For secure deletion concepts, the U.S. National Institute of Standards and Technology provides guidance in NIST SP 800-88 Rev. 1. Your institution may define which methods you must use.

How to choose retention periods for each data category

There is no single retention period that fits every study. Your decision depends on participant risk, consent promises, research needs, audit needs, and institutional rules.

Use the questions below to make defensible choices. Then write the answer into your schedule in plain language.

Questions for raw audio and video

• Do you need the recording after transcription and quality review?
• Did participants consent to audio storage after transcription?
• Does the recording include faces, voices, names, or sensitive background details?
• Will anyone need the recording for translation, verification, or dispute review?
• Can an anonymized transcript meet the research need instead?

Questions for identifiable transcripts

• What identifiers must remain for analysis?
• When will direct identifiers be removed or replaced?
• Who can access the identifiable version?
• Do coded speaker labels still connect to a linking key?
• When can the identifiable version be deleted?

Questions for anonymized transcripts

• Is the transcript truly anonymized, or only de-identified?
• Could rare roles, events, or locations still identify a participant?
• Does consent allow future use, teaching, sharing, or archiving?
• What metadata will travel with the transcript?
• Does the archive or repository require a specific format?

Questions for consent forms

• What does institutional policy require for consent record retention?
• Do sponsor, legal, or regulatory rules add a longer period?
• Where will signed forms live during the study?
• Can you store consent forms separately from response data?
• How will you record withdrawal or limits on future use?

Questions for analysis files

• Do coded excerpts include identifiers or sensitive context?
• Does your qualitative analysis software store files in an approved location?
• Can you export a clean archive copy?
• What files support publications or audits?
• Which temporary files should be deleted after project closeout?

Common questions

Can we delete audio right after transcription?

Yes, if your IRB approval, consent form, institutional policy, and research needs allow it. Many teams wait until transcription quality review ends so they can correct errors.

Should consent forms be stored with transcripts?

Usually, it is safer to store consent forms separately from transcripts. This reduces the chance that identity and research responses sit in the same place.

What is the difference between de-identified and anonymized transcripts?

De-identified transcripts remove or reduce identifiers, but a code key or context may still allow re-identification. Anonymized transcripts should not have a practical path back to the participant.

What if the consent form and institutional policy disagree?

Do not guess. Ask your IRB office, records office, sponsor contact, or data protection officer for written guidance before you retain, delete, or share the data.

Do we need to document deletion of drafts?

Yes, if drafts contain study data or identifiers. A simple disposal log can show that temporary transcription files, exports, and duplicates were removed as planned.

Can anonymized transcripts be kept forever?

Only if your consent language, IRB approval, institutional policy, and archive plan allow long-term retention. Also check whether the transcript is truly anonymized.

What should a disposal log include?

Include the file category, storage location, disposal date, method, approver, person who completed the action, and any exception. Avoid listing participant names unless policy requires it.

Final checklist before you approve the schedule

• Each data category has its own retention rule.
• Audio, transcripts, consent forms, linking keys, and analysis files are listed separately.
• The schedule matches the IRB approval and consent wording.
• Institutional policy and sponsor terms have been checked.
• Access roles and storage locations are named.
• Disposal methods are clear and realistic.
• Audit trail records are defined before deletion starts.
• Exceptions and amendments have a written approval path.

A clear retention schedule protects participants and makes research records easier to manage. If transcription is part of your workflow, GoTranscript provides the right solutions through professional transcription services that can support your project’s document process.