TIME IS RUNNING OUT FOR 2026 TAX WRITE-OFFS

Protecting Specialized Dragon Vocabulary Before Edits

By Martel Electronics

Martel VOX Elite laptop; screen display simplified for illustration.

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:

  1. XML for custom words and their supported properties.
  2. 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.

Export commands only when commands are in scope

If the reporter relies on custom commands, create a separate supported command export. Put it in 04-custom-commands. Use a name such as:

Nora-Production_custom-commands_2026-11-19_pre-edit.dat

The actual extension should be whatever Dragon creates; do not rename it to match this example. Record the command export count only if Dragon or a trustworthy inspection method provides a true count. Do not count visual rows and report a precise total if the list is paginated, filtered, or grouped.

Commands are outside the ten-word import exercise in this guide. Their separate export exists to prevent a vocabulary change project from overlooking another personalized resource.

Build the ten-entry illustrative review set

The fictional production profile contains many entries. Nora chooses ten invented entries as the inspection set for a controlled practice import. The copied export may contain more than these ten entries; the worksheet reports the ten inspected targets separately from any total that Dragon reports importing.

ID Written form Illustrative spoken form Resource type Proposed decision
D01 Oriole Harbor Review same as written Custom phrase Keep
D02 Talren Bay Authority “tall-ren bay authority” Custom phrase Keep
D03 Mireya Sorn “mih-ray-ah sorn” Custom phrase Keep
D04 Halvik Rone “hall-vick roan” Custom phrase Keep
D05 Pelden Weir “pell-den weer” Custom phrase Verify
D06 Novarin seal “no-vah-rin seal” Custom phrase Keep
D07 RQ-18 “R Q eighteen” Custom phrase Keep
D08 East Lydon pier “east lie-don pier” Custom phrase Keep
D09 Brindleworks “brindle works” Custom word Verify
D10 Sorrellan gauge “sor-ell-an gauge” Custom phrase Keep

All ten entries are invented. The spoken-form notes are not linguistic standards; they simply make the practice exercise explicit.

Notice that the proposed decisions are not all “keep.” Two entries remain Verify. A backup should preserve uncertainty rather than silently turn it into an approved spelling.

Distinguish written form from spoken form

Dragon custom vocabulary can associate what a person says with what Dragon should write. The visible text and the spoken form serve different functions.

For example, the fictional identifier RQ-18 might be spoken as “R Q eighteen.” The written form preserves the desired letters, hyphen, and digits. A multiword name such as Talren Bay Authority may need only the written phrase if its pronunciation is ordinary for the trained user.

Do not add a speculative spoken form to every entry. Preserve the form that exists in the production export, and use a copied working list for proposed changes. If the export does not make a property human-readable, do not guess at it.

Also keep commands out of this table. Saying a phrase that triggers an action is different from dictating a phrase that should appear as text.

Make a human-readable inventory without changing the export

Copy the supported export selected for the import into 05-practice-import and name the copy with _working-copy. If word properties are part of the check, use a copied XML export; use a copied TXT export for a check limited to that simpler word-list format. Review a separate readable TXT copy for the ten invented entries. Create an inventory with these columns:

Field Purpose
ID Stable reference for the exercise
Written form Expected visible text
Spoken form Existing or proposed spoken form, if applicable
Present in pre-edit export Yes, no, or unresolved
Source for spelling Approved reference location
Intended scope Permanent, case-only, or unresolved
Practice import status Not attempted, imported, rejected, or unresolved
Practice result Observed saved text
Production decision Keep, revise, remove, or defer

The source column matters. A reporter’s memory may be enough to recognize a familiar name but not enough to establish its official spelling. In real work, use an authorized source and follow the applicable confidentiality rules.

Create checksums for the protected originals

A checksum is a compact fingerprint calculated from a file’s bytes. It can show whether a protected export changed after the checkpoint. It does not encrypt a file, judge its completeness, or prove who created it.

On Windows 11, an approved administrator can use a built-in or organization-approved checksum method. Record SHA-256 values for the original XML, TXT, profile package when practical, and command export. Save the results in 06-checksums.

An illustrative checksum record might look like:

