Does a client's dated rules history qualify? A temporal context scorecard for introducers

Short answer

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.

Visual briefFull-size diagram
Eight criteria on the left are checked one by one while a dial on the right swings between weak, borderline and strong and settles at borderline for a fictional 320-person staffing firm, with the two must-have criteria highlighted.
Illustrative rating for a fictional staffing firm's pay-rate history. A conversation aid, not SourceX's review.

This scorecard is part of the guide to temporal context in an ordinary workflow, 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.

CriterionStrongBorderlineWeakWho usually answers
1. Company size50 or more full-time employees at peak, contractors excludedClose to 50, or mostly contractorsClearly under 50 full-timeOwner or HR
2. Operating historySeveral years of cases, with the systems that held themA system change split the historyUnder two years of casesOperations lead
3. Rights to licenseThe company owns its rules and case recordsCarrier, client or vendor terms uncheckedRecords belong to a clientCOO or counsel
4. English share (outside the U.S., Canada and the EU)At least 70% of rules and case notes in EnglishMixed, share unknownMostly another languageOperations lead
5. Retained rule versions (must-have)Every superseded version kept, with effective and issue datesSome old versions, dates partialDocuments updated in placePolicy, pricing or HR owner
6. Decisive date per case (must-have)Each case stores the date that picks the rules, separate from othersOne date field that mixes eventsNo usable dateClaims, sales or HR lead
7. Case-to-version linkClosed cases cite a version number or attach a snapshotVersion can be inferred from datesNo way to tellTeam lead
8. Entry-date trailAn audit history shows when records were entered or correctedCreated date onlyNothing beyond current valuesSystem 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.

ResultRuleWhat it means for an introduction
Strong fitCriteria 5 and 6 strong, nothing weakIntroduce the principal, COO or CFO
Borderline fitCriteria 5 and 6 at least borderline, one or two others weak or borderlineIntroduce, naming the weak rows plainly
Weak fitCriterion 5 or 6 weak, or criterion 1 or 3 weakHold; 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.

Criterion230-person insurance agency, U.S.320-person staffing firm, Australia75-person property manager, Canada
1. Company sizeStrongStrongStrong
2. Operating historyStrong: claims since 2016StrongBorderline: new system in 2024
3. RightsBorderline: carrier agreements uncheckedStrongStrong
4. English shareStrong (U.S.)Strong: English throughoutStrong (Canada)
5. Retained rule versionsStrong: every endorsement kept with datesBorderline: award pay tables kept, some dates missingWeak: lease rules updated in place
6. Decisive date per caseStrong: loss date separate from report dateStrong: shift date on every timesheetBorderline
7. Case-to-version linkStrong: endorsement cited on settlementsWeak: rate version not stored on payslipsWeak
8. Entry-date trailBorderline: created date onlyStrongWeak
ResultStrong fit, with carrier rights named as an open itemBorderline fitWeak 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.

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 shows how to list systems without opening them, and the 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 page; for what a review asks the company to prepare, see the temporal context review packet. The wider method is in the 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, check who qualifies, and read the terms before introducing the principal, COO or CFO.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Is temporal context only relevant to insurers?

No. Any company whose rules change over time can score well: staffing firms with pay-rate tables, distributors with price lists, lenders with credit policies. Insurance is simply the clearest example because the loss date decides which terms apply.

Does the company need special database features to score strong?

No. Temporal tables help, but dated documents kept in a document system and cited on each case can score just as well. What counts is whether old versions survive with their dates.

Can I ask to see an old price list or policy to confirm it exists?

No. Ask whether superseded versions are kept, where and for how long. Partners stay at metadata level; SourceX reviews documents under its own agreement with the company.

Sources

  1. martinfowler.com/articles/bitemporal-history.html
  2. learn.microsoft.com/en-us/sql/relational-databases/tables/tempor…
  3. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment