This decision tree is part of the claims document completeness review hub. It answers one question for claims workflow consultants: who, inside one insurer or administrator, can say yes to a conversation about checklists, missing-item requests and final receipts?
Access is not authority in a claims operation
Separate the two lists before the first conversation. People on the first list are useful; only people on the second can open a licensing discussion.
Who has access (useful, not sufficient):
- Completeness reviewers and adjusters, who create checklist entries, requests and receipt logs.
- The claims system administrator, who knows what the platform stores and can run reports.
- The document repository owner in IT or records management, who knows where attachments live and for how long.
- The claims standards team, who maintain checklist templates and their versions.
Who has authority (needed before any discussion):
- The chief claims officer or head of claims, who owns the process and the records it creates and brings the case to the CEO.
- The CEO, who decides whether company data is licensed and signs.
- General counsel or the privacy officer, who reads carrier, reinsurance and administration agreements and privacy obligations and sets the limits.
The system map shows which system each access holder administers, which helps when the convener needs to describe the records internally.
Walk the tree: from checklist owner to signer
Each question moves one level up. Stop at the first yes to question 4.
- Does this person keep one kind of record? A reviewer, adjuster or administrator says yes. Thank them, note the system and years, and ask who owns completeness review across claims.
- Does this person own the completeness process? Usually the head of claims operations. Ask them to convene and to bring in the CEO, who decides on company data.
- Are the claims the company's own, or handled for someone else? A carrier writing its own business answers for its own files. A managing general agent or third-party administrator may hold files under contracts that give the carrier rights in them. If so, flag the contracts for counsel.
- Can this person commit company records to an agreement? That person is the introduction: the CEO.
- Does anyone else have to consent? A parent group, a board, a reinsurer or a fronting carrier may. Note it; SourceX will ask.
Two mistakes are common. The first is treating the claims system administrator's offer of a report as permission. The second is stopping at the head of claims operations, who understands the records best and usually cannot sign.
Records that need counsel, carrier or privacy review
Claim files hold personal and sometimes health information about claimants and third parties, so several branches need someone else's yes.
| Record class | Who decides | Why | Typical handling |
|---|---|---|---|
| Checklist templates and versions | CEO, with counsel | Company know-how, little or no personal data | Often the easiest starting point |
| Checklist instances and sign-offs | Counsel and privacy officer | Tie reviewers and claims together | Reviewer names pseudonymized |
| Missing-item requests and letters | Counsel and privacy officer | Name claimants and describe losses | De-identified or excluded |
| Received documents | Counsel, privacy officer and, where relevant, the carrier | Heaviest personal and sometimes health data | Often excluded; metadata may remain |
| Files handled for a carrier | Counsel, against the administration agreement | Carrier may hold rights in claim files | In scope only as the contract allows |
| Litigated or disputed claims | Counsel | Possible holds and privilege | Left alone |
Insurance privacy rules add a layer. The NAIC's Model 672, adopted in some form by many states, implements the Gramm-Leach-Bliley Act for insurers and sets conditions for disclosing nonpublic personal financial and health information to third parties, with health information generally needing authorization. Retention rules point the other way only on timing: the NAIC's market conduct model calls for claim files to be kept for the calendar year of closure plus three years, which says how long records exist, not who may reuse them. Why data rights matter explains what SourceX's review establishes.
A carrier and an administrator: how the path changes (Illustrative)
Two fictional companies show how the tree branches. Neither is a real organization, case or deal.
| Step on the tree | 900-person regional property carrier | 450-person third-party claims administrator |
|---|---|---|
| Access holders | Reviewers, ClaimCenter administrator, records management | Adjusters, claims platform administrator, client portal owner |
| Convener | Head of claims operations | VP of claims services |
| Whose files? | The carrier's own | Each client carrier's, under administration agreements |
| Signer | CEO, with the COO preparing the case | CEO |
| Extra review | Privacy officer; reinsurer notice if contracts require | Counsel against every client agreement |
| Likely starting scope | Templates, then de-identified request and receipt history | Templates and process records the administrator owns; client files only as contracts allow |
The carrier's path is shorter. The administrator's path is not disqualifying; it adds a contract review per client, which changes timing and scope.
What stays unknown until SourceX's rights review
When the signer agrees to talk, these questions remain open: which record classes and years are in scope after privacy and contract review; what de-identification is required; whether any buyer wants completeness histories; and whether an offer follows, with its payout and schedule.
Qualification check before the introduction. 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; the first valid introduction within the 90-day window is credited when the company submits a verified application, and one partner is credited per company.
Useful background: the worked exception case shows what the records can explain, the document revision history checklist helps with versioned files, what a data audit is covers the review itself, and claims notes data and the insurance page cover the 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.
Once the head of claims operations has agreed to bring in the CEO, who can say yes, and counsel has flagged any carrier contracts, register as a partner, check the company on who qualifies and read the program terms before making the introduction.