This map is part of the roadside repair authorizations guide, which walks through one out-of-network breakdown. Here the focus is the joins: which system holds what, and which identifier carries the case from one to the next.
Six systems behind one roadside repair
A single breakdown at night touches more tools than most fleets realize, and each is owned by a different team.
- Telematics or driver app. Fault codes, location and the driver's report, keyed by unit.
- Service desk. The breakdown ticket, call log and vendor search, in-house or outsourced.
- Vendor inbox or portal. The outside shop's quote, often an email, sometimes a text.
- Purchasing. The approval against a limit and the PO.
- Fleet maintenance system. The work order with system and part codes.
- Accounts payable. The vendor invoice, the match to the PO and any variance note.
Regulation explains only part of what survives. Section 396.3 of the federal motor carrier rules obliges carriers to hold certain maintenance paperwork for a year at the location that houses or services the vehicle, and for six months once the unit leaves their control. Part 379 lists minimum periods for other carrier documents and hands everything past them to management. No rule tells a fleet to keep an off-hours quote or the name on a verbal approval, so joins differ widely from one carrier to the next.
System, record, linking key, owner
| System | Record | Linking key it should carry | Typical owner | Where the key drops |
|---|---|---|---|---|
| Telematics or driver app | Fault event, driver report | Unit number, timestamp | Fleet manager | Driver phones the desk instead of using the app |
| Service desk | Breakdown ticket, call log | Ticket ID, unit number | Service desk lead or provider | Event logged by phone without the unit ID |
| Vendor inbox or portal | Quote | Ticket ID in subject or reference | Service desk | Quote arrives by text and is typed up later |
| Purchasing | Approval and PO | PO number, ticket ID, approver | Fleet manager, purchasing | Verbal approval noted as approved per FM |
| Fleet maintenance system | Work order | PO number, unit number, repair code | Maintenance manager | Outside repair entered as a lump-sum line |
| Accounts payable | Invoice and variance note | PO number | Controller | Invoice keyed without the PO |
The service desk row deserves a second look when the desk is outsourced. The ticket ID then belongs to the provider, and the fleet's records join only if someone copied it onto the PO.
A joined breakdown case (Illustrative)
A fictional 260-person refrigerated carrier. A trailer reefer unit fails on a Sunday afternoon, far from any contracted shop. All identifiers are invented.
| Step | System | Record | Keys present |
|---|---|---|---|
| Fault | Telematics | Reefer temperature alarm on trailer T-318 | T-318, 15:42 |
| Ticket | Service desk | Ticket RS-90214, vendor search logged | RS-90214, T-318 |
| Quote | Vendor inbox | Quote emailed with RS-90214 in the subject | RS-90214 |
| Approval | Purchasing | Weekend manager approves, PO 55107 issued | PO 55107, RS-90214, approver name |
| Repair | Fleet system | Work order coded to the refrigeration system | PO 55107, T-318, repair code |
| Invoice | Accounts payable | Vendor invoice matched to PO 55107 | PO 55107 |
| Follow-up | Fleet system | No repeat refrigeration fault within 30 days | T-318, same repair code |
This case joins cleanly because every step carries at least one key from the step before, and the follow-up uses the same repair code as the original. Because the VMRS scheme, maintained by TMC, can code a job anywhere from the system level to a single part, a second refrigeration fault on T-318 can be matched to the first even years afterward.
Handoffs where the chain usually breaks
Walk the six handoffs and note which ones a given fleet can vouch for.
- Driver to desk. Breaks when the call is not tied to a unit. Ask whether off-hours events are logged in the same tool as daytime ones.
- Desk to quote. Breaks when quotes arrive by phone or text. Ask what share of quotes are written.
- Quote to approval. Breaks when approvals are verbal. Ask whether the approver's name and limit are recorded against the quote.
- Approval to work order. Breaks when outside repairs are lumped together. Ask whether the PO appears on the work order.
- Work order to invoice. Breaks when accounts payable keys invoices without the PO. Ask the controller how unmatched invoices are handled.
- Repair to repeat failure. Breaks when codes are inconsistent. Ask whether repairs are coded with VMRS or a house scheme.
What usually stays missing: the policy that set the approval limit in a given year, and call notes held by an outside breakdown service. Record them as unknowns. Part 379 notes that records can be kept in any technology that reproduces them accurately and must be protected from unauthorized access or modification, so ask where older years now sit rather than assuming they are gone. The fleet maintenance records page covers the diagnostic side of the same work orders.
What the fleet manager can confirm without exports
Every question above is answerable in conversation. A partner records the answers as metadata: which systems, which keys, which years, rough counts of out-of-network repairs. No tickets, invoices or exports change hands. A DOT compliance consultant or an insurance agent handling a fleet renewal often already knows which systems a fleet runs. Telematics data raises its own ownership questions, covered in who owns equipment data, and the officer who can authorize a licensing discussion is found with the decision tree for these records.
The fleet needs 50+ full-time employees at peak (contractors 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 90% of the data is in English. Unknown until SourceX reviews it: SourceX's current data needs, how vendor and service-provider contracts affect rights, preparation needed and any offer. Partners sign the Channel Partner Agreement first; attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application. Capture the answers in the referral brief template.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the fleet manager confirms that unit, ticket and PO numbers carry through from the service desk to accounts payable, register as a partner, check the fleet against who qualifies and read the program terms before you introduce the executive who decides.