When manufacturing, construction, transport, and similar operations run alcohol checks before clocking in, starting work, dispatch, or crew duty, they need a sheet to record the results. This sheet is not just a list that collects readings. It is a record that lets you confirm, in sequence, whether a person was subject to a check for a given shift, whether a test was actually carried out, and whether any required handling was finished after the result was reviewed. With too few fields, it is hard to tell a missed test from a retest or an input error; with too many, site staff end up seeing personal information unrelated to the work.
Alcohol checks may use methods such as reviewing breath test results, and the results sheet should first record the facts needed for site operations rather than details of how the testing equipment works. The criterion for choosing what to include is not the possibility that it might be useful later, but who makes what decision by looking at that field. Keep the information that links the person, the shift concerned, the test result, and the handling progress, and separate content with a different viewing scope, such as objections or separate fact-finding, to keep the sheet concise.
First decide what questions the results sheet must answer
Each column in the results sheet should answer one operational question. The internal ID number and shift type answer "who is subject to a check for which shift," and the test time and result confirm "whether the check was validly completed." The handling status and the reviewer's details show whether the confirmation procedure after the result is finished.
A useful method is to lay out the existing form and write next to each field who reads it and what decision they make. For example, the site manager confirms whether the day's checks are complete, and a staff member in a separate role can see whether additional checks are progressing. Columns whose purpose no one can explain can be classified as candidates for deletion rather than kept out of habit.
If laws or internal industry standards require a specific form, those fields must be met first. Then review the fields added for internal convenience separately, so you do not confuse required fields with customary ones.
Link the person, shift, test, and handling
The minimum fields differ by site, but they can generally be divided into information to find the person and shift subject to the check, information to judge whether the test was completed, and information to confirm follow-up handling. If names alone make it hard to tell apart people with the same name, you can consider using an internal ID number together with the shift or task type. It is better to first ask whether the combination fits the purpose than to record more identifying information.
| Field group | Information to keep in the sheet | Task it confirms |
|---|---|---|
| Person and shift | Internal ID number, shift or task type | Confirm who is subject to the check for that shift |
| Test facts | Test time, valid result, device information where needed | Distinguish completed tests from those needing a retest |
| Handling progress | Handling status, reviewer, link number to a separate record | Track whether follow-up checks are complete |
Record the device name, display unit, and test method when they are actually used to distinguish what a result means or to confirm that tests were done under the same conditions. Conversely, a home address, personal contact details, reasons for drinking, or explanations of private life have little basis for inclusion in the results sheet if they are not used to judge whether the day's check is complete.
Do not treat a blank as a result value
A blank result and a valid result recorded as zero are different. If blanks are automatically filled with zero, you cannot tell completed tests from tests that could not be done. So, in addition to a valid result, you need to define the statuses actually used on site, such as not tested, error during testing, retest in progress, and under further review.
As a hypothetical example, suppose the result field for one person on the night shift is blank and the site staff member wrote only "difficulty testing." The observable fact is that there is no test time and no valid result for that shift. Without attributing this to a specific cause, you can classify it as "not tested" or "error during testing" from the defined statuses and, if a retest or separate check is needed, record a link number. The case is complete only when you can confirm that a valid result has been recorded and the defined confirmation procedure has been wrapped up.
This standard also applies to retests. If the first attempt and the repeat attempt are overwritten in the same single field, it is hard to know what happened. If you separate test entries or use link numbers, you can track the fact that there was a re-check while still seeing the final result.
Keep free-text notes out of the site completion sheet
A free-text field makes it easy to record exceptions, but it tends to accumulate health information or personal explanations unrelated to the purpose of the check. On the site results sheet, you can use the defined handling statuses and link numbers to separate records first, and move detailed accounts into a record with restricted access only when they are needed.
For example, the content of objections, the circumstances of a refusal to test, and additional fact-finding materials do not need to be viewed by everyone who checks whether the day's site checks are complete. Even if you split the two records, decide which number links them and who can find them in which storage location. Even when an entered test time or handling status is wrong, rather than erasing the original entry, record the fact and time of the correction so the flow of the record can be understood.
Test whether the slimmed-down form actually works
After reducing the form, check whether people are creating separate ledgers again from paper printouts or electronic data. If the system holds only results while the site records the reviewer separately, you need to decide again why that information is needed and which record serves as the reference. Separating information the equipment or system records automatically from information staff enter manually also reduces duplicate entry.
Before finalizing, you can test it with shifts that include people with the same name, missed tests, retests, and entries corrected after being entered wrong. If you can tell the person, the test progress, and the final handling status apart without extra notes, the necessary fields are in place. Conversely, if each particular case needs a separate explanation, it is better to first review whether the status categories or the way records are separated are appropriate, rather than adding the missing fields.
Article 29 of Korea's Personal Information Protection Act requires personal information controllers to take safety measures, including establishing an internal management plan and keeping access logs. If you store the results sheet electronically, divide who can view and edit it according to the purpose of the record; if you store it on paper, set out who can take it out and where it is kept. Minimizing fields and securely managing the records you need must be designed together.
