Claim-question-to-closure record chain: the keys that link policy, claim, email and letters end to end

Short answer

A company connects claim-question-to-closure records by following five keys in order: the policy number and endorsement dates in the policy system, the claim number and loss date in the claims system, the conversation ID on each email thread, the claim-number folder in the document library, and the version number on each coverage letter. The links usually hold inside each system and fail at the hand-offs. The weakest is the policy copy, which can be taken before a late endorsement is processed.

Visual briefFull-size diagram
Six linked records in a row, from endorsement to payment, joined by their keys; the link between the endorsement and the claim's policy copy is shown weak in orange, then repaired in green by a policy refresh.
Illustrative claim. Every link holds on a shared key except the policy copy, which was taken before the endorsement was processed.

This record chain is part of the claim-question-to-closure records guide, which covers what a partner can learn about the archive as a whole. Here the job is narrower: step, record, key and system, one row at a time.

The chain, step by step

Illustrative. A 450-person regional property insurer, fictional. A bakery's commercial property policy gains a spoilage endorsement effective March 1; underwriting processes it on March 18. A freezer fails on March 9, and the bakery's broker reports the claim the next day.

StepRecordKey that joins it to the next stepSystem
1. Policy changeSpoilage endorsement, effective March 1, processed March 18Policy number; effective and processed datesPolicy administration system
2. Claim openedDraft claim with a copy of the policy as of the March 9 loss dateClaim number, policy number, loss dateClaims system (ClaimCenter)
3. Coverage questionBroker email asking whether spoiled stock is coveredClaim number in the subject; conversation IDMail server
4. Evidence request and receiptHandler asks for temperature logs and stock invoices; files arriveSame conversation ID; claim-number folderMail, then the document library
5. Coverage positionLetter version 1.0 declining spoilage; version 2.0 confirming itClaim-number folder; major version numberDocument library
6. ClosurePayment issued and claim closedClaim numberClaims system

Illustrative. The insurer, bakery, dates and letters are fictional.

Read the key column downwards. Steps 2 to 6 share the claim number, directly or through a folder. Step 1 does not: it joins only through the policy number and the dates, which is why it is the link most likely to fail.

LinkHow it breaksWhat repairs itQuestion for the claims team
Policy to claimEndorsement processed after the policy copy was takenA logged policy refresh or re-check on the claim"When a policy changes after a claim opens, how does the claim learn about it?"
Claim to emailBroker starts a new thread without the claim numberConversation ID, or a shared inbox filed by claim"Is broker email filed to the claim, or left in personal mailboxes?"
Email to documentsAttachments never saved to the claim folderA filing rule or a records team that files them"Where does an attachment go if the adjuster does not file it?"
Letter to letterVersion 2.0 saved as a new file, or version 1.0 overwrittenLibrary versioning switched on, with enough versions kept"If a coverage position changes, is the first letter still there?"
Letter to paymentPayment recorded only in a finance systemPayment status mirrored in the claims system"Where would I see that this claim was paid?"

In the Illustrative bakery claim, the first row is the weak link. The copy taken on March 10 predates the March 18 processing, so the adjuster's case view shows no spoilage coverage and version 1.0 declines. The broker's reply, in the same conversation, attaches the endorsement; the adjuster re-checks the policy, and version 2.0 reverses the position. The chain holds only if the re-check left a dated trace and version 1.0 survived. What the case view alone leaves out reads the same kind of claim with and without that context.

What each key is, according to the vendors

  • Policy copy (step 1 to 2). Guidewire documents that ClaimCenter copies the policy from the policy administration system when a draft claim is created, that the copy reflects the policy as of the loss date, and that the policy system remains the system of record. The copy is a snapshot. If an endorsement is processed after the snapshot, the claim does not show it until someone refreshes or re-checks the policy.
  • Claims opened before the policy is confirmed. Guidewire also covers the case where first notice of loss arrives before the policy can be matched, so the claim starts on a placeholder policy keyed from what the caller said. Payments stay blocked until that placeholder is replaced from the policy system. In such setups a policy pull is already a routine step on the claim; whether it carries a date is for the carrier to say.
  • Email thread (step 3 to 4). In Microsoft Graph, an Outlook message carries a conversationId for the thread it belongs to and an internetMessageId in RFC 5322 format. A broker reply that drops the claim number from the subject can still be tied to the thread.
  • Letter versions (step 5). SharePoint libraries can keep major versions (1.0, 2.0) and minor versions of a file, with version history for each. The default organization setting in SharePoint in Microsoft 365 is a manual limit of 500 major versions with no expiration; libraries set up differently may keep fewer.

None of this proves a given insurer kept the trail. It shows which keys can exist, so a partner knows what to ask.

Joining the chain without moving any record

A partner does not test links; the insurer describes them. The useful answers are short: which identifier each system uses, since which year each link has held, and which link is known to fail. "Claim number on email since 2019, folders since 2017, letters versioned since the 2020 migration, policy refresh not logged" is a complete description of a chain. For scoring each link pass, partial or fail, use the claim-question-to-closure completeness checklist.

How records would ever move is decided after SourceX's review and a signed agreement with the insurer. Naming vendor products here does not imply SourceX has a connector for any of them; any export field nobody has checked should be marked unknown. Microsoft Outlook records and Microsoft SharePoint records describe those systems in more detail.

Who can authorize the introduction

Claim records hold policyholder and claimant information, so the sponsor is senior: the chief claims officer with general counsel or the chief privacy officer, or the CEO at a smaller carrier, MGA or TPA. Where a TPA handles the claims, ownership of the records may sit with the carrier; who owns claims data at a TPA explains why that matters before anyone is introduced.

The company has to clear the same bar as any referral: 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.

Unknown until SourceX reviews it: whether claimant data can be de-identified to a buyer's standard, which lines of business and years would be in scope, regulatory and reinsurance limits on reuse, and what the insurer would be paid. Partners never ask for or handle claim files, letters or emails, and sign the Channel Partner Agreement before submitting introductions. The insurance industry page covers the wider fit.

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 an insurer you advise can name the key for each link and the year each one started holding, register as a partner, check the insurer against who qualifies, and read the program terms before introducing its claims or legal sponsor.

  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

Is the claim number enough to link everything?

Inside the claims system, yes. Outside it, only if people typed or filed it. Email threads can often be followed by conversation ID instead, but the policy side links by policy number and dates, not by claim number.

Does the chain need every link to be useful?

No. A chain that holds from claim creation to payment but is weak on policy context is still a clear description. Say which link is weak and for which years.

Can a partner test the links?

Only by asking how the systems are used. The partner never runs a query or opens a claim; the claims operations lead or records manager answers from what they know.

Sources

  1. docs.guidewire.com/cloud/cc/202411/cloudapibf/cloudAPI/topics/1…
  2. docs.guidewire.com/cloud/cc/202507/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…
  5. learn.microsoft.com/en-us/sharepoint/set-default-org-version-limits
  6. refer.sourcex.si/terms

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