All tasks

Transcribing testimonies and interviews

Turning recorded interviews and testimonies into text, without the recording ever leaving your organisation.

Outcome

A searchable draft transcript linked to the original recording, with every passage used in public or legal work checked by listening.

Data gate

  • Public: a published speech or broadcast can use a cloud or local route after account review.
  • Internal: a staff meeting or non-public interview needs an approved organisation account or a verified local route.
  • Identifiable: testimony, protected sources, and recordings that reveal identity or location stay on an organisation-controlled device in a verified local workflow.

Use AI when

  • A draft transcript will save time and a person can listen back.
  • The language, audio quality, and speaker overlap are tested on a short sample first.
  • The output remains linked to the audio and is never treated as the record by itself.

Do not use AI when

  • The only available route uploads protected audio to a consumer cloud service.
  • Nobody can review the language or identify speakers correctly.
  • The recording must be deleted, altered, or detached from its chain of custody.

Workflow

  1. Prepare: classify the recording, confirm consent, copy it to an approved non-synced folder, and test one non-sensitive minute.
  2. Process: transcribe locally where the recording is sensitive, preserving time references.
  3. Verify: listen to every quotation and check names, places, numbers, dates, and negations.
  4. Store: keep the checked transcript, audio, reviewer, and corrections under the same access controls. Remove temporary working copies.

Human verification checklist

  • The correct recording, language, and speakers were used.
  • Every quotation was confirmed against its exact audio passage.
  • Names, numbers, places, and the words that reverse meaning were checked.
  • The working folder is not synced to a personal cloud account.

If it fails

Try a clearer sample, a more suitable model, or speaker-by-speaker sections. If the error rate still makes review slower or unsafe, stop and transcribe manually. Do not repair uncertain testimony by guessing.

Start next

Follow the offline recipe below. is a local engine, but the device, folder, and model still need to be checked before sensitive use.

Prompts for this task

  • Controlled route

    Clean up a transcript without changing what was said

    25 minutes · Gives you short sections

    Do not paste this into a cloud tool.

    Answer in [ANSWER LANGUAGE], even if the material below is in another language.
    
    Below is a machine transcript of a recorded interview, and it stays on my own computer, so work only with what is here and keep the whole answer local. Clean it up for reading.
    
    You may:
    - Fix punctuation, capitalisation and the obvious spelling of the names I list below.
    - Remove filler sounds and repeated false starts.
    - Keep the speaker labels exactly as they are.
    
    You may NOT:
    - Complete an unfinished sentence.
    - Replace a word you think was misheard.
    - Reorder anything.
    - Remove a repetition that carries meaning.
    
    Keep every [inaudible] marker and its timestamp where it is.
    
    Give me, in this order:
    A. The cleaned transcript.
    B. A list of every change you made that was more than punctuation, with the original wording beside it.
    C. The lines you could not make sense of, quoted, so a person can listen again.
    
    Names and terms spelled correctly: [LIST THE NAMES AND PLACES]
    
    Transcript:
    [PASTE THE TRANSCRIPT]
    How to use it
  • Redact first

    Turn messy meeting notes into checkable minutes

    15 minutes · Gives you short sections · Works on a phone

    Answer in [ANSWER LANGUAGE], even if the material below is in another language.
    
    You are writing the minutes of a meeting from one person's rough notes. Work only from the notes below.
    
    Rules:
    1. Never invent a decision. If the notes do not say a decision was taken, it was not taken.
    2. Never assign an action the notes do not assign. Give one role per action, exactly the role the notes name, and where the notes name none write "No owner in the notes".
    3. Never invent a date. Where the notes give no date, write "No date in the notes".
    4. Copy names, figures and dates exactly as the notes write them. Do not correct them.
    5. Anything you are unsure about goes in section D. Do not guess in A, B or C.
    6. Keep every section short. One line per item.
    
    Give me, in this order:
    A. Decisions taken. One line each, with who decided it as the notes record it. Where the notes say only "the meeting", write that.
    B. Actions. One line each: what is to be done, the one role the notes assign it to, and the date the notes give.
    C. Discussed without a decision. One line each.
    D. Unclear in the notes. One line each: what is missing or contradictory, and which section above it would belong to.
    
    Notes:
    [PASTE YOUR NOTES]
    How to use it
  • Redact first

    Write a community summary you can read aloud

    20 minutes · Gives you a message to send · Works on a phone

    Answer in [ANSWER LANGUAGE], even if the material below is in another language.
    
    Write a short message that goes back to the people who attended a community meeting. It will be read aloud as well as sent, so write it to be spoken.
    
    Rules:
    1. Use no personal name, not even a first name. Say "the organisers", "a participant", "the health office".
    2. Use no direct quotes. Write what was agreed, not who said what.
    3. Promise nothing the notes do not contain. Where the notes do not say who will do a thing, write that it is not decided yet.
    4. Short sentences, plain words. No jargon and no abbreviation a first-time reader would not know.
    5. Where a date, a place or a figure is not in the notes, leave a clear gap marked [ADD BEFORE SENDING] instead of filling it in.
    
    Give me one message, in this order, with no heading longer than one line:
    A. What the meeting was about, and how many people came if the notes say so, in two or three sentences.
    B. What was decided. One short sentence each.
    C. What happens next, including the date of the next meeting, and what is still open.
    D. How to raise something the meeting missed, in two sentences, using the contact line I paste below.
    
    Notes:
    [PASTE YOUR NOTES]
    
    Contact line for the last paragraph:
    [HOW PEOPLE CAN REACH YOU]
    How to use it
  • Public material only

    Build an interview guide from your topics

    15 minutes · Gives you a checklist · Works on a phone

    Answer in [ANSWER LANGUAGE], even if the material below is in another language.
    
    I have an interview tomorrow. Build a guide from the topics below. The person I will interview may have lived through hard events, so every question must be open, must not suggest its own answer, and must not ask for a detail we do not need.
    
    Rules:
    1. Write no question that carries its own answer. The words of the answer you expect must not appear in the question.
    2. Ask for no identifying detail beyond what the topic needs. No exact address, no full name of a third person, no employer, no date of birth.
    3. Ask about events and sequence, not about feelings the person has not offered.
    4. Every question must be answerable with a refusal. Add no question that assumes the person will continue.
    5. Invent no organisation name, no project name and no place where the recording will be kept. Leave each of those as a gap marked [FILL IN BY HAND].
    6. Plain words. One idea per question.
    
    Give me, in this order:
    A. An opening script to read aloud: who I am, what the interview is for, where the recording and the notes will be kept, that the person may stop at any moment or skip any question, and how to withdraw consent later. Plain language, under 150 words, no legal terms.
    B. Eight to twelve questions, grouped under the topics below, each with one follow-up question under it.
    C. Questions to avoid, six at most, each with its reason in three or four words: suggests the answer, reopens the harm, or asks a detail we do not need.
    D. A closing script: what happens next, and one sentence checking the person is still comfortable with what they gave.
    
    Topics:
    [LIST YOUR THREE OR FOUR TOPICS]
    How to use it

Tools that help with this

Step-by-step guides for this

Last checked: 2026-09-01