This scorecard is part of the claim-question-to-closure records guide. If you need the keys that connect each step first, read the claim-question-to-closure record chain.
The scorecard
Ask the claims operations lead and the records or IT manager. Score what they know, and score "not sure" as partial.
| Check | How to check it at metadata level | Pass | Partial | Fail |
|---|---|---|---|---|
| 1. Coverage | Ask which years each system holds: claims, policy, email, documents | All four overlap for 3+ years | One system shorter, or replaced mid-period | No period where claims and email both survive |
| 2. Policy context | Ask how a claim learns of an endorsement processed after it opened | Re-check or refresh is logged on the claim | Adjusters re-check by habit, not logged | Claim keeps its first policy copy only |
| 3. Identifier on email | Ask what share of claim email carries the claim number or is filed to the claim | Shared inbox or filing rule for most claims | Claim number usually typed, no filing rule | Email left in personal mailboxes |
| 4. Identifier on documents | Ask where attachments go if nobody files them | Every file in a claim folder or tagged | Most filed; mailbox attachments not swept | No folder or tag convention |
| 5. Letter versions | Ask whether a superseded coverage letter is kept | Library versioning on, with enough versions retained | New file saved, linked only by name | Overwritten |
| 6. Timestamps | Ask whether a document's received date is the receipt date or the upload date | Receipt, request and response dates kept separately | Upload date only, but close to receipt | Scanned mail dated by scan day, weeks late |
| 7. Outcome | Ask where you would see that the claim was paid or closed | Payment and closure in the claims system | Payment in finance, claim status mirrored | Outcome only in a separate finance system |
Scoring bands
- Ready to discuss: five or more passes and no fail on any check.
- Discuss with a known gap: a fail on check 2, 5 or 6 only. The decisions survive but one piece of context is weak; SourceX can judge whether that matters for the lines and years in question.
- Not yet: a fail on check 3 or check 7. Without the questions or the outcomes, the trail has no start or no end. Note which years fail; a later period may pass after a system change.
These bands are a way to describe an archive, not a promise. Suitability for AI training or evaluation is decided in SourceX's review.
The test case: an endorsement missing from the case view
Check 2 is the hardest check to answer in the abstract, so test it with a concrete pattern rather than a general question.
Illustrative. A mid-term change to a fleet policy adds three vehicles from the first of the month, but the change sits in an underwriting queue for three weeks. One of the new vehicles is in a collision during that gap. The claim snapshot was taken before the change existed, so the adjuster sees an unlisted vehicle and reserves the claim as uncovered. The agent sends the signed change request; the reserve and the position are corrected.
Ask three things about that pattern, none of which needs a record:
- Roughly how often does a mid-term change land after its effective date?
- When it lands on an open claim, does the claim record a dated re-check?
- Does the first, mistaken position survive as an earlier version next to the corrected one?
Three yes answers turn check 2 into a pass and make the archive more interesting, not less: a trail that keeps question, wrong premise, correction and final answer records the full reasoning.
An Illustrative completed scorecard
Illustrative. A 290-person commercial lines MGA, fictional, scored in one call.
| Check | Score | What the team said |
|---|---|---|
| 1. Coverage | Pass | Claims system and document library from 2016; shared claims inbox from 2018 |
| 2. Policy context | Fail | Re-checks happen but are not logged; claim keeps first copy |
| 3. Identifier on email | Pass | Shared inbox with claim-number filing since 2018 |
| 4. Identifier on documents | Pass | Folder per claim number; attachments swept nightly |
| 5. Letter versions | Partial | Versioning switched on in 2021; earlier letters saved as new files |
| 6. Timestamps | Pass | Mailroom stamps the receipt date on scans |
| 7. Outcome | Pass | Payments run in the claims system |
Result: discuss with a known gap. From 2021 the trail is nearly complete; before 2021 the letters link only by file name, and on any claim where an endorsement arrived late the policy system's processed date is needed to explain the outcome.
What the vendor documentation says about these checks
Three of the seven checks lean on how common tools behave by default. The table separates what the documentation settles from what only the insurer can answer.
| Check | What the documentation settles | What it leaves for the claims team |
|---|---|---|
| 2. Policy context | Guidewire ClaimCenter takes its copy of the policy from the policy administration system when a draft claim is created, as of the loss date; the policy system stays authoritative | Whether anyone refreshes that copy after a late change, and whether the refresh is dated on the claim |
| 2. Policy context, unverified policies | A claim opened on an unverified policy must be refreshed from the policy system before payments are allowed, so some setups already record a refresh step | Whether this insurer opens claims that way at all |
| 3. Identifier on email | In Microsoft Graph, an Outlook message carries a conversationId for its thread, so a broker reply without the claim number can still be traced | Whether the thread was ever filed against the claim, or sits in one person's mailbox |
| 5. Letter versions | SharePoint libraries can keep major versions with a viewable history; the Microsoft 365 organization default is 500 major versions with no expiration | Whether this library uses the default, or a low limit that drops early letters on busy files |
A partial on check 3 is therefore less damaging than it looks, while a fail on check 5 cannot be repaired after the fact: an overwritten letter is gone.
Who answers, and who authorizes
Route each check to the person who actually knows: checks 1, 3 and 4 to the records or IT messaging manager, checks 2, 5 and 7 to claims operations, check 6 to whoever runs the mailroom or document intake. None of them can approve licensing. That decision sits with the CEO, with the chief claims officer, general counsel or the chief privacy officer advising.
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: de-identification of claimant data, regulatory and reinsurance limits, which lines and years are in scope, and any offer. Partners never ask for or handle claim files, emails or letters, and sign the Channel Partner Agreement before submitting introductions. For a broader first screen, use the insurance operations screening worksheet. If the insurer is replacing core systems, the ERP replacement handoff checklist shows how to time the conversation; retention questions are covered in how long to keep business records after closing, and recorded calls in call center closure recordings.
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, MGA or TPA you advise scores ready to discuss, or discuss with a known gap, register as a partner, check it against who qualifies, and read the program terms before introducing its sponsor with the scorecard.