# Referral terms update communication plan | SourceX

Canonical: https://refer.sourcex.si/guides/the-partner-communication-plan-after-program-terms-change
Last updated: 2026-11-04

A new terms version is a communication task only where someone relied on your old words. Start with section 11 of SourceX's terms, which says what each version changed. List every statement your team made that rests on the changed section, find who received it, and send each audience a short dated note in a fixed order: people about to act on your words first, then your own introducers, then published material, then the log. Quote the new wording and link it. Never tell anyone how the change applies to their own signed documents.

This plan is for the compliance or communications lead at a partner firm, network or fund. Keeping your own pages accurate is one job, and saving the version that governed each referral is another; the [guide to saving the applicable terms version](/guides/why-a-partner-should-save-the-applicable-terms-version) covers the second. This page is about people: the CEOs, colleagues and readers who already heard last month's wording.

## What a new version changes, and what it leaves alone

Section 11 opens: "SourceX may publish new versions of these terms." It then sets the limit that shapes every note you send: "Signed agreements are never silently replaced; rates and exceptions in signed agreements are preserved." The sample Channel Partner Agreement says the same from its side. Section 7.2 makes the agreement and its Schedule A prevail over inconsistent website terms, and Schedule A paragraph 9 says: "Website updates, calculator changes and dashboard edits do not change this Agreement." Section 8 of the terms adds that a signed Schedule A's rate, calculation base and cap prevail over the website text.

So a new version can make your sentences wrong without changing anyone's contract. That split decides the tone of the plan: you are correcting what you said, not announcing what someone's rights now are.

Section 11 also lists, version by version, what changed. As of 28 October 2026 it holds five change lines.

| Version | Section named | What the change line says (paraphrased) | Reaches earlier referrals? |
|---|---|---|---|
| 2026-10-12 | 4 | The reward calculation, the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, applies to all referrals | Yes, including those submitted earlier, in the line's own words |
| 2026-10-19 | Agreement | Partners now sign the Channel Partner Agreement (version 2026-10-19) | The line does not say; SourceX decides |
| 2026-10-21 | 3 | Section 3 states what counts as an existing relationship with SourceX | The line does not say; SourceX decides |
| 2026-10-22 | 5 and 9 | Section 5 states the payment deadline and conditions in Schedule A's words; section 9 links an unsigned sample agreement | The line does not say; SourceX decides |
| 2026-10-22.2 | 4 | Section 4 defines Actual Supplier Payout in Schedule A's words | The line does not say; SourceX decides |

Where a change line is silent about referrals already in progress, your note is silent too. The published terms do not settle that point, and SourceX does.

## Who heard the old wording

Most terms changes concern partners, not companies. A company's fit is set by SourceX's screening criteria, which the screening page says vary with SourceX's current data needs and the specific program. A company's payment is set in its own signed agreement. So the audiences differ in what they could do with a stale sentence.

| Audience | What they may have heard from you | What a stale line could cause | Order |
|---|---|---|---|
| CEOs you answered on a program point | A direct answer to their question, such as what counts as already known to SourceX | A decision made on an answer that is now incomplete | 1 |
| Your own introducers: staff, associates, network members | Your FAQ, your onboarding deck, your summary of the reward | The same wrong line repeated to dozens of people | 2 |
| Agencies and assistants | Templates, drafts and saved replies | New copy built on the old wording | 2 |
| Readers of published material | Pages, posts, newsletters, slides | A misunderstanding at scale, but slowly | 3 |
| Anyone you reported program terms to, such as a fund's LPs or committee | A summary in an update | A file that later contradicts the terms | 4 |

Every note that mentions the program carries your own connection: you may be paid a reward by SourceX if a company you introduce completes a licensed transaction. Section 4 of the terms is the line to rest the company side on: "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation."

## The versioned update rollout checklist

Day 0 is the day you notice a new version stamp.

**Day 0: read and classify**

1. Record the new version, its publish date and the date you read it, and save a copy of the page.
2. Read the new change line in section 11, then compare the named section with your saved copy of the previous version, word for word.
3. Classify the change. **Log only:** the new text matches everything your team says. **Correct:** something your team said is now wrong or incomplete. **Reach back:** the change line says it applies to referrals submitted earlier, so people with past introductions are in scope too.

**Day 0 to 1: find and freeze**

4. Search everything your team sends for the changed section: FAQ answers, decks, email templates, saved replies, scheduled posts and agency drafts. Search for the idea, not only the words; paraphrases are where stale lines hide.
5. Pause any sequence or scheduled post that carries the old line until it is fixed.

