# Partner FAQ content ownership: an owner map | SourceX

Canonical: https://refer.sourcex.si/guides/a-referral-partner-s-public-faq-needs-a-named-review-owner
Last updated: 2026-11-05

Every answer in a public FAQ about SourceX is a claim made in your name, and it goes stale the moment SourceX changes the page you paraphrased. Give each answer one named owner, the SourceX sentence it restates with that page's version or updated date, the events that force a re-read and a fixed review date. Questions only SourceX can answer get a pointer to SourceX, not an answer. Any answer that loses its owner comes down until someone takes it on.

The partner FAQ is the page nobody owns. It is usually written once, by whoever launched the partnership, and then left alone while the program it describes keeps moving.

## Why a partner FAQ goes stale faster than the rest of your site

Three things make an FAQ fragile. Each answer is a compressed paraphrase, so a small change in the source can make it wrong. The question-and-answer format reads as a rulebook, so readers act on it. And SourceX's program pages move often: the changelog in section 11 of the terms records versions dated 12, 19, 21, 22 and 22.2 October 2026, each changing a section, from the reward calculation to the name of the agreement partners sign. The who-qualifies page carries its own updated date, 27 October 2026 when we read it, and says that programs change and a screen holds only for the date it was made.

There is also a question of accountability. Section 255.1 of the FTC's Endorsement Guides, in the search excerpt we read, says "Endorsers may be liable for statements made in the course of their endorsements," and in our paraphrase it also makes advertisers answerable for misleading statements made through endorsements. Whether the Guides reach your FAQ is a question for your own counsel. Either way, the person who publishes an answer cannot hand its accuracy to SourceX: section 7.1 of the sample Channel Partner Agreement says "Partner is not an agent of SourceX and may not commit SourceX to prices, licenses, payouts or other obligations."

## What your FAQ may answer, and what it should route

Before assigning owners, sort the questions. Some can be answered by restating SourceX's own words, some belong to SourceX, and some belong to the reader's own adviser.

| Question type | Examples | What the FAQ does |
|---|---|---|
| Restate a published sentence | What is the reward? Who decides for the company? How big must a company be? Which countries? How is credit decided? Does the company get paid less? | Answers in SourceX's words, cites the page and version, links it |
| Route to SourceX | What would this company be paid? Who buys the data? How likely is acceptance? What security reports exist? How does a firm account relate to its people's own accounts? | Says SourceX answers this and links SourceX's page; never guesses |
| Route to the reader's adviser | Can my profession accept a referral reward? Is the reward taxable where I live? Does my client contract allow an introduction? | Says it is a question for the reader's own counsel, tax or ethics adviser |

Two routed rows deserve a sentence each. SourceX need not reveal Acquisition Partner names, contracts, prices or margin to partners (section 4.6 of the sample agreement), so a partner who answers "who buys the data" is guessing or leaking. And where the published terms do not settle a question, such as how a firm's account relates to the personal accounts of its people, the honest answer is that SourceX decides it; the [personal versus firm-owned links worksheet](/guides/how-to-handle-personal-versus-firm-owned-referral-links) helps a firm prepare that question.

## The review cadence and owner map

One row per answer. The owner is a named person with a named deputy; "marketing" is not an owner.

| Answer | Owner (Illustrative) | Rests on | Re-read when | Fixed review |
|---|---|---|---|---|
| What is the reward? | Partnerships lead | The offer block, quoted whole, and terms section 4 | New terms version; a signed Schedule A that differs | Quarterly |
| Does the company get paid less? | Partnerships lead | Terms section 4 | New terms version | Quarterly |
| Who decides for the company? | Compliance lead | Who-qualifies, ownership section | Who-qualifies updated date changes | Quarterly |
| Which countries and sizes fit? | Compliance lead | Who-qualifies screening profile and its geography sentence | Who-qualifies updated date changes | Quarterly |
| How is credit decided? | Partnerships lead | Terms sections 2 and 3 | New terms version | Quarterly |
| What does the partner agreement cover? | Compliance lead | Terms section 9 and the sample agreement | New agreement version; your agreement nears its one-year end | Every renewal |
| Who buys the data? | Compliance lead | No answer; routed to SourceX | SourceX publishes anything new on the point | Quarterly check that it still routes |
| Can my profession accept a reward? | Compliance lead | No answer; routed to the reader's adviser | A reader says the routing is unclear | Quarterly check that it still routes |

Four rules keep the map alive.

1. **One owner, one deputy, per answer.** When the owner leaves, the deputy takes the answer or it comes down.
2. **Triggers beat the calendar.** The fixed review is a backstop; a new terms version means a re-read that week, whatever the calendar says.
3. **A visible checked-against line.** The FAQ shows, near the top, the terms version and date it was last checked against: "Checked against SourceX terms version 2026-10-22.2, since replaced by version 2026-11-04 on 28 October 2026."
4. **Conflicts go to SourceX.** If two SourceX pages seem to answer a question differently, the owner asks SourceX in writing and publishes nothing on the point until it replies.

