> ## Content Index
> Fetch the complete content index at: https://pulsecorp.co/blog/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to annotate an interview transcript, with a worked example
- URL: https://pulsecorp.co/blog/annotate-interview-transcript/
- Published: 2026-11-17T12:00:00.000Z
- Updated: 2026-11-18T04:38:50.000Z
- Description: Learn how to annotate an interview transcript: what to mark, a simple key your team can share, and a short worked excerpt that shows each kind of note.
- Author: Khyati Ojha

"Can you send me your notes on that interview?" asks a colleague who is taking over your study at a parcel delivery company. You have just read a transcript where a customer explains why they stopped using parcel lockers. What should you mark so your colleague can follow your thinking?

Marking up a page like this is how you annotate an interview transcript.

Keep the customer's words untouched, and add short notes beside them: the strong quotes, the surprises, the workarounds, the contradictions and anything to check later.

A shared key for those notes lets anyone on the team pick up the page and read it the way you did.

## The short version

- Never edit what the participant said; your notes live beside their words.
- Annotation is open noting while you read; coding comes later, with agreed labels.
- Mark five things: surprises, contradictions, workarounds, strong feelings and questions that may have shaped an answer.
- Put a line number on every note, so a theme can be traced to the exact words.
- Listen to the audio before you quote anything from an automatic transcript.

## What an annotated interview transcript is

When you read a transcript, you notice things: a sharp quote, an odd answer, a habit nobody planned for. An annotated interview transcript is the word-for-word record of an interview with those notices written beside it, in a separate layer, so the participant's words never change.

That separate layer matters because other people will read your notes later. It might be you in a week, a colleague taking over the study, or the person checking a finding against its source. Each of them needs to see what the customer said and, apart from it, what you thought about it.

