# Coverage query records across systems: a map | SourceX

Canonical: https://refer.sourcex.si/guides/coverage-query-escalation-records-across-systems
Last updated: 2026-11-04

Reconstructing an escalated coverage query takes three joins: the policy number with its term, the effective date that places the event inside one policy version, and a reference between the written coverage response and the service ticket. A fourth join, from complaint register entry back to ticket, matters when the query became a complaint. The effective-date join is the one most often missing, because service desks rarely store the version the agent was looking at.

This map is part of the [coverage query escalation guide](/guides/workflow-coverage-query-escalation). The [exception examples page](/guides/coverage-query-escalation-exception-examples) tells the story of one case; this page shows the wiring underneath it.

## The four systems and what each holds

In a typical carrier or managing general agent, the records for one coverage query sit in four places, each run by a different team.

**Policy platform.** Holds the policy, every policy change and the form set in force for each version. In Guidewire PolicyCenter, a policy change is a job created against a policy with a required effective date. Owned by underwriting operations.

**Service desk.** Holds the question as it arrived, replies, internal notes, reassignments and closure codes. Many desks keep a change history per ticket: Zendesk stores an audit for each update, though its account-wide audit list leaves out archived tickets, which have to be fetched one by one. Owned by client service.

**Document repository.** Holds the written coverage response, usually filed against the account or policy. Owned by underwriting, sometimes shared with client service.

**Complaint register.** Holds complaints, the formal log compliance keeps for regulators. Owned by compliance.

## System map: record, linking key and owner

| System | Record | Linking key it carries | Links to | Owner |
|---|---|---|---|---|
| Policy platform | Policy and policy period | Policy number plus term start | Ticket field or subject line | Underwriting operations |
| Policy platform | Policy change (endorsement) | Effective date and job number | Event date in the ticket | Underwriting operations |
| Policy platform | Underwriting referral note | Policy number; sometimes ticket number | Escalation note in the ticket | Underwriting |
| Service desk | Ticket with question and replies | Ticket number; policy number field | Policy, letter, complaint | Client service |
| Service desk | Change history (audits) | Ticket number and timestamps | Escalation sequence | Client service |
| Document repository | Coverage response letter | Policy number; ticket number if cited | Ticket closure | Underwriting |
| Complaint register | Complaint entry | Complaint number; ticket number if linked | Original ticket | Compliance |

Two keys do the heavy lifting: the policy number and the ticket number. Everything else is either a date that must be compared, or a reference someone had to type.

## One fully joined case (Illustrative)

A second fictional case, different from the one on the exception page, shows the joins at work. All identifiers are invented.

1. **Ticket SD-51907** opens on July 3. A broker asks whether hail damage on June 28 at a warehouse is covered. The policy number field reads PX-30882; the location appears only in the email body.
2. **Policy PX-30882** has three versions. Version 2, effective June 1, added the warehouse to the property schedule as location 4; version 3, effective July 1, raised its limit.
3. **Date placement.** June 28 sits after June 1 and before July 1, so version 2 governs: the warehouse was scheduled, at the lower limit. This is a comparison, not a stored link.
4. **Location match.** The ticket names the street address; the schedule lists location 4 by number and address. Matching the two is manual unless the desk captures the location number.
5. **Change history on SD-51907** shows an agent quoting the version 3 limit, a reassignment to the underwriter and closure with the code "answer revised".
6. **Letter CR-1144** in the repository cites PX-30882, location 4 and version 2, and carries SD-51907 in its reference line.
7. **Complaint register:** none. Had one followed, a link back to SD-51907 would add the fourth join.

Seven records, four systems, one case anyone could follow. Lose any of three things, the event date on the ticket, the prior versions on the policy, or the ticket number on the letter, and the case still has a question and an answer, but no way to show which schedule and limit the answer had to use.

## The joins that fail most often

| Join | How it fails | What to ask the company |
|---|---|---|
| Ticket to policy | Policy number typed free-text, or changed at renewal | Is the policy number a required, validated field on tickets? |
| Event to version | Event date left in an attachment; only current version migrated | Is the event date a field? Are prior versions kept? |
| Ticket to letter | Letter cites neither ticket nor query | Does the letter carry the ticket number, or the ticket a link to the letter? |
| Escalation to referral | Referral discussed by email only | Are referral notes kept on the policy or in email? |
| Complaint to ticket | Complaint register kept separately with no link | Do complaint entries cite the original ticket? |

Export capability varies by platform, version and contract, so the company's own administrators should confirm what history each system can produce.

## Before the introduction: owner, rights and qualification

A map like this tells SourceX how much of a case history can be rebuilt. It does not settle who can license it. The policy platform, the service desk, the repository and the complaint register usually have four different owners, and a managing general agent writing on a carrier's paper may need to check its carrier agreements. The [who-can-license decision tree](/questions/who-can-license-coverage-query-escalation-records) sorts that out; insurance questions about the licensing deal itself sit on [data licensing and cyber insurance coverage](/questions/data-licensing-cyber-insurance-coverage), and a company winding down rather than migrating should read [D&O tail coverage in a wind-down](/questions/d-and-o-tail-coverage-wind-down).

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, and the first valid introduction within the 90-day window is credited when the company submits a verified application. Buyer interest, the rights result and any offer stay unknown until SourceX reviews the opportunity. More sector pages sit under [industries](/industries), and the general pattern of escalation records is on [support escalation records](/data-types/support-escalation-process).

## 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.

If the company's administrators confirm that policy number, event date and ticket references join across its systems, [register as a partner](/register), check the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) before you make the introduction.

## Sources

- https://docs.guidewire.com/cloud/pc/202411/cloudapibf/cloudAPI/topics/122-PCjobTypes/03-policy-changes/c_initiating_a_policy_change.html
- https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_audits/
- https://refer.sourcex.si/terms
