When Dragon writes a number as a word instead of a digit, inspect formatting rules before assuming it misheard you. The recognized quantity may be correct while its written representation follows a profile setting. A result such as five instead of 5 is a different problem from fifteen instead of fifty.
Use a disposable document and write down the exact number, surrounding words and output. This guide follows Dragon 16 desktop formatting. Available behavior can depend on the profile language and region, so include those details in the test record.
Determine whether the quantity is correct
Dictate a short sentence with an ordinary number and compare its meaning with the output. Then try a different quantity using the same sentence structure. If the quantity is wrong, investigate recognition and audio separately rather than changing every number-formatting option.
If the quantity is right but the form is wrong, define the intended convention. A prose report, an account reference and a currency amount may require different representations. Do not impose a global digit rule merely because one form field expects a numeric entry.
Inspect the active auto-formatting settings
Nuance's Auto-Formatting dialog documentation describes number-related settings, including a threshold used for ordinary numbers and separate rules for other categories. Open the settings for the active profile and record the current choices before changing them.
Separate ordinary numbers from special formats
Dates, times, prices, telephone numbers and units can have their own behavior. A telephone-style output is not necessarily controlled by the same setting as a simple count. Test the category that actually fails, using harmless sample values rather than real personal identifiers.
Check language and region
A regional profile can affect conventions such as telephone and currency formatting. Confirm the profile used for the document and the intended audience. Do not copy another user's settings without checking whether their language and regional requirements match yours.
| Sample category | What to compare |
|---|---|
| Ordinary count | Correct quantity and word-versus-digit representation |
| Decimal | Digit sequence and decimal separator |
| Date or time | Order, separators and intended convention |
| Reference code | Leading zeros and whether it should be treated as prose |
Change one rule and repeat the same sentences
Use a small set of samples covering values around the setting you changed. Repeat the original sentence rather than inventing a completely different test after every adjustment. This makes the effect easier to distinguish from normal recognition variation.
Keep the before-and-after outputs. If a change fixes ordinary counts but makes another document type less convenient, reconsider whether it belongs in the global workflow. A profile setting affects more than the single paragraph that prompted the investigation.
Check word properties for a local context
Nuance's Word Properties reference includes formatting associated with individual vocabulary entries and surrounding numbers. If only a particular unit or specialized phrase behaves unexpectedly, inspect that entry before adding a broad workaround.
For example, a department might require a particular representation beside an approved abbreviation. Define the intended phrase and review any local property changes with the vocabulary owner. This is an illustrative design question, not a preconfigured rule that every Dragon installation contains.
Avoid confusing corrections with preferences
When correcting output, distinguish a misrecognized quantity from a formatting choice you dislike. Repeatedly treating a correct number as an acoustic error can distract from the actual rule that produced its appearance. Keep the sample sentence and intended written convention explicit.
If a prompt offers to remember a formatting preference, read it before accepting. Understand the scope of the proposed change and whether it matches the team standard. Do not approve a lasting preference simply to dismiss the window quickly.
Validate the actual document task
After adjusting settings, test the real type of field or application with nonconfidential values. Confirm that a reference code retains meaningful zeros and that the receiving system interprets a decimal as intended. Correct-looking text in a blank document is not a complete validation of a business form.
Keep a short profile note listing the rule changed, its purpose and the examples checked. Our PowerMic hardware guide can help with a separate device decision, but representation errors should first be traced to the recognized value, applicable formatting rule and context. The right fix preserves the number's meaning while producing the form your document actually requires.
