The same result can appear with different numbers of digits on a breathalyzer screen, in test management software, and in a downloaded file. For example, the screen may show 0.020 while the report shows 0.02. Safety managers and quality or technical staff have to judge from this difference whether the data changed or whether the equipment performs differently, but the length of a number alone does not support either conclusion.
Display resolution is the smallest interval of change that a screen or file can show as distinct. The International Vocabulary of Metrology (VIM) also describes resolution as the smallest change in a measured quantity that causes a perceptible change in the corresponding indication. This concept concerns how finely a value is displayed, and it must be kept separate from how close a measured value is to the reference value or how consistent repeated values are under the same conditions. The starting point is to read, in this order, the display digits, the measurement performance with its conditions, and the format of the stored data.
Read the unit and display interval first
A screen that shows three decimal places can express a change at that digit. You can confirm that it shows 0.020 and 0.021 as different values. But you cannot assume that the difference between the two numbers directly reflects an actual difference in what was measured. The sensor's response, the test conditions, and the processing that converts a signal into a number are separate from how many digits the screen shows.
So in the display specs, check the unit of the result, the number of decimal places, and the display interval for each step of change. If the items you are comparing do not use the same unit, you cannot compare their digits at all. Different units can change both the size of the number and the position of the last digit, so first sort out whether the values are shown in the same unit.
Accuracy and repeated results are different questions from the displayed number
After display resolution, look at the measurement performance data. What you need here is a description of accuracy or the permissible range, together with the conditions under which that description applies. A figure presented without conditions such as concentration or temperature is hard to compare directly with figures from other equipment or other test environments.
Interpret separately whether values from repeated tests come out close to one another. The fact that repeated results cluster together does not by itself show they are close to the reference value, and the fact that one result is close to the reference value does not show how consistent repeated results are. In reports, it is better not to group "decimal places," "performance descriptions with stated conditions," and "repeated test results" as if they were the same evidence.
| What to separate | What to check | What it tells you |
|---|---|---|
| Device screen | Unit, decimal places, display interval | How finely the user reads the number |
| Measurement performance data | Applicable conditions and permissible range | How to interpret performance under the stated conditions |
| Stored and exported values | Stored unit, digits, whether rounding applies | Why the screen value and file value differ |
| Report figures | Whether the original value is used and the display rules | Where the value was processed during transmission |
A trailing zero does not create new measurement information
You can append a trailing zero to a stored value so that 0.02 appears as 0.020. This change helps unify the reading format, but it does not add any newly measured information. This is also why a design change that increases the decimal places on a screen cannot be described as an improvement in measurement performance.
The opposite is also possible. The screen may show a short value for quick reading, while the downloaded file keeps a longer-format value. However, which value is the original and which rounding rule was applied must be confirmed through product documents or integration settings. Without such confirmation, you must not estimate the sensor's resolution or measurement performance from the number of digits in a file.
Look for screen-file differences along the conversion path
When the screen value and the file value differ, rather than immediately calling it a measurement error, follow the path the number took. Compare the value the device produced, the value the software read in, and the value shown on the screen or in the report, all for the same test. Record each stage's unit and digit handling at the same time so you can tell whether the change comes from the display format or from a unit conversion.
In particular, a missing last digit and a changed unit are different in nature. The first may be a matter of reducing the displayed digits or rounding. The second is a conversion that changes the meaning of the number, so unless you confirm the unit applied and the order of conversion, you cannot judge whether the values match from the screen number alone.
A check sequence in a hypothetical case
Consider a hypothetical case. A worksite's management screen shows results to three decimal places, but the downloaded file contains the same results only to two decimal places. The person in charge suspects the readings were stored incorrectly because the third digit is missing from the file.
In the observation step, collect the screen value and file value for the same test and note the unit and notation format of each. In the interpretation step, distinguish whether the file changed the screen value arbitrarily or whether the file format is set to round at a certain digit. If the product documents or integration settings specify the storage format and rounding rule, and that rule explains the relationship between the two values, there is no basis for concluding from the reduced decimal places alone that measurement performance has dropped.
One possible action is to keep the original value exported by the device, the value read by the software, and the final report value linked to a single test record. The completion criterion is that you can explain the unit and conversion order of all three values and can recheck which stage the report figure came from. This approach lets you identify where the number actually changed, instead of guessing whether a hidden last digit is real measurement information.
Write the comparison conclusion after the display specs
When you compare two devices or two management screens, the statement "it has more decimal places" only describes a difference in display format; it cannot be a performance conclusion. First confirm whether they use the same unit, and record each screen's display interval. Then compare the conditions and performance descriptions in each device's documents on the same basis, and what remains is the range you can actually compare.
When you change management software or report templates, it is also better to record changes to display policy separately from changes to measurement performance. Record changes such as adding digits or keeping trailing zeros as changes to display rules. Add a statement that measurement performance has changed only when there is separate performance evidence. Decimal places can let you read a result more finely, but they do not by themselves prove accuracy.
