sayhushWhen dictating numbers and dates, say the unit and context, then compare the transcript with the original source. Use explicit dates and time zones when readers need them. Type exact values directly whenever a recognition mistake would be difficult to notice.
Include the unit and currency
“Fifteen” alone does not tell a reader whether you mean minutes, items or dollars. Say the unit in the sentence and verify it afterward. For money, include the actual currency rather than assuming a dollar sign means the same thing to every recipient. Dictation does not validate an amount against an invoice or budget.
Avoid ambiguous date shorthand
A numeric date such as 03/04 can be read differently across regions. In an international message, write the month name and year when necessary. If you say “next Thursday,” consider replacing it with the actual date before sending. The text may be read days later, when the original reference point is unclear.
State the intended time zone
For scheduling language, verify the date, time and zone yourself. “Nine tonight” is incomplete for someone elsewhere. An illustrative target sentence is: “The review is on 12 November 2026 at 9 pm Pakistan time.” Confirm that the real event uses those details; this example is not a calendar action and Sayhush does not save it to a calendar.
Check negatives, decimals and ranges
Read back values such as 0.5, 15, 50, minus 2 and “between 5 and 8.” A tiny recognition or punctuation change can alter the meaning substantially. Where exact notation matters, enter it directly from a verified source. Do not infer correctness from a sentence that sounds fluent.
Keep identifiers out of the guessing process
Order references, account numbers and long serial codes are often better copied directly than spoken. Avoid dictating secrets into a cloud workflow. For ordinary public identifiers, compare every character after insertion and make sure a space or punctuation mark was not added. Recognition is not a checksum or validation system.
Use a final detail pass
Before sending, scan the draft specifically for amounts, units, dates, time zones and names. Compare each with the source, then read the full sentence for context. This pass is separate from grammar editing. A well-written paragraph can still contain the wrong deadline, and the sender remains responsible for the final message.
Your quick checklist
- Include units and the intended currency.
- Use an explicit date when relative wording could confuse.
- Verify the time zone.
- Compare exact values with the source before sending.