# Temporal context in company records | SourceX

Canonical: https://refer.sourcex.si/guides/concept-temporal-context
Last updated: 2026-11-04

Temporal context means judging a past decision by the rules and facts that were valid when it applied, not by what the system shows today. In insurance, a claim for a March loss must use the policy terms in force in March, even if an endorsement changed them in April. The useful record keeps superseded versions with their effective dates and links each case to the version that was applied.

## What does temporal context mean in an ordinary business workflow?

It means every decision has a "valid as of" date, and the record must let you rebuild what was true on that date. Most business systems show the current state; temporal context asks for the state at a moment in the past.

Martin Fowler's essay on bitemporal history frames this as two separate timelines: when something actually happened, and when the system came to know about it. Records can lag behind reality, so a correct reading needs both dates. Some databases support this directly. Microsoft's SQL Server documentation describes system-versioned temporal tables that keep a history table and a period of validity for every row, and a `FOR SYSTEM_TIME AS OF` query that returns the rows valid at a chosen moment. Most companies' archives are less tidy, which is why the questions on this page matter.

### Worked timeline: a claim under an earlier endorsement (Illustrative)

Illustrative: a 180-person regional insurance agency services a commercial property policy for a client that runs two warehouses. All dates and amounts are fictional.

| Date | Event | System | Which terms are "current" |
|---|---|---|---|
| Jan 1 | Endorsement 2 takes effect: $10,000 deductible | Policy admin system | Endorsement 2 |
| Mar 18 | Roof leak damages stock in warehouse B | Loss date, recorded later | Endorsement 2 |
| Mar 25 | Endorsement 3 issued, effective Apr 1: deductible raised to $25,000 | Policy admin system | Endorsement 2 (3 not yet effective) |
| Apr 9 | Client reports the loss | Claims system, first notice | Endorsement 3 |
| May 20 | Adjuster settles the claim | Claims system, payment | Endorsement 3 |

The correct deductible is $10,000, because the loss happened on March 18. But on every day the claim was open, the policy screen showed endorsement 3 and $25,000. An adjuster, or an AI model, reading the current screen would apply the wrong figure. The record that matters is the one that shows the adjuster looked up the terms as of the loss date.

This is a different trap from a backdated change, where an endorsement is processed after the date it takes effect; that case is traced in the [claim question to closure record map](/guides/chain-claim-question-to-closure). Here every change was entered on time. The risk comes only from reading the right record at the wrong date.

## Which fields make temporal context visible in a record?

Temporal context only survives in an archive when a handful of fields exist and point at each other. In the illustrative claim, they are spread across three systems.

| Field | System in the example | Why it matters |
|---|---|---|
| Effective date and end date of each endorsement | Policy admin system | Defines which terms were valid on any given day |
| Superseded endorsement documents, kept after replacement | Document management | Lets a reviewer read the old terms, not only the new ones |
| Date of loss, separate from date reported | Claims system | Sets the "as of" date for the lookup |
| Deductible and limits applied at settlement | Claims payment record | Shows which version the adjuster actually used |
| Adjuster note citing the endorsement number | Claim file notes | Connects the decision to the rule it relied on |

The pair that carries the most weight is the date of loss and the endorsement number cited at settlement. With both, a reviewer can confirm the decision followed the terms then in force; without them, the record shows an outcome but not the reasoning.

## Where does temporal context break down, and what stays uncertain?

Even well-kept archives lose temporal context in predictable places.

- **Overwritten rules.** The system stores only the current deductible, and the old value survives only in a PDF that no case links to.
- **One date for two events.** The claim keeps a single "claim date" that mixes loss date and report date, so the correct lookup cannot be rebuilt.
- **Silent corrections.** A later adjustment changes the settled figure without a note, leaving two amounts and no explanation of which terms applied.
- **Mid-term changes outside the system.** An endorsement agreed by email and entered weeks later creates a gap between the paper terms and the system terms.

Each of these leaves uncertainty a reviewer has to record rather than guess around. A reviewer can work with a recorded gap; an unrecorded one makes every later decision in the file harder to trust.

## Does the company qualify, and what stays unknown?

The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, 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.

Gather metadata only: which systems hold the rules and the cases (policy admin, claims, document management), how many years of superseded versions exist, who owns them, and whether carrier or client agreements restrict reuse. Never ask for or handle raw claim files or policy documents.

What stays unknown until SourceX reviews the opportunity: SourceX's current data needs, the rights review outcome, the de-identification needed, the company's offer and any reward. SourceX licenses approved business data directly from companies and manages the agreement, rights review, data preparation, delivery and payout. Related reading: [claims notes as a data type](/data-types/claims-notes-data-ai), [the Model Context Protocol explained for advisors](/resources/mcp/model-context-protocol), [contract review records in M&A](/resources/mcp/mcp-manda-contract-review) and the full list of [data types](/data-types).

## Go deeper on temporal context

- [Questions an introducer should ask about temporal context](/questions/does-temporal-context-data-qualify): a short question set for checking whether a client's dated records could qualify.
- [Record gaps that make temporal context hard to assess](/questions/temporal-context-evidence-gaps): a guide to the missing dates and versions that weaken this kind of evidence.
- [Temporal context review packet](/resources/temporal-context-review-packet): a checklist of what belongs in an evidence packet for SourceX review.

## 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 a client keeps superseded rules with their effective dates and can show which version each case used, [register as a partner](/register), check [who qualifies](/who-qualifies), and read the [program terms](/terms) before introducing the decision-maker.

## Sources

- https://refer.sourcex.si/terms
- https://martinfowler.com/articles/bitemporal-history.html
- https://learn.microsoft.com/en-us/sql/relational-databases/tables/temporal/overview?view=sql-server-ver17
- https://learn.microsoft.com/en-us/sql/relational-databases/tables/querying-data-in-a-system-versioned-temporal-table?view=sql-server-ver17
