This template is part of the claims document completeness review hub. Fill it after a first conversation with the head of claims operations and keep every line to facts the company can confirm.
The template: eight fields and one question
Each field takes a line or two. Where an answer is not known, write "unknown" and name who could check.
| Field | What to write | Good entry (format) | Never include |
|---|---|---|---|
| 1. Company | Carrier, MGA or administrator; full-time headcount at peak; country | "Regional property carrier, about 900 full-time staff, U.S." | Policyholder or broker names |
| 2. Task | The completeness workflow in a sentence | "Judging claim files complete before decision and chasing missing items" | A specific claim |
| 3. Records | Record classes by name | "Checklists, missing-item requests, receipt logs, claim revision history" | The claim documents |
| 4. Systems | Claims platform, document repository, correspondence, spreadsheets | "Claims platform being replaced; separate repository" | Logins, exports |
| 5. History | Years of closed claims, per system if different | "About nine years of closed commercial property claims" | Retention advice |
| 6. Volume | Closed files a year, read from a report | "Roughly 20,000 closed files a year" | Loss amounts |
| 7. Access event | A documented date, with its source | "Old platform read-only for one year after cutover" | Vendor contract terms |
| 8. Authority | Convener, decision-maker, adviser | "Head of claims operations; COO with general counsel" | Opinions on the deal |
| Open question | The gap that most limits the history | See below | Speculation about specific files |
What makes a completeness brief useful
Name the four record classes separately (field 3). Each lives in a different place. The checklist and revision history usually sit in the claims system; receipts sit in a repository; requests may be activities, letters or email. A brief that says "claim files" tells SourceX nothing about which of these survived. The system map shows where each class usually lives.
Say whether requests are dated and written (field 3 or the open question). In California, for example, an insurer that needs more information gives written notice of what it requires, updated every 30 days, and accepts or denies within 40 calendar days of proof of claim. Rules like these mean the request trail is often complete and dated, which is worth one line. Other states differ.
Give history as the system shows it (field 5). Legal minimums vary by state, and many insurers hold far more in an old platform than any rule requires. Ask the administrator, not the room.
Choose the open question carefully. The most informative one for this workflow is about versions: when an attachment belonged to a different claim version, was the correction recorded as a request and receipt, and do those links survive a migration? Platforms often hang everything off the claim alone; in Guidewire ClaimCenter, for example, a follow-up activity is created from an existing claim with an activity pattern code. Whether the revision is recorded too is a configuration question for the company.
A completed brief (Illustrative)
The values describe a fictional 900-person regional property carrier. They are Illustrative: not a real company, case or deal, and not a forecast.
| Field | Completed entry |
|---|---|
| 1. Company | Regional property and casualty carrier, about 900 full-time staff at peak, United States |
| 2. Task | Judging commercial property claim files complete before decision, and chasing missing items |
| 3. Records | Checklists with template versions, missing-item requests and letters, receipt logs, claim revision history |
| 4. Systems | Claims platform being replaced next year; separate document repository staying in place |
| 5. History | About nine years of closed commercial property claims in the old platform; eleven years in the repository |
| 6. Volume | Roughly 20,000 closed files a year, from the platform's closed-claims report |
| 7. Access event | Old platform read-only for one year after cutover, per the project plan |
| 8. Authority | Head of claims operations as convener; COO as decision-maker, with general counsel |
| Open question | When an attachment belonged to a different claim version, was the correction recorded as a request and receipt, and will those links survive the migration? |
What the example leaves out matters as much: no claim numbers, no claimant details, no loss amounts, no reinsurer or broker names.
What never goes in the brief
- Documents or extracts. Not one checklist, letter or estimate, even redacted.
- Identifiers. No claim, policy or request numbers.
- Value estimates. No guesses at what the records are worth or what a deal might pay.
- Legal conclusions. Whether files handled for other carriers can be licensed is for counsel and SourceX's rights review.
Before forwarding, 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 70% of the data is in English. Partners sign the Channel Partner Agreement first; the first valid introduction within the 90-day window is credited when the company submits a verified application. Buyer interest, the rights result, the de-identification required and any offer stay unknown until SourceX reviews the opportunity. The who-can-say-yes tree helps fill field 8.
SourceX licenses approved business data directly from companies for AI training and evaluation and manages the agreement, rights review, data preparation, delivery and payout. The warm introduction brief frames the first conversation, the portfolio review handoff checklist suits advisors with several companies, and the client opportunity brief generator formats the fields. The insurance page covers the wider sector.
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 eight fields and the open question are filled and the head of claims operations is ready to forward the brief, register as a partner, confirm the company on who qualifies and read the program terms before you submit.