Logistics exception histories: separate company knowledge from client data with a field-by-field origin screen that asks who wrote each entry, who supplied it and whom it describes

Short answer

A logistics exception history, meaning the delay, damage, shortage and claim records plus how each one was resolved, can signal a company worth introducing. But a single record usually blends the company's own judgment with shippers' order data, carriers' status updates and consignees' personal details. Screen each field by origin before anything else: who wrote it, who supplied the facts, and whom it describes. Introduce the company when its own resolution work is substantial, its CEO wants the conversation and the client and personal layers can be left out or cleared in review.

Visual briefFull-size diagram
A three-circle Venn diagram of company-written, client-supplied and personal data, with exception fields placed in it: root cause and resolution in the company-only area, PO and SKUs in the client-only area, consignee address where client and personal overlap, and the update to the client where company and client overlap; carrier ETAs sit outside the circles as third-party data.
Where the fields of one exception record usually fall; the company-only area is the knowledge an introduction can rest on.

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 layerWho wrote itWho supplied the factsWhom it describesDefault sort
Exception code, timestamp, statusCompany staff or its systemThe companyThe shipmentCompany knowledge
Shipment reference, PO numbers, SKUs, declared valueThe shipper's booking or order feedThe clientThe client's goodsClient-supplied
Consignee name, address and phoneBooking dataThe clientA receiving person or businessPersonal and client data
Carrier status updates, ETAs, delivery notesThe carrierThe carrierThe movementThird party
Root-cause note and investigationCompany staffThe company, drawing on carrier and client factsThe failureCompany knowledge
Resolution chosen and its approvalCompany staffThe companyThe decisionCompany knowledge
Updates sent to the clientCompany staffMixedThe client relationshipMixed
Claim documents: bill of lading, invoice, inspection photosThe claimant and othersThe client or consigneeThe lossClient-supplied or third party
Claim decision letterThe carrierThe carrierThe claimCompany knowledge when the company is the carrier
Rates and accessorial chargesRate agreementsContract termsCommercial termsConfidential 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 resultLTL carrierWarehousing operatorFreight brokerage
Root cause and resolutionWritten narratives by company staffSupervisors' notes, mixed into client recordsWritten by brokerage staff, stored by the client
Where records sitThe company's own TMSEach client's WMSThe client's TMS
Client-supplied shareShipment references and claim documentsMost fieldsMost fields
Personal dataConsignee details, removableEnd customers' addressesConsignee details
Likely pathIntroduce if the CEO wants it; client and personal layers scoped outContracts decide first; see the 3PL data ownership questionCounsel 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:

  1. Which systems hold exception records, and whose account or tenant is each one?
  2. Roughly how many years of history, and about how many exceptions a year?
  3. Do staff write free-text root-cause and resolution notes, or only choose codes?
  4. What share of exceptions is recorded in client-owned systems?
  5. Do customer contracts say who owns operating records created while serving the client?
  6. For claims, does the company decide them as the carrier, or pass them to carriers as a broker or forwarder?
  7. Which personal details appear, such as consignees or drivers?
  8. 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.

  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

Are exception codes alone enough to interest anyone?

Codes show that something went wrong, not how it was handled. The fields that carry a company's knowledge are the written investigation, the resolution chosen and the reasons for it; if staff only pick codes from a list, there is much less of the company's own work to talk about.

Does removing consignee addresses and rates turn client data into company data?

No. Removing personal and commercial details is part of preparation, but who owns the underlying records is a separate question settled by the company's contracts and SourceX's rights review.

Should a freight advisor name the shippers whose loads appear in the records?

No. Client names stay out of every message. The introduction describes the company's own work at a level of record types, years and systems, and nothing more.

Sources

  1. refer.sourcex.si/who-qualifies
  2. refer.sourcex.si/terms
  3. ecfr.gov/current/title-49/subtitle-B/chapter-III/subc…
  4. sourcex.si/workflows/logistics-exception-resolution
  5. sourcex.si/how-it-works

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