File Size SHA-256 Checked
Nora-Production_custom-words_2026-11-19_pre-edit.xml Illustrative only EXAMPLE-NOT-A-REAL-HASH 2026-11-19

Never publish real hashes when the organization’s security policy treats backup metadata as confidential. In this article the value is explicitly a placeholder, not a computed result.

After copying the protection package to approved backup storage, recalculate or verify the hashes according to policy. A matching hash supports the conclusion that the copied bytes match the checkpoint. It does not prove the file will import successfully; that requires a supported practice check.

Choose a safe practice context

Do not test an import by overwriting the only working production profile. The practice context should be authorized, separate, and reversible.

Possible supported contexts include:

  • A new disposable practice user profile created for the installed Dragon edition.
  • A designated training computer or virtual environment approved by the organization and Dragon licensing terms.
  • A restored copy on a replacement computer prepared through qualified support.

The safest choice depends on the license, edition, organization policy, and reason for the test. A disposable profile on the same Windows 11 laptop may prove that the file can be read, but it does not prove that the practice profile has the production user’s acoustic training, microphone setup, commands, or CAT integration.

Write the boundary in the record:

This practice import checks whether the copied export is accepted and whether ten selected entries appear as expected in the practice vocabulary. It does not validate the complete production profile or promise recognition behavior.

Import only the copied practice list

Open the authorized practice profile, confirm its name, and use Dragon’s supported Import list of words or phrases workflow. Select the copied working file in 05-practice-import, leaving the protected original in 02-custom-words unchanged. Importing that copy may add the entire exported list. The ten-entry inspection that follows is a sampled check, not a statement that only ten entries were imported or that all other entries were validated.

If the import wizard requests further action, preserve the exact message and review it before continuing. Keep the protected original unchanged while following the matching Dragon guidance or contacting qualified support. Record:

  • Practice profile name.
  • Dragon product and build.
  • File selected.
  • Import start and completion time.
  • Any warning or rejected entry.
  • Whether the imported words appear in Dragon’s vocabulary management interface.

A successful wizard completion means the supported import process accepted the file. It does not establish that every word has the intended properties or that dictation will always produce the expected text.

Verify the entries before dictating

Inspect the practice profile’s vocabulary through Dragon’s supported vocabulary-management interface. Look for each of the ten written forms. Record only what can actually be observed.

ID Expected written form Import observation Next action
D01 Oriole Harbor Review Present, illustrative Test in passage
D02 Talren Bay Authority Present, illustrative Test in passage
D03 Mireya Sorn Present, illustrative Test in passage
D04 Halvik Rone Present, illustrative Test in passage
D05 Pelden Weir Present but spelling source unresolved Defer production decision
D06 Novarin seal Present, illustrative Test in passage
D07 RQ-18 Present, illustrative Inspect written form
D08 East Lydon pier Present, illustrative Test capitalization
D09 Brindleworks Present but scope unresolved Defer production decision
D10 Sorrellan gauge Present, illustrative Test in passage

These are invented observations for teaching the recordkeeping method. They are not actual Dragon results.

An entry’s presence is one checkpoint. Its properties and behavior are separate checkpoints. If the written form is absent, do not proceed as though the import succeeded for that entry. If it is present but unexpected, preserve the observation and consult the matching Dragon guidance before changing the production profile.

Use a fixed fictional passage

Create a passage that includes every target in ordinary context. Keep it short enough to repeat without fatigue and unusual enough to reveal the intended forms.

Mireya Sorn met Halvik Rone at East Lydon pier for the Oriole Harbor Review. Talren Bay Authority asked them to inspect the Novarin seal and Sorrellan gauge marked RQ-18. Pelden Weir delivered the fictional Brindleworks drawing.

The passage, people, places, authority, equipment, and drawing are entirely invented.

Before each practice attempt:

  1. Confirm the disposable practice profile is open.
  2. Confirm the intended stenomask or microphone is selected.
  3. Open a fresh practice document.
  4. Read the same passage at the reporter’s sustainable practice pace.
  5. Save the resulting text before manual correction.
  6. Mark any interruption or misread line as Not testable.

