An interlock installed in a vehicle is a device that controls whether the vehicle can start based on the breath test result the driver provides and other inputs. The handset is the device that measures breath, and the control box is the central processing unit that connects to the vehicle and handles start control and event storage. DATECH's AF-i1 stores vehicle ACC, engine start, test result, and tamper-related events with date and time information, and its guidance states that log events can be managed and downloaded in dedicated PC software.
Fleet managers or installation and operations staff may run into a connection error or save error when trying to download records for a certain period for routine inspection, internal review, or a support request. What matters at that point is not to make the error go away quickly but to clearly record the relationship between the original events that may remain on the device and any files already created. A handover note is not a memo saying "the download didn't work"; it is a document that lets the next person judge what was attempted, how far it got, and which materials are still the originals.
First narrow down where the error occurred
Download failures can look like the same problem but occur at different points. You need to distinguish whether it stopped before the PC and device connected, whether the extraction was interrupted after the target period was selected in the dedicated software, or whether the error occurred when opening the saved file. Without this distinction, support staff also find it hard to judge whether they should look at the connection or at the file itself.
In the handover note, record the management number that identifies the vehicle, the device identification, the displayed version of the software used, and the date and time of the work. Then record the start and end dates you tried to download and the event conditions selected. Rather than a vague range such as "recent records," record what was actually selected, such as "selected March 1, 00:00 to March 31, 24:00," so the range does not change when retrying.
If an error message appeared on screen, it is better to record the message exactly as shown rather than summarizing it from memory. If you took a screenshot, also record the file name and where it is kept. However, error screens and partial files do not replace the original logs on the device.
Do not mix originals, extracted files, and review copies
The original log means the event records stored by the interlock device. The AF-i1 guidance states that it stores data related to interlock use and can store about 500,000 test results and operating events. A problem during a download does not mean you can immediately conclude that the device's records are gone; in the handover note, state factually whether you confirmed the records for the target period on the device.
A file created on the PC once the download started is an extracted file, separate from the original log. Even if a file was created, you need to check separately whether it contains the entire requested period, whether it opens normally, and up to what point events are included. Treat a copy that has been sorted, filtered, or annotated for analysis as a review copy. If you add notes or edit rows directly in the original extracted file, it becomes hard to explain later which content came from the device.
If you organize the nature of each material and the next action on one page, as in the table below, shift staff or outside support staff can avoid confusing the files.
| Category | What to record in the handover note | Next action |
|---|---|---|
| Original events remaining on the device | Target vehicle and device, period checked, whether records on the device were confirmed | Do not decide whether to delete or reset; keep the current confirmed state |
| Extracted file created on the PC | File name, storage location, time created, whether it opens normally | Keep a separate copy of the original file and do not modify it |
| Interrupted partial file | Time extraction stopped, file size, last point confirmed as included | Do not label it as data for the whole period; mark it as a partial file |
| Review copy | Filters, sorting, and notes applied, and who did the work | Keep it separate from the original extracted file and use it only for analysis |
Do not treat a partial file as a successful download
For instance, consider a hypothetical case. A manager tried to download a month of events for April, and after the program froze during extraction, one file remained on the PC. If opening the file shows only early-April events and it is not confirmed whether data for the end of the month is there, the observation is "file created" and the interpretation is "whether the entire requested range was extracted successfully is unconfirmed." A possible action is to copy and keep that file as a partial file and to record the selected period, the time it stopped, and the on-screen error message in the handover note.
The completion criterion in this case is not the fact that a file exists. It is a state where it has been confirmed that the entire requested period was actually extracted, or where the unconfirmed range and the status of the remaining partial file have been clearly communicated. If you manually stitch the needed events from several files into what looks like a single official download file, it becomes even harder to tell duplicates from gaps.
If you download the same period again and end up with two or more files, record each file's creation time and the order of extraction attempts. If you have not yet compared whether two files contain the same events, it is accurate to write "duplication unconfirmed." You must not discard an earlier file as incomplete when there is no comparison result.
Hand over the preservation state before retrying
A retry is not a procedure for hiding the cause or tidying up records; it is work to check the failed extraction again. So first gather the screen records, extracted files, and work notes you already have in one place, and separate a read-only archive copy from a review copy. Also record the state of the connection to the device and vehicle and what was confirmed on the cable or program screen used, but do not fill in unconfirmed items with guesses.
The actual connection method, file format, and retry scope for the AF-i1 must be handled based on the guidance for the product and dedicated software currently in use. When staff request support, pass on the device identification, the selected period, the stage at which it failed, the error message, and the status of the files created, all together. Then the support process can decide where to start checking without overwriting data that was already retrieved successfully.
Clearing the device's settings, resetting it, or disconnecting the device to resolve the error cannot be an alternative to a handover note. Such actions do not fit the purpose of preserving originals, especially when it has not been confirmed what effect they have on the records. If you do not know whether events for the target period remain on the device, write "unconfirmed," not "none," to leave a starting point for the next action.
The handover note lets the next person work with the same range
A good handover note is not a document for shifting blame but one that preserves the boundaries of the data. If you record, in order, the vehicle and device, the period you tried to download, the screen stage that failed, the remaining files, and the confirmation status of the original log, the next person is less likely to reanalyze the same file or download the wrong period.
For operations staff in particular, it is more useful to report the status of the original events, the existence of partial files, the unconfirmed range, and whether support was requested separately, rather than only reporting "download failed." This way, you do not mistake records that have not been retrieved for retrieved data, and you can continue follow-up checks without losing the files and work history already created.