TypeVelo.
← Guides Hub

Typing for Transcription Work

Transcription is the only common typing job where you do not set the pace. Everything else — writing, coding, data entry, chat — lets you go as fast or as slowly as you can. Transcription hands you a recording of somebody talking and asks you to keep up with them, which turns typing from a productivity question into a synchronisation one.

That single difference reorganises everything. A high burst speed is worth much less than it is elsewhere, because bursts do not help with a source that never bursts. Sustained accuracy at a fixed pace matters enormously, because falling behind compounds: every second lost has to be recovered while new audio keeps arriving.

This page covers what the work actually asks for, why the usual speed figures predict it badly, and which parts of it are trainable.

Speech is slower than typing, and that is not the problem

Conversational speech runs at a rate most competent typists can nominally match. The difficulty is not the average rate; it is that speech is uneven and typing has to absorb the unevenness.

A speaker produces a dense clause, then pauses, then produces three words, then trails off, then restarts. Your typing has to buffer the dense parts and use the pauses to catch up, which means you are constantly holding text you have heard but not yet written. The size of that buffer — how many words you can hold while your hands work through the previous ones — is closer to the real limiting skill than raw speed.

This is why a typist who scores well on a one-minute test can struggle badly with transcription and why someone with a modest figure can be excellent at it. The test measures the rate at which you can convert visible text into keystrokes. Transcription measures the rate at which you can convert heard speech into keystrokes while holding a queue.

Why the pause and rewind loop dominates

Nobody transcribes in real time from a single pass. The work is a cycle: play a few seconds, pause, type, rewind slightly, play again.

That cycle is where the time goes, and it is why foot pedals exist. A pedal moves play, pause and rewind off the keyboard and onto your feet, so your hands never leave home position to operate the audio. The gain is not the pedal press itself; it is the removal of a hand movement that would otherwise happen several times a minute, each one requiring the hands to find their position again afterwards.

The same logic makes keyboard shortcuts for playback control the minimum viable substitute if a pedal is not available, and makes a mouse-driven player the worst option by a wide margin. Anything that takes a hand off the keys costs the position-recovery time described in hand position and the home row, several times a minute, for hours.

What playback speed actually trades

Most transcription software will slow audio down, and the reflex is to treat that as a beginner's setting. It is closer to a throughput control.

Slowing to around 75% typically lets a transcriber type continuously rather than in the play-pause-rewind cycle, and continuous typing is far more efficient per minute of audio than a cycle that pays a restart cost every few seconds. The audio takes a third longer to get through, and the total time to a finished transcript often falls.

Speeding up works in the opposite direction and is useful for a different task — reviewing a transcript you have already produced, where you are checking rather than writing.

The practical rule is to pick the speed at which you stop needing to rewind. That is a different criterion from the speed at which you can just about keep up, and it is usually slower.

The parts that are not typing at all

A large share of transcription time is spent on decisions rather than keystrokes, and they are worth naming because they are invisible in any speed figure.

Spelling of names is the biggest. A proper noun you cannot spell stops the work completely and no amount of typing speed helps. Experienced transcribers keep a running list for each project and mark uncertain spellings for a single pass at the end rather than stopping each time.

Punctuating unpunctuated speech is the second. Speakers do not produce sentence boundaries; you decide where they go, and that decision cannot be made until you have heard enough of what follows. This is genuine cognitive load happening in parallel with typing, and it is why transcription is more tiring than its keystroke count suggests.

And formatting conventions — speaker labels, timestamps, inaudible markers — are typed constantly and are usually the same few strings. These are the strongest candidate for text expansion or shortcuts of any typing job, since the same handful of tokens accounts for a substantial fraction of the keystrokes.

What to practise

Sustained pace rather than peak pace. The relevant skill is holding one speed for a long stretch without drifting, which is exactly what the sustained pace drill trains and what a short test cannot measure. A twenty-minute endurance test is a better proxy for the work than any number of one-minute attempts.

Punctuation density, because transcripts are punctuation-heavy in a way ordinary practice text is not. Speaker labels use colons, quoted speech uses quotation marks, and hesitation markers use dashes and ellipses. The punctuation-heavy test and the sentence punctuation drill both target this directly.

And capitals, because proper nouns arrive constantly and shift timing is what produces stray capitals under pace. The capitals test will show you whether that is a weakness before it becomes an editing problem.

What is worth less than it looks: chasing a higher figure on ordinary prose. Beyond the point where you can comfortably exceed conversational speech, more peak speed does not shorten a transcription job.

How the work is actually priced, and why that matters

Transcription is generally paid per audio minute rather than per hour, which makes your ratio of working time to audio time the number that determines your earnings.

A common benchmark for clean single-speaker audio is somewhere around four working minutes per audio minute for someone competent, rising sharply with poor audio, multiple speakers, accents or technical vocabulary. Those multipliers vary enough between individuals and material that any single quoted figure should be treated as illustrative rather than as a standard.

The useful consequence is about where effort goes. If your ratio is dominated by rewinding, playback speed and pedal use are worth more than typing practice. If it is dominated by name lookups, a project glossary is worth more than either. Measuring which part of the cycle actually consumes your time is more valuable than improving the part that is easiest to measure.

Frequently Asked Questions

What typing speed do I need for transcription?

Enough to exceed conversational speech comfortably, after which more peak speed adds little. Sustained accuracy at a steady pace matters far more, because falling behind compounds while new audio keeps arriving.

Why does my test speed not predict how well I transcribe?

Because you are not reading. Transcription asks you to hold a queue of words you have heard while your hands work through the previous ones, and that queue is the real constraint.

Is a foot pedal worth it?

For regular work, generally yes — not for the pedal press itself but because it keeps both hands on the keys. Operating playback by hand costs a position recovery several times a minute for hours, and a mouse-driven player is the worst of the options.

Should I slow the audio down?

Usually yes. Aim for whatever pace lets you keep typing without ever going back — that beats keeping up and re-listening, even though the audio takes longer to get through.

What should I practise specifically?

Holding one pace over a long stretch, punctuation density, and capitals. Transcripts carry far more colons, quotation marks and proper nouns than ordinary practice text, and shift timing under pace is what produces stray capitals.