This decision tree is part of the detention charge disputes guide. It does one job: get a partner from "who knows about these records" to "who can authorize a discussion about them", without mistaking access for authority.
The decision tree, question by question
Work down the tree in order. Each question either names a role to talk to or sends you to the next question.
- Who runs the detention dispute process day to day? Usually the operations director, sometimes a carrier relations or settlements manager. This person is your sponsor: they know the volume, the systems and the gaps. They can say whether the history is worth describing. They usually cannot approve licensing alone. Go to question 2.
- Who owns each record class? Carrier pay lines, revisions and approvals belong to the controller or AP manager. Stop events and appointments belong to operations, administered by IT. Dispute email belongs to whoever administers the mail system, often IT under a retention policy. Owners confirm what exists. Go to question 3.
- Who holds the keys to the systems? The TMS administrator and the Microsoft 365 administrator know what can be exported and when access ends. Microsoft Purview eDiscovery, for example, lets a compliance administrator search mailboxes and export results as PST files, with export packages expiring 14 days after creation. That is a technical capability, not a decision right. Go to question 4.
- Who can decide to license company data? The CEO. In a founder-owned broker, that is usually the owner; in a private equity portfolio company, the board or sponsor may want to see it. Go to question 5.
- Does anything need sign-off beyond the CEO? Counsel reviews shipper contracts, carrier agreements and personal data in the records. If yes or unsure, the answer at this point is "the CEO, after counsel". Go to the end.
- End: SourceX's rights review. No one at the company can say yes to a specific dataset before this. The review decides which records can be used, in what form and under what conditions.
Roles at a broker and what each can approve
The table is the evidence asset: one row per role, what they own, and what they can and cannot approve.
| Role | Owns or controls | Can authorize a licensing discussion? | Signs off on |
|---|---|---|---|
| Operations director | The dispute process, coverage knowledge | Usually not alone; the natural sponsor | Accuracy of the description |
| Carrier relations or settlements manager | Dispute threads, carrier contacts | No | Which disputes were handled and how |
| Controller or AP manager | Carrier pay lines, revisions, approvals | No; confirms financial records exist | Completeness of the pay history |
| TMS administrator | Exports, access dates, field history | No; access is not authority | What the system can produce |
| Microsoft 365 administrator | Mailboxes, retention settings, eDiscovery | No | Which mailboxes survive and how far back |
| General counsel or outside counsel | Contract review, privacy review | Advises the CEO | Restrictions in shipper and carrier terms |
| CEO | Decisions on company assets | Yes, and signs | The decision to open a discussion |
| Board or sponsor | Oversight of material decisions | No; may want visibility | Depends on the company's governance |
Sign-offs that sit outside the executive team
Detention records are not purely the broker's own. Three kinds of third-party interest can affect what the CEO is able to approve.
- Shipper contracts. Many brokerage agreements include confidentiality terms covering load details, facility names and rates. Counsel reads these before anything else is decided.
- Carrier agreements. Broker-carrier contracts and rate confirmations may limit how carrier invoices and correspondence are shared. The carrier does not usually need to approve, but the terms decide what must be removed.
- Personal data. Dispute threads name drivers, dispatchers and dock staff, with phone numbers and email addresses. Under the GDPR, personal data is any information relating to an identified or identifiable natural person; similar concepts apply in other jurisdictions. For EU-based brokers, or records about EU individuals, counsel has to assess this before any reuse is discussed.
The data rights explainer sets out why this question comes before any discussion of value. A partner never answers it on the company's behalf.
Where the answer stays unknown
Even with the CEO engaged and counsel involved, these remain open until SourceX reviews the opportunity with the company:
- Whether shipper and carrier terms allow reuse at all, and with what redaction.
- Which record classes are in scope: stop events, pay revisions, email, or only some.
- What must be de-identified, such as driver names or facility addresses.
- Whether there is dataset demand for detention dispute records.
- The company's offer, which is set in its own agreement with SourceX, and any reward.
For SourceX, the introduced company needs 50+ full-time employees at peak (contractors excluded; owner-operators under contract do not count), 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.
Three company shapes and who to introduce (Illustrative)
The tree lands in different places depending on how the company is owned and run. These three shapes are Illustrative, not real companies.
| Company shape | Sponsor | Likely authorized contact | Extra gate |
|---|---|---|---|
| Founder-owned broker, 120 staff | Operations director | Founder and CEO | Outside counsel on shipper terms |
| Private equity-backed broker, 450 staff | VP of operations | CEO, with the CFO | Sponsor or board visibility |
| Brokerage division of an asset carrier, 900 staff | Division operations lead | Parent company CEO | Group legal and privacy review |
In a distressed situation, authority can shift again: a trustee or assignee may control the records, which the page on trucking company bankruptcy covers. Where a fractional CFO is engaged, that person may be a useful sponsor; see fractional CFOs for logistics companies. Before the introduction, the system map of detention records helps the sponsor describe what exists, and the referral brief template gives them something to forward. Partners sign the Channel Partner Agreement before submitting, and the first valid introduction within the 90-day window is credited when the company submits a verified application.
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.
Once the sponsor has agreed to bring in the CEO, who can authorize a discussion, register as a partner, confirm the company on who qualifies and read the program terms before you make the introduction.