This template is part of the detention charge disputes guide. The warm introduction brief is the general version; this one asks the questions specific to detention.
How to use the template
Fill it in after one conversation with the sponsor, usually the operations director, then send it back to them for correction. Three rules keep it useful:
- Metadata only. Describe record classes, systems, years and volumes. Never attach or quote an invoice, email, export, screenshot or customer name.
- Confirmed or marked. Every entry is either confirmed by the sponsor or labeled "estimate" or "unknown", with the basis for any estimate.
- Forwardable. Write in plain sentences the CEO can read cold. If a line needs the partner to explain it, rewrite it.
The client opportunity brief generator produces a general draft you can adapt; the fields below are the ones a detention history needs.
The blank template
Copy the left column and fill in the middle one. The right column tells you where the answer normally comes from.
| Field | Fill in | Where the answer comes from |
|---|---|---|
| Company | Sector, headcount at peak (full-time, contractors excluded), country, years operating | Sponsor; public profile for years operating |
| Business task | One sentence on how detention invoices are checked and settled | Sponsor |
| Record classes | Which of: stop arrival and departure events, appointment records, appointment and dispute emails, original carrier invoices, revised invoices, approvals, rate confirmations | Sponsor and AP manager |
| Systems | TMS name, mail system, AP or accounting system, any tracking integration | TMS administrator |
| Years of history | First and last year for each record class, and any gaps | TMS administrator and mail administrator |
| Volumes | Loads per year, loads with a detention line, disputed lines; estimate or report-based | TMS report run by the company |
| Access event | Any contract end, migration cutover or retention deletion with its date | Contract or project plan |
| Open question | The one thing nobody can yet confirm | Sponsor |
| Record owners | Who owns each record class | Sponsor |
| Authorized contact | Who can authorize a licensing discussion | Sponsor, confirmed with that person |
| Not shared | A line stating what the partner did not see or receive | Partner |
The access event matters because it is the only real urgency. If the company's Microsoft 365 subscription or the legacy TMS contract is ending, record the date from the contract. Microsoft documents that a business subscription moves through Expired, Disabled and Deleted stages, that data is accessible to admins only while Disabled, and that a new subscription does not restore deleted data. If there is no access event, write "none known"; do not invent one.
Completed example (Illustrative)
A fictional freight broker, written up after a planning call with its operations director. Every value is invented.
| Field | Entry |
|---|---|
| Company | Freight broker, 260 full-time staff at peak, U.S., operating 16 years |
| Business task | Checking carrier detention invoices against appointment times and free-time terms, and settling disputes by revised invoice |
| Record classes | Stop arrival and departure events; appointment confirmations and dispute threads; original and revised carrier invoices; AP approvals; rate confirmations |
| Systems | Legacy TMS being replaced; dispute team shared mailbox in Outlook; AP approvals inside the TMS carrier pay module |
| Years of history | TMS: about 7 years of settled loads. Shared mailbox: since year 4 of the 7; earlier threads in personal mailboxes, coverage not confirmed |
| Volumes | About 48,000 loads a year; roughly 11% carry a detention line; about 1,900 disputed lines a year (estimate from a TMS report) |
| Access event | Legacy TMS read-only access ends at contract expiry in the second quarter |
| Open question | When a carrier arrived before the booked slot, did the team apply one start rule consistently, and does the TMS keep the original billed line after a revision? |
| Record owners | Operations director (stop events), AP manager (carrier pay), IT manager (mailbox) |
| Authorized contact | CEO, with the operations director as sponsor |
| Not shared | No exports, samples, logins, invoices, emails or customer names |
The open question is the most useful line. It tells the CEO and SourceX what is uncertain without anyone overstating the history. Two other lines deserve a second look before sending. The mailbox coverage note matters because early threads sat in personal mailboxes: Microsoft documents that a deleted Microsoft 365 user can be restored with their data within 30 days, after which the account and mailbox are permanently deleted, so any departed rep's threads may already be gone. And the TMS line says "being replaced" without promising what the old system can produce; whether settled loads come out with their revision history is for the company's administrator to confirm, and the brief should not claim an export nobody has checked.
What to leave out, and why
A good brief is short because of what it omits.
| Leave out | Why |
|---|---|
| Customer or shipper names | Confidential to the company, and often restricted by contract |
| Carrier names and invoice amounts | Commercial terms, and not needed to judge fit |
| Driver or staff names | Personal data; the rights review decides how it is handled |
| Screenshots or sample exports | Partners never handle raw records |
| A value estimate or reward figure | Unknown until SourceX reviews it; any number would mislead |
| Claims about buyer interest | SourceX has not reviewed the opportunity yet |
SourceX licenses approved business data directly from companies for AI training and evaluation and manages the agreement, rights review, data preparation, delivery and payout. What stays unknown until SourceX reviews the opportunity: dataset demand for these records, the rights result, the company's offer and any reward.
Checks before you send it
- ☐The sponsor has read and corrected every line.
- ☐Headcount is full-time staff at peak, contractors excluded, and is 50 or more.
- ☐The company has a documented operating history and, as far as the sponsor knows, rights to license its records.
- ☐Location is covered. 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.
- ☐The authorized contact, the CEO, is named and knows the brief is coming. The who-can-say-yes decision tree explains the other roles.
- ☐System and year entries match what the detention system map would show.
- ☐You have signed the Channel Partner Agreement.
The first valid introduction within the 90-day window is credited when the company submits a verified application. More logistics examples sit under industries.
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 sponsor has confirmed the brief and the authorized contact expects it, register as a partner, check the company on who qualifies and read the program terms before you submit the introduction.