This template belongs to the classification corrections guide, which explains what to inventory before a broker platform migration. This page gives you the form itself and one completed Illustrative example.
The blank template
Copy the fields into an email or a document. Each one should take a sentence or a number. If a field is unknown, write "unknown" and who could answer it; a blank invites guessing.
| Field | What to write | Where the answer comes from |
|---|---|---|
| Company | Full-time headcount at peak, country, importing company or broker | Compliance director or HR |
| Business task | One sentence on why corrections happen at this company | Compliance director |
| Record classes | Amended entries, correction filings with reason codes, broker notes, cited precedents, internal approvals, product master changes | Compliance director |
| Systems | Plain-text names: broker platform, filing software, mail archive, ERP product master | IT or the integrator |
| Years of history | First and last year each system covers, as the system shows it | System administrator |
| Volume | Rounded count of corrections and how it was counted | Filing software report |
| Record owners | Who authored each class: importing company, broker, consultant | Compliance director |
| Open question | The one rights question the review should start with | Compliance director with counsel |
| Records event | Migration, contract end or archive date, confirmed by the company | IT or the vendor contract |
| Internal sponsor | Name and role of the person who will sponsor the discussion | Compliance director |
| Executive sign-off | The CEO, who can authorize a licensing discussion | Internal sponsor |
| Not shared | A line confirming no records, samples or client names are attached | You |
Twelve fields fit on one page. If a field runs longer than two lines, it probably holds detail that belongs in the later review, not in the brief.
How to fill each field without touching a record
Most fields are answered from memory or a system report. Three need care.
Volume. A correction on an unliquidated entry often goes through a post summary correction, which carries up to five reason codes. That makes reason codes a clean way to count: the filing software can report how many corrections were filed per year without anyone reading one. Round the number and say it came from a report.
Years of history. Entry records are generally kept for five years from the date of entry, so many companies hold at least that much. Older material often sits in a previous broker platform or an archive. Write what each system actually holds, not the retention policy.
Record owners. Separate what the importing company wrote from what a broker or consultant wrote. A broker's records about a client's business are confidential and may be shared with third parties only in listed cases, including the client's written authorization. If broker notes are central, say so; that is the open question.
Cited precedents are a lighter case. The rulings themselves are public in CROSS; what the company holds is its own record of which ruling it relied on for which part.
A completed brief (Illustrative)
The company below is fictional, invented for this page. It is not a real account, an offer or a completed deal.
| Field | Example entry |
|---|---|
| Company | About 260 full-time staff at peak, U.S. industrial components company that imports its parts |
| Business task | Correcting tariff classifications when a product's stated end use or spec changes after import |
| Record classes | Amended entries with reason codes, broker notes, cited precedent numbers, internal approvals, product master changes |
| Systems | Broker platform being replaced, customs filing software, Microsoft 365 mail, ERP product master |
| Years of history | About seven years of entries; broker notes from year two onward |
| Volume | About 600 corrections, counted from reason codes in the filing software |
| Record owners | Importing company for approvals and product data; broker for notes; one outside consultant memo set |
| Open question | Whether broker notes are the importing company's records or the broker's under the brokerage agreement |
| Records event | Read access to the old broker platform ends at contract expiry; date confirmed by the company |
| Internal sponsor | Director of trade compliance |
| Executive sign-off | CEO, with the CFO and general counsel |
| Not shared | No entries, notes, specifications or client names attached |
Read it as SourceX would. The open question tells the reviewer where to start. The records event explains why the conversation is timely without inventing urgency. The volume line says how it was counted, so nobody mistakes an estimate for an audit.
Mistakes that weaken a brief
| Mistake | Why it hurts | Fix |
|---|---|---|
| Attaching a sample entry | Moves client data before any rights review | Describe the record class instead |
| "Lots of corrections" | Gives the reviewer nothing to weigh | A rounded count and its method |
| Naming IT as the decision-maker | Confuses access with authority | Name the internal sponsor and the CEO, who signs off |
| Hiding the broker question | The review finds it later and stalls | Put it in the open question field |
| Promising demand or a reward | Nobody can know either before review | Keep the brief factual |
For the covering note that goes with the brief, use the warm introduction brief for a business owner. The client opportunity brief generator can format the same fields. If the executive sign-off line is hard to fill, the who-can-say-yes decision tree walks through it, and the exception examples show what kind of case makes the history worth describing.
What the brief cannot settle
The brief starts a conversation. It does not decide whether records can be licensed, whether a buyer wants them, how they would be de-identified or whether any offer follows. Those wait for SourceX's rights review. For the rules behind the field notes, see CBP's page on post summary corrections, the record retention rule at 19 CFR 163.4, the broker confidentiality rule at 19 CFR 111.24 and the public rulings database, CROSS.
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 70% of the data is in English. Partners sign the Channel Partner Agreement before submitting introductions, and the first valid introduction within the 90-day window is credited when the company submits a verified application. Consultants who advise on classification should also read the tariff classification consultant guide; the industries hub lists neighboring sectors.
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 compliance director has checked every field and named the CEO as the one who signs off, register as a partner, confirm the company on who qualifies and read the program terms before you send the brief.