Run three testable attempts. Three is a worksheet design choice, not a universal accuracy standard. The aim is to compare results from repeatable practice conditions before deciding which vocabulary entries need attention.

Score exact forms, not impressions

For each target, compare the saved text with the accepted written form. Use simple statuses:

  • Exact — the target appears in the intended written form.
  • Different form — the words are present but spelling, spacing, capitalization, punctuation, or characters differ.
  • Substitution — a different word or phrase appears.
  • Omitted — the target is missing from the saved text.
  • Not testable — the reporter misspoke, the input was interrupted, or the sentence was not captured as planned.

Do not change a status after manually correcting the practice text. Keep the original recognized output and the reviewed copy separate.

An illustrative row might read:

Attempt ID Expected Observed Status Note
P1 D07 RQ-18 RQ eighteen Different form Hyphen and digits differ

This row is made up. It demonstrates how a specific observation produces a specific review question. It does not claim that Dragon normally treats that identifier in a particular way.

Do not convert a practice check into an accuracy claim

Ten targets over three testable attempts create thirty target opportunities. The arithmetic can help ensure the worksheet is complete, but it is not a marketable recognition rate.

The set is too small, too specialized, and too dependent on the reporter, microphone, profile, passage, and environment to support a broader claim. Report the individual observations instead:

  • D01 appeared in the intended form in all three saved practice outputs.
  • D07 appeared differently and needs property review.
  • D05 remains unresolved because the source spelling was not confirmed.

Those statements are more useful than a percentage. They identify what needs action and what remains uncertain.

Decide whether the protection package is adequate

The pre-edit package is ready only when the checklist can be answered with evidence:

  • The exact production profile is identified.
  • The custom-word export exists in the supported format.
  • A readable inventory copy exists when appropriate.
  • The broader profile backup or export is preserved separately.
  • Custom commands are protected if they are in scope.
  • The original protected files have not been edited.
  • A copy of the custom-word list was accepted by a separate supported practice context.
  • The ten intended written forms were inspected.
  • Practice observations and unresolved items are recorded.
  • The storage location follows the organization’s security rules.

If any item is missing, label the package Incomplete. That label is useful. It prevents the existence of a folder from being mistaken for proof of recoverability.

Make production changes in small batches

Once the protection package is complete, create a separate change worksheet. Work through the selected vocabulary entries in manageable groups so each change can be reviewed.

A cautious batch might contain five to ten verified entries. For each entry, record:

  • Pre-edit written form.
  • Pre-edit spoken form or property, when visible and relevant.
  • Authorized spelling source.
  • Proposed change.
  • Reason.
  • Person approving the change under the organization’s process.
  • Post-edit practice sentence.
  • Saved observation.
  • Keep, revise, or reverse decision.

Start with changes that have clear evidence. Defer entries such as fictional D05 and D09 until their spelling or scope is resolved.

After one batch, save the profile through Dragon’s normal supported process. Use a fresh practice passage and preserve the result before starting the next batch. Small batches make it easier to connect an unexpected behavior to a specific change.

Preserve the pre-edit package after a successful edit

Do not delete the checkpoint simply because the first post-edit practice looks good. Retain it according to the organization’s backup and records policy.

Add a completion note rather than altering the original readme. The note can state:

  • When the production edit began and ended.
  • Which worksheet identifies the changed entries.
  • Which Dragon profile was changed.
  • Who performed and reviewed the work.
  • Whether a post-edit custom-word export was created.
  • Whether any entry was reversed.
  • Where the next recovery point is stored.

Create a post-edit export with a new timestamp. Never overwrite the pre-edit file. The two exports can then be compared through an approved method without destroying the earlier state.

Know when to restore and when to ask for help

A restore is not the first response to every unexpected word. First determine whether the issue is a vocabulary entry, a command, a microphone selection, a different open profile, a CAT translation, or a manual formatting expectation.

Stop and seek qualified help when:

  • The production profile will not open.
  • Dragon displays a profile or backup message that requires support guidance.
  • The profile, vocabulary, or command menus differ materially from the instructions for the installed edition.
  • The only available backup is on a device awaiting service.
  • Imported entries need review for duplicate or conflicting forms.
  • The reporter cannot identify which profile was active during the export.
  • Licensing or activation is uncertain on the proposed practice computer.
  • Confidential case data may have been copied to an unapproved location.

