Driver report to asset return record chain: the keys that link a DVIR defect, a work order and the next dispatch

Short answer

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.

Visual briefFull-size diagram
Six record links click together from DVIR defect to work order, approval, closed work order, release check and next load; the link between the closed work order and the next load is highlighted as weak and then repaired with a recorded release check.
Illustrative: trailer 2209. The trailer number runs through every record; the fault ID and the release check are the links most easily lost.

This page is part of the driver report to returned vehicle guide. 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.

StepRecord createdKey carried forwardTypical systemWho writes the key
1. Driver finds a defectDVIR with one or more defectsUnit number, DVIR ID, defect IDSamsara or another ELD appSystem
2. Load is reassignedDispatch change on a planned loadUnit number, load numberTMSSystem for IDs; reason typed
3. Repair is openedWork order with line itemsWork order number, defect ID if linkedSamsara maintenance or a shop systemSystem if same platform; typed otherwise
4. Cost is approvedVendor estimate and approvalEstimate number, approverShop system, accounting or emailOften a person, outside any system
5. Repair is closedClosed work order, resolved defectWork order number, mechanic on the defectSamsara maintenance or shop systemSystem
6. Unit returns to serviceRelease check, then next loadInspection or road-test record, load numberMechanic DVIR, shop log or TMSVaries; 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.

HopWhat happensRecord and keyHeld by
Monday 04:10Night driver's pickup walk-around flags a dead marker lamp and a cracked rear door hinge on trailer 2209Inspection report listing tractor 61 and trailer 2209, two fault IDsDriver app
Monday 04:40Dispatcher swaps in trailer 2214 for the grocery runLoad G-8812, trailer number changedTMS
Monday 09:00Yard mechanic fixes the lamp in-houseWork order 7731 with the lamp fault attachedSame platform, so the fault ID carries
TuesdayHinge goes to an outside body shop; quote approved by textQuote number on a phone, nothing on 7731Nobody's system
ThursdayBody shop invoice arrives; 7731 closed with both faults resolvedClosed order, mechanic named on the lamp fault onlyDriver app and accounting
Thursday 22:30Trailer 2209 leaves on load G-8907 behind tractor 58Load number, new tractor numberTMS

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.

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. The completeness checklist turns each break into a pass, partial or fail mark.

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 lists the objects that platform tends to hold, and telematics data monetization covers the wider category.

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.

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, check the carrier on who qualifies and read the program terms before you introduce the owner.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Is the unit number enough to link the whole chain?

It links records to the same truck, not to the same repair. A unit with three defects in a month has three chains that share one unit number. The defect ID or work order number is what keeps them apart.

The fleet runs a separate shop system, not Samsara maintenance. Does the chain still work?

It can, but the defect-to-work-order link then depends on how the shop records the defect, often as a typed reference or nothing. Ask how a mechanic knows which DVIR a job came from and mark the link accordingly.

Do I need API access or exports to map the keys?

No. Ask the fleet manager which field holds each key and whether it is filled by the system or typed. You never pull data, and SourceX does not claim a connector to any fleet tool.

Sources

  1. refer.sourcex.si/terms
  2. developers.samsara.com/docs/digital-vehicle-inspection-reports
  3. kb.samsara.com/hc/en-us/articles/32504504318989-Work-Orders…
  4. ecfr.gov/current/title-49/subtitle-B/chapter-III/subc…

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment