# Who can license coverage query records? | SourceX

Canonical: https://refer.sourcex.si/questions/who-can-license-coverage-query-escalation-records
Last updated: 2026-11-04

Start with the operations director, who runs the service desk and knows where escalated coverage queries go, but do not stop there. The decision to open a licensing discussion sits with the CEO, advised by general counsel, while the head of underwriting and compliance own the policy versions, referral notes, letters and complaint register. For a managing general agent, the carrier's rights under its agreements can be decisive. The decision tree below shows the order to ask in.

This page is part of the [coverage query escalation guide](/guides/workflow-coverage-query-escalation). It answers one question: whom to introduce, and who can actually say yes.

## The decision tree, question by question

Work down the questions in order. Each answer either moves you to the next question or tells you who to add to the introduction.

**Q1. Who runs the service desk where coverage queries arrive and escalate?**
That person, usually the operations director or head of client service, is your **sponsor**. They can describe record classes, years and systems. Go to Q2.

**Q2. Who owns the policy versions, endorsements and referral notes?**
Usually the head of underwriting or underwriting operations. If that person is not the sponsor, they must be informed and supportive. Go to Q3.

**Q3. Who owns the complaint register and the retention schedule?**
Usually compliance. Compliance knows how queries and complaints link, what the retention schedule says, and how the company vets outside parties: the NAIC Insurance Data Security Model Law, in states that have adopted it, requires licensees to keep a written information security program and to exercise due diligence when selecting third-party service providers. Go to Q4.

**Q4. Is the company writing on its own paper, or on a carrier's?**
- Its own paper (a carrier): go to Q5.
- A carrier's paper (a managing general agent or program administrator): **general counsel must read the carrier, program and binding authority agreements** before anyone discusses licensing. Then go to Q5.

**Q5. Do the records include personal information about individual policyholders?**
- Commercial lines only, with business insureds: still go to Q6, but privacy limits are narrower.
- Personal lines, or individuals named in commercial files: **legal or privacy sign-off is needed**. The NAIC privacy model generally bars disclosing nonpublic personal financial information to a nonaffiliated third party without notice and a chance to opt out, and states adopt their own versions. Go to Q6.

**Q6. Who can approve a discussion about licensing company data?**
The CEO. That person is the **authorized contact** your introduction must reach. If nobody can be named, the introduction is not ready.

## Who owns which coverage query records

| Record class | Typical owner | Can open a licensing discussion? | Why they matter |
|---|---|---|---|
| Service tickets, escalation notes, closure codes | Operations director or client service head | Rarely alone | Best first contact; knows systems and volumes |
| Policy versions, endorsements, form library | Head of underwriting operations | No; must support | Without versions, answers cannot be checked |
| Underwriting referral notes and coverage letters | Head of underwriting or chief underwriting officer | No; must support | Holds the authority behind each answer |
| Complaint register, retention schedule | Compliance officer | No; advises | Knows regulatory limits and links |
| Carrier, program and broker agreements | General counsel | No; clears rights | Decides what reuse agreements allow |
| Company data as an asset | CEO | Yes | The authorized contact |
| Service desk or platform administration | IT or you, the advisor | No | Access is not authority |

The underwriting side of the same work has its own page on [underwriting referral triage](/guides/workflow-underwriting-referral-triage). The [system map](/guides/coverage-query-escalation-records-across-systems) shows how the records owned by these different people join into one case.

## Where legal, carrier or policyholder sign-off comes in

Three situations add sign-offs beyond the CEO's yes.

**Carrier rights.** A managing general agent often issues policies and handles service on a carrier's behalf. The agreements may give the carrier rights in policy forms, policy data or correspondence, or require consent for any reuse. Some say nothing. Only general counsel can read them, and only SourceX's rights review can confirm what they allow for a specific dataset.

**Policyholder information.** Coverage queries name insureds, locations and sometimes individuals. Where personal lines or individual consumers are involved, privacy law and the company's notices apply. That is why de-identification is decided during rights review, not assumed.

**Broker confidentiality.** Brokers send queries on behalf of clients, and some broker agreements carry confidentiality terms. General counsel checks these alongside the carrier agreements.

None of these is a reason not to introduce the company. They are reasons to make sure general counsel is copied from the start. [Why data rights matter](/proof/why-data-rights-matter) explains what SourceX's rights review settles.

## What stays unknown until SourceX's rights review

A partner can confirm who the sponsor is and who decides. A partner cannot confirm, and should not suggest:

- whether a buyer wants coverage query escalation records;
- what the rights review concludes about carrier, broker or policyholder limits;
- what must be removed or de-identified;
- what the company would be offered, if anything.

How buyers judge datasets in general is covered on [how AI labs and data users evaluate datasets](/proof/how-ai-buyers-evaluate-datasets). Insurance questions about the licensing deal itself, such as notice clauses in the company's own cyber policy, sit on [data licensing and cyber insurance coverage](/questions/data-licensing-cyber-insurance-coverage). Claims files raise similar ownership questions; see [claims notes data](/data-types/claims-notes-data-ai).

## Four qualification facts to confirm first

1. **Records:** policy versions, service questions and coverage responses exist for several years and can be linked at least by policy number.
2. **Ownership:** the company, not only its carrier partners, holds rights to license them, subject to review.
3. **Authority:** the CEO, who can approve a discussion, is named.
4. **Size and location:** the introduced company needs 50+ full-time employees at peak (contractors excluded), a 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.

## 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 tree ends at the CEO and general counsel is aware, [register as a partner](/register), check the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) before you introduce the sponsor and the decision-maker together.

## Sources

- https://content.naic.org/sites/default/files/model-law-672.pdf
- https://refer.sourcex.si/terms
- https://content.naic.org/sites/default/files/model-law-668.pdf
