# Claim question to closure: cross-system records | SourceX

Canonical: https://refer.sourcex.si/guides/chain-claim-question-to-closure
Last updated: 2026-11-04

A referral partner can describe a claims organization's question-to-closure history entirely from metadata: which system holds the claim and its copy of the policy, where questions and evidence requests travel (usually email), where the received documents are filed, how far back each goes, which identifier ties them together, and who owns each step. No claim file is opened. The case to test is a claim where the relevant endorsement never appeared in the case view.

## The business task: answering a coverage question with evidence

An adjuster receives a claim, checks what the policy covers, asks the insured or broker for evidence, and gives a final answer. In commercial lines the coverage question is often the hard part: which endorsement applied on the loss date, and what proof was needed to confirm it. A closed claim with its questions, requests and final position records a professional judgment from start to finish. [Claims notes as a data type](/data-types/claims-notes-data-ai) explains why that judgment is scarce in public data.

Those steps are scattered across at least three systems, plus a fourth that supplies the policy. In a Guidewire shop, the claim gets a snapshot of the policy, taken from the policy administration system at draft creation and dated to the loss, while the policy system stays the source of truth. Questions and requests travel by email, where each message keeps a thread identifier (Microsoft Graph calls it conversationId) alongside its own internet message ID. Evidence and letters land in a document library that can keep numbered major and minor versions of every file.

## What metadata can a referral partner collect about claim-question-to-closure without reading private content?

Counts, ranges, identifiers and owners for each system, gathered in a conversation with a claims operations lead and an IT or records manager. Below is the packet for a fictional 600-person regional commercial lines insurer; every value is Illustrative.

| Packet field | Claims system (ClaimCenter) | Email (Microsoft 365) | Document library (SharePoint) | Policy administration system |
|---|---|---|---|---|
| Objects | Claims, exposures, policy copy, notes, activities, letters | Adjuster mailboxes, shared claims inbox, broker threads | Estimates, rental agreements, photos, coverage letters | Policies, endorsements |
| Range and volume | 2015 to today; about 140,000 commercial auto and liability claims | Shared inbox since 2018; mailboxes on a seven-year rule | 2017 to today; roughly 2.1 million files | 2012 to today |
| Key identifier | Claim number, policy number, loss date | Claim number in the subject, when adjusters add it | Folder per claim number | Policy number, endorsement effective and processed dates |
| Filed to the claim automatically? | Not applicable | Unknown | Yes, by folder | Copied at claim creation only |
| Owner | Claims operations director | IT messaging lead; legal holds the retention policy | Records manager | Underwriting operations |

The fourth column matters even though conversations usually start with the other three, because the endorsement problem below starts there. Two more answers complete the packet: since which year adjusters reliably put the claim number on email, and whether the claims team can refresh a claim's policy copy after an endorsement is processed. For the email side, the [mailbox metadata inventory template](/resources/a-metadata-only-microsoft-outlook-inventory-template-for-company-introductions) lists per-mailbox fields; [Microsoft SharePoint records](/systems/microsoft-sharepoint) covers the library side.

## When the endorsement is missing from the case view

This is the Illustrative case drawn in the graphic above, and it is the one the packet should help a sponsor recognize.

A hired-auto endorsement is effective June 1. An employee has an accident in a rented van, and the claim is created on June 12; the claims system snapshots the policy as it stands that day. Underwriting processes the endorsement on June 20, back-dated to June 1, eight days after the copy was taken. The adjuster, reading the case view, sees no hired-auto coverage and declines on June 24. On June 26 the broker emails the endorsement. On July 2 coverage is confirmed and the declination reversed.

Every fact needed to explain the reversal exists, but in three places: the processed date in the policy system, the broker email in a mailbox, and the reversal letter in the library. A partner does not need any of them. The packet answers that matter are plain: does the policy system keep both effective and processed dates, can a claim's policy copy be refreshed, and is broker email filed to the claim? "Yes", "no" and "not sure" are all useful.

## Who can authorize the discussion, and what stays unknown?

Claim records hold policyholder and claimant information, so the decision sits with the CEO, who can authorize a licensing discussion and sign; the chief claims officer often sponsors the introduction, with the general counsel or chief privacy officer advising. A claims supervisor can describe the records but cannot authorize licensing them.

Before introducing, check:

- 50+ full-time employees at peak, contractors excluded, and a documented operating history.
- Rights to license: regulators, reinsurance treaties, TPA contracts and privacy notices can all limit reuse. Note what you hear; SourceX's review assesses it.
- A named decision-maker who will take a first call.
- 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 never ask for or handle claim files, letters or emails. What stays unknown until SourceX reviews it: whether claimant data can be de-identified to a buyer's standard, which lines and years a buyer would want, what regulatory limits apply, and what the company would be paid. The [insurance industry page](/industries/insurance) covers the wider fit, [mailbox records](/systems/microsoft-outlook) the email side, and the [systems hub](/systems) other record locations.

## Go deeper on claim-question-to-closure records

- [How policy, email and claim records link](/guides/claim-question-to-closure-record-linkage): a record-chain table of each step, its record, its key and its system.
- [Claim-question-to-closure completeness checklist](/resources/claim-question-to-closure-completeness-checklist): a pass, partial or fail scorecard for judging whether the records are complete enough to discuss.
- [What the case view alone leaves out](/guides/claim-question-to-closure-missing-context): one Illustrative claim read before and after its surrounding context is added.

## 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 claims team can fill in the packet and say from which year email and letters are filed against the claim number, [register as a partner](/register), check the insurer against [who qualifies](/who-qualifies), and introduce the sponsor under the [program terms](/terms).

## Sources

- https://refer.sourcex.si/terms
- https://docs.guidewire.com/cloud/cc/202411/cloudapibf/cloudAPI/topics/111-CCFNOL/02-claims/c_retrieving-policy-information.html
- https://learn.microsoft.com/en-us/graph/api/resources/message?view=graph-rest-1.0
- https://support.microsoft.com/en-us/sharepoint/lists/documents-and-library/how-versioning-works-in-lists-and-libraries