Do not restore a full profile merely to correct one CAT dictionary entry. Do not import a command file to solve a custom-word issue. Match the recovery action to the resource that actually changed.

A practical rollback decision tree

Use this sequence after an edit produces an unexpected result:

  1. Preserve the observation. Save the uncorrected practice output and note the open profile.
  2. Confirm the input. Verify the intended stenomask or microphone and the Windows 11 input selection.
  3. Confirm the resource layer. Decide whether the issue is Dragon vocabulary, a command, the CAT dictionary, or formatting.
  4. Review the batch. Identify the exact entries changed since the last successful checkpoint.
  5. Reverse the smallest supported change. If one verified edit caused the issue, reverse that edit through Dragon’s interface and retest.
  6. Consult support before a full restore. If profile recovery is needed or the next step is unclear, preserve logs and contact qualified support.
  7. Restore only from the identified protected point. Follow the supported method for that Dragon edition and document the result.

This order limits collateral change. It also avoids using a complete profile restore as an undocumented experiment.

Why ordinary Windows backup still matters

Dragon’s export tools protect application-specific resources, while the organization’s Windows 11 backup protects the broader computer environment. Both may be necessary.

A complete device plan can include approved backups for:

  • CAT cases and dictionaries.
  • Dragon profile packages and custom exports.
  • Work documents and delivery files.
  • Approved application installers and license records.
  • Organization-managed configuration documentation.

No single export covers all of these. Store recovery instructions with enough detail that an authorized person can identify the right package without opening confidential work unnecessarily.

Matching the workflow to a Martel VOX laptop

For a supported voice-writing setup, review the current Martel VOX Elite Voice-Writing Laptop Package. Confirm the selected Dragon edition, CAT software arrangements, installation work, and transfer responsibilities on the written order. The vocabulary-protection record then describes what the reporter already owns and what the setup specialist is expected to preserve.

Before a setup appointment, identify the profile, use Dragon’s supported exports, preserve the broader profile separately, and test a copy in an authorized practice context. Keep unresolved entries in the handoff note so they are reviewed deliberately during setup. The written evidence should establish which resources are protected and which still need attention.

Readers comparing available voice-writing systems can continue at the Martel VOX and Dragon laptop category. Bring the protection record to the equipment discussion so any selected transfer service has a clearly defined scope.

A one-page pre-edit checklist

Before editing the production vocabulary, confirm:

The checklist is complete only when the evidence exists. Checking a box from memory does not create the missing export.

Frequently asked questions

1. Is exporting custom words the same as backing up my Dragon profile?

No. The custom-word export protects a list of words and phrases, with supported properties when the chosen format includes them. The broader user profile contains additional resources Dragon uses for the individual user. Protect both when both are important.

2. Should I choose XML or TXT for custom words?

Use Dragon’s current guidance for the installed edition. Official help indicates XML when word properties need to be included. A text file can be useful for readable review, but it should not be assumed to preserve every property.

3. Can I open and clean the XML file in a text editor?

Do not edit the protected original. A general editor can change structure or encoding. Make changes through supported Dragon tools, and work from a duplicate only when the official import format permits the planned review.

4. Does a successful export prove that every word I care about is present?

No. It proves that Dragon created an export file. Inspect the relevant entries and keep a source-based inventory. A nonempty file can still come from the wrong profile or omit an entry the reporter expected.

5. How do I confirm which Dragon profile is active?

Use Dragon’s profile interface and record the exact open profile name before exporting. Do not rely on a Windows account name, desktop shortcut, or memory of the last session.

6. Are custom commands included in the custom-word export?

Treat them as separate resources. Use the supported command export for the installed professional edition when commands are in scope, and record that file separately from vocabulary exports.

7. Is my CAT dictionary part of the Dragon user profile?

No assumption should be made that it is. CAT dictionaries, jobs, layouts, and application preferences belong to the CAT environment. Protect them through that application’s supported process.

