Research Interview Recording Checklist: Prepare Audio, Labels and Backups

A research interview recording checklist protects the interview from preventable audio failures and protects the participant from careless handling. It should connect the study protocol, participant agreement, equipment setup, file identity, backup plan and post-session handoff.

Use this as an operational companion to the approved research plan. It does not replace ethics review, organizational policy, applicable law, safeguarding procedures or the participant’s choices.

Assign recording roles before fieldwork

Name one recording owner for each session. That person checks authorization, starts and stops devices, monitors audio, labels files and completes the transfer log. A moderator who is already listening, probing and watching the participant may miss a quiet failure, so assign a separate producer or note taker when the study risk and staffing justify it.

Define who may:

• approve recording and any backup method;
• explain the recording to participants;
• operate and monitor each device;
• access the raw file and identity key;
• transfer, transcribe, review and delete copies;
• respond to withdrawal, disclosure or equipment incidents.

Use a research interview notes template to preserve observations and time markers without pretending notes are a verbatim record. Record role changes in the session log rather than relying on memory.

Confirm authorization and participant understanding

Check the approved protocol before inviting participants. Match the recording method, purpose, data types, storage location, access group, retention period and downstream uses to what was authorized. If the team wants to add video, a second recorder, automated transcription or a new vendor, route that change through the required review before using it.

Before recording begins, explain in accessible language:

• what will be captured and why;
• who will receive or review it;
• how it will be protected and retained;
• whether participation or recording is optional;
• how questions, corrections or withdrawal requests are handled;
• what cannot be guaranteed, such as removal of findings already irreversibly aggregated, if the approved process says so.

Follow the study’s documented consent method. A generic meeting recording consent form may offer useful operational prompts, but research teams must use the version approved for their study and population. Never infer agreement from silence or from joining a call.

Copy this pre-interview recording checklist

RESEARCH INTERVIEW RECORDING CHECKLIST

Study / session code:
Date, time and time zone:
Moderator / recording owner / note taker:

AUTHORIZATION
[ ] Current protocol and participant materials verified
[ ] Recording type and purpose are authorized
[ ] Backup method is authorized
[ ] Participant agreement will be confirmed before recording
[ ] Accessibility, interpreter and safeguarding needs checked

EQUIPMENT AND SPACE
[ ] Primary device charged, updated and in usable storage state
[ ] Approved backup tested and assigned
[ ] Microphone placement tested with representative voices
[ ] Room noise, notifications and interruptions controlled
[ ] Headphones and required adapters available
[ ] Device clocks synchronized

FILES AND HANDOFF
[ ] Session code and filename prepared
[ ] Approved transfer destination available
[ ] Access group and retention rule confirmed
[ ] Incident and handoff log ready
[ ] Temporary-copy deletion owner assigned

Complete the checklist close enough to the session that it reflects current conditions. A test performed weeks earlier does not prove the battery, cable, permissions or available storage are ready today.

Test the real recording chain

Test from the participant’s expected position through the microphone, device, application, file output and playback. A moving level meter only proves that some signal is entering the system. Record at least a short sample, stop it, locate the file and listen through headphones.

Ask both interviewer and a representative second voice to speak at normal volume. Check clarity, distance, room echo, clothing noise, table vibration and whether one voice overwhelms another. For remote interviews, verify the approved platform settings and whether local, cloud or separate-track capture is actually available to the assigned account.

Do not install unapproved software or change privacy settings minutes before an interview. If the chain fails, use the authorized fallback: reschedule, switch to notes only, move rooms or replace a tested component. The voice recorder for interviews guide can help compare practical placement and equipment factors, but the study’s security requirements control the choice.

Prepare the room, device and microphone

Reduce predictable interference without making the setting uncomfortable. Close doors where appropriate, silence notifications, disable voice assistants if required, move vibrating phones away from the table and tell nearby colleagues that a private session is in progress without revealing the participant’s identity.

Place the microphone on a stable surface away from cups, papers, fans and direct handling. Keep it close enough for clear speech but outside the participant’s personal space. If an interpreter joins, test all three voices and decide how turns will be identified.

Check battery, charging, storage, input selection, recording format and any automatic sleep or file-length limit. Keep power cables secured to avoid trips. If the discussion is remote, use headphones to prevent echo and confirm that screen sharing will not expose participant lists, messages or unrelated study data.