**Method note.** The map was built for this guide from SourceX's terms (version 2026-10-22.2, since replaced by version 2026-11-04 and its section 11 changelog), the who-qualifies page as updated on 27 October 2026, the sample Channel Partner Agreement and two FTC sources, all read on 28 October 2026. The quarterly backstop is our suggestion, not a SourceX rule; SourceX's terms say nothing about partner FAQs. The map has not been tested across a partner population.

## One real answer, audited against source, scope, timing and permission

The draft answer below is invented for an Illustrative 25-person consultancy. The sources it is checked against are real.

**Question:** Who at the company needs to agree?
**Draft answer:** "Any senior executive can sign the company up, and our link takes care of the credit."

**Evidence.** The who-qualifies page says: "Under the program, opening a licensing discussion and signing for the company fall to the CEO." The first half of the draft fails. The second half fails against section 2 of the terms, which says attribution is decided from dated records and "an earlier link click alone does not decide credit."

**Scope.** "The CEO" is the right answer for an operating company, but not the whole one. The same page says that once a company is acquired the acquirer's CEO decides, and that a formal insolvency process can move control of the assets away from the CEO. The owner adds one line pointing to the [closed-business authority map](/guides/who-can-authorize-a-referral-for-a-closed-business) rather than writing an estate rule of their own.

**Timing.** The answer rests on a page updated on 27 October 2026, so the owner logs that date. When the updated date changes, the answer is reread.

**Permission.** Restating SourceX's published words raises no company-permission question. Introducing the FAQ under a heading such as "Our partner SourceX" is different: section 4.5 of the sample agreement says "Neither Party may publicly identify the other as a partner or disclose non-public deal details without written authorization, except as legally required." The heading waits for SourceX's written authorization, filed with the answer's record.

**Approved answer:** "The company's CEO decides whether it talks to SourceX and signs for it. If the company has been acquired, the acquirer's CEO decides; if it is in a formal insolvency process, the CEO may not be enough. Credit for an introduction is decided from dated records, not from a link click. Source: SourceX who-qualifies page (updated 27 October 2026) and terms section 2 (version 2026-10-22.2, since replaced by version 2026-11-04)."

One more answer shows why some sentences must stay word for word. Asked "Which countries?", the FAQ should carry SourceX's sentence unaltered: 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. SourceX publishes no other country rule, so any shorter version drops a condition.

## Publish with the disclosure and the checked-against line

The FAQ's own commercial connection needs to be visible where readers use it. The FTC's FAQ on its Endorsement Guides, in the search excerpt we read, tells affiliates linking to a retailer: "You should disclose your relationship to the retailer clearly and conspicuously on your site, so readers can decide how much weight to give your endorsement." In our paraphrase, the same FAQ warns that disclosures found only on an about page or at the end of a post are likely to be missed. Put a plain line at the top of the FAQ and beside any partner link inside an answer, such as "We may be paid by SourceX if a company we introduce licenses data to it; the company is paid the same either way." The second clause rests on section 4 of the terms, which has SourceX pay the reward separately and never deduct it from the company's agreed compensation. Partners sign the Channel Partner Agreement before submitting introductions, so whoever signed is the party the line names. The [FTC disclosure examples for referral posts](/resources/ftc-disclosure-examples-referral) cover wording for other channels.

When an answer fails a re-read and cannot be fixed that week, take it down and say so: "This answer is being updated; see SourceX's terms." Log the change in the answer's evidence packet, as the [claim approval evidence log](/guides/how-to-archive-approval-evidence-for-public-partner-claims) describes.

Two related pages cover what this one does not. The [partner FAQ experiment](/guides/the-partner-faq-experiment-that-removes-repeated-questions) measures whether an FAQ reduces repeated questions, and the [attribution FAQ for a multi-partner firm](/guides/the-referral-attribution-faq-for-a-multi-partner-firm) handles internal credit questions a firm answers for its own people. For more partner guides, browse the [guides hub](/guides).

## Where an owner map falls short

- **An owner can be wrong on schedule.** The map makes someone responsible; it does not make them right. A second reader for any answer about money or authority is cheap insurance.
- **Copies escape it.** Answers pasted into proposals, chat replies and slide notes do not get the update. Keep the FAQ as the one place answers live and link to it.
- **SourceX's silence is not an answer.** Where the published terms and agreement say nothing, the FAQ says SourceX decides, and the owner asks.
- **FTC materials are guidance.** Whether they apply to your FAQ, and how, is for your 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.

Name an owner for each answer before the FAQ goes live, [register as a partner](/register) so the disclosure line names the right party, link [who qualifies](/who-qualifies) from every fit answer and record the [program terms](/terms) version on the page.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://www.ftc.gov/business-guidance/resources/ftcs-endorsement-guides-what-people-are-asking
- https://www.ecfr.gov/current/title-16/chapter-I/subchapter-B/part-255/section-255.1
