# Driver report to asset return record chain | SourceX

Canonical: https://refer.sourcex.si/guides/driver-report-to-asset-return-record-linkage
Last updated: 2026-11-04

A company connects driver-report-to-asset-return records by following two identifiers. The unit number travels through every system, so it ties records to the same truck. The defect identifier ties records to the same repair, and it usually survives only where one system holds both the driver's report and the work order. The chain then needs an approval reference, a close event, a release check and the next load. The links most easily lost are the defect ID crossing into a separate shop system and the release check before redispatch.

This page is part of the [driver report to returned vehicle guide](/guides/chain-driver-report-to-asset-return). It maps the chain key by key; the main guide covers what metadata to collect overall.

## The chain at a glance: step, record, key and system

Six steps carry a defect from discovery to revenue. Each row names the record created, the key it carries forward and whether a system writes that key or a person types it.

| Step | Record created | Key carried forward | Typical system | Who writes the key |
|---|---|---|---|---|
| 1. Driver finds a defect | DVIR with one or more defects | Unit number, DVIR ID, defect ID | Samsara or another ELD app | System |
| 2. Load is reassigned | Dispatch change on a planned load | Unit number, load number | TMS | System for IDs; reason typed |
| 3. Repair is opened | Work order with line items | Work order number, defect ID if linked | Samsara maintenance or a shop system | System if same platform; typed otherwise |
| 4. Cost is approved | Vendor estimate and approval | Estimate number, approver | Shop system, accounting or email | Often a person, outside any system |
| 5. Repair is closed | Closed work order, resolved defect | Work order number, mechanic on the defect | Samsara maintenance or shop system | System |
| 6. Unit returns to service | Release check, then next load | Inspection or road-test record, load number | Mechanic DVIR, shop log or TMS | Varies; often not recorded |

Two of those hops are held by software when maintenance runs on the same platform as the driver app. Samsara's maintenance help pages say a reported fault can be attached to a work order as a line item, that every work order belongs to a single asset, and that closing the order marks the attached faults resolved. Its API reference adds a `resolvedBy` field naming the mechanic, and lets a mechanic file an inspection from the dashboard or through the API. Everywhere else in the table, the join depends on habits, not software.

## Trailer 2209, hop by hop (Illustrative)

A fictional 340-person food distributor pulls refrigerated trailers with whichever tractor is free that night. Trailers are where unit identity gets slippery, so this case follows one trailer rather than one truck. All values are invented.

| Hop | What happens | Record and key | Held by |
|---|---|---|---|
| Monday 04:10 | Night driver's pickup walk-around flags a dead marker lamp and a cracked rear door hinge on trailer 2209 | Inspection report listing tractor 61 and trailer 2209, two fault IDs | Driver app |
| Monday 04:40 | Dispatcher swaps in trailer 2214 for the grocery run | Load G-8812, trailer number changed | TMS |
| Monday 09:00 | Yard mechanic fixes the lamp in-house | Work order 7731 with the lamp fault attached | Same platform, so the fault ID carries |
| Tuesday | Hinge goes to an outside body shop; quote approved by text | Quote number on a phone, nothing on 7731 | Nobody's system |
| Thursday | Body shop invoice arrives; 7731 closed with both faults resolved | Closed order, mechanic named on the lamp fault only | Driver app and accounting |
| Thursday 22:30 | Trailer 2209 leaves on load G-8907 behind tractor 58 | Load number, new tractor number | TMS |

Three things stand out. The lamp fault has a clean system-held trail. The hinge fault closes on the strength of an invoice, with no named mechanic and no check before the next load. And the trailer's two loads sit behind two different tractors, so a join on the tractor number alone would scatter this one repair across two vehicles.

The federal rule in 49 CFR 396.11 asks the carrier to certify, on the original report, that each listed defect was fixed or did not need fixing before the equipment runs again. Whether that certification is written against both faults, and where it lives, is the question this case leaves open.

## Where the links snap

These are the breaks that turn one chain into separate fragments. Each is a question of fact the fleet manager can answer from memory.

1. **Defect ID does not cross systems.** When the shop uses a separate maintenance system, the work order may cite the DVIR by date and unit, or not at all. One unit with two open defects then has two repairs nobody can tell apart.
2. **Shop renumbering.** A migration to a new shop system often restarts work order numbers. Pre-migration history survives but cannot be joined by number.
3. **Approval outside the record.** Vendor estimates approved by phone, text or email leave the work order with a cost but no approver or approval date.
4. **Batch closing.** Work orders closed at month end, after the truck already left, put the close after the next dispatch and reverse the apparent order.
5. **Missing release check.** The work order closes and the next record is a load. Nothing shows anyone checked the repair.
6. **Unit identity drift.** A tractor renamed in the telematics app, or a VIN that appears only in the shop system, splits one truck into two records.

The missing context guide shows what a reader concludes when only one system survives; see [what a standalone Samsara export loses](/guides/driver-report-to-asset-return-missing-context). The [completeness checklist](/resources/driver-report-to-asset-return-completeness-checklist) turns each break into a pass, partial or fail mark.

## Five questions that reveal which links are system-held

Ask these in order. Each answer marks one link as system-held, typed or absent.

1. "When a driver reports a defect, does the work order show which DVIR it came from, and is that automatic?"
2. "Has the shop changed maintenance systems, and in which year did work order numbers restart?"
3. "Where would I see who approved a vendor repair, and the amount?"
4. "Do mechanics close work orders when the job ends, or later in a batch?"
5. "What has to happen between a closed work order and the next load, and where is it recorded?"

Write down the year each practice started. A link that became system-held in 2022 means the chain holds from 2022, not across the whole archive. The [Samsara records page](/systems/samsara-export-data) lists the objects that platform tends to hold, and [telematics data monetization](/questions/telematics-data-monetization) covers the wider category.

## Link owners and the CEO who can sign off

Each link has its own owner: the safety manager for DVIRs, the operations or dispatch manager for the TMS, the fleet maintenance manager for work orders, and finance or the fleet manager for approvals. None of them alone can authorize licensing the joined history. That is the CEO, who in an owner-run fleet is usually the owner.

Before you introduce, confirm the company has 50+ full-time employees at peak (contractors and leased owner-operators excluded), a documented operating history, rights to license the records 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.

Left for SourceX's review: de-identification, any contract limits on reuse, the years a buyer would value and the payout. You describe keys and owners; you never export or forward records. Advisors who support carriers' IT can find related context in [IT support for trucking companies](/guides/it-support-for-trucking-companies).

## 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.

If the fleet manager can tell you which of the six links are system-held and from which year, [register as a partner](/register), check the carrier on [who qualifies](/who-qualifies) and read the [program terms](/terms) before you introduce the owner.

## Sources

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