Claim question to closure across the claims system, mailboxes and document library: an introducer's record map

Short answer

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.

Visual briefFull-size diagram
A date line for one commercial auto claim: the hired-auto endorsement is effective June 1, the policy is copied to the claim June 12, the endorsement is processed June 20, the claim is declined June 24, the broker emails June 26 and coverage is confirmed July 2.
Illustrative. The claim copied the policy eight days before the endorsement was processed, so the case view never showed it.

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 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 fieldClaims system (ClaimCenter)Email (Microsoft 365)Document library (SharePoint)Policy administration system
ObjectsClaims, exposures, policy copy, notes, activities, lettersAdjuster mailboxes, shared claims inbox, broker threadsEstimates, rental agreements, photos, coverage lettersPolicies, endorsements
Range and volume2015 to today; about 140,000 commercial auto and liability claimsShared inbox since 2018; mailboxes on a seven-year rule2017 to today; roughly 2.1 million files2012 to today
Key identifierClaim number, policy number, loss dateClaim number in the subject, when adjusters add itFolder per claim numberPolicy number, endorsement effective and processed dates
Filed to the claim automatically?Not applicableUnknownYes, by folderCopied at claim creation only
OwnerClaims operations directorIT messaging lead; legal holds the retention policyRecords managerUnderwriting 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 lists per-mailbox fields; Microsoft SharePoint records 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 covers the wider fit, mailbox records the email side, and the systems hub other record locations.

Go deeper on claim-question-to-closure records

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, check the insurer against who qualifies, and introduce the sponsor under the program terms.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Can I describe claims records without seeing claim files?

Yes. Claim counts by line, date ranges, which system holds correspondence and attachments, which identifier links them and who owns each step are enough. Claim files, claimant names and coverage letters stay with the insurer.

Is a claims organization on an older or homegrown claims system still relevant?

It can be. The tools on this page are examples. What matters is whether policy context, evidence requests and final responses can be linked, and from which year.

Does SourceX connect to Guidewire or Microsoft 365?

This page names those tools only to show where claim records commonly sit. It does not describe a SourceX connector. If the company proceeds, it decides what to share under a signed agreement.

Sources

  1. refer.sourcex.si/terms
  2. docs.guidewire.com/cloud/cc/202411/cloudapibf/cloudAPI/topics/1…
  3. learn.microsoft.com/en-us/graph/api/resources/message
  4. support.microsoft.com/en-us/sharepoint/lists/documents-and-library…

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment