The type of record never settles the question. The same exception log can be mostly the company's knowledge at a carrier and mostly a client's data at a warehouse operator, and only the origin of each field tells you which one you are looking at.
An exception record in plain terms
An exception is any shipment that leaves the plan: late, damaged, short, over, refused or misrouted. SourceX's own description of the workflow follows four steps (a shipment goes wrong, the team contacts carriers, a fix is arranged, the customer is updated) and says the trail sits in transportation management systems and carrier portals as exception records, carrier communications and resolutions.
Claims add a regulated rhythm for some firms. Under 49 CFR Part 370, which covers claims handled by motor carriers and freight forwarders, the carrier acknowledges a written claim within 30 days and says what further documents or information it needs, then within 120 days pays, declines or makes a firm compromise offer in writing, or reports the status in writing at that point and every 60 days while the claim stays open. A carrier's claim file therefore holds two kinds of material side by side: documents the claimant sent and letters the carrier wrote.
The exception-record origin screening
Ask three questions of every field, then sort it. The screen works from a field list or a blank form the company describes, never from real records.
| Field or layer | Who wrote it | Who supplied the facts | Whom it describes | Default sort |
|---|---|---|---|---|
| Exception code, timestamp, status | Company staff or its system | The company | The shipment | Company knowledge |
| Shipment reference, PO numbers, SKUs, declared value | The shipper's booking or order feed | The client | The client's goods | Client-supplied |
| Consignee name, address and phone | Booking data | The client | A receiving person or business | Personal and client data |
| Carrier status updates, ETAs, delivery notes | The carrier | The carrier | The movement | Third party |
| Root-cause note and investigation | Company staff | The company, drawing on carrier and client facts | The failure | Company knowledge |
| Resolution chosen and its approval | Company staff | The company | The decision | Company knowledge |
| Updates sent to the client | Company staff | Mixed | The client relationship | Mixed |
| Claim documents: bill of lading, invoice, inspection photos | The claimant and others | The client or consignee | The loss | Client-supplied or third party |
| Claim decision letter | The carrier | The carrier | The claim | Company knowledge when the company is the carrier |
| Rates and accessorial charges | Rate agreements | Contract terms | Commercial terms | Confidential commercial data |
The rows that matter most are the root cause, the resolution and, for carriers, the claim decision. If those fields carry written reasoning rather than a code picked from a list, and they sit in a system the company controls, the company's knowledge layer may be worth a conversation. If the useful content lives mostly in client-supplied fields or inside a client's own system, it is client data, and SourceX's screening guidance usually treats client-owned material as a poor fit.
Some layers are routinely stripped anyway. SourceX's workflow page lists consignee addresses, rates, names, emails and phone numbers, and account and payment numbers as removed before anything is shared. Stripping them is preparation; it does not change who owns what remains.
Three exception files on the screen (Illustrative)
Illustrative. The three operators below are invented to show the screen working; none is a real company, and no outcome is implied.
Original work. A 260-person regional less-than-truckload carrier whose overage, shortage and damage desk has kept ten years of exceptions and claims in its own TMS. Investigators write narrative findings, and the claims team issues written dispositions under its claim procedures.
Mixed content. A 180-person contract warehousing operator whose exception logs live inside each client's warehouse management system instance, interleaving its supervisors' notes with client SKUs, order data and end customers' addresses.
Uncertain ownership. A 140-person freight brokerage running a managed transportation program, where the client's TMS holds every exception the brokerage handled and the services agreement's work-product clause has not been read since it was signed.
| Screen result | LTL carrier | Warehousing operator | Freight brokerage |
|---|---|---|---|
| Root cause and resolution | Written narratives by company staff | Supervisors' notes, mixed into client records | Written by brokerage staff, stored by the client |
| Where records sit | The company's own TMS | Each client's WMS | The client's TMS |
| Client-supplied share | Shipment references and claim documents | Most fields | Most fields |
| Personal data | Consignee details, removable | End customers' addresses | Consignee details |
| Likely path | Introduce if the CEO wants it; client and personal layers scoped out | Contracts decide first; see the 3PL data ownership question | Counsel reads the services agreement; perhaps only the brokerage's own escalation playbooks |
The brokerage is the hard case. Its people did the thinking, yet the records may belong to the client under a contract nobody has checked. The screen can say that the knowledge is the brokerage's work; only the contract and SourceX's rights review can say whether the brokerage may license it.
Who owns the records, and where they started
Trace the origin of the material through four facts:
- The employing entity. Which company employed the people who wrote the investigations and resolutions at the time, and does it still hold the records?
- The system and its tenant. The company's own TMS or WMS, a client's instance, or a carrier's portal. Records that company staff wrote inside a client's system sit under the client's day-to-day control, and the contract decides who owns them.
- The customer contracts. Warehousing and logistics services agreements may say who controls operating records; the company's counsel reads them, not the advisor.
- Acquired operators. If the company bought other carriers or warehouses, their histories may sit in separate entities. A parent and its subsidiaries count as one referred company: the USD 50,000 floor applies once, to the group's first qualifying transaction, however many of them license; later qualifying transactions within the Repeat Window pay 15%.
The CEO of the entity that holds the records decides whether to talk. Operations leaders, the claims manager and the TMS administrator explain what exists; they do not authorize.
Before any introduction: 50+ full-time employees at peak (contractors excluded), years of documented operating history, rights to license and a CEO who authorizes the conversation. 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.
Questions to bring to the CEO, with no files attached
Eight questions, each answerable from memory or a system's settings page:
- Which systems hold exception records, and whose account or tenant is each one?
- Roughly how many years of history, and about how many exceptions a year?
- Do staff write free-text root-cause and resolution notes, or only choose codes?
- What share of exceptions is recorded in client-owned systems?
- Do customer contracts say who owns operating records created while serving the client?
- For claims, does the company decide them as the carrier, or pass them to carriers as a broker or forwarder?
- Which personal details appear, such as consignees or drivers?
- Was any part of it ever licensed to someone else for AI training? SourceX asks suppliers to confirm that it was not.
Never ask for exports, screenshots, sample exceptions, portal logins, client names or rate sheets. If the CEO starts sending examples, stop them and point to the questions instead. The live guide to identifying logistics exceptions and their resolutions and the OS&D freight data type describe the records in more depth, and the screening worksheet for logistics and warehousing businesses gives the fit questions in a form you can reuse.
Where field-by-field screening goes wrong
- Origin is not ownership. A field written by company staff can still belong to a client under contract. The screen points to where rights questions sit; it does not answer them.
- Codes look like knowledge. A long history of coded exceptions with no written reasoning can look rich and hold little of the company's own judgment. Question 3 catches this.
- Regulated claim files vary. Part 370 covers motor carriers and freight forwarders. For a broker, a warehouse or any other operator, do not assume the claim file looks like a carrier's; ask question 6 instead.
- Demand is decided later. Whether exception histories match a current program is checked only in SourceX's review, and a clean screen can still be declined.
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 the screen shows that a logistics company's own investigations and resolutions carry the history and its CEO wants to talk, register for a partner link, confirm the company on who qualifies and read the attribution rules in the program terms before you submit; the logistics and warehousing industry page shows where these companies usually fit.