This template is part of the interchange exception resolution guide. Fill it after a conversation with the operations director, using only facts the carrier can confirm.
The blank brief: eight lines and one question
Each line takes a phrase or a short sentence. Where you do not know, write "unknown" and name who could check.
| Line | What to write | Example of the right level | Never write |
|---|---|---|---|
| 1. Carrier | Type of operation, full-time headcount at peak, country | "Drayage carrier, about 300 full-time staff, U.S." | Customer or provider names |
| 2. Drivers | Employees or owner-operators, roughly what share | "Mostly employee drivers" | Driver names |
| 3. Exception task | The kind of equipment exception resolved | "Per diem disputes after missing gate events" | A specific move |
| 4. Systems | Plain names for tracker, dispatch, mailbox, dispute log, accounting | "Tracker service, dispatch platform, shared mailbox, ERP" | Logins, device lists |
| 5. History | Years covered, per system if they differ | "Dispute log since 2020; mailbox since 2018" | Retention advice |
| 6. Volumes and outcomes | Disputes per year or in total; how outcomes are recorded | "About 700 a year; credits recorded in accounting" | Dollar amounts |
| 7. People | Who owns the records day to day; who can authorize a licensing discussion | "Operations director; CEO" | Opinions on value |
| 8. Platform event | A documented upgrade, migration or contract end, with its source | "Dispatch platform replaced in Q2 per signed plan" | Guessed deadlines |
| Open question | The single gap that most limits the history | See the notes below | Speculation about specific disputes |
Notes on lines that need care
Line 2, drivers. Carriers with owner-operator fleets can have long dispute histories and still fall short of 50 full-time employees, because contractors are excluded. Ask this early.
Line 3, exception task. Equipment disputes take several forms, such as per diem, damage claimed at the gate or a wrong equipment number. The UIIA, the industry's standard handover contract, covers liability and other interchange issues, but the brief only needs the kinds the company actually disputes, in its own words.
Line 5, history. Give years per system, because they rarely match. If delay decisions sit in the mailboxes of dispatchers who have left, ask whether those mailboxes still exist: in Microsoft 365, a mailbox is kept as an inactive mailbox only if a hold or retention policy was applied before the account was deleted.
Microsoft 365Line 6, outcomes. The outcome is what makes a dispute record useful, so say where it is recorded: a credit memo, a status in the dispute log, an email. If outcomes live only in email, say so; that is still an outcome, just a harder one to join.
Line 7, people. The operations director is usually the owner and sponsor; the signer is the CEO. The who-can-say-yes tree explains how to tell them apart.
Line 8, platform event. Only documented dates count. The retention timeline shows which records an upgrade puts at risk first.
The open question. For this workflow, the most informative question is usually whether delay reasons were ever coded, or only written in email. It tells SourceX how much of the reasoning survives in structured form.
A completed brief (Illustrative)
The entries describe a fictional carrier. They are Illustrative: not a real company, dispute or deal, and not a forecast.
| Line | Completed entry |
|---|---|
| 1. Carrier | Drayage carrier serving rail ramps, about 310 full-time staff at peak, United States |
| 2. Drivers | Mostly employee drivers; a small owner-operator group not counted in headcount |
| 3. Exception task | Disputing per diem and damage charges when a gate event is missing or contested |
| 4. Systems | Asset tracker service, dispatch platform, shared dispatch mailbox, dispute spreadsheet, accounting ERP |
| 5. History | About six years of disputes in the spreadsheet; tracker history for four years; mailbox archived since 2019 |
| 6. Volumes and outcomes | Roughly 4,000 disputes in total; credits and rejections recorded in accounting, most with the dispute number |
| 7. People | Operations director owns the records; CEO can authorize a licensing discussion, with general counsel |
| 8. Platform event | Dispatch platform replacement with cutover set in the signed project plan for next spring |
| Open question | Were delay reasons ever coded in the dispatch platform, or only written in email? |
What is missing is deliberate: no container numbers, no provider or customer names, no invoice amounts, no sample emails.
Before you send it
- Read each line and ask whether anything would need redacting. If so, remove it.
- Confirm the basics. The introduced company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license 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.
- Sign the Channel Partner Agreement before submitting. The first valid introduction within the 90-day window is credited when the company submits a verified application.
- Set expectations: buyer interest, what provider and tracker contracts allow, and any offer stay unknown until SourceX reviews the opportunity.
The warm introduction brief has wording for the covering note, and the client opportunity brief generator formats the lines. For the wider dispatch picture, see how to assess dispatch and service workflows in transportation and AI-to-human handoff data.
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.
When all eight lines and the open question are filled and the operations director is ready to forward the brief, register as a partner, confirm the carrier on who qualifies and read the program terms before you submit.