Protecting Specialized Dragon Vocabulary Before Edits
By Martel Electronics
A specialized Dragon vocabulary may represent years of careful work. It can contain party names, medical terms, technical phrases, unusual capitalization, written-form preferences, and spoken forms that make a voice writer’s everyday dictation more predictable. A large edit made without a recovery plan can blur which resource changed and make a familiar profile harder to trust.
The safest starting point is not another vocabulary edit. It is a small protection package: identify the active Dragon user profile, export the custom words in a supported format, back up or export the broader user profile through Dragon’s supported tools, preserve commands separately when they matter, and prove that the custom-word file can be read in a disposable practice context. Only after those steps should the production vocabulary change.
This guide uses a fictional reporter and invented names. Every person, matter, term, date, file name, test sentence, and result is illustrative. The examples are not customer data, a court record, a Martel performance result, or a promise that a particular word will be recognized.
First identify what needs protection
People often say “my Dragon dictionary” when they mean several different resources. Before making changes, separate them on paper.
Custom words and phrases
Dragon can export a list of custom words and phrases from the open user profile. The official Dragon guidance allows a text or XML export. XML is the more appropriate choice when word properties need to travel with the entries. A plain-text list is useful when the goal is a human-readable inventory or a simpler word list, but it should not be assumed to preserve every property.
This export is the center of the exercise. It shows which custom lexical entries Dragon can export through its own interface at that moment.
The complete Dragon user profile
A Dragon user profile is broader than a word list. Dragon describes it as the files used to process what the user says. It can include microphone and acoustic information, vocabularies, custom words, and other user-specific resources. The profile therefore needs its own supported backup or export plan.
A custom-word XML file is not a complete profile backup. A profile backup is not a convenient substitute for a readable word inventory. Preserve both when both matter.
Custom commands
Commands can be exported and imported separately in supported professional Dragon editions. They should not be mixed into a custom-word count. A phrase that inserts text or performs an action may be a command even when the user remembers it as “a word I added.” Record the command resource separately and follow the current Dragon instructions for the installed edition.
CAT dictionaries and case files
CAT software and Dragon contribute complementary resources to a voice-writing workflow. For CATalyst VP, Stenograph describes Dragon vocabulary for voice recognition and a separate Personal VoiceCommands dictionary for transcript formatting. For EclipseVox, the publisher’s training covers the relationship between vocabulary entries, pronunciation, written output and Eclipse dictionaries. Keep the CAT user resources and Dragon profile in their respective supported backup plans, and verify each saved set before editing.
The related Martel guide Moving Case CATalyst or Eclipse to a New Laptop explains the larger migration distinction. This guide stays narrower: protect the Dragon vocabulary before changing it on the existing supported installation.
Define the change before touching the vocabulary
Write one sentence describing the proposed edit. Good examples include:
- Remove a set of obsolete fictional case names after review.
- Correct the written form of six verified organization names.
- Add a new group of technical terms for an upcoming practice matter.
- Consolidate duplicate entries that produce competing written forms.
- Move a reviewed custom-word set into a new supported practice profile.
Avoid vague descriptions such as “clean up Dragon.” That phrase does not state what will change, which profile is in scope, or how the user will decide whether the result is acceptable.
For the illustrative exercise, reporter Nora Ellery plans to review ten invented entries added during a fictional matter called Oriole Harbor Review. Her change statement is:
Export the current custom words, protect the complete production profile, and verify a copied import in a separate practice profile by inspecting ten selected entries before changing production vocabulary.
That statement is deliberately conservative. It does not promise that the practice profile will behave like the trained production profile. It asks only whether the exported entries can be inspected and imported through a supported workflow without risking the production environment.
Record the active environment
Create a one-page protection record. Complete it while Dragon and the relevant CAT software are available, not later from memory.
| Field | Illustrative entry |
|---|---|
| Windows edition | Windows 11 Pro |
| Computer | Martel VOX Elite voice-writing laptop |
| Dragon product and edition | Record the exact installed customer-facing name |
| Dragon version/build | Copy from the application’s About screen |
| Active user profile | Nora-Production |
| Profile language | English |
| Input device | Record the selected stenomask or microphone |
| CAT application | Record the installed application and version |
| Proposed edit | Ten-entry Oriole Harbor review |
| Protection folder | Approved private location |
| Protection date | 2026-11-19, illustrative |
| Person performing work | Nora Ellery, fictional |
Do not infer the Dragon edition from a desktop shortcut. Open the application and record what the software reports. Menu names and capabilities can vary by edition and release. If the current interface does not match the official instructions available for that installed product, stop and use the matching help or qualified support.
The Windows 11 folder is only a destination for supported exports. Do not copy an internal application directory and call it a backup unless the software publisher specifically directs that procedure for the installed edition.
Create a protected folder with an evidence-friendly name
Use an approved private location with enough space and access control for the profile package. A simple fictional folder structure is:
Dragon-Protection/
2026-11-19_Nora-Production_Pre-Oriole-Edit/
01-readme/
02-custom-words/
03-user-profile/
04-custom-commands/
05-practice-import/
06-checksums/
The date is written year-month-day so folders sort chronologically. The profile label is included because a computer may contain more than one user. The words Pre-Oriole-Edit explain why the package exists.
Use the organization’s approved encrypted storage or managed backup location. Real case names, protected health information, confidential party names, and client data should not be copied into personal sync services or casual training folders. The fictional examples in this article are safe only because they are invented.
Place a short readme in 01-readme with:
- The active profile label.
- The Dragon product, edition, and build.
- The Windows 11 computer label.
- The reason for the protection package.
- The export formats created.
- The time the export completed.
- The person who performed the work.
- Any warning, interruption, or unresolved question.
- A clear statement that the package has not yet been restored into production.
This readme turns a collection of files into an auditable checkpoint.
Export the custom words through Dragon
Open the exact production user profile that contains the entries. Confirm the profile name again before starting. Then use Dragon’s supported Export custom word and phrase list function. The current official help for professional Dragon products describes the export under the Vocabulary area of the DragonBar or the product’s current Vocabulary Center.
Create two exports when the installed edition supports them:
- XML for custom words and their supported properties.
- TXT for a readable comparison list.
Use descriptive names rather than words.xml:
Nora-Production_custom-words_2026-11-19_pre-edit.xml
Nora-Production_custom-words_2026-11-19_pre-edit.txt
Do not edit either file in place. If a review copy is needed, duplicate it and append _working-copy to the duplicate’s name. The original export should remain unchanged.
After the export, verify four basic facts:
- The expected file exists in
02-custom-words. - Its size is greater than zero bytes.
- Windows 11 shows the expected modified date and time.
- The file name matches the active profile and pre-edit purpose.
These checks do not prove that every desired entry is present. They do catch an empty export, a file saved to the wrong folder, and confusion between two similarly named profiles.
Why XML and text serve different purposes
The official Dragon guidance states that XML should be selected when word properties need to be exported. That makes XML important for a supported transfer where those properties matter. The text export is easier to scan, compare, and annotate, but it should not be treated as a full-fidelity replacement for XML.
Keep both original exports read-only in practice. Review a copied text list when looking for obvious spelling or scope issues. Never rely on opening and resaving an XML file in a general-purpose editor; that can change encoding, structure, or properties in ways the user did not intend.
If the installed edition offers only one relevant supported export, document that limitation. An unavailable format should remain unavailable in the record, not be fabricated by renaming another file extension.
Protect the broader user profile separately
Use Dragon’s supported profile backup or export function for the installed edition. Current Dragon documentation describes profile backup and export as distinct capabilities from exporting custom words. Follow the exact help that matches the installed product.
Save the resulting profile package in 03-user-profile and name it clearly:
Nora-Production_profile_2026-11-19_pre-edit
The output may be a folder or packaged file depending on the supported method. Preserve it as Dragon creates it. Do not rearrange its internal files for convenience.
Record whether the action was:
- A manual profile backup.
- A profile export intended for supported transfer.
- A copy created by an approved managed backup process.
- Another publisher-supported action identified by name.
If the profile is currently open and Dragon reports that it must be closed or saved first, follow that prompt. Do not force-copy files while they may be in use.