A transport operator that dispatches vehicles from several depots needs to confirm drivers' alcohol check results before each trip, and the head office needs to collect and manage the status of each depot. But each depot has a different first departure time, irregular dispatches after the last scheduled run, and different staff working hours. So the fact that data has come in by a single time set by the head office is not enough to conclude that every driver's pre-trip check is complete.
In this article, an alcohol check means the task of checking the people due to drive through a pre-driving test or a check procedure set by the company. When managing several depots, you need to look separately at the state in which the depot has finished checking the drivers who will actually operate, and the state in which those results have arrived at the head office system or summary data. Designing the closeout around this distinction keeps you from confusing problems to sort out immediately at the site with problems to recover in the communication and aggregation process.
Set the site closeout to fit each depot's departure flow
If the head office aggregation time is used as the check completion time for every depot, depots with early-morning departures and depots with frequent ad hoc dispatches are treated by the same standard. It is more practical to set, for each depot, when pre-trip checks must be finished and when the roster is finalized to reflect same-day dispatch changes. The time the head office receives data is treated as a transmission deadline, which means something different from the site closeout.
The site closeout is not about filling in blanks on a roster. It is the step of comparing the people actually scheduled to depart with the check results, reflecting not only the drivers originally dispatched but also cancelled trips, vehicle changes, and replacement drivers. The depot must decide whether anyone among the final dispatched drivers has no linked check result.
Mark "not checked" and "not received at head office" separately
When drivers remain unchecked at a depot, the people subject to pre-trip checks have not been fully accounted for. On the other hand, when a depot has finished checks but the results do not appear on the head office screen, it may be a communication failure, a missed transmission, or a delay in processing receipt. If both situations are marked "incomplete," it becomes hard to tell whether the depot needs to recheck who is dispatched or the head office needs to restore the data delivery route.
You can consider separating site check completion and head office receipt in the head office status table. A depot marked site complete but not received at head office is one where the results kept at the depot should be compared with that day's final dispatch. Even if a depot is marked as received at head office, the depot manager must check separately that no one among those actually scheduled to drive is unchecked.
| Management stage | What to decide | Next action |
|---|---|---|
| Depot site closeout | Is anyone actually scheduled to drive missing a check result? | Sort out the remaining people and changed dispatches at the depot |
| Head office transmission deadline | Has the site's completed data reached head office aggregation? | Confirm where the original records are and how they will be sent for depots not yet received |
| Daily aggregate wrap-up | Are an interim report and data received late the same check entries? | Distinguish duplicates, omissions, and content differences before reflecting them in the totals |
This distinction is not about adding more labels. For example, when a depot not yet received is found on the head office screen, if there is an interim report that the site closeout is done, you can first check the original records and the delivery route. Conversely, if the site closeout itself is not finished, sorting out whether the people actually due to drive have been checked comes before restoring the transmission.
When the dispatch changes, recheck who must be checked
At transport sites, the dispatch schedule first drawn up may not hold until the end of the day. If drivers change because of absences, vehicle problems, or extra trips, then even if every name on the original roster has a check result, you need to look again at whether the people who actually departed were included in the checks. So in each depot's report, it is useful to show the number of people actually scheduled to drive and the final number checked, rather than just totaling the drivers assigned to the depot.
As a hypothetical case, suppose Depot A finished checks for the initial dispatch roster before the first departure and sent the results to the head office. A replacement driver is then brought in to cover an absence, but the head office screen already shows "received." The fact to observe is not the received mark but whether the replacement driver's check result is linked to the final dispatch schedule. If the result is missing, the depot compares the changed dispatch with whether that driver was checked, and the head office reflects why the initial totals and the additional data differ. The site closeout is complete when the final number dispatched and the number checked match and the basis for that comparison is recorded.
During a communication failure, link original records to interim reports
When communication is cut off, the site checks may be done but receipt at head office may be delayed. In this case, you need a method in which the check results kept at the depot serve as the original records, and the interim report includes information that identifies which depot, which dispatch or shift it concerns, and the drivers involved. That way, the head office can tell not just that "the data hasn't come in," but which check entries are delayed.
Once communication is restored, compare whether the interim report and the formally transmitted data are the same entries. Rather than merging them by file name or transmission time alone, look at the depot, the dispatch, the driver, and the information that identifies the actual check. If the contents differ, it is better to assign roles so that differences are checked against the depot's original records, rather than fixing the first report as correct or overwriting it with the later data.
Record why totals changed after closeout
Data arriving after closeout can change the daily totals. If they differ from the numbers already used in operations meetings or reports, you need to record which data from which depot was added or corrected and when, so the difference can be explained. This becomes material for reflecting the causes of failures or omissions in the next operating standard, without relying on staff members' memories.
The time settings of depot equipment and the head office server are also items to check. Time differences can make it look as though a check was done later than it really was, or a normal transmission arrived after the deadline. In the daily wrap-up, look at unchecked cases, transmission delays, duplicate receipts, and mismatches in who was due because of dispatch changes separately, and for recurring types, you can consider adjusting the deadline or reporting route.
Divide responsibility between site decisions and head office aggregation
An appropriate structure is for the depot manager to decide whether everyone due to be checked before actual departure has been accounted for, and for the head office aggregation staff to manage data receipt, duplicates, and the status of corrections. Even if one person handles both tasks, the work standard should record that site checks and head office receipt are different decisions.
What matters in closing out alcohol checks across several depots is not quickly switching the head office screen to complete. It is confirming, in order, whether checks of the people actually scheduled to drive are finished at each depot and whether those results are fully reflected in the head office totals. Only with this distinction can you decide, when a delay occurs, what to handle first: comparing who is dispatched, checking original records, restoring transmission, or correcting the totals.
