How to update a referral brief after material facts change: a four-tier materiality test, a versioned change log and a notice routine that never edits silently

Short answer

Never edit an approved brief silently. When a fact it relies on changes, log the old value, the new one, the date you learned it and who told you, then grade the change. Cosmetic fixes wait for the next version. Changes to fit, scope, authority or the company's history with SourceX need a new numbered version approved by the CEO, a short note to SourceX saying what changed, and every earlier version kept on file.

Visual briefFull-size diagram
A timeline of three versions of one Illustrative referral brief: v1 approved and sent with the introduction; v2 after a Tier 2 change, a record family closed, which the CEO re-approves and SourceX is told about; v3 after a Tier 3 change, a new CEO, where the brief is paused and SourceX is told; superseded versions are kept.
Illustrative. A generic logistics company's brief across three versions, following the tiers and notice routine on this page.

For a portfolio operations analyst, briefs age faster than expected. A portfolio company reorganizes, a founder hands over the CEO role, a records system migrates, counsel pulls a record family back. The brief SourceX holds then describes a company that no longer exists in that form, and the person who sent it is the only one who knows.

Four tiers of change, from a typo to a new decision-maker

Grade every change before doing anything else. When a change could sit in two tiers, use the higher one.

TierKind of changeExamplesWhat happens next
0, cosmeticWording or formattingA misspelled system nameFix it in the next version; no notice
1, detailA labeled estimate refined without changing the pictureA volume band moves from 200,000 to 300,000 records to 250,000 to 350,000; a system renamed after an upgradeLog it; the next approved version carries it to SourceX
2, fit or scopeA fact that bears on the published fit tests or on what is open for discussionThe peak full-time figure corrected; a record family closed; records found to be partly client-owned; the English share of offered records changedStop forwarding, confirm, get CEO approval for a new version, notify SourceX
3, authority or historyWho can say yes, who controls the company, or whether SourceX already knew itA new CEO; an acquisition; an earlier application or email exchange with SourceX comes to lightPause; the right person decides; SourceX hears what you learned

Two judgments trip people up. First, peak headcount is historical. A layoff that takes full-time staff from 140 to 90 changes today's count, not the peak, so on its own it is a Tier 1 note; discovering that the true peak was 46 is Tier 2. The note on counting full-time employees explains the measure. Second, control is not a detail. SourceX's screening page is direct about acquisitions: "Once a company is acquired, the acquirer's CEO decides for it, not the former board." After a sale, the old approval no longer speaks for the company, and a parent with its subsidiaries shares a single reward cap. Whether the acquirer's own past dealings with SourceX affect credit for the introduction is not something the terms spell out; SourceX settles that in its duplicate review, and the log should not guess.

The duplicate rule is the other Tier 3 trigger. Section 3 counts any earlier lead, account or email exchange between the company and SourceX as a relationship, however it began. If the CEO mentions, months later, that someone once filled in a SourceX form, that is a change to the brief's history, not a footnote.

What to re-collect after a change, and what must stay fixed

A change tells you which lines to re-ask. Leave the rest alone, so the CEO is not asked to reconfirm the whole brief every time.

TriggerLines to re-askAsk whom
Restructuring or layoffsPeak full-time figure and month; who now owns each open systemThe CEO, or the finance lead the CEO names
System migrationSystems, the years each covers, what moved and what stayed behindThe administrators of the old and new systems
Counsel review or a client disputeWhich families are open; whose records they areThe CEO, with counsel's conclusion in the company's own words
CEO change or acquisitionWhether the company still wants the conversationThe new CEO
A remembered contact with SourceXWhen, through whom, about whatThe CEO

Some things never change in a revision. The original introduction date and its evidence stay as they were, because "Attribution is decided from dated records, including written introduction evidence, existing applications and preexisting relationships" (section 2). The CEO's original approval stays in the file as history even after a successor arrives. And earlier versions are kept, marked superseded. Never present a revised brief as a new introduction: whether any credit follows is SourceX's decision, made from those dated records.

The change log and notification protocol

A log row per changed field, and seven steps that run in order.

VersionLearned onFieldWasNowSourceTierApproved bySourceX told
The new version numberThe date you heardThe brief line affectedThe old valueThe new value, labeledWho said it, and how0 to 3The CEO or named sponsor, with dateDate and channel, or "not needed"
  1. Freeze. Stop forwarding the current version as soon as you suspect a Tier 2 or Tier 3 change.
  2. Log. One row per field, quoting the source's own words where you can.
  3. Grade. Assign the tier, and take the higher of two candidates.
  4. Confirm. Check the new fact with the company person who owns it, and label it fact, estimate or unknown.
  5. Approve. The CEO, or a sponsor the CEO named for this purpose, approves the new version. After an authority change, the new CEO decides whether there is a brief at all.
  6. Notify. Send SourceX the new version with a three-line note: what changed, when you learned it, what is still unknown. Our own timing, not a program rule: within two business days of approval for Tier 2, and the same day you learn of a Tier 3 history finding.
  7. Archive. Keep every version with its date, marked superseded.

