A fleet can have a dashboard full of vehicle locations and still struggle to answer a simple question about last month’s trip. The map looks complete, but the export has missing timestamps. The driver’s name has changed in the account. The camera recording sits in a different system. The person who knew the settings has left the company.
Keeping records is not just a storage question. Someone has to know what was saved, which vehicle it describes, what time its clock used and whether another person can open it without the original account. A useful retention process answers those questions before a customer dispute, crash or software change makes them urgent.
Start with a record inventory, not a folder
List the systems that describe a trip. That list may include electronic logging devices, dispatch software, position reports, fuel transactions, inspection records, maintenance systems and cameras. Do not assume that one vendor stores everything because its dashboard displays information from several services.
For each record type, name the person who owns the account, the format available for export and the setting that controls deletion. Note whether the vendor keeps older material elsewhere after it disappears from the dashboard. A blank search result and a deleted record are different problems. Staff need a way to tell them apart.
Keep that inventory readable by someone outside the daily dispatch team. A list that says only “ask Maria” will fail when Maria is on leave. Record the system name, responsible role and approved recovery procedure without putting passwords in the document.
Separate retention rules from software defaults
A subscription’s default storage period is not a legal conclusion. Nor does a minimum recordkeeping period automatically settle how long every file connected with a particular trip should remain available. Applicable rules, contracts and a specific preservation duty can call for different treatment.
The federal hours-of-service rule in 49 CFR 395.8 sets requirements for records of duty status and supporting documents. Staff responsible for storage should check the current rule and the records it covers, rather than copying a number from a vendor’s sales page. Other types of records may have different requirements.
IT Supply Chain’s discussion of ELD retention describes the operational problem of notices arriving while routine deletion continues. The practical lesson is to connect the people receiving notices with the people who can actually stop a scheduled purge. For a specific incident, counsel should determine what must be preserved and how long the hold should remain.
Keep the meaning of each timestamp
Time fields deserve their own notes. One export may use coordinated universal time while another displays the terminal’s local time. A report may show the time an event happened, the time a device recorded it or the time a server received it. Those values should not be treated as interchangeable.
Retain the original fields and document any conversion used in a working copy. When a clock or time zone is uncertain, mark that uncertainty rather than silently changing the value. A neat-looking timeline is not useful if it hides an unsupported assumption about when something happened.
The same care applies to location. A plotted point is a recorded position, not a continuous account of everything between that point and the next. Keep the source coordinates, units and any available accuracy information. Do not replace the underlying file with a screenshot of a route drawn between sparse observations.
Carry the identifiers with the files
A vehicle number used by dispatch may differ from the identifier used by a device vendor. Drivers can switch trucks. Devices can be replaced. Account labels can be edited. An export without the matching identifiers may become difficult to interpret even when the file itself is intact.
Include a dated reference connecting the relevant vehicle, device and account identifiers. Retain the history needed to explain a change without overwriting the old relationship. Limit access to personal details, and share only what the particular review requires.
A useful handover should explain which field identifies a trip and which field merely describes it. A customer name or free-text trip label can help someone search, but it should not be the only connection between several record sets.
Preserve originals and label working copies
Keep an original export separate from spreadsheets prepared for analysis. Sorting rows, adjusting time zones or deleting empty columns may make a working copy easier to use, but those changes should not silently replace the source material.
Record who exported the files, when the export occurred, which date range was requested and whether the system reported any omissions. A file checksum can help detect later changes to that same file. It does not prove that the original export contained every relevant record or that every recorded value was correct.
Store the export instructions with the records. Include any vendor documentation needed to interpret unusual fields. A proprietary file that requires a discontinued application can be harder to recover than an ordinary spreadsheet, even if both have survived in storage.
Test recovery without the usual account
A backup test should involve opening the material, not just checking that a scheduled job reports success. Ask someone with the right permission to retrieve a sample and explain what it contains. They should be able to identify the vehicle, date range, time zone and source system without relying on the original dispatcher.
Test what happens if an account is closed or a staff member leaves. Can the business still read older exports? Does the backup depend on the same login as the live system? Are the instructions available to an authorized replacement? Resolve those questions before moving to another vendor.
Make preservation a documented handoff
When a preservation request or incident notice arrives, record its receipt and send it promptly to the designated reviewer. The person deciding the scope and the person changing system settings should confirm the handoff. Silence between departments is not confirmation that deletion stopped.
Keep a record of the systems checked, the changes made, the person responsible and any gaps found. Ask vendors to explain what can and cannot still be recovered. Do not promise that an export is complete merely because a download finished.
A readable backup is a set of records plus enough context to understand them. The goal is not to collect every available file forever. It is to apply the right retention decision, preserve material when required and leave the next reviewer with an account they can actually follow.