8. Can I test by importing into my production profile?

That is risky because the test changes the resource being protected. Use an authorized disposable practice profile or another supported isolated context, subject to licensing and organization policy.

9. What does the practice import actually prove?

It can show that the copied file is accepted by the supported import workflow and that expected entries appear in the practice vocabulary. It does not prove complete profile recovery or guaranteed recognition.

10. Why run three practice attempts?

Three attempts reduce the temptation to treat one result as conclusive. The number is an illustrative worksheet choice, not a universal standard or a basis for advertising an accuracy percentage.

11. Should I remove every case-specific name when a matter ends?

Not automatically. Follow the organization’s retention, confidentiality, and vocabulary policy. A term may be reusable, required for an appeal, or inappropriate to retain. Record the reason and authorized source for each decision.

12. What if I cannot verify a person’s spelling?

Mark it unresolved and defer the production change. A vocabulary entry should not make an uncertain spelling look authoritative.

13. What if a custom phrase and a command use similar spoken words?

Document both resources and test in a safe context. Similar spoken triggers can create confusing behavior. Do not delete either one until the reporter understands which layer produced the result.

14. Can a checksum replace an import test?

No. A checksum can show that bytes match an earlier copy. It does not show that Dragon accepts the file, that the correct profile was exported, or that the entries behave as intended.

15. Should the backup stay on the same laptop?

The working package may begin there, but the recovery copy should follow the organization’s approved backup policy and should not depend entirely on the same device surviving.

16. Does Windows 11 File History protect Dragon correctly?

It may contribute to a broader computer backup, but it does not replace Dragon’s supported vocabulary and profile exports. Confirm the organization’s restore process and the publisher’s instructions for the installed edition.

17. Can I rename the exported profile’s internal files?

Preserve the package as Dragon creates it. Rename only the outer package or destination when the supported workflow allows it. Rearranging internal files can make a restore unsupported or confusing.

18. What if Dragon reports rejected entries during import?

Save the message, record the affected entry, and stop changing the original. Review the import format and the installed edition’s official help or ask qualified support.

19. Can I use real case names in a training import?

Only when the training environment and storage are authorized for that information. A safer demonstration uses invented names like those in this guide.

20. Does ordering a VOX laptop establish my Dragon software entitlement?

Confirm the selected software options and the written order. Preparation for a Dragon workflow and the right to activate a particular Dragon license are separate matters. Record whether the order supplies a new entitlement, installs a license already held by the reporter, or leaves that step with the buyer or school.

21. Does this procedure apply to Speechmatics?

Dragon’s export and profile procedures apply to the resources discussed here. If your EclipseVox session instead uses Speechmatics, organize its custom dictionary and other resources according to that route’s publisher instructions. Check the software release before building the protection plan. Eclipse 10 and 11 list local Speechmatics; Eclipse 12 offers the additional cloud choice alongside local processing. A local Speechmatics Enhanced installation must use a Boost Box bought from the EclipseVox publisher or a qualifying laptop purchased there. Record the selected arrangement with the saved resources.

22. When should I create the next checkpoint?

Create one before a meaningful batch of changes and another after the batch is reviewed. Keep distinct timestamps so the pre-edit state is not overwritten by the post-edit state.

23. Who should approve production vocabulary changes?

Follow the reporter’s organization, school, court, firm, or agency process. The person making the change should not invent approval. Record who reviewed the source and decision when policy requires it.

24. What should I bring to support if recovery is needed?

Bring the exact Dragon product and build, Windows 11 details, profile name, export method, on-screen message text, protection-package timestamp, change worksheet, and a description of what happened. Do not send confidential files until an authorized support channel requests them.

Protect first, edit second

A specialized vocabulary is easier to improve when the existing state is identified and recoverable. Export the custom words, protect the complete user profile, separate commands and CAT resources, verify a copied import in a disposable practice context, and keep unresolved spellings out of the production batch.

The completion record should identify the accepted entries, the unresolved ones, and the protected state available for recovery. That gives the reporter a practical starting point for the next vocabulary change and a clear explanation of the work already checked.

Martel Electronics