Prepare for the RMR by training decisions, not just pace. Pre-commit protocols for unknown names, rapid numbers, and unparseable phrases so nothing at the machine requires deliberation. Choose strokes deliberately between brief forms and phonetic writes based on what you actually own. Keep your dictionary conflict-free by scoping entries, and measure progress with a hesitation log rather than accuracy scores alone.
Why raw speed alone stalls: the hesitation cascade
Speed alone is not the skill being built. The RMR-level difficulty is the hesitation cascade: when you pause to decide a stroke, every following word arrives while your fingers are still idle.
At faster dictation, the buffer between your writing and the speaker's voice shrinks. On shorter, slower takes you can drop a word and rejoin within a clause; at advanced speeds a two-second deliberation costs a full sentence, and re-entering mid-thought means your next strokes lack context. The cascade matters because errors cluster: one pause produces three or four dropped words, and reconstructing them from memory afterward is far less reliable than capturing them live.
The remedy is decision speed, trained alongside raw pace. Before a take, decide what you will do with an unknown name (phonetic placeholder), a rapid number (digit protocol), and a phrase you cannot parse (write what you hear and move on). During the take, enforce the rule without exceptions. Afterward, review the audio and grade your decisions, not just your accuracy: a take with clean strokes and one freeze tells you more than a perfect slow take.
Writing tight versus writing for transcription: choosing strokes on purpose
Writing tight maps words and phrases to brief strokes to cut stroke count. Writing for transcription tolerates more phonetic, multi-stroke renderings. RMR-level dictation forces you to switch between the two deliberately.
A brief form is a single stroke standing for a whole word; a phrase stroke compresses several words into one stroke; a multi-stroke phonetic write spells a word out. Tight writing reduces finger travel and stacking risk and frees mental bandwidth for the next clause. The tradeoff: every brief you deploy must already live confidently in your hand and your dictionary. An unfamiliar brief costs you exactly the deliberation you were trying to save.
Practice the switch by content type. Literary passages reward phrase strokes and familiar briefs; technical testimony loads up on terms where phonetic writing is safer. Mark a practice transcript by type before taking it, then check whether your stroke choices matched. Where you forced a brief you half-remembered, demote it: write that word phonetically until the brief survives repeated drills. Ownership is demonstrated under speed, not decided at your desk.
Misstrokes versus conflicts: fix the right thing in your dictionary
A misstroke is a one-time wrong key combination; a conflict is a standing clash where one stroke maps to two words. They need different fixes: drill the first, restructure the dictionary for the second.
Check your raw notes after practice takes and classify errors before fixing anything. A misstroke usually shows as a garbled translation of a word you normally write cleanly; the fix is targeted drilling of that stroke transition, often the spacing between strokes. A conflict shows as the same stroke translating to two different words depending on context; no amount of drilling fixes it, because the dictionary itself is ambiguous. Conflicts get resolved by adding a distinct stroke or scoping the entry.
Use this decision table when you audit a practice take, classifying each observed problem before choosing a fix:
| Problem you observe | Likely cause | First fix |
|---|---|---|
| One garbled word you normally write well | Misstroke at a stroke boundary | Drill the specific stroke transition, then re-take the same passage |
| Same stroke producing two different words | Dictionary conflict | Add a distinct stroke or scope the entry to a job dictionary |
| Names or technical terms left untranslated | No dictionary entry exists | Phonetic placeholder during the take; add entries afterward |
| Words crowding together or merging | Stroke spacing breaking down under speed | Slow final-stroke spacing in drills before pushing pace higher |
Scenario: the unfamiliar surname that costs the next sentence
Mid-take, an unusual surname arrives. The wrong move is stopping to fingerspell it; the right move is a phonetic placeholder stroke plus immediate re-anchoring to the clause in progress.
Picture a take where the speaker says a surname like Kowalczyk. A candidate freezes, fingerspells letter by letter, and while spelling, the next six words — the substance of the answer — go unwritten. Worse, re-entering mid-sentence, the candidate misjudges where the clause began and stacks two strokes together. The transcript now has a correctly spelled name sitting inside a broken sentence, and the candidate spends the following lines reconstructing lost content from memory.
The better decision is a phonetic placeholder — KOLCHIK or similar — struck without hesitation, with attention returned immediately to the sentence. The name is recoverable later from audio or context; a dropped answer is not. This is why the protocol is decided before the take: at dictation pace there is no time to weigh options, only to execute one. Writers who rehearse placeholder behavior for names treat unknowns as routine, not as emergencies.
Scenario: a well-meant dictionary fix that creates a conflict
Cleaning up notes, a candidate adds a witness's name as a brief to the main dictionary — where that stroke already translates a common phrase. Scoping the entry to a job dictionary avoids the clash.
After a practice deposition take, a candidate notices a witness name repeatedly misstroking. The quick fix feels obvious: assign a new brief and place it in the main dictionary so it is available everywhere. But that stroke already carries a high-frequency translation used in ordinary sentences. Days later, in a different take, the old word suddenly renders as the witness name. The candidate now has two problems: a conflict that spreads across all future work, and a mystery error that is hard to trace back to its source.
The better decision is scoping: add the name brief to a job dictionary for that specific matter, and only promote it to the main dictionary after confirming the stroke is free and the term recurs often enough to be worth owning. Dictionary hygiene is a professional practice skill, not a cleanup chore: main dictionaries accumulate entries across a career, and every ambiguous entry taxes future takes. Audit before you add, and prefer narrowly scoped fixes.
A drill that measures decision speed, not just pace
Take unfamiliar audio at your target pace, then self-audit with a log: count full-stop hesitations, unresolved untranslates, and stacked strokes. Trend these across weeks; the log, not your feeling, shows progress.
Run the drill several times a week. Use audio you have never heard, take it once without pausing, and immediately mark every place you froze, guessed, or stacked. Keep a simple log with three columns: hesitation events, unresolved untranslates, and strokes you had to repair. The point is to make decision failures visible. Accuracy alone hides them — you can score well on a take and still have frozen twice, dropping content you never noticed losing.
Grade each take against these milestones:
- Zero full-stop hesitations in the take; brief slowdowns are acceptable, stops are not
- Every untranslated word is resolvable afterward from context or audio — nothing is simply gone
- You can name the trigger for each hesitation: a name, a number, a phrase you lacked a protocol for
- Your log shows the same triggers recurring less often across weeks, not just higher raw accuracy
A preparation sequence and readiness checks you can actually use
Sequence preparation as protocol sheet, dictionary audit, decision drills, mixed-content takes, then full simulations. You are ready when your logs are clean and your decisions are automatic — not when a single take goes well.
A realistic sequence, adaptable to your baseline: first, write a one-page protocol sheet covering names, numbers, and unparseable phrases; second, audit your dictionary for conflicts and dead briefs; third, run the decision-speed drill from the previous section; fourth, mix literary and technical takes in the same week so switching becomes automatic; fifth, simulate full conditions, including sustained takes without restarts. Stretch the middle stages as long as your logs demand; compress nothing that still produces hesitations.
Treat these as readiness checks — learning milestones rather than predictions of any result: you write through unknowns without stopping; your untranslate log trends down over consecutive weeks; you can explain every brief you deploy and where it lives in your dictionary; a simulated take leaves you with raw notes you can resolve without guessing. For current test structure, eligibility, and administration details, rely on NCRA directly — this article teaches skills, not logistics.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.