# Temporal context records: qualification scorecard | SourceX

Canonical: https://refer.sourcex.si/questions/does-temporal-context-data-qualify
Last updated: 2026-11-04

Rate a client on eight criteria: headcount, operating history, rights, English share where it applies, whether superseded rules are kept with effective dates, whether each case records the date that decides which rules apply, whether a closed case shows the version used, and whether the system logs when records were entered. Two are must-haves: retained rule versions and a decisive date on each case. Both strong and nothing weak means a strong fit.

This scorecard is part of the guide to [temporal context in an ordinary workflow](/guides/concept-temporal-context), where a March loss must be settled under the policy terms in force in March, not the April endorsement. That guide explains the idea. This page turns it into a rating sheet for a call with an operations, claims or finance lead, who can answer every row without sharing a file.

## The rating sheet: eight criteria

Mark the answer closest to what the client says.

| Criterion | Strong | Borderline | Weak | Who usually answers |
|---|---|---|---|---|
| 1. Company size | 50 or more full-time employees at peak, contractors excluded | Close to 50, or mostly contractors | Clearly under 50 full-time | Owner or HR |
| 2. Operating history | Several years of cases, with the systems that held them | A system change split the history | Under two years of cases | Operations lead |
| 3. Rights to license | The company owns its rules and case records | Carrier, client or vendor terms unchecked | Records belong to a client | COO or counsel |
| 4. English share (outside the U.S., Canada and the EU) | At least 70% of rules and case notes in English | Mixed, share unknown | Mostly another language | Operations lead |
| 5. Retained rule versions (must-have) | Every superseded version kept, with effective and issue dates | Some old versions, dates partial | Documents updated in place | Policy, pricing or HR owner |
| 6. Decisive date per case (must-have) | Each case stores the date that picks the rules, separate from others | One date field that mixes events | No usable date | Claims, sales or HR lead |
| 7. Case-to-version link | Closed cases cite a version number or attach a snapshot | Version can be inferred from dates | No way to tell | Team lead |
| 8. Entry-date trail | An audit history shows when records were entered or corrected | Created date only | Nothing beyond current values | System administrator |

Criterion 4 applies only outside the U.S., Canada and the EU; elsewhere, mark it strong. 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.

## Reading strong, borderline and weak

Start with the two must-haves.

| Result | Rule | What it means for an introduction |
|---|---|---|
| Strong fit | Criteria 5 and 6 strong, nothing weak | Introduce the principal, COO or CFO |
| Borderline fit | Criteria 5 and 6 at least borderline, one or two others weak or borderline | Introduce, naming the weak rows plainly |
| Weak fit | Criterion 5 or 6 weak, or criterion 1 or 3 weak | Hold; past decisions cannot be checked against the rules then in force |

Why those two? A past decision can only be judged against the rules valid at the time if both halves survive: the old rule and the date that selects it. Martin Fowler's essay on bitemporal history describes two timelines, when something happened and when the system learned of it, and notes that records can lag behind reality. Criteria 6 and 8 capture those two timelines; criterion 5 supplies the rules that sit on them.

Some companies score criterion 5 strong without realizing it. Microsoft's SQL Server documentation describes system-versioned temporal tables that keep a history table with a period of validity for every row, maintained by the database engine. A company whose pricing or policy tables were built this way may hold a complete version history that nobody in operations has ever looked at. Ask the system administrator, not only the business owner.

## Three companies scored (Illustrative)

All three are fictional; every mark came from a conversation.

| Criterion | 230-person insurance agency, U.S. | 320-person staffing firm, Australia | 75-person property manager, Canada |
|---|---|---|---|
| 1. Company size | Strong | Strong | Strong |
| 2. Operating history | Strong: claims since 2016 | Strong | Borderline: new system in 2024 |
| 3. Rights | Borderline: carrier agreements unchecked | Strong | Strong |
| 4. English share | Strong (U.S.) | Strong: English throughout | Strong (Canada) |
| 5. Retained rule versions | Strong: every endorsement kept with dates | Borderline: award pay tables kept, some dates missing | Weak: lease rules updated in place |
| 6. Decisive date per case | Strong: loss date separate from report date | Strong: shift date on every timesheet | Borderline |
| 7. Case-to-version link | Strong: endorsement cited on settlements | Weak: rate version not stored on payslips | Weak |
| 8. Entry-date trail | Borderline: created date only | Strong | Weak |
| Result | Strong fit, with carrier rights named as an open item | Borderline fit | Weak fit |

The staffing firm is the case shown in the graphic. It keeps the decisive date perfectly but cannot always show which pay-rate version produced each payslip. A reviewer could still infer the version from dates where the old tables survive, which is why it lands borderline rather than weak.

## Five questions that fill the sheet

1. **When a policy, price list or rule changes, is the old version kept with its effective dates?** "Every endorsement is stored with effective and issue dates" is a real answer. "We update the document" is not. (Criterion 5.)
2. **Does each case record the date that decides which rules apply?** In claims it is the loss date; in sales it may be the quote date; in staffing the shift date. (Criterion 6.)
3. **For a closed case, can you tell which version of the rules was used?** Look for a version number, an endorsement reference or an attached snapshot. (Criterion 7.)
4. **Is there an audit history of when records were entered, not just when events happened?** That second timeline shows late entries and corrections. (Criterion 8.)
5. **Who could authorize a conversation about licensing these records?** The CEO, or the principal in an owner-run agency; carriers or clients may hold rights in some documents. (Criterion 3.)

Three or more confident answers suggest a company worth introducing. For why the surrounding documents matter more than isolated files, see [how to identify useful workflow context](/guides/how-to-identify-useful-workflow-context-instead-of-isolated-files).

## Who answers which rows, and what a score cannot show

Business owners answer criteria 5 to 7; a system administrator answers criterion 8 and often knows more about criterion 5 than anyone expects; the CEO or principal, who can authorize a licensing discussion, answers criterion 3. For a company running NetSuite, the [metadata-only NetSuite inventory template](/resources/a-metadata-only-netsuite-inventory-template-for-company-introductions) shows how to list systems without opening them, and the [company qualification checklist](/resources/company-qualification-checklist) covers the company-level basics.

A score cannot show how many cases pass an acceptance check, what de-identification is needed, whether carrier or client agreements limit use, or whether any buyer wants this task type. SourceX settles those in review. To describe the weak rows accurately, use the [temporal context evidence gaps](/questions/temporal-context-evidence-gaps) page; for what a review asks the company to prepare, see the [temporal context review packet](/resources/temporal-context-review-packet). The wider method is in the [business introducer guide to operational data licensing](/guides/a-business-introducer-guide-to-operational-data-licensing).

## 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 dates and records the decisive date on every case, [register as a partner](/register), check [who qualifies](/who-qualifies), and read the [terms](/terms) before introducing the principal, COO or CFO.

## Sources

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