# Samsara export missing context: before and after | SourceX

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

A single-system driver-report-to-asset-return export loses the reasons and the money. A telematics export keeps the reported fault, the vehicle and its cleared status, sometimes with the technician who signed it off. It drops how long the truck was out of service, which load moved and whether it delivered on time, what the repair cost, who approved it and whether anyone checked the truck before it went back out. That context lives in the TMS, the shop system and often an inbox.

This page belongs to the [driver report to returned vehicle guide](/guides/chain-driver-report-to-asset-return). It reads one fictional repair twice: first from the telematics record alone, then with the records around it.

## Before: unit 7062 as the telematics record shows it

Illustrative. A fictional 380-person refrigerated carrier hauling grocery freight. Every value is invented.

| Field in the telematics export | Value |
|---|---|
| Vehicle | Unit 7062, tractor |
| Inspection | Pre-trip report, Tuesday 03:50, at a customer yard |
| Defect | Steer tire sidewall cut, marked unsafe to operate |
| Defect status | Resolved, Wednesday |
| Cleared by | Named technician |
| Post-repair inspection | None filed |
| Next inspection | Pre-trip report, Thursday 02:30, nothing found |

The vendor documents a field naming who cleared each defect, so the sign-off is real data. Its help center also says a defect attached to a work order clears when that order closes, so "resolved" can simply mean the paperwork was finished.

### What a reader concludes

A driver spotted a damaged tire, it was replaced within a day and the next pre-trip was clean. Routine. The reader cannot tell whether the replacement happened at the yard or the shop, what it cost, whether a temperature-controlled load sat waiting, or whether Thursday's pre-trip was the first time anyone looked at the new tire.

## After: the same repair with dispatch and shop records attached

Add the TMS, the shop system and the fleet manager's phone log, and the same day and a half reads very differently.

- **TMS, Tuesday 04:10.** The loaded trailer is due at a distribution center at 09:00. Dispatch reschedules the delivery appointment to the afternoon and notes "tire."
- **Phone, Tuesday 05:00.** The maintenance manager authorizes a roadside tire vendor by phone. Nothing is written down at the time.
- **Shop system, Tuesday 11:30.** A work order is opened after the fact, listing two steer tires replaced as a pair, a vendor road-service charge, the defect as a line item and a note that the manager approved the vendor by phone.
- **TMS, Tuesday 15:00.** The load delivers six hours late; the customer's detention and late-delivery notes are attached to the load.
- **Shop system, Wednesday.** The vendor invoice arrives and the work order closes, which resolves the defect.
- **TMS, Thursday 03:05.** Unit 7062 is dispatched after the next driver's pre-trip.

Now the reader sees a roadside repair approved by phone, a work order written afterward to record it, a grocery delivery that missed its window, and a defect marked resolved a day after the tire was actually changed because the invoice drove the close. Same truck, same days, a different record.

## Reading it the other way: a TMS export without the defect

The loss runs in both directions. A dispatch-only export for the same week shows unit 7062 idle from Tuesday to Thursday and a late load with a one-word note. It cannot tell a tire replacement from a driver vacation, a missing permit or a slow freight week. Forecasting and utilization analysis built on that export would count the idle days as lost capacity with no cause, which is the gap [driver-based forecasting](/guides/driver-based-forecasting) runs into when operational drivers are missing. The [dispatch and service workflow guide](/guides/how-to-assess-dispatch-and-service-workflows-in-transportation) covers the operations side in more depth.

## The lost-context table: what each single system drops

Each row is context a single export cannot hold, where it usually lives and who owns it.

| Context a reader needs | Telematics export alone | TMS export alone | Where it usually lives | Usual owner |
|---|---|---|---|---|
| What the driver reported | Yes: defect and DVIR | Two-word note at most | Telematics app | Safety manager |
| How long the unit was out | Inspection times only | Idle days, no cause | TMS plus work order dates | Operations manager |
| Which load moved and how it ended | No | Yes | TMS | Dispatch lead |
| What was found and replaced | Defect only | No | Work order line items | Fleet maintenance manager |
| Cost and approver | No | No | Shop system, accounting or email | Fleet manager or finance |
| Post-repair inspection before the next load | Only if a mechanic DVIR was filed | No | Mechanic DVIR, road-test log or nowhere | Shop lead |
| Whether the defect came back | Later DVIRs, unlinked | No | Telematics history for the unit | Safety manager |

Federal rules set a three-month minimum for keeping the DVIR, the certification of repairs and the driver's review certification under 49 CFR 396.11, and reports may be kept electronically. That floor covers the left-hand column only. The other columns follow each company's own retention habits, which is why the partner asks about them separately. For the repair-order side as a data category, see [fleet maintenance records](/data-types/fleet-maintenance-records); for the identifiers that rejoin the columns, see the sibling guide on [driver report to asset return record linkage](/guides/driver-report-to-asset-return-record-linkage).

## Scoping the restorable context with the fleet

A partner's job is to learn which rows of the table the company can restore, for which years, and who controls each system. Ask, do not collect.

- **Records that exist:** DVIRs and defects, dispatch history, work orders and line items, vendor invoices, approval trails.
- **Who owns them:** safety for inspections, operations for dispatch, maintenance for work orders, finance or the fleet manager for approvals.
- **Who can authorize a licensing discussion:** the CEO (in an owner-run fleet, usually the owner), because the joined history crosses all four teams.
- **Company baseline:** 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.
- **Unknown until SourceX reviews it:** how driver and location data would be removed, whether vendor or shipper contracts limit use, which years a buyer wants and what the company would be paid.

If a TMS replacement is planned, the export decision for dispatch history will be made soon. That is a real reason to raise the conversation now, and the [completeness checklist](/resources/driver-report-to-asset-return-completeness-checklist) gives you the questions to ask first. The page on [what data is missing from AI training](/questions/what-data-is-missing-from-ai-training) explains why joined operational histories like this are scarce.

## 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 carrier can restore downtime, approvals and dispatch changes alongside its inspection records, [register as a partner](/register), check it 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
