Let them speak: collecting and reviewing audio and video responses in many languages

Let them speak: collecting and reviewing audio and video responses in many languages

When someone can answer in their home language and by speaking, you often learn more in two minutes of audio than you would from a page of written answers.

Collecting spoken responses is one of the simplest ways to make participation easier for people who are not comfortable writing in English. It is especially useful for parents, service users and residents who can explain nuance more naturally when they speak. The catch is the back office. Audio and video files feel heavier and harder to review. This article shows how to offer short media replies without creating a huge new burden on staff.

Why offer audio and video at all

Spoken responses can change the conversation in three ways:

  • They lower the effort barrier. Speaking is faster and less intimidating than writing, especially in a second language.
  • They capture tone and emphasis, which helps you interpret meaning where a literal translation might not.
  • They reveal issues people might not type out, like local practicalities or emotional reactions.

At the same time, if you simply attach a folder full of mp4s to your inbox and ask colleagues to listen to them, nothing will get done. The aim is to design the participant experience and the review process so both sides are quick and respectful.

Design questions so spoken answers work

Spoken answers need slightly different prompts from written ones. Keep these principles in mind.

  • Keep prompts short and singular. Ask one thing per question so answers stay concise.
  • Ask for a time-limited reply. People answer more directly when you give them a one or two minute expectation.
  • Offer examples of what to say. A short script helps people get started.
  • Avoid jargon and long clauses. Short sentences translate better and are easier to transcribe.
  • Give the option to record a short summary plus a longer explanation. This makes review easier.

Examples:

  • Less useful prompt: Tell us everything about your journey to the clinic, including any problems and what you think should change.
  • Better prompt: In one or two minutes, tell us about your last visit to the clinic. What worked well? What one change would make it better?

  • Less useful prompt: Describe your experience using our website and any accessibility issues you found.

  • Better prompt: In about one minute, tell us one thing you found easy and one thing you found difficult when using the website.

These small changes make answers shorter, easier to transcribe and more actionable.

Low-friction ways to collect media

Choose collection methods that fit the people you are asking and the devices they use.

  • In-browser recording: The easiest option for participants. No app install, records directly from a phone or laptop, and submits alongside the survey.
  • File upload: Use when people already have a voice note or video. Accept common formats like mp3, m4a and mp4.
  • WhatsApp or messaging: Common in many communities. If you accept replies this way, make sure you have a consistent process to move files into your secure system.

Practical settings and tips to reduce friction:

  • Limit length to 1 or 2 minutes by default. Longer files increase storage and slow staff review.
  • Offer automatic compression so uploads are small but still clear.
  • Accept mobile-friendly formats: mp3/m4a for audio, mp4 for video.
  • Warn participants about data use and offer a Wi-Fi upload option if files are large.

Simple participant guidance you can copy:

  • Record for about 60 seconds if you can. Short answers help us act faster.
  • Find a quiet spot and hold the phone close to your mouth.
  • If you are sending a video, hold the phone sideways and make sure your face is lit from the front.

Consent wording should be short, clear and visible just before recording.

Example micro-consent:

I agree that my recording will be used to help improve services. Staff may transcribe and translate it for review. My name will not be shared without my permission.

If you need more detail, link to a longer privacy statement. Always allow people to opt out and give an alternative such as a short written answer.

Automatic transcription and translation - useful, not perfect

Automatic transcription and machine translation are the tools that make reviewing spoken responses scalable. Use them, but with an expectation of imperfection.

What they do well:

  • Convert audio to searchable text quickly so staff can skim content.
  • Produce a translated transcript so non-speakers can understand the gist.

What to watch out for:

  • Accuracy drops with background noise, heavy accents, dialects and domain-specific words.
  • Punctuation and sentence boundaries may be wrong, which can change meaning.
  • Translation can miss cultural nuance or the intended emphasis.

Practical rules:

  • Use transcripts as a first pass, not a final record. Listen to the original recording if the transcript raises doubts.
  • Keep the original audio or video attached to the response for verification.
  • Allow participants to check or correct their transcript where possible.

If a response contains technical or legal wording, plan for human review before you act on it.

A simple review workflow staff will actually use

The best workflows assume staff have limited time. Make the first pass as quick as scanning emails.

  1. Triage new media replies daily or a few times a week. Mark any potential safety issues for immediate follow-up.
  2. Read the translated transcript first. If it looks clear, add tags and a one-line summary without listening to the file.
  3. If the transcript is unclear or the response is sensitive, listen to the audio and correct the summary.
  4. Add a confidence score to each summary: High, Medium, Low. This helps others know when to verify the original file.
  5. Use short clips for sharing. If a colleague needs to hear a point, export a 20-30 second clip rather than a full file.
  6. Archive original media after 6 to 12 months according to your retention policy, unless you have consent to keep it longer.

This process keeps people from needing to listen to every minute of every file and still preserves the option to verify when it matters.

Fail-safes for privacy and accessibility

Make sure the convenience you offer does not create new barriers.

  • Offer a text alternative. Some participants may prefer to type or need assistive technology.
  • Make captions available for videos and share transcripts by default.
  • Allow anonymous submissions when appropriate, and minimise personal data collection.
  • Use access controls so only authorised staff can play original media.
  • Encrypt files in transit and at rest and set a clear retention schedule.
  • Give participants a clear way to ask for deletion of their recording.

If responses might contain sensitive personal information, flag them for specialist review and avoid automatic sharing.

Quick checklist to get started

  • Decide whether you will accept audio, video or both.
  • Set a clear maximum recording length, such as 60 or 120 seconds.
  • Provide short participant instructions and micro-consent text.
  • Use in-browser recording where possible to reduce friction.
  • Enable automatic transcription and translated transcripts for admin review.
  • Build a triage-and-tagging workflow so staff can skim and act quickly.
  • Put storage, access control and retention rules in place before you start collecting.

Start small, iterate, and learn from the recordings

Begin with a small pilot: one question, a one month window and a simple triage workflow. Compare response rates and the quality of insight with your written-only approach. Ask staff how long it takes to review each reply and adjust the recording length or review steps accordingly.

Hearing people in their own voices can change what you hear and what you decide to do next. With short prompts, clear consent, sensible limits and a transcript-first review process, you can make spoken responses practical and powerful without creating extra admin work.

Fiona Fernandes

Fiona Fernandes

Engagement & Insights Lead

Fiona Fernandes is Engagement & Insights Lead at Hearo. She writes about multilingual communication, inclusive feedback, and practical ways organisations can hear from more of the people they serve. Her focus is on making surveys and community engagement easier to take part in, easier to understand, and more useful for everyone involved.