This gap analysis is part of the guide to temporal context in an ordinary workflow, which follows one property claim decided under terms that changed partway through the year. Here the question is what a reviewer can and cannot rebuild when parts of such a record are gone, across a whole archive rather than one file.
Six kinds of evidence a review expects
To judge one decision against the rules valid at the time, a reviewer needs to rebuild two timelines: when things happened, and when the company knew. Six kinds of evidence carry those two timelines.
| Expected evidence | Which timeline it rebuilds |
|---|---|
| Old rule versions with start dates | What the rules said on any given day |
| Decisive date, separate from other dates | Which day's rules apply to this case |
| Issue or entry date of each change | When the company knew the rules had changed |
| Link from the case to the version used | Which rules the decision-maker actually applied |
| Payment and later corrections | Whether the decision stood or was reversed |
| Authority table in force at the time | Whether the decision-maker was allowed to decide |
A database built for this can answer "what was true on that date" directly. Microsoft's SQL Server documentation describes a FOR SYSTEM_TIME AS OF query that returns the rows valid at a chosen point in time. Most archives are not built that way, so the evidence has to be assembled from documents and fields, and that is where gaps appear.
What archives usually keep, and what they lose
The pattern reflects how policy, claims and pricing systems are commonly run, not a survey of companies.
| Evidence | Usually kept | Usually missing | Usual owner |
|---|---|---|---|
| Old rule versions | Documents in a shared drive or document system | Start dates on older versions | Policy administration |
| Decisive date | A date on every case | A separate loss or quote date in older systems | Claims or sales operations |
| Issue date of each change | Start dates | The date the change was entered or issued | Policy administration |
| Case-to-version link | The amount paid or price charged | A version number on the decision | Claims or finance |
| Corrections | The final figure | The first decision and the reason it changed | Finance |
| Authority table | Today's approval limits | Limits in force in earlier years | Operations or HR |
The wrong conclusion each gap invites
The table uses the illustrative March claim. Each row removes one record and shows what a reviewer would wrongly conclude.
| Missing record | What a reviewer sees instead | Wrong conclusion it invites |
|---|---|---|
| Retired endorsement 2 | Only endorsement 3 in the file | The $10,000 deductible looks like an error or a favor |
| Loss date (only report date kept) | April 9 as the only date | Endorsement 3 appears to apply |
| Issue date of endorsement 3 | A start date with no entry date | Cannot tell whether the change was known when the claim opened |
| Link from claim to the version used | A payment with no reference | Cannot check whether the adjuster followed the rules |
| Payment and any later correction | A settlement figure with no follow-up | Cannot tell whether the result stood or was reversed |
| Settlement authority table for May | Today's authority limits | Cannot check whether the approver was allowed to approve |
The first two rows are the most damaging, because they make a correct decision look wrong. The others leave a decision unverifiable rather than misread. Data platforms describe the same concern from the buyer side: micro1 says (checked 2026-10-18) its quality step flags issues such as missing evidence. That shows interest in the category, not demand for any particular archive.
Ten years at an insurance agency, estimated (Illustrative)
Illustrative and fictional. A 230-person commercial insurance agency is asked, for each kind of evidence, how many of its last ten years of claims (2016 to 2025) carry it.
| Evidence | Years available, out of 10 | Why it falls short |
|---|---|---|
| Superseded endorsements | 10 | Document system kept every version |
| Separate loss date | 6 | Old claims system had one combined date until 2020 |
| Issue dates | 4 | Recorded only since a policy system upgrade |
| Case-to-version link | 3 | Adjusters cite endorsement numbers only since 2023 |
| Payments and corrections | 8 | Earlier payment history archived in summary form |
| Authority table | 2 | Approval limits kept only as current settings |
Read across, 2023 to 2025 is the fully checkable slice except for authority in 2023, and 2020 onward supports rebuilding which rules applied, though not always which the adjuster cited. That is a concrete description an owner can give in one paragraph. The graphic on this page draws these six columns.
Describing the gaps in an introduction
| Instead of | Say |
|---|---|
| "We keep full history." | "Every endorsement since 2016; loss dates kept separately from 2020." |
| "Adjusters follow the policy." | "Settlements cite the endorsement number from 2023 onward." |
| "Approvals are controlled." | "Current authority limits are on file; earlier limits are not." |
Give years and who answered, and note any migration dates. Issue dates deserve special care: Martin Fowler's essay on bitemporal history points out that records can lag behind reality, so the date a change was entered is a separate fact from the date it took effect. When a company is winding down or changing systems, these dates matter even more; the data opportunity handoff checklist for a startup shutdown covers that case. Where rule changes were discussed in chat before being entered, the metadata-only Microsoft Teams inventory template shows how to describe those channels without opening them.
Who can fill the gaps, and what stays unknown
Policy administration owns versions and issue dates; claims operations owns loss dates and adjuster notes; finance owns payments and corrections (the resource on MCP for CFO dashboards explains why finance figures need traceable evidence behind them); operations or HR owns authority tables. The CEO, or the principal in an owner-run agency, can authorize a licensing discussion, and carrier agreements may affect rights in some documents.
The company test does not change: 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: how many cases pass, the de-identification needed, the rights review outcome and SourceX's current data needs. To rate a client first, use the temporal context qualification scorecard; for what a review asks the company to prepare, see the temporal context review packet. Claim-file records more broadly are covered in claims notes as a data type.
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 client can say which years carry each kind of evidence, as in the table above, register as a partner, check who qualifies, and read the terms before introducing the decision-maker.