Annotation is also different from coding. Annotation is open and personal: you write whatever strikes you, in your own words. Coding comes later, when the team tags passages with agreed labels from a [codebook](https://pulsecorp.co/glossary/codebook/), the shared list of labels and what each one means. Good notes are what the codebook gets built from.

Linguists use a much more formal notation for pauses, overlaps and tone, as in [discourse analysis](https://pulsecorp.co/glossary/discourse-analysis/). For customer research, plain notes with line numbers do the job.

## A short annotated excerpt, line by line

Seeing one page marked up is the quickest way to learn the habit. Here is a made-up excerpt from the parcel locker study, with line numbers on the left and the reader's notes on the right. Each kind of note appears once, so you can copy the pattern.

| Line | Who         | What was said                                                                              | Note                                                               |
| ---- | ----------- | ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------ |
| 1    | Interviewer | When did you last pick up a parcel from a locker?                                          |                                                                    |
| 2    | Customer    | A while ago. I don't use them anymore.                                                     |                                                                    |
| 3    | Interviewer | What changed?                                                                              |                                                                    |
| 4    | Customer    | The one by the station was always full, so my parcels went to a locker across town.        | Highlight: main reason. Nearest locker full, parcel sent elsewhere |
| 5    | Interviewer | What did you do then?                                                                      |                                                                    |
| 6    | Customer    | I started sending everything to my office. The front desk keeps it for me.                 | Margin note: workaround. Office desk replaces the locker           |
| 7    | Interviewer | How does that compare with the locker?                                                     |                                                                    |
| 8    | Customer    | The locker was great when it worked. I liked it.                                           | Contradiction: liked lockers, still stopped. Read with line 4      |
| 9    | Interviewer | You said "always full." What happened?                                                     |                                                                    |
| 10   | Customer    | Annoying. I got the message that my parcel was ready, walked there, and it had been moved. | Feeling: keep "Annoying" exact. Message and location did not match |
| 11   | Interviewer | Would you use lockers again?                                                               | Question shaped answer? Yes or no question, weigh lightly          |
| 12   | Customer    | If I knew in advance where it would go, yes.                                               | Check later: do others know about the move before it happens?      |

Read the notes alone and the story is already there. The customer liked lockers, stopped when parcels were moved to a far locker, and found a workaround at the office. The question to check in the next interviews is whether other customers hit the same surprise.

The notes also leave two things alone. They never rewrite line 10 into tidier words, and they never decide that "the locker network is too small." That is a finding, and one interview cannot carry it.

![A made-up transcript page with numbered customer lines on the left and matching notes on the right: highlight, margin note, contradiction, feeling and check later](https://pulsecorp.co/blog/content/images/2026/11/annotate-interview-transcript-3t4iu1.webp "The parcel locker excerpt as an annotated page. The customer's words stay as spoken; notes sit in their own column.")

The parcel locker excerpt as an annotated page. The customer's words stay as spoken; notes sit in their own column.

## Five things worth marking on every transcript

A full page of highlights helps nobody, because when everything is marked, nothing stands out. These five kinds of moments are worth a note on almost any customer interview, and each one shows up in the excerpt above.

### 1\. Surprises against what the team expected

Before you read, write down what the team thinks the answer is. In the parcel study, the team might expect people to quit lockers because they are far from home. A customer who lived next to one and still quit is a surprise, and surprises are where new findings start.

### 2\. Contradictions inside one person's answers

People often say two things that pull against each other, like the customer in lines 4 and 8\. Mark both lines and link them in one note. The gap between "I liked it" and "I stopped" is usually where the real reason sits.

### 3\. Workarounds people invent

A workaround is a step a customer takes that the service never planned for, such as the office front desk in line 6\. Workarounds show what people value enough to work for. They also show what the company is competing with, even when nobody calls it a rival.

### 4\. Strong feelings, in their exact words

When someone uses a strong word like "annoying," mark it and keep it exact. A [verbatim quote](https://pulsecorp.co/glossary/verbatim-quote/), the participant's words exactly as spoken, is what makes a finding believable later. A paraphrase such as "mildly frustrated" loses the force of what they said.

### 5\. Places where the question may have shaped the answer

Some answers come out of how the question was asked. Line 11 is a yes or no question, so the "yes" in line 12 carries less weight. Noting this is part of [reflexivity](https://pulsecorp.co/glossary/reflexivity/), which means being honest about how the research itself shaped what you heard.

## Agree a key, check the audio, then start coding

Notes from three people are hard to read if each person marks things differently. So before the team starts, agree a short key, check the transcripts against the audio where it matters, and decide when notes turn into codes.

A one-line key is enough. Give each note type a symbol or colour: highlight, margin note, contradiction, feeling, question to check. Add your initials to each note and a line number to every memo. A memo is a longer note about a whole interview or a pattern across several, written so someone else understands it without you. Annotate a copy or a comment layer, and keep the original transcript as it was. If your interviews follow [an annotated qualitative interview guide](https://pulsecorp.co/blog/qualitative-interview-guide/#:~:text=A%20qualitative%20interview%20guide%20is%20a%20flexible,it%20into%20a%20survey.), keep it open beside the transcript so you can see which question each answer came from.

Automatic transcripts are a draft, so listen to any passage you plan to quote. Word error rate is the share of words the software gets wrong. A [2025 systematic review of 29 studies](https://link.springer.com/article/10.1186/s12911-025-03061-0#:~:text=Reported%20word%20error%20rates,conversational%20or%20multi%2Dspeaker%20scenarios.) of speech recognition for clinical notes found word error rates from under 9% in controlled dictation to over 50% in conversations with several speakers. Names, product terms and short answers are where mistakes tend to hide, so mark them for a listen.

Then watch for repeats. When the same note shows up in transcript after transcript, such as "parcel moved without warning," it is ready to become a code in the codebook. Keep the line numbers with every code, so each theme can be traced back to the exact words. From there, the steps for [how to analyze qualitative data](https://pulsecorp.co/blog/how-to-analyze-qualitative-data-methods-steps-examples/) take over.

![Three boxes joined by arrows, notes then codes then themes, above a team key listing highlight, margin note, contradiction, feeling and check later](https://pulsecorp.co/blog/content/images/2026/11/annotate-interview-transcript-igy43g.webp "Notes become codes, and codes become themes, with the line number kept at every step.")

Notes become codes, and codes become themes, with the line number kept at every step.

If a note repeats across several transcripts, make it a code. If it appears once, keep it as a note and keep reading.

## Where Pulse fits

Annotation takes time, so it pays to spend that time on the surprises and contradictions, and less of it on waiting for transcripts and searching for quotes.

With [AI-moderated customer interviews on Pulse](https://pulsecorp.co/product/ai-interviews/#:~:text=Each%20interview%20arrives%20as,while%20the%20study%20runs.), every interview arrives as a full transcript alongside its recording, while the rest of the study is still running. You can start annotating the first interviews before the last ones finish, and play the recording beside any line you plan to quote. Personal data is redacted from transcripts, which makes annotated copies easier to share inside the team.

When the study ends, Pulse groups what participants said into themes, each with the quotes behind it, and every quote links to the transcript it came from. That gives your annotations a direct check: you can open a theme, follow a quote to its line, and compare it with your own notes.

You can try this on your own study with a free trial and a free study. To see it on your transcripts, [book a demo with Pulse](https://pulsecorp.co/demo/).

## Questions readers ask

### 1\. What is an example of a transcript annotation?

A short note beside a line that says what you noticed and why it matters. Next to "I started sending everything to my office," a note might read "Workaround: office desk replaces the locker." It names the type of note, says what happened in plain words and leaves the customer's words unchanged.

### 2\. Should annotations go on the transcript or in a separate document?

Keep them on a copy of the transcript or in a comment layer, so each note sits next to the line it is about. A separate document loses that link unless every note carries a line number. Whichever you choose, the original transcript stays untouched and everyone on the team can open the notes.

### 3\. Should two people annotate the same transcript?

For the first few interviews, yes. Two readers who annotate the same transcript and then compare notes find out quickly whether the key works and where they read things differently. Once their notes mostly match, each person can annotate their own share of the transcripts.

### 4\. How do I check that interview themes are backed by real quotes?

Follow each theme back to its quotes, and each quote back to its line in the transcript. If you annotated with line numbers, this is quick: the note, the code and the theme all point to the same words. A theme with no clear line behind it needs more evidence before anyone acts on it.