A missing unit is a safety hazard, not a typography issue

What it is

A unit omission hazard arises when a number loses its unit, leaving the receiver unable to determine its physical quantity or scale uniquely while still appearing complete enough to act on. A unit is not decorative copy to remove for space. An isolated “10” could mean millimetres or inches, grams or milligrams, Celsius or Fahrenheit. In medication, manufacturing, logistics, weather alerts, and device control, that ambiguity can directly become a dose, dimension, load, or temperature error.

Why it happens

A number provides a position on a scale; its unit binds that value to a physical dimension and magnitude. Page context can make a unit seem obvious, but context disappears in copy and paste, screenshots, screen-reader output, truncated notifications, reordered columns, API transfer, and print. A distant column heading or colour-only association also makes value–unit mispairing easier. NIST's complete quantity declaration includes both numerical value and measurement unit. In software, that calls for the unit to travel as structured semantics and to appear with the visible value, rather than surviving only in pixels or a variable name.

Studying it

Use failure mode and effects analysis to trace measurements through capture, storage, conversion, notification, export, and manual transcription, recording every point where a unit is removed, hidden, or attached to the wrong value. Comprehension studies can ask participants to perform dose, threshold, or equipment-setting tasks from a full page, truncated notification, screenshot, spoken output, and pasted table. Manipulate unit proximity, symbol familiarity, dual display, and missing context; measure unit identification, order-of-magnitude errors, recovery time, and confidence. Code near misses and support cases separately as omitted unit, wrong unit, wrong dimension, or bad conversion instead of collapsing them into “numeric entry error.”

Where it stops holding

Counts and mathematically dimensionless ratios need no physical unit, though labels such as items, multiples, or percent may still be essential to meaning. A fixed unit shown persistently at field level can reduce repetition, but it must remain attached in records, exports, and accessible names. A familiar domain abbreviation may fail across languages, professions, or assistive technology; similar symbols, case, and prefixes can differ by orders of magnitude. Dual-unit display can create a second hazard path if labels are unclear or values become mismatched.

Applying it

• Store and transmit number, canonical unit, and physical dimension as one inseparable structure. For consequential actions, fail closed with a useful explanation when a unit is missing, unknown, or dimensionally incompatible.
• Place units beside their values in inputs, readings, thresholds, chart axes, tables, notifications, and confirmations. If a unit appears only in a heading, preserve the association under freezing, responsive reflow, copying, and screen-reader navigation.
• Include both machine-readable unit identifiers and human-localized labels in exports, APIs, logs, and clipboard output. Do not make consumers infer a default from column order, filenames, or undocumented context.
• Inject omitted units, unknown units, wrong dimensions, truncated labels, confusable abbreviations, and mismatched dual units. Ask testers to interpret and re-enter values away from the source page, verifying that every value still resolves to exactly one unit and dimension.

Related

• Same group: S2.04.1 Length, weight, and temperature use different measurement conventions · S2.04.2 Conversion rounding can create inconsistencies · S2.04.3 Users need to be able to switch units
• Adjacent: S2.04 Units of measurement · S2.09 Regional differences in input validation
• Search terms: unit omission hazard · unit ambiguity · quantity declaration