# Fleet repair trail completeness checklist | SourceX

Canonical: https://refer.sourcex.si/resources/driver-report-to-asset-return-completeness-checklist
Last updated: 2026-11-04

A driver-report-to-asset-return trail breaks through missing identifiers, conflicting timestamps, overwritten form versions and unrecorded outcomes. The break that matters most is a repair that closes without an inspection record: the work order says "done," the next record is a load, and nobody can tell a verified fix from a paperwork close. The twelve checks below, grouped into five dimensions, let a fleet systems advisor mark each one pass, partial or fail in a conversation, without opening a DVIR or a work order.

This checklist is part of the [driver report to returned vehicle guide](/guides/chain-driver-report-to-asset-return). For the identifiers behind the linkage checks, see the related page on [driver report to asset return record linkage](/guides/driver-report-to-asset-return-record-linkage).

## Scoring rules before you start

Score each check pass (2), partial (1) or fail (0). Twelve checks give 24 points. "Unknown" scores 0 until someone confirms it, and you note who could answer. Record the year each practice began; a pass from 2022 onward is a different trail from a pass since 2015.

Ask the safety manager, the fleet maintenance manager and the operations manager together if you can. Every question below is about where and how records are kept, never about what a record says.

## Coverage and linkage checks

Coverage asks how much history exists; linkage asks whether one repair can be followed from system to system.

| Check | Question to ask | Pass | Partial | Fail |
|---|---|---|---|---|
| C1. Inspection history | Since which year are DVIRs and defects kept? | Five or more years | Two to five years | Only the legal minimum, or unknown |
| C2. Repair history | Since which year are work orders kept, including any old shop system? | Five or more years, migrations documented | Years exist across systems with a gap | Under two years |
| C3. Dispatch history | Since which year can loads and unit assignments be retrieved? | Five or more years | Two to five years | Under two years |
| L1. Defect to work order | Does the work order show which DVIR defect it came from? | System link, same platform | Typed reference | No reference |
| L2. Work order numbering | Did work order numbers restart in a migration? | No restart, or a mapping table kept | Restart with no mapping, years known | Restart, years unknown |
| L3. Unit identity | Is the unit number the same in telematics, shop and TMS? | Same everywhere, VIN held too | Mapped by a list someone keeps | Inconsistent names |

What earns a pass on L1: the shop opens the job from the reported fault itself, so the reference is written by software rather than retyped. Samsara's help center describes that arrangement for fleets on its maintenance module, with a single asset per order and attached faults clearing when the order closes. A separate shop package can still pass when its import keeps the original fault number; it scores partial when a mechanic copies a date and a unit and nothing else.

## Timestamp and outcome checks

### Timestamps

Timestamps decide whether the record tells events in the order they happened.

| Check | Question to ask | Pass | Partial | Fail |
|---|---|---|---|---|
| T1. Close timing | Do mechanics close work orders when the job ends, or in a batch later? | Closed at job end | Mixed | Month-end batch closing |
| T2. Out-of-service window | Can you see when a unit was taken off and put back on dispatch? | Both times recorded in the TMS | Only the next dispatch | Neither |

A fail on T1 is easy to miss. If work orders close at month end, the close lands after the truck's next load and the record reverses cause and effect.

### Outcomes

Outcomes show whether the repair held and who paid for it.

| Check | Question to ask | Pass | Partial | Fail |
|---|---|---|---|---|
| O1. Approval recorded | Where would I see who approved a vendor repair, and the amount? | Approver and amount on the work order | Amount only; approver in email | Neither recorded |
| O2. Recurrence | Who notices if the same defect comes back on later DVIRs? | Recurrence flagged or reported | Someone checks by habit | Nobody compares |

## Gap checks, including the return-to-service test

These two checks look for known holes. The first concerns form versions; the second is the case this checklist exists to test.

| Check | Question to ask | Pass | Partial | Fail |
|---|---|---|---|---|
| G1. Inspection form versions | Has the DVIR checklist changed, and are old versions kept? | Dated versions kept | Changes known, versions lost | Unknown |
| G2. Return-to-service record | What happens between a closed work order and the next load, and where is it recorded? | Mechanic DVIR or road-test entry required | Relies on next driver's pre-trip | Nothing between close and dispatch |

Score G2 on what the fleet can point to, not on what it says it does. Federal regulation (49 CFR 396.11) requires a repair certification on the original report before the equipment is used again; a pass here asks for more than that signature, namely a dated check that the fix worked. Samsara's API documentation lets a mechanic file an inspection of their own from the dashboard or by API, which gives the check a timestamp and a name. Three practices come up, and each scores differently: a required mechanic inspection or road test (pass), reliance on the next driver's pre-trip walk-around (partial), and a shop lead's judgment with nothing written (fail). Note the year the current practice began.

### A scored example (Illustrative)

A fictional 190-person ready-mix concrete supplier with 85 mixer trucks and its own yard shop, scored on one forty-minute call with the plant operations lead, the shop foreman and the safety coordinator.

| Group | Marks | Points |
|---|---|---|
| Coverage | C1 pass, C2 partial (shop software replaced in 2020), C3 pass | 5 of 6 |
| Linkage | L1 pass, L2 partial, L3 pass | 5 of 6 |
| Timestamps | T1 partial (foreman closes jobs on Fridays), T2 pass | 3 of 4 |
| Outcomes | O1 partial (amounts logged, approvals by phone), O2 fail | 1 of 4 |
| Gaps | G1 pass, G2 partial (next morning's pre-trip is the check) | 3 of 4 |

Total: 17 of 24. The sentence that goes into the introduction: "Mixer inspections, shop jobs and batch-ticket dispatch since 2017, with a shop software change in 2020; faults link to jobs; repair approvals happen by phone; the morning pre-trip is the only release check." The sentence carries the meaning; the number is a summary.

## Owners behind each check and the sign-off

The checklist names the owners for you: safety for C1, G1 and O2; maintenance for C2, L1, L2, T1 and O1; operations for C3 and T2; whoever keeps the unit list for L3. The person who can authorize a licensing discussion sits above them all: the CEO, who in an owner-run carrier is usually the owner.

Confirm the carrier has 50+ full-time employees at peak (contractors and leased owner-operators excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. The [company fit checker](/tools/company-fit-checker) runs the same basics.

What stays unknown until SourceX reviews it: how driver and location data would be removed, whether telematics, shipper or lender agreements restrict use, which years a buyer wants and what the company would be paid. Partners never export or forward records. For carriers in restructuring, [trucking company bankruptcy](/industries/trucking-company-bankruptcy) covers who controls the records; investors can read [value creation without multiple expansion](/guides/value-creation-without-multiple-expansion) for the portfolio angle. The [Samsara records page](/systems/samsara-export-data) describes what that system tends to hold.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

When you can describe the carrier's repair trail in one honest sentence from its checklist, [register as a partner](/register), confirm it on [who qualifies](/who-qualifies) and read the [program terms](/terms) before you introduce the owner.

## Sources

- https://refer.sourcex.si/terms
- https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-396/section-396.11
- https://kb.samsara.com/hc/en-us/articles/32504504318989-Work-Orders-for-Maintenance-Management
- https://developers.samsara.com/docs/digital-vehicle-inspection-reports
