When you prepare a quote for breathalyzers or an alcohol management system, you need to settle the unit of the test results early, just as you settle the unit price and the test method. A unit here is the notation attached to a reading that tells you the basis of the result. If the units shown on the device screen, in results stored on the device, in computer files, and on printouts differ from your existing log or submission forms, the meaning of the numbers can change or comparison can become difficult when you transfer records after purchase.
This problem grows at worksites where many people are tested, at places reviewing devices that print or store results, and where existing records must be managed alongside results from a new device. If you organize the units you need and where they must appear at the quote stage, you can compare whether candidate devices fit your workflow and filter out in advance configurations that would require manual conversion or separate form changes after delivery.
Why the same number does not mean the same result
A reading does not have complete meaning from the number alone. You also need to see which unit the value is shown in to compare it correctly with earlier records, results from other devices, and internal management criteria. If someone jots down only the number on the screen and passes it on without the original unit, people reading the record later will find it hard to know the basis of that value.
Having staff rewrite values in a different unit after purchase complicates the record trail. The original result from the breathalyzer, the number the staff member transferred, and the basis used for conversion may not all be kept. Standardizing units is not about arbitrarily rewriting the original result; it is closer to matching the notation the work requires with the device's output range while keeping the meaning of the original result.
Four output locations to organize before requesting a quote
It is hard to judge unit support with a single question such as "Can it be changed?" The practical scope of use differs depending on whether only the screen changes or whether stored data and printouts use the same notation too. In your request for quotation, it is better to state not only the units you need but also where those units must appear.
| Location to check | What to ask at the quote stage | Answer needed for the purchase decision |
|---|---|---|
| Device screen | Is the required unit displayed right after the test? | The display range the model supports |
| Results stored on the device | What unit is attached to results kept in the device? | How the stored original results are notated |
| Computer files and printouts | Do files and printouts also fit your work forms? | An actual file or print sample |
| Comparison with existing records | Can new results be read alongside past logs? | How to reconcile any differences |
For example, if the screen shows the notation you need but the file transferred to a computer keeps only values on a different basis, it may be convenient for on-site checks but not suitable for record management afterward. Conversely, even if a device has print or storage functions, you cannot assume it automatically provides the units and formats you need. That is why you should get actual output samples from each candidate and compare them side by side with your existing documents.
A check sequence in a hypothetical case
For instance, suppose a worksite where several workers test before their shift and a manager records the results in an existing monthly log. The new device's demo screen shows the desired unit, but the storage file and printout it will provide have not yet been checked. The fact observed here is that "only the screen display has been confirmed," and you must not interpret this as meaning the same notation applies to stored data as well.
A possible action is to send the supplier a blank copy of your existing log together with the display locations you need, and to request separate samples of the screen, stored data, and printout from the candidate device. Do not assume that values share the same basis just because a file's column headings look familiar; confirm which unit each value is in. The completion criterion is that, when the manager compares the log they will actually use with the device's output, they can read the needed items and units without transcribing or converting anything separately.
If this process reveals an unsupported format, your options change. You can compare a different configuration that provides that format, or reconsider your internal workflow to see whether a separate reconciliation step is really needed. The important thing is not to choose a device on the assumption that conversion will be possible, but to reveal before the quote where conversion happens and how the original results will be kept.
A unit issue does not end with one device's settings
If you plan to add more devices or place devices in several locations, check whether the notation standard set at the first purchase carries over to later configurations. Even with the same model name, if you do not specify the options included in the quote, the output method, and the scope of initial settings, you cannot expect the same output on the next order. Rather than simply copying an earlier purchase order, it is safer to keep the screen and file samples you confirmed earlier as reference documents.
The same applies when you review configurations that connect to a computer or link to access control. If test results are sent to another system, you need to check whether unit information travels with the values and how they appear on the receiving side's screens and reports. If the notation on the device screen differs from that in the management system's reports, site staff and managers may end up looking at different numbers while talking about the same result.
What to record in the quote is the scope of application, not the feature name
In the quote or configuration specification, it is better to record the agreed scope of application than to list only broad feature names such as "unit change," "data storage," or "print support." For example, specifying whether the required unit applies to the screen, the results stored on the device, computer files, or printouts makes the acceptance criteria clear at delivery. Do not treat features you did not see in the demo as supported; mark them as unconfirmed.
At delivery inspection, check the test results against the conditions written in the quote. Do not stop at looking at the screen; compare whether the stored data and actual printouts keep the agreed notation. If you prepare for these checks from the quote stage, the unit question becomes a criterion for choosing the right device and configuration for the purpose, not a manual workload for staff after purchase.