Define labels without exposing identities

Prepare the session code before the call. A useful filename pattern is STUDYCODE_PARTICIPANTCODE_YYYY-MM-DD_SESSION01_RAW. Keep names, email addresses, diagnoses, employment details or other unnecessary identifiers out of filenames because filenames often appear in sync logs, exports and support systems.

Maintain the code-to-identity key only when the protocol requires it, in a separate restricted location. The recording owner should not invent new abbreviations during fieldwork. Publish a short naming dictionary that defines date format, session numbering, raw versus redacted status and version rules.

Record the expected filename in the session log before starting, then compare it with the actual output. If a device generates its own name, rename only after safe transfer and preserve traceability from original to controlled filename. Never overwrite the only copy during relabeling.

Plan backups as controlled copies

A backup is useful only if it is tested, permitted and independently capable of capturing the session. It should not share the same likely failure as the primary method. Two applications on one overloaded laptop may fail together; two devices on the same unstable power supply may do the same.

Assign a backup owner and trigger. Decide whether the backup runs throughout or starts only after a primary failure. Document where it stores data, whether it uploads automatically and how it will be deleted if the primary succeeds. More copies increase confidentiality and retention work, so do not create extras by habit.

Use a simple decision table:

Start, monitor and stop deliberately

At the session opening, confirm participant identity using the minimum necessary method, repeat the approved recording explanation and obtain the required agreement. Then announce that recording is starting and verify the indicator. Do not capture informal pre-session conversation by default.

The recording owner should monitor discreetly without staring at the device. Watch level, elapsed time, battery and storage warnings. Note important time markers, interruptions, participant requests, sensitive off-record segments and technical events. If the participant asks to pause, acknowledge the request, stop capture and confirm when or whether it may resume.

At the end, ask whether the participant wants to add or clarify anything, then state that recording is stopping and verify that it stopped. Avoid discussing identifying logistics while the recorder is still running unless that content is intentionally authorized.

For interviews where recording is approved and participants have been clearly informed, Kuno can help turn captured audio into a reviewable draft transcript and notes. Researchers remain responsible for consent, access, interpretation and final evidence. Explore Kuno

Verify, transfer and log the file

Immediately after the session, confirm that the file exists, has plausible duration and can be played. Listen near the beginning, middle and end rather than assuming a visible waveform means the whole interview is usable. Do not edit the only source file to improve it.

Transfer through the approved encrypted or controlled route. Record session code, original and controlled filename, capture device, file size or other integrity evidence if required, source location, destination, transfer time, person completing it and person confirming receipt. Restrict access to the named group.

If transcription follows, the audio transcription software guide explains workflow considerations, while a research debrief template helps the team separate immediate interpretation from verified evidence. Do not upload research audio to a convenient personal tool merely because it is fast.

Handle failures and sensitive moments

Write incident triggers before fieldwork. Examples include accidental pre-roll, missing agreement, wrong participant code, unexpected third-party presence, disclosure requiring a safeguarding response, corrupted output, lost device or unauthorized synchronization.

When an incident occurs, stop unnecessary processing, preserve relevant evidence without spreading it, notify the designated owner and follow the study response procedure. Do not conceal a failure by recreating dialogue as a quotation. Label notes and recollections honestly.

The research lead decides whether the interview may continue, be repeated, be excluded or require further review under the approved process. A participant’s welfare and choices take priority over completing the planned question list. Document facts, decisions, owners and dates separately from speculation.

Complete final recording QA

Before marking the session ready for transcription or analysis, confirm:

• Participant agreement and any limits are documented.
• The actual capture matches the authorized method.
• Start, pause, resume and stop events are logged where relevant.
• The recording is playable across sampled points.
• The filename follows the study convention and avoids unnecessary identity data.
• The identity key, if needed, remains separate and restricted.
• Primary and backup copies are accounted for.
• Transfer destination and access group are correct.
• Temporary copies have an assigned deletion action.
• Technical or participant incidents have been escalated.
• Notes distinguish observations, summaries and direct quotations.
• A responsible researcher owns transcription and interpretation review.

Use recording support as part of a controlled research workflow. With authorized, consented capture, Kuno can draft transcripts and notes for human verification; it does not decide what participants meant or whether evidence is fit for a research conclusion. See Kuno