# Referral dataset uncertainty: a known-unknown grid | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-record-what-you-do-not-know-about-a-dataset
Last updated: 2026-11-04

Record unknowns as entries, not omissions. For each fact in a referral summary, write its status (confirmed by the company, estimated with a range and its basis, or unknown), who can close the gap (the company itself, or only SourceX's review) and the date you asked. Keep the summary to metadata the CEO has approved, attach no records, and send the open items with the introduction so the first call starts from them instead of discovering them.

A summary that quietly drops what nobody knows reads as more certain than it is. The reader cannot tell a fact the partner checked from one the partner assumed, and the first surprise in review costs more trust than an honest blank would have.

## An unknown is a line in the summary, not a hole in it

Two disciplines that have nothing to do with referrals reached the same rule. The US Intelligence Community's analytic standards, ICD 203, say analytic products should indicate and explain the basis for the uncertainties behind major judgments, and should note what causes them, including the type, currency and amount of information and knowledge gaps. In machine learning, the Datasheets for Datasets questionnaire asks dataset creators, "Is any information missing from individual instances?" and wants the reason written down. Neither treats a gap as something to smooth over.

SourceX's own materials already work this way. The Illustrative private data summary on its how-it-works page gives an approximate volume and marks licensing rights as pending review, which is a known unknown stated plainly. A partner's referral summary should be no more confident than that.

The overall shape of a history summary is covered in [describing operating history without exposing records](/guides/how-to-describe-operating-history-without-exposing-records); this page adds a second dimension to every line, who can close the gap. It does not tell you whether a given company fits; the screening profile on [who qualifies](/who-qualifies) and SourceX's review do that.

## The context to gather before any line is coded

Gather each line from the CEO or the person the CEO names, in conversation. Never from files, screenshots or a login.

| Field | Who usually supplies it | Typical status at referral |
|---|---|---|
| Legal entity and who controls it | CEO | Confirmed |
| CEO knows and wants the conversation | CEO | Confirmed, or the introduction waits |
| Peak full-time headcount, contractors excluded | CEO or finance lead | Confirmed or estimated |
| Location and the language of the records | CEO | Confirmed |
| Systems in use and since when | Operations lead or administrator, via the CEO | Estimated |
| Record types and who created them | Operations lead | Confirmed or estimated |
| Rough volume per system | Operations lead | Estimated |
| Material that belongs to clients, or contract limits | CEO, later counsel | Unknown until review |
| Dated events: migration, retention purge, shutdown | Administrator | Confirmed when dated |

Two lines are fixed by the program rather than by the company. Introduced companies need 50 or more full-time employees at peak. And on geography: 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. If either is unknown, that unknown goes first on the grid, because nothing else matters until it is answered. A deeper interview for portfolio CEOs is in [mapping operating records without asking for them](/guides/map-operating-records-without-asking-for-the-records).

## The known-unknown evidence grid

Every fact gets exactly one code, and the code carries two answers: how sure you are, and who can make you surer.

| Code | Status | How to write it | Who can close it |
|---|---|---|---|
| C | Confirmed by the company | The fact, the person who stated it, the date | Already closed; re-confirm on the first call |
| E | Estimate | A range, its basis, the person, the date | The company, if it chooses to count |
| U1 | Unknown, the company can answer | The question, and who at the company would know | The company, in its own time |
| U2 | Unknown until SourceX reviews it | The question, marked "for review" | Only SourceX's review, often with the company's counsel |
| U3 | Unknown to anyone yet | The question, and what would answer it | Nobody today; note the trigger |
| X | Deliberately not asked | The category of thing you declined to collect | Not applicable: stays out of the summary |

Here is the grid filled in for an Illustrative company: a 240-person managed IT services firm, invented for this page.

| Fact | Code | Entry as written in the summary |
|---|---|---|
| Peak full-time headcount | C | 240 full-time employees at peak in 2024, contractors excluded (CEO, 2026-10-21) |
| Location and language | C | Operates in the U.S.; records in English (CEO, 2026-10-21) |
| Helpdesk in use since | C | Current helpdesk since 2018 (operations lead, via CEO, 2026-10-21) |
| Ticket volume | E | 250,000 to 350,000 tickets since 2018; basis: the operations lead's typical monthly volume times years; not counted (2026-10-21) |
| Tickets before 2018 | U1 | Were tickets from the earlier system carried across? Administrator would know |
| Who created the records | C | Tickets and resolution notes written by the firm's own engineers (operations lead, 2026-10-21) |
| Client contract limits on reuse | U2 | Do managed-service contracts restrict reuse of ticket content? For review |
| Personal details in tickets | U2 | Extent of personal details and how they would be removed: for review |
| Relevance to current programs | U2 | For review; SourceX checks this against current data needs |
| Readability of a retired 2012 to 2017 system | U3 | Unknown until the company decides to look; trigger: the server's retirement date |
| Customer names, sample tickets, logins | X | Not collected |

Notice what the grid does not contain: no value estimate, no claim that the records are "clean" or "complete", and no sample. The client-contract line matters most here. A managed IT firm's tickets are its own work, but they describe clients' systems, and SourceX's screening guidance treats material that belongs to clients as usually not a fit. Labeling it U2 keeps the partner from either promising it away or ruling the company out. The difference between the ticketing system and the systems around it is explained in [what a system of record is](/questions/what-is-a-system-of-record).

## Four habits for estimates, constraints and open questions

Each is short enough to apply while you write.

**Every estimate is a range with a basis.** "About 300,000 tickets" invites a reader to treat 300,000 as a count. "250,000 to 350,000, from typical monthly volume, not counted" tells them what kind of number it is. Never turn an estimate into a value, a payout or a reward.

**Constraints are written as constraints, not verdicts.** A retention purge, a records set that lives in customers' own systems or a privacy notice that predates any AI use narrows what might be licensed. Write what it is and when it applies; SourceX decides what it means.

**Unanswered questions name their owner.** "Unknown" alone is unfinished. "Unknown; the administrator would know; the company may choose to check" is a usable line, and so is "for review".

**Every line carries a date.** An estimate from a March conversation is weaker than one from last week. When you ask again, replace the date rather than adding a second line.

Words to keep out of the summary entirely: lots, tons, massive, clean, complete, full history, unique. If you cannot attach a range or a source to an adjective, delete it. Turning confirmed lines into a short introduction without inflating them is covered in [making the introduction useful without overselling the dataset](/guides/how-to-make-the-introduction-useful-without-overselling-the-dataset); this page is about the lines nobody can confirm yet.

## From an approved grid to the first call

The grid becomes the handoff in three steps.

1. **The CEO approves the text.** Send the CEO the grid as you will submit it. Anything the CEO strikes stays out. The summary is the company's description of itself, not your assessment.
2. **The partner submits; the company applies.** Your introduction carries the approved summary and no attachments. You must have signed the SourceX Channel Partner Agreement before submitting. Credit then follows the earliest valid introduction of a company new to SourceX inside the 90-day attribution window and is recorded once the company submits a verified application. The company's own application asks for systems, years of history and what can be exported, and needs no files.
3. **The first call runs on the grid.** A short agenda: re-confirm the C lines; close any U1 items the company chose to answer; hear how SourceX will handle the U2 items in review; agree who records the U3 triggers. Any item still open after the call keeps its code and gets a new date.

When the company asks you something only SourceX can answer, say so and route it; [handling details you cannot verify](/guides/when-a-contact-wants-details-you-cannot-verify) has the phrasing. If the summary's weakest line is time coverage, [describing an archive's time coverage](/guides/how-to-describe-an-archive-s-time-coverage-accurately) gives a notation for it.

