At aviation worksites, when the result of a pre-shift or pre-task alcohol check is reviewed, it is easy to treat that result as if it immediately meant the person can perform all of their duties. But an alcohol check is a procedure that confirms whether a check was carried out in a set way at a specific point in a shift, and the decision to assign actual work, such as aircraft maintenance, ground handling, or vehicle movement, can come with separate conditions.
Here, job approval means confirming the requirements of the job itself, such as qualifications, completed training, and internal authorization to perform a specific task. Deployment approval means deciding which person to assign to which location, time slot, and task on a given day. The alcohol check result, job approval, and deployment approval can be viewed on one screen, but you need to keep separate what each means and who confirmed it, so the basis for decisions does not blur during shift changes or rotations.
The three checks answer different questions
The alcohol check deals with the question "has the alcohol-related check required for this shift been completed?" The staff member who reviews the result should be able to record the time of the check, the person checked, and how it links to that shift. This check alone does not mean access rights to specific equipment or qualifications to perform maintenance work have also been reviewed.
Job approval is a check of whether "this person meets the requirements to perform the task they are about to take on." Deployment approval, by contrast, decides whether "within today's staffing and work plan, we will actually assign this task to this person." Because the same person may be a candidate for maintenance support in the morning and vehicle movement in the afternoon, you need a structure that does not simply carry over the earlier flag when the job changes.
| Category | What it aims to confirm | Who uses the result |
|---|---|---|
| Alcohol check | Whether the check before that shift was completed | Check staff and the deployment supervisor |
| Job approval | Whether task-specific qualifications, training, and internal authorization are in place | Job supervisor |
| Deployment approval | Whether to actually deploy the person to that day's location, time, and task | Deployment supervisor |
The reason for keeping the three items in separate columns is that completing one item does not mean completing another. If a screen or roster uses only a single catch-all flag such as "ready," the next person on shift will find it hard to trace which conditions were confirmed.
Do not turn a test-completed flag into a cleared-for-deployment flag
An operating screen may need to show both whether the check was completed and the final deployment status. But if the check-completed value is automatically converted into "cleared for deployment," a separate review may be skipped when a job or work plan changes. Even when the two items are shown linked together, it is clearer to design the system so that the cleared-for-deployment flag appears only after the deployment supervisor has confirmed it.
Especially where several job groups use the same check location, the affiliation or scheduled task of the people tested can get mixed up. The job of the check staff here is to link each result accurately to the right worker, not to judge everything from qualifications and training to access rights. If roles are crammed excessively into one form, it also becomes unclear, when something is missed, whom to ask to re-confirm which fact.
When a check result has not been confirmed or is not linked to a shift, it is better not to leave it as a blank. For example, you can use statuses that show the follow-up action, such as "check not completed" or "re-check needed due to shift change." This is not a suggestion to disclose individual results widely, but an operational suggestion to pass the minimum check status needed for deployment decisions to the relevant staff.
For a changed deployment, start with what changed
As a hypothetical example, consider an employee who completed a morning check and is then deployed to vehicle movement around aircraft instead of the originally scheduled maintenance support task. The facts to observe are that the morning check was completed and that the task actually being assigned differs from the original plan. The check-completed record remains, but it may not be a record that the job approval needed for the changed task and the deployment decision for that day have also been completed.
The interpretation of this situation is closer to "new check items have arisen to link to the changed deployment" than to "the check has become invalid." One possible approach is for the deployment supervisor to specify the changed task, ask the person responsible for confirming that task's qualifications, training, and internal authorization to review it, and then reflect the outcome in the deployment roster. The completion criterion is that the check result, the job approval for the changed task, and the final deployment decision for that task are each recorded separately, along with who confirmed each one.
Having this process reduces cases where the approval flag for a previous task is inadvertently carried over to a new task. Conversely, if nothing has changed and the check result is already linked to the assigned task and working hours, the procedure can be streamlined to avoid repeating the same check unnecessarily. Which items to re-check should be decided according to each operator's current procedures and task-specific standards.
At shift changes and handovers, hand over "pending conditions," not "people"
At shift changes, it is better to pass on specifically the conditions not yet reflected in deployment decisions than to hand the next person all the test results. For example, write the task and the outstanding check together, such as "of 2 candidates for afternoon vehicle movement, 1 has completed the alcohol check and is awaiting job approval confirmation for the changed task." The next person can then see what is missing for whose task.
Handover notes do not need to repeat readings or unnecessary personal circumstances. It is enough to distinguish, to the extent needed for deployment, whether the check was completed, the scheduled or changed task, and who still needs to confirm what. It is advisable to limit access to individual check information to those who need it for work, and to align display screens and handover materials with that scope.
If the entry management screen and the work deployment roster are run separately, you need to decide who will do the final cross-check between them and when. An indication that entry is permitted does not mean approval of a specific work deployment, and conversely, having a name on the deployment roster does not mean that day's check is done.
Write the boundaries of each approval item into the policy documents
Operating standards can at least set out separately the alcohol check staff, the person responsible for confirming job requirements, and the person responsible for finalizing the day's deployment. Also specifying which records each person checks and to whom things are passed when something is incomplete or changes reduces guesswork in on-site decisions. Even if you want to bring several approval statuses together in one system, the setup needs to keep the basis and the confirming person for each item separately.
Article 36 of Korea's Occupational Safety and Health Act requires employers to identify hazards and risk factors arising from work and other sources, assess the risk, and establish and implement improvement measures to reduce it. When designing alcohol check and deployment procedures at aviation worksites, the points where a test-completed flag masks other job conditions, or where checks break off during a changed deployment, can also be examined as risk factors.
The key is not to show more checks. The alcohol check should be recorded as an alcohol check, job approval as job approval, and the deployment decision as a deployment decision. Only then can you trace who needs to confirm what when the day's work changes, and avoid giving a single check result too much meaning.
