This before-and-after reading is part of the claim-question-to-closure records guide. The keys that join the pieces are set out in the claim-question-to-closure record chain; this page shows what is lost when they are not joined.
Before: the claim as the claims export tells it
Illustrative. A 380-person specialty liability insurer, fictional. A building contractor holds a general liability policy. A visitor slips at a job site and sues the property owner, who asks the contractor's insurer to defend it as an additional insured.
The claims export holds these fields:
- Claim opened on September 4; policy copy attached; insured is the contractor.
- Activity: "Tender received from property owner."
- Activity: "Coverage review." Note: "No additional insured endorsement on policy. Decline tender."
- Letter generated September 15: tender declined.
- Activity on September 29: "Coverage re-review." Note: "Accept tender."
- Letter generated October 1: tender accepted. Defense counsel assigned.
A reader of the export sees an insurer that reversed itself in two weeks. It cannot tell whether the first answer was careless, whether the second was a commercial concession, or whether a fact arrived late. The superseded September 15 letter may not even be in the export, depending on how letters were stored.
Guidewire's documentation explains part of why. ClaimCenter attaches a copy of the relevant policy to a claim when it is created, and that copy reflects the policy as of the loss date, taken from the policy administration system, which remains the system of record. Whatever the policy system learns later is not in the copy unless someone refreshes or re-checks it.
After: the same claim with its context restored
Add three sources and the reversal becomes a reasoned decision.
- Policy system. A blanket additional insured endorsement was effective from the policy's July 1 renewal but processed only on September 20, after the claim's policy copy was taken. The case view never showed it.
- Email. The property owner's tender letter arrived by email with the construction contract attached, which required the contractor to name the owner as an additional insured. On September 22, the contractor's broker replied in the same thread with the processed endorsement. An Outlook message in Microsoft Graph carries a conversationId for its thread, so the reply can be tied to the tender even though the broker changed the subject line.
- Document library. The decline letter is version 1.0 and the acceptance version 2.0 of one file in the claim folder. SharePoint libraries can keep major versions with a viewable history, so the superseded position survives beside its replacement.
Now the sequence reads: tender, contract requirement, case view without the endorsement, decline, broker supplies the endorsement, re-check, acceptance. That is a complete piece of professional reasoning, including a wrong premise and its correction. For a buyer training or evaluating systems that handle coverage questions, the after version is the valuable one; the before version teaches a model that insurers reverse without cause. What data is missing from AI training explains why records of corrected judgment are scarce.
What is lost, and where it lives
| What a reader needs | In the claims export alone | Where the context lives | Key that joins it |
|---|---|---|---|
| The exact question asked | An activity title | Tender email and its attachment | Claim number or conversation ID |
| The contract term behind the tender | Not present | Attachment filed to the claim folder | Claim-number folder |
| Why the first answer was wrong | Not stated | Endorsement processed date in the policy system | Policy number and dates |
| Who supplied the missing fact | Not stated | Broker's reply in the same thread | Conversation ID |
| The first coverage position | Sometimes missing | Letter version 1.0 | Version history on the file |
| The reasoning for the reversal | A one-line note, if any | Adjuster note plus the email and letters together | Claim number |
Two rows are almost never recoverable from the export: who supplied the missing fact, and why the first answer was wrong. Adjuster notes are a partial bridge; claims notes as AI training data covers what they usually hold.
Questions that tell you which version the insurer can produce
Five questions, asked of the claims operations lead or records manager, show whether the after version exists. None needs a record.
- Since which year is email about a claim filed to the claim, or kept in a shared inbox, rather than in personal mailboxes?
- Are attachments saved to the claim folder as a rule, or only when an adjuster remembers?
- Is the document library versioned, and are superseded letters kept as earlier versions?
- Does the policy system record both the effective and the processed date of each endorsement?
- When a policy changes after a claim opens, is the re-check logged on the claim?
Four or five yes answers for a run of years suggest the connected history can be rebuilt. If the insurer is replacing its claims system, consolidating offices or shortening mailbox retention, the context is at risk first; the office closure checklist and the guide to exporting data before canceling SaaS cover what tends to be lost in those events.
Who can authorize the introduction, and what stays unknown
Claim records hold policyholder and claimant information, and the CEO is the one who can authorize discussing a license of them; the chief claims officer often sponsors the introduction, with general counsel or the chief privacy officer advising. A claims supervisor can answer the five questions but cannot authorize the next step.
The company must meet the program tests: 50+ full-time employees at peak (contractors excluded), 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 and third-party data can be de-identified to a buyer's standard, which lines and years would be in scope, regulatory and reinsurance limits on reuse, and any offer. Partners never ask for or handle claim files, emails or letters, and this page does not imply SourceX connects to Guidewire, Outlook or SharePoint. Partners 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 work with can answer yes to most of the five questions, it may hold the after version of its claims; register as a partner, check it against who qualifies, and read the program terms before introducing its sponsor.