## How the grid can mislead, and what it does not measure

- **Codes can look like rigor they do not have.** A C line is still one person's statement. The grid records who said what and when; it does not verify anything.
- **The biggest unknown may decide everything.** A single U2 line on client contracts can remove most of a dataset in review. Do not let a grid with mostly C lines suggest a mostly settled case.
- **Programs move.** SourceX applies the criteria of a specific program, and a company that does not fit one may fit another later. A grid is valid on its dates.
- **Metadata can still be confidential.** If you know a company's systems from board materials or a client engagement, that knowledge is a reason to ask the CEO, not content for the grid.
- **Recollections drift.** Estimates of volume and start dates given from memory can miss in either direction. That is why E lines carry ranges and bases.

**Methods note.** The grid was built on 2026-10-27 from SourceX's published screening profile and program terms, the uncertainty standard in ICD 203 and the missing-information question in Datasheets for Datasets. It measures how a summary states its facts. It does not measure record quality, demand, rights or value, and SourceX has not published data on whether summaries written this way change review outcomes. To test it, count for your next ten introductions how many U2 lines SourceX resolves on the first call compared with summaries written without codes; those figures are not yet published anywhere.

The [company fit checker](/tools/company-fit-checker) is a quick, non-binding screen to run before you start a grid, and the [guides hub](/guides) lists related pages.

## 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.

Once the CEO has approved a grid with its unknowns showing, [register for a partner link](/register), check the confirmed lines against [who qualifies](/who-qualifies) and read the [program terms](/terms) before you submit.

Writing an honest referral summary is partner work; assessing SourceX as a company to invest in is a separate question, and investor materials can be requested through the [SourceX investor overview](https://sourcex.si/investors).

This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/how-it-works
- https://archive.dni.gov/files/documents/ICD/ICD-203.pdf
- https://arxiv.org/pdf/1803.09010
- https://sourcex.si/investors
