# Temporal context review packet: contents list | SourceX

Canonical: https://refer.sourcex.si/resources/temporal-context-review-packet
Last updated: 2026-11-04

A temporal context review packet is eight documents, prepared by the company in this order: a case class summary, the task specification, a register of rule versions with start and issue dates, a date map, a note on how decisions cite versions, the history of approval authority, an acceptance check, and volume and rights notes. Each describes records; none contains a claim file. Together they let SourceX test whether past decisions can be checked against the rules valid at the time.

The packet belongs to the guide to [temporal context in an ordinary workflow](/guides/concept-temporal-context), which shows why a past decision has to be read against the terms of its own day. Partners do not assemble it. This page shows what the company's records would need to produce later, under SourceX's agreement with the company, so an introducer can tell an owner what preparing involves.

## Eight divider sheets, in filing order

The order moves from what kind of decision is being checked, to the rules and dates it depends on, to the test each case must pass.

| Sheet | Document | What it shows | Prepared by | Usually drawn from |
|---|---|---|---|---|
| 1 | Case class summary | The decision type, years covered and systems involved | Claims manager | Claims system |
| 2 | Task specification | The decision rule in one or two sentences | Claims manager | Claims procedures |
| 3 | Rule version register | Every rule version with its start and issue dates | Policy administration | Policy admin and document systems |
| 4 | Date map | Which date decides the rules, and which field stores each date | Claims system administrator | Claims system |
| 5 | Version citation note | How settlements record the version they relied on | Claims supervisor | Payout worksheets |
| 6 | Authority history | Settlement limits by role and the dates they changed | Operations or HR | Approval policies |
| 7 | Acceptance check | The pass-or-fail test for each case | Claims manager with compliance | Sheets 2 to 6 |
| 8 | Volume, span and rights notes | Case counts, retention, migrations, carrier limits | Principal or COO with counsel | All of the above |

Sheet 4 is the one owners tend to skip and reviewers ask for first. A case usually carries four or five dates, and only one of them selects the rules. The date map says which field holds which date, so nobody has to guess.

## Each sheet, filled in for one claim class (Illustrative)

**Illustrative and fictional.** A 230-person commercial insurance agency handles property claims for business clients. All dates and amounts below are invented for the example.

**1. Case class summary.** "Commercial property claims decided while policy terms changed mid-term; 2018 to 2025; policy admin system, claims system and document system."

**2. Task specification.** "Settle the warehouse B claim using the deductible in force on the date of loss. If the loss date falls before an endorsement's effective date, apply the earlier endorsement, regardless of what the current policy screen shows."

**3. Rule version register.** Version 2 (endorsement 2): $10,000 deductible from January 1. Version 3: $25,000 deductible, issued March 25, starting April 1. Some policy systems keep this automatically: Microsoft's SQL Server documentation describes temporal tables that hold a history table with each row's period of validity, managed by the database. Where the agency has nothing like that, the register is compiled from dated documents.

**4. Date map.** Loss date (decides the rules), report date, settlement date and payment date, each with the field that stores it.

**5. Version citation note.** "Staff enter the version number on the payout worksheet; required since 2023."

**6. Authority history.** Approval limits by staff grade, with the dates each limit changed.

**7. Acceptance check.** Set out in the next section.

**8. Volume, span and rights notes.** About 60 mid-term change claims a year; claims system replaced in 2020; carrier agreements to be checked for limits on claim data.

## The acceptance check on two claims (Illustrative)

A case passes only if all four conditions hold:

1. The deductible applied matches the endorsement in force on the loss date.
2. The payout worksheet cites that endorsement.
3. The approver held settlement authority on the payment date.
4. No later correction reversed the amount.

| Condition | Claim A | Claim B |
|---|---|---|
| Deductible matches loss-date endorsement | Pass: $10,000 under endorsement 2 | Fail at first: $25,000 applied under endorsement 3 |
| Worksheet cites the endorsement | Pass: endorsement 2 cited | Fail: endorsement 3 cited |
| Approver held authority | Pass: within the May limit | Pass |
| No later correction | Pass | Fail: corrected to $10,000 a month later |
| Result | Passes | Fails, even though the final figure is right |

Claim B fails because the first decision used the wrong date, and the check judges the decision, not only the final amount. That distinction is exactly what makes a passed case useful: it shows someone reading the rules as of the right day.

Data vendors are building review tooling around checks like this one. micro1, for example, describes (checked 2026-10-18) a platform whose quality step flags missing evidence and whose trajectory review lets reviewers inspect an agent's steps and tool calls. That shows interest in the category; it says nothing about demand for a particular company's claim files.

## Keeping the packet at metadata level

Every sheet describes records by type, field, date range and count. The packet does not include claim files, policy documents, client names, payment records or screenshots. Where rule changes were agreed in chat before being entered, the [metadata-only Slack inventory template](/resources/a-metadata-only-slack-inventory-template-for-company-introductions) shows how to describe those channels without reading them. The same discipline applies outside insurance: support teams with versioned macros face the same question, covered in [how to identify support tickets with useful resolution context](/guides/how-to-identify-support-tickets-with-useful-resolution-context).

## What review settles after the packet

The packet tells SourceX whether a review is worth scoping and what to test. Its emphasis on dates follows a well-known distinction: Martin Fowler's essay on bitemporal history separates when something happened from when the system learned of it, and notes that records can lag behind reality. Review then settles how many cases pass, what de-identification is needed, whether carrier or client agreements restrict use, and whether any buyer wants this task type. Advisors curious about how AI tools query records like these can read the [Model Context Protocol explainer](/resources/mcp/model-context-protocol) and the page on [contract review records in M&A](/resources/mcp/mcp-manda-contract-review).

The company must meet the basics: 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.

Before raising a packet at all, rate the client on the [temporal context qualification scorecard](/questions/does-temporal-context-data-qualify); to describe what sheets 3 to 6 will reveal, use the [temporal context evidence gaps](/questions/temporal-context-evidence-gaps) page.

## 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 claims manager says the agency could write sheets 1 to 8 from records it already keeps, [register as a partner](/register), check [who qualifies](/who-qualifies), and read the [terms](/terms) before introducing the principal or COO.

## Sources

- https://learn.microsoft.com/en-us/sql/relational-databases/tables/temporal/overview?view=sql-server-ver17
- https://martinfowler.com/articles/bitemporal-history.html
- https://www.micro1.ai/blog/introducing-flow
- https://refer.sourcex.si/terms
