TranskribatorTranskribator
A transcription style guide: names, numbers, pauses and unclear speech
Editorial standard

A transcription style guide: names, numbers, pauses and unclear speech

How to make a short transcription style guide for speaker labels, names, numbers, timecodes, pauses, unclear passages and exceptions.

The Transkribator team5-minute read
SOURCECONSISTENT TEXT CONVENTIONSSpeakers:Names:Numbers:Unclear speech:FROM WORDS TO RESULTS
Working with a real recordingIllustrated training exampleTemplate to copy
Editorial standard

A style guide reduces arbitrary differences between files

Without an agreed rule, one editor writes “Speaker 1,” another uses a name, and a third merges remarks. A number appears in words in one passage and in digits in another. These differences make searching, quoting and comparing versions harder even if each choice is acceptable on its own.

A useful guide is short and reflects the team’s actual work. It need not reproduce a full reference on Russian usage. Focus on the decisions that cause the most disagreement in your own recordings.

Workflow

Build rules from recurring points of disagreement

  1. Collect examples of inconsistency

    Take several transcripts and list cases handled differently. Keep private client material out of the shared guide by replacing examples with fictional teaching excerpts.

  2. Describe the decision and its basis

    For every case, define a default, a permissible exception and a check. For example, use a name after confirming it against the recording or attendee list. Use a neutral label until then.

  3. Show examples of what to use and what to avoid

    Two short examples explain a rule faster than an abstract definition. Show when a timecode is required, what [inaudible 00:12:08] looks like and how to mark a speaker change.

  4. Assign an owner for revisions

    Include the version, date and person who approves new rules. If an exception keeps recurring, update the guide so the decision is easy to find. Revise past material only if separately requested and after assessing the effect.

Worked example

Reviewing one disputed passage

This is a fictional training example. The names, circumstances and outcomes are included solely to explain the method.

Excerpt from a training recording · 12:40
Maria: We sent twenty-five kits. [pause] No, twenty-six. One was returned to the warehouse.

The correction matters in the finished text. If project rules call for digits for measurable quantities, write “25 … no, 26” in a verbatim transcript, or “We sent 26 kits. One was returned to the warehouse” in an edited paraphrase.

Mark the pause only if it matters for the task. Use the name “Maria” only after verification. The fictional excerpt shows why a guide should cover both numbers and self-corrections.

Speakers: stable labelsNames: only afterverificationNumbers: one ruleUnclear speech: marker andtimecodeEach rule includes an example, an exception and a check
Four groups of rules cover most editing discrepancies in working transcripts.
ItemStandardException / check
SpeakerConsistent labelKeep a label for an unidentified speaker
NameVerified spellingAvoid inferring it from a job title
NumberFormat for the taskPreserve self-corrections
InaudibleMarker + timecodeListen again
Ready-to-use template

Style guide template

Fill in the sections you actually need and add one example to each.

Template for your workSelect and copy
Name and version:
Purpose:
Speaker label format:
Verifying names:
Numbers, dates and units:
Timecodes:
Pauses and emotions:
Unclear speech:
Overlapping speech:
Self-corrections:
Direct quotes and paraphrases:
Exceptions:
Who approves changes:
Check the result

Check whether the rules work in practice

  • Every rule makes sense without an oral explanation.
  • There is a safe teaching example and an exception.
  • Unclear passages lead to verification instead of guesswork.
  • The document has a version and an owner.
ExamplesReal discrepanciesRulesDefault and exceptionApplicationConsistent formattingVersionUpdates and review
A style guide grows out of recurring cases and remains testable through examples.
Frequently asked questions

A closer look

How long should the guide be?

Long enough to capture common decisions without having to look through messages. Start with one or two pages and expand when recurring cases arise.

Should old transcripts be corrected?

Record the new rule version and decide separately which old material needs to be updated.

Keep working with the recording