None of this is new to people who document data. In Datasheets for Datasets, the maintenance section's own explanation reads: "The questions in this section are intended to encourage dataset creators to plan for dataset maintenance and communicate this plan to dataset consumers." It also asks how the retirement of older versions will be communicated. A referral brief is not a dataset, but whoever relies on it needs the same assurance that they hold the current version. SourceX's terms model the habit as well: they carry a dated version history, and section 11 says "Signed agreements are never silently replaced".

Method note. The tiers and steps apply SourceX's program terms (Version 2026-10-22.2, since replaced by version 2026-11-04) and screening page, checked 2026-10-27, with the maintenance practice from Datasheets for Datasets. The tier boundaries and the two-business-day timing are our framework. SourceX has not published how it treats a revised brief or whether a change alters review timing.

One brief through three versions (Illustrative)

Illustrative. A generic 210-person third-party warehousing company, invented facts and dates.

VersionLearned onFieldWasNowSourceTierApproved bySourceX told
v14 AugustWhole briefNoneFirst approvalThe CEONot gradedThe CEO, 4 AugustSent with the introduction
v22 SeptemberOpen familiesWarehouse management records and yard camera footageWarehouse management records onlyOperations director, by email2The CEO, 5 September8 September
v22 SeptemberPick record volumeAbout 2 million, estimate2.5 to 3 million, read from the system dashboardWarehouse system administrator1The CEO, 5 September8 September, same note
v36 OctoberCEOFounder-CEOCEO appointed by a new parent groupThe founder, by phone; a public announcement3Pending the new CEO6 October: told the brief is paused

Version 3 is less a version than a stop sign. The founder's approval of v2 was valid when given, and it stays in the file. But the company now answers to a parent group, the group's chosen CEO has never heard of the conversation, and only that person can restart it. The note to SourceX says exactly that and nothing more: who changed, when the analyst learned it, and that no one is speaking for the company until the new CEO does.

Labels after an update: estimates stay estimates

An update tempts people to tidy. Four rules keep labels honest.

SituationWrong moveRight label
A figure is revised by the same methodCalling the new number a factStill an estimate, with the method named
A figure is now counted from an exportKeeping the old range alongside itA fact, with who counted and when
A record family is closedLeaving its volume in the totalsRemove its figures entirely
An open question is answeredDeleting the questionMove it to facts, naming who answered

New unknowns created by the change get an owner and a date, the same as the old ones. A changed brief with fewer unknowns than its predecessor deserves a second look: changes usually create questions.

Handing over a revised brief, and the first call after it

Where the brief sits decides what you send.

  • Before the first call. Send the latest version with the change note. Open the call with two minutes for the CEO to confirm the change in their own words, then run the original agenda: SourceX's process, open families at metadata level, next steps.
  • After review has started. Send the change note to the person at SourceX handling the referral. Do not re-argue the opportunity; the company speaks for itself.
  • After a Tier 3 change. No call until the new authorizer has decided. If they say no, close the referral and record the reason.

The routine pairs naturally with two others. When it is SourceX's criteria rather than the company that change, the criteria change register for network maps handles the rows affected. When the change is a narrowed scope, the scope boundary statement is the document to version. And for a starting layout of the brief itself, the group booking change referral brief template shows a one-page format.

Where a change log can mislead

  • False precision. A tidy log can make guesses look audited. The labels matter more than the rows.
  • Noise. Sending every Tier 0 or Tier 1 change to a CEO wears out goodwill. Batch them into the next version.
  • Late learning. Funds often hear of changes weeks after they happen. The log records when you learned, not when the change occurred, and should say so.
  • Confidential sources. A change heard in a board meeting cannot enter the brief until the company confirms and approves it.
  • Upstream only. Once a company signs with SourceX, its own agreement governs changes; SourceX's how-it-works page says a material change after the Dataset Deal Confirmation needs a signed amendment. The referral brief is not that document and should never pretend to be.
  • Unpublished treatment. SourceX has not said how it weighs a revised brief, so no tier here predicts an outcome.

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.

Before your next introduction, set up the change log alongside the brief, then register for a partner link, confirm the fit facts the log will track on who qualifies and reread sections 2 and 3 of the program terms, which decide what a history change means. The venture platform overview and the guides library cover the rest of a portfolio team's routine.

Keeping a referral brief current and assessing SourceX as a business to back are two separate tasks; for the second, SourceX shares company and commercial metrics with investors directly and takes requests through its investor page.

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.

  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

Does a revised referral brief restart the 90-day attribution window?

Do not assume it does. Credit is decided from dated records under section 2 of the terms, and SourceX makes that decision. Keep the original introduction date visible in the change log and present the revision as an update, never as a fresh introduction.

Who approves a revised brief when the CEO has just left?

Nobody from the old arrangement. The previous CEO's approval stays in the file as history, and the brief is paused until the new CEO decides whether the company wants the conversation at all. If an acquirer now controls the company, its CEO decides.

Should a fund tell SourceX about a change it learned in a board meeting?

Not until the company has approved it for the brief. Board information belongs to the company; the routine here moves a change into the brief only after the company person who owns that fact has confirmed it and the CEO has approved the new version.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. sourcex.si/how-it-works
  4. arxiv.org/abs/1803.09010
  5. sourcex.si/investors

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