Checking that passenger alcohol check results carry through to logs and retained records

6 min read

At passenger vehicle transport sites, checking whether a transport worker has been drinking does not end the moment the result appears on the test screen. A breath test is a procedure for checking whether someone has been drinking by having them blow into a device, and a check log is a document that records that procedure and its result in a set format. The readings stored by electronic equipment, the paper or electronic check log, and printouts or files kept separately can each play a different role.

The Rules on Alcohol Checks and Records for Passenger Transport Workers set out the definitions of transport operators and transport workers, breath tests, and the retention of check logs. So a workplace needs to first determine from the original text whether it falls within the scope of these rules, and then check whether the result of an actual test carries through to the check log and retained records without a break. The key is to distinguish the fact that "a test was done" from the state that "the required records were made and kept so they can be found."

First separate who is covered from what is being checked

The starting point of the check is not the type of equipment or the log format, but confirming whether the business and the people fall under what the rules call transport operators and transport workers. Even with the same vehicles, if the business type, driving duties, or employment relationship differs, other standards or procedures may also need to be considered. This is why you must not take an attendance-based alcohol management method used in another industry, or an internal safety checklist, and assume it is a check log for passenger transport.

For a check that assumes the workplace is covered, it is useful to pick one check made before the start of a shift and trace it. You must be able to find that person's identity, when the check was done, the breath test result, the mark left by the person who confirmed the result, and where those records are kept. Identity here goes beyond whether a name is written down. It is the basis for confirming that the test result and the log entry refer to the same transport worker.

Test results and the check log are not the same record

The screen or stored file of testing equipment can show that a breath test took place and what the result was. However, whether the fields the equipment stores match everything that must be recorded in the check log is a separate question. Conversely, an attendance mark or signature in the log does not by itself prove that a breath test was actually carried out.

So you need to compare the equipment screen, printouts, and downloaded electronic data with the log line by line. When comparing, do not look only at the result values. Check whether there is a marker linking each to a particular check of a particular transport worker. Gaps can remain if you rely on only one source, for example when the equipment data has the result and time but the log needs the checker's confirmation mark.

What to compare What to look at What to do if something is missing
Breath test result Whether the person tested and the time of the check can be identified Set an identification standard that can link it to the log
Check log Whether the fact of the test and the result are linked to that transport worker Distinguish blank fields from who is responsible for filling them in
Retained records Whether the same check can be found again later Standardize storage locations and record names

This table does not present a new mandatory form. It is a framework for looking at the links between records you already use. For example, it is safer to treat fields the equipment stores automatically as automatic records only after confirming them on actual printouts or management screens. For parts whose function has not been confirmed, decide who will fill the gap and how, such as writing them by hand or entering them in an electronic log.

Follow one check all the way through to find gaps

Take a hypothetical case. Suppose a transport operator gave transport worker A a breath test before a morning trip, and the equipment stored the test time and result. However, the check log contains only A's name, there is no way to tell in which file the corresponding equipment data can be found, and the file names show only the vehicle or date. The observed fact is that "both the test data and the log exist, but they do not immediately link up as A's single check."

There is no need to stretch this situation into an equipment error or a test that was not done. However, it can be interpreted that, when the retained records need to be checked, linking the person in the log to the result in the electronic data may take time or be confused with another person's data. As a possible action, you can set an identification standard used in common in the log and the electronic data, and have the person who stores files classify the data according to that standard.

It is also better to set the completion criterion not as "the file exists," but as "starting from one check of one person in the log, you can find the result data and explain that they are the same check." If you then change the sample and confirm that the same flow works for other dates and other shifts, you can see whether the system depends only on a particular staff member's memory or a one-time cleanup.

For retention, being able to recheck matters more than being stored

Retained records may include records in different formats, such as paper logs, equipment printouts, and electronic files. What matters here is not that records exist in several places, but whether they connect without contradiction when you look up the check you need later. If the date written in the paper log and the date format in the electronic file differ, or names are written inconsistently, errors can arise in the linking process even though the records exist.

Operationally, you can specify separately what the person who writes the log, the person who transfers or prints test data, and the person who manages storage locations each do. For example, rather than writing a broad role such as "records officer," decide who checks for blank fields in the check log after each shift and who puts that day's test data in the designated storage location. The aim is to keep the storage locations and the way files or documents are distinguished consistent so the same records can be found even when staff change.

Whether the rules have been amended, the boundaries of who is covered, and the specific fields required in the check log must be checked again against the current original text of the rules. Confirm what information the equipment stores or prints from the official feature materials for the model you use, and it is best not to interpret those features broadly as automatically completing the statutory log. By checking scope, test performance, log entries, and retained records separately and then linking them back into a single check, you can confirm whether results carry through to records and retention.

※ This article is general information, not legal advice on any individual case. Please consult a lawyer or other professional about specific matters, and because laws can be amended, check the latest text at the Korea Law Information Center.

References

#passenger transport
#alcohol check log
#record retention
Considering our products?
We'll help you decide.