Backup drivers are candidates identified in advance who can be contacted and assigned driving duties when a vacancy arises. However, the fact that a name and phone number are on the list does not tell you whether the person can be reached now, whether a call-up can be arranged in a particular time slot, or whether they are already assigned to other work. The more a site relies on the list to fill dispatch gaps, the more it needs to distinguish the number of people on the list from the number who can actually respond and be assigned.
In workplace alcohol management, the pre-trip check procedure also continues separately. A procedure that confirms before a trip whether someone has been drinking, such as a breath test, does not replace a "reachable" mark on the backup list, and conversely, being reached does not mean someone is ready to drive. The key is to design the backup driver contact list as data that manages candidates' latest contact and assignment status, and that hands over to the dispatch and pre-duty check procedures that apply at the workplace once a call-up is actually decided.
Manage current status, not names
At a minimum, the list can record separately how the person can be contacted, the contact hours or scope of arrangement the person has confirmed, when the information was last checked, and whether they are currently assigned. Contact hours here are not an item that imposes a duty to answer at any time. They are information showing when, within the scope already agreed with the person, you can check whether a call-up is possible.
It is also better not to keep "available" as a single fixed mark. A candidate not yet asked, a candidate you tried to contact and are waiting to hear from, a candidate who accepted a call-up request, and a candidate assigned to other work are in different states. In particular, once a call-up is accepted, change the assignment status immediately so the same person is not still counted as a backup for another location.
There is no need to classify candidates by putting alcohol check results or past readings on the list. Even though there are rules dealing with alcohol checks and records for transport workers, such as the Rules on Alcohol Checks and Records for Passenger Transport Workers, the backup staff contact list should not be treated as a statutory form replacing that check log. Check the scope and procedure of the actual pre-trip check separately against the workplace's standards and the applicable rules.
Divide changes that require updates by status
Treating a contact as a wrong number or excluding them permanently just because they did not answer the phone once can actually lower the reliability of the list. Write down only confirmed facts separately, such as whether the call came at a bad time, whether the contact details changed, or whether the person was busy with other work, and do not guess at unconfirmed reasons. It is more appropriate to record the action needed for the next check than detailed reasons concerning the person's private life.
| Change that occurred | Current status to record | Next action |
|---|---|---|
| No answer to calls or texts | Awaiting response | Check again using the agreed contact method |
| Contact details or contact hours changed | Stop using previous information | Update with new information after confirming with the person |
| Assigned to another trip or task | Assigned for that time slot | Set when to check again after the work ends |
| Affiliation or list manager changed | Scope needs review | The new manager checks contact information and duplicate entries |
The statuses in the table are not labels for performance reviews or decisions on penalties. They are operating information for not counting the wrong number of available people at the next call-up request. For example, whether to include someone "awaiting response" in the available count is decided by site standards, but if they are included, you need a distinction such as not counting them as confirmed until they actually respond.
Do not count the same person in two places
As a hypothetical case, consider a situation in which Location A and Location B each put the same driver on their backup list to prepare for vacancies. If Location A requests a call-up in the morning and the driver accepts, but the driver still shows as "available" on Location B's list as before, the two locations may each think they have secured that one person.
What to observe is not the number of names on the list but the time of the request, whether there was a response, whether it was accepted, and where the person is currently assigned. The interpretation in this case is not that the two lists are wrong, but that there is no way to communicate changes in the assignment of shared candidates. As a possible action, you can mark duplicate candidates and decide that whichever location received the actual request first, or a designated coordinator, changes the status on the other list to "assigned" as soon as the request is accepted.
Set the completion criterion clearly as well. The update is complete when the person who accepted Location A's request is removed from Location B's count of people who can be confirmed, and the person responsible and the time for rechecking availability after the work ends have been set. Simply leaving the name on both lists is not completion.
Combine routine checks with checks when something happens
Routine updates alone struggle to keep up with sudden changes in contact details or same-day assignments, while fixing the list only when something happens leaves names that have gone unused for a long time. So it is realistic to set routine check times that match the workplace's actual frequency of backup call-ups and agreed conditions, and also to update whenever a contact attempt fails, an assignment changes, or an affiliation changes. There is no need for the list itself to invent a particular statutory update cycle.
Recording the last check date and who checked it for each candidate lets you find outdated information all at once. However, you must not judge a candidate's working conditions or qualifications just because the person doing the checks has changed. The list manager organizes the latest contact and assignment information, and at the stage of actually confirming a call-up, links what information the separate dispatch and pre-trip check procedures need.
Give contact details only to those who need them
The backup list may contain personal contact details, so it is best to provide it only to the extent needed by the people handling call-ups and updates. If the list is kept posted on a company-wide board or in a group chat, old files may remain, raising the chance of calling the wrong number or spreading personal information unnecessarily.
When distributing a new list, also decide how to recall the previous version or stop it from being used for call-ups. For candidates whose contact details changed, do not stop at confirming the new number has been entered. Check that the old number is not still being used from an outdated version of the list. Managed this way, the backup driver list becomes not just an emergency contact network but operating data showing whom to contact, and in what order, to check availability at the moment a request is made.