**Day 1 to 2: people who act next**

6. CEOs you answered on the changed point: one short personal note, never a newsletter. What you said, the new words in quotation marks, the version and the link. Questions about their own company go to SourceX.
7. Your introducers and agencies: an internal note with the old line, the new line, the date to stop using the old one and the replacement wording.

**Day 2 to 5: published material**

8. Correct each published item with a dated note where a reader could have relied on it. The [same-day correction steps](/guides/how-to-correct-an-overenthusiastic-message-before-it-spreads) apply when the old line was also overstated.

**Day 5 onward: close it**

9. Log the version, what changed, who was told and when, and which items were corrected.
10. Set the next check. Version stamps arrive without warning, so a calendar check is the only reliable trigger.

**Every note contains:** the version stamp, the quoted new words, the link to the terms, the date you read them and your reward disclosure. **No note contains:** a reading of which version governs the recipient's own introduction, a promise that an introduction in review is unaffected, any amount, or urgency.

## One change, rolled out (Illustrative)

Illustrative. A generic advisory firm, invented people and notes; the quoted terms text is real.

In September the firm's partner FAQ said: "A company is new to SourceX unless it has already applied." A CEO who had a short email exchange with SourceX the year before asked whether that mattered, and an associate answered no, citing the FAQ.

On 21 October section 3 gained this sentence: "A relationship includes any earlier lead, account or email correspondence between SourceX and the company, however it began." The FAQ line is now incomplete, so the change is classed **Correct**.

The note to the CEO:

> In September we told you that only an earlier application mattered to SourceX's records. SourceX's terms now say more. Section 3 of version 2026-10-21 reads: "A relationship includes any earlier lead, account or email correspondence between SourceX and the company, however it began." This concerns only whether our introduction can be credited to us. SourceX pays any reward separately, so your company's payment would be the same either way, and SourceX decides how its records apply to any company. The terms are at refer.sourcex.si/terms.

The internal note tells the associates to stop using the FAQ answer that day, gives the replacement ("SourceX checks its own records, including earlier leads, accounts and email correspondence; it decides whether an introduction is credited"), and asks each of them to list any company where they gave the old answer. The FAQ page is corrected with a dated line. Nobody predicts how SourceX will treat the CEO's company; that is decided in duplicate review.

## Check evidence, scope, timing and permission before each note goes out

- **Evidence.** The quoted words come from the live page on the day you send, not from memory or a colleague's summary.
- **Scope.** Say only what the changed section says. A change to section 3 is not a reason to restate section 5 from memory.
- **Timing.** People who act next hear first, and individually. A CEO should never learn of a correction from a newsletter you sent to everyone.
- **Permission.** A note to a CEO uses only what that CEO told you for the introduction. Naming SourceX publicly as your program needs SourceX's written authorization under section 4.5 of the sample agreement, so a public correction that names it needs that authorization on file.

Partners on a signed Schedule A or addendum that differs from the default keep their own terms, as the rewards page notes for the cap. If your network mixes standard and signed exceptions, segment the internal note by governing document; the [plan for custom versus standard terms](/guides/how-to-keep-custom-terms-from-confusing-standard-partners) shows how. When the stale line came from someone else's copy rather than your own, the [correction loop for outdated criteria](/guides/when-a-regional-partner-shares-outdated-country-criteria) is the closer fit.

## Where a rollout plan falls short

- **Frequent versions.** Section 11 lists five versions published between 12 and 22 October 2026. Notes that arrive every few days stop being read, so batch every Log-only change into the record and write to people only when a Correct or Reach-back change touches them.
- **Silence in the terms.** Several change lines do not say whether they reach introductions already submitted. Your note cannot fill that gap; SourceX decides.
- **Memory.** People repeat what they heard in a meeting, not what the FAQ says. Ask each introducer where they used the old line, not just whether they read the note.
- **Fit criteria move separately.** The screening page changes on its own schedule, and a company that missed one program may suit another later. A terms version stamp will not tell you when that happens.
- **It is not legal advice.** How a change bears on your own agreement is a question for SourceX and your own counsel.

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

Put the next version check in the calendar today, then make sure everyone who introduces companies for you has [registered](/register) and signed, links [who qualifies](/who-qualifies) instead of paraphrasing it, and quotes the [program terms](/terms) with the version they read. More guidance for partner teams is in the [guides hub](/guides).

## Sources

- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/rewards
