# Coverage query escalation referral brief | SourceX

Canonical: https://refer.sourcex.si/resources/coverage-query-escalation-referral-brief-template
Last updated: 2026-11-04

A company introduction about coverage query escalation is a short brief the operations director can forward to the decision-maker unchanged. It states the company's size, the business task, the record classes (policy versions, service questions and escalation notes, written coverage responses), the systems, years held, rough query volumes, any documented access event, the open question about superseded wording, and who sponsors and who decides. It holds no policyholder names, policies, letters, exports or carrier names. The nine-line template comes first, then one completed Illustrative example.

This template is part of the [coverage query escalation guide](/guides/workflow-coverage-query-escalation). Fill it in after a first conversation with the operations director, using facts someone at the company can confirm.

## Copy this brief: nine lines for the operations director

Copy the lines below into an email or document. Replace each bracket with one or two plain sentences, or "unknown, [role] can confirm".

1. **Company:** [carrier, managing general agent or program administrator; full-time headcount at peak; country; own paper or a carrier's]
2. **Business task:** [the coverage question workflow in one sentence]
3. **Record classes:** [policy versions and changes with effective dates; service tickets with escalation notes; coverage response letters]
4. **Systems:** [policy platform, service desk, document repository, by type]
5. **Years held:** [first and last year per system]
6. **Volume:** [escalated coverage queries per year, and where the number comes from]
7. **Access event:** [a dated change in access, and the document that sets it, or "none known"]
8. **Open question:** [the gap that most limits the history]
9. **Authority:** [sponsor; decision-maker; legal adviser]

## Field notes for insurance records

**Line 1, own paper or a carrier's.** This single phrase tells SourceX whether carrier agreements are part of the rights question. It is more useful than any carrier name, which should stay out. Leave policyholders out too: the NAIC privacy model, a template for state laws, generally bars sharing nonpublic personal financial information with a nonaffiliated third party without notice and a chance to opt out, and a brief should never be where that question arises.

**Line 3, policy versions.** Ask whether the policy platform keeps every version with its effective date, or only current terms. A company that keeps every version can show which wording applied on any date; one that keeps only current terms cannot. If a migration is planned, ask which of the two the new platform will hold.

**Line 5, years held.** Retention rules may set a minimum, but what a company actually keeps varies by system. Write what the company says, per system.

**Line 6, volume.** Count escalated queries, not all service tickets. The escalated ones carry the reasoning. If the service desk tags escalations, the count comes from a report; if not, an estimate from the operations director is fine, marked as an estimate.

**Line 8, open question.** For coverage queries, the hard cases are the ones where an endorsement changed the relevant wording mid-term and the question arrived afterward. Ask whether coverage responses cite the endorsement they relied on, and whether the service desk keeps a change history. Desks differ, so the operations director's answer is enough. The [exception examples page](/guides/coverage-query-escalation-exception-examples) shows why that history matters.

**Line 9, authority.** The sponsor and the decision-maker are usually different people. The [who-can-license decision tree](/questions/who-can-license-coverage-query-escalation-records) helps fill the line.

## Completed brief for a fictional MGA (Illustrative)

The values below describe a fictional managing general agent. They are **Illustrative**: no real company, policy or deal, and no figure is a forecast.

1. **Company:** commercial lines managing general agent writing property business through retail brokers; about 260 full-time staff at peak; United States; writes on carrier paper.
2. **Business task:** answering broker coverage questions where the answer depends on the policy version in force on the event date, escalating to underwriting when it does.
3. **Record classes:** policy versions and policy changes with effective dates; service tickets with escalation notes and closure codes; written coverage responses.
4. **Systems:** legacy policy platform being replaced; service desk; document repository.
5. **Years held:** about seven years of tickets; coverage letters for ten; depth of version history in the legacy platform unconfirmed.
6. **Volume:** roughly 1,500 escalated coverage queries a year, from the service desk's escalation tag, as read by the operations director.
7. **Access event:** legacy platform read-only access ends six months after cutover, per the project plan.
8. **Open question:** when an endorsement changed the relevant wording, does each coverage response cite the endorsement it relied on, and will superseded versions survive the migration?
9. **Authority:** operations director as sponsor; chief operating officer to decide; general counsel to review carrier and broker agreements.

## Sharing test: is each line metadata?

Before the brief leaves your hands, test each line against one rule: it describes records but does not contain any.

| Line | Passes when it says | Fails when it includes |
|---|---|---|
| Company | Type, headcount, country, paper | Carrier or program names |
| Business task | The workflow in general terms | A specific broker's question |
| Record classes | Names of record types | A sample letter or ticket |
| Systems | System types or product names | Logins, exports, screenshots |
| Years and volume | Ranges and counts with a source | Per-account or per-broker figures |
| Access event | A date and the document that sets it | Pressure or guesses |
| Open question | The gap in general terms | Details of a real loss |
| Authority | Roles and, with permission, names | Opinions about price or value |

If a line fails, rewrite it. The [warm introduction brief](/resources/a-warm-introduction-brief-for-a-business-owner) helps with the covering message, and the [client opportunity brief generator](/tools/client-opportunity-brief-generator) can format the nine lines.

## Qualify the company and send it

Confirm these before the operations director forwards the brief:

- **Size and history:** the introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license and an authorized contact.
- **Location:** 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.
- **Paperwork:** 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.
- **Unknowns:** buyer interest, the rights result, the de-identification required and any offer stay unknown until SourceX reviews the opportunity.

SourceX licenses approved business data directly from companies for AI training and evaluation and manages the agreement, rights review, data preparation, delivery and payout. Related reading: [insurance agency service requests](/data-types/insurance-agency-service-requests-ai), a finance workflow handled the same metadata-only way in [procurement approvals and exception workflows](/guides/how-to-assess-procurement-approvals-and-exception-workflows), and the [insurance industry page](/industries/insurance).

## 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 every line passes the sharing test and the operations director is ready to forward the brief, [register as a partner](/register), confirm the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) and [reward rules](/rewards) before you submit the introduction.

## Sources

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