How to archive approval evidence for public partner claims: a claim approval evidence log that freezes the published words, the source as it read that day, the approver and every permission, so a stranger can rebuild the decision a year later

Short answer

Archive each public claim as one evidence packet, sealed on the day it goes live: the words exactly as readers saw them, where and to whom they ran, a saved copy of the SourceX sentence they rest on with its version or update date, a note of what that sentence does not cover, who approved the claim, any written permission it needed and, later, when and why it came down. Support you collect after publication cannot stand in for the packet, because it shows today's facts, not the ones you relied on.

Visual briefFull-size diagram
An evidence folder for one Illustrative public claim holding six labeled cards, words as published, source as it read that day, scope note, approver, permissions and retired; the first five carry green ticks as filed on the live date while retired stays open, beside a dashed box of evidence found later, marked with an orange cross and the label does not count.
Illustrative claim and folder. The six cards follow the evidence log on this page; no real partner archive is shown.

The person who builds a claim archive rarely reads it. A successor, counsel, SourceX or a CEO holding a screenshot opens it later, usually after the source has moved on.

Who opens the archive, and what each one asks

Who asksTheir questionThe packet field that answers it
SourceXDid we authorize this, and what exactly did it say?Permissions, with the dated written authorization, and the capture of the published words
A company's CEOIs this what your page told me in March?The capture, with its date and channel
Your counselWhat did you rely on, and did it exist when you published?Source sentence, saved source copy, approver and approval date
Your successorIs this still true, and who owns it now?Re-check triggers, owner role and the retirement record

Counsel's question is the one an archive is built for. The FTC's policy statement on advertising substantiation, in the search excerpt we read, says later evidence does not rescue a claim: "nor does it mean that subsequent evidence of truthfulness absolves a firm of liability." Whether that policy reaches a particular partner post is for your own counsel; as a design rule it settles the timing, because the packet must be complete on publication day.

SourceX's own requirements are short. The program terms contain no marketing rules, and section 8 leaves confidentiality to the signed Channel Partner Agreement, which partners sign before submitting any introduction. In the sample agreement, section 4.5 says "Neither Party may publicly identify the other as a partner or disclose non-public deal details without written authorization, except as legally required," and section 7.1 says "Partner is not an agent of SourceX and may not commit SourceX to prices, licenses, payouts or other obligations." Where a marketing question falls outside those lines, SourceX decides, and its written answer belongs in the packet.

Identify the claim, the audience and your commercial connection

Archive by claim, not by asset. A landing page can hold eleven claims and a slide can hold three, and each one ages on its own schedule. A claim is the smallest statement a reader could act on: "SourceX pays our reward separately", "companies need 50 or more full-time employees at peak", "the CEO decides". Give each an ID that survives redesigns and reposts.

Record the audience beside it: a sentence cleared for a client newsletter is not cleared for a public post that founders, journalists and competitors will read. Then record the commercial connection, which changes how readers weigh every claim on the page. The sample agreement names the Partner as "[an individual, or entity type and jurisdiction]", so the party that could be paid may be you personally or your firm. The packet says which, and quotes the disclosure line that ran beside the claim, with its placement.

The claim approval evidence log

One row per field, one packet per claim. Fields one to eight are filed on publication day; nine and ten stay open until the claim comes down.

#FieldWhat to captureWhy it matters later
1Claim ID and exact wordsThe sentence as readers saw it, including text inside images and alt textParaphrased logs cannot settle a dispute about wording
2Channel, audience and live dateURL or channel, list or audience, date and time it went liveApproval was given for one audience on one date
3Capture as publishedA dated PDF or screenshot of the rendered page, on a desktop and a phoneLayout can hide a condition the draft showed
4Source sentenceThe SourceX sentence quoted exactly, its URL and section, and the terms version or the page's updated dateSourceX pages change; the version number is the only fixed reference
5Saved source copyA dated copy of the source page as it read that dayProves what the sentence said even after the live page changes
6Scope noteWhat the source does not say, written in one lineMost stale claims fail on scope, not on accuracy
7DisclosureThe exact disclosure line and where it sat relative to the claimShows readers could weigh your interest
8Approver and basisName, role, date, and the checklist or review step usedAnswers who decided, and on what
9Re-check triggersNew terms version, a changed updated date on the source page, a new agreement version, your agreement's end dateTells a successor when the claim must be read again
10Retirement recordDate, reason, replacement wording and the copies chased downCloses the packet without deleting it

Permissions sit across fields 4 and 8 and deserve their own folder: SourceX's dated written authorization wherever the claim identifies SourceX as your partner, and the CEO's written permission wherever a company is named or recognizable. A restated public program fact needs no company permission. An outcome about a named company always does, and so does anything that would let a reader recognize the company.

Method note. The ten fields were built for this guide from SourceX's terms (version 2026-10-22.2, since replaced by version 2026-11-04), the sample Channel Partner Agreement (sections 4.5 and 7.1), the who-qualifies page as updated on 2026-10-27, the FTC's substantiation policy statement and section 255.1 of its Endorsement Guides, all read on 2026-10-28. The log has not been tested in a dispute, and no data on how partner claims are challenged has been published.

Check evidence, scope, timing and permission: one real claim

The draft below is attributed to an Illustrative 30-person consultancy, but the source it leans on is a real SourceX sentence: "Using a partner costs the company nothing: SourceX pays our reward separately."

Evidence. Section 4 of the terms says: "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation." The second half of the claim matches it. Field 4 records the sentence, section 4, version 2026-10-22.2, since replaced by version 2026-11-04; field 5 holds the saved copy. The same sentence is the published basis for a related point partners often want to make: the company is paid the same amount whether or not a partner introduced it, because SourceX funds the reward from its own share.

Scope. "Costs the company nothing" says more than the source. The sentence covers the company's agreed compensation; it says nothing about the time the company spends on preparation or its own advisers. The scope note reads: "Source covers payment only, not effort." The approved wording becomes "SourceX pays our reward separately; it is never deducted from what the company is paid."

Timing. The claim holds while version 2026-10-22.2, since replaced by version 2026-11-04 is current. Section 11 says "SourceX may publish new versions of these terms," so field 9 lists the next version as the trigger, plus the end of the consultancy's one-year agreement.

Permission. The draft sat under the heading "Our partner SourceX". That identifies SourceX as a partner, so it waits for SourceX's written authorization under section 4.5, filed in the permissions folder with its date. Without it, the heading goes and the claim stays.

Disclosure. Field 7 records the line beside the claim: "We may be paid by SourceX if a company we introduce licenses data to it."

Section 255.1 of the FTC's Endorsement Guides, in the search excerpt we read, puts the same idea in time: "An advertiser may use an endorsement of an expert or celebrity only so long as it has good reason to believe that the endorser continues to subscribe to the views presented." Whether the Guides reach your content is your counsel's call; the logic carries over either way, since a claim stays approved only while its basis lasts.

When the source changes under a live claim (Illustrative)

Illustrative. The partner and its four claims are invented; the dates come from the changelog in section 11 of SourceX's terms.

ClaimApprovedSource eventPacket actionStatus
A: "Partners sign SourceX's Channel Partner Non-Circumvention and Non-Disclosure Agreement"2026-10-152026-10-19: the agreement partners sign becomes the Channel Partner AgreementRetired; replacement names the current agreement; old capture keptCorrected
B: "A company SourceX already knew is not credited to us"2026-10-152026-10-21: section 3 now says any earlier lead, account or email correspondence counts as a relationshipRe-read; wording widened to match section 3Live
C: "SourceX may pay us the greater of $50,000 plus 5% and 15% of what it actually pays the company, with no cap for the company and its group"2026-10-162026-10-22.2: section 4 defines Actual Supplier Payout in Schedule A's wordsRe-read; still true; new version recorded in field 4Live
D: "Every company we introduce is pre-approved"Rejected 2026-10-16None neededPacket kept with the rejection reason: who-qualifies says such lines imply an acceptance nobody has givenNever published

Claim A was accurate on the day it ran and wrong four days later, so a capture without a version number proves little. Claim D shows why rejected drafts are archived too: a sentence that resurfaces in a colleague's deck is easier to stop when the reason is on file. For the event-level record of which terms governed each introduction, see why a partner should save the applicable terms version; for claims that rest on your own counts, the dated cohort file for growth claims does the same job.

Publish with the disclosure, or correct and close the packet

A claim goes live only when fields one to eight are filed. When a trigger fires, the owner rereads the claim against the new source and records one outcome: still true, reworded or retired.

Retiring a claim is a sequence, logged in field 10:

  1. Remove or correct it at the source, with a dated correction note where readers will see it.
  2. Chase the copies: decks, PDFs, partner bios, pinned posts, email signatures, templates.
  3. If you know a reader acted on the old wording, tell them what changed.
  4. Close the packet with the date and the replacement claim's ID.

Keep the archive under a role, such as head of communications, so it survives departures. Closed packets are kept, not deleted, for as long as your counsel sets; SourceX's terms say nothing about it. For the name-and-logo questions that often sit beside a claim, the fund endorsement checklist covers who may speak for whom, and the angle-versus-claim edit helps decide which sentences need a packet at all; the guides hub collects the other partner marketing guides.

Where an evidence log falls short

  • It records a decision; it does not make the claim true. A packet with a weak source is a well-filed mistake.
  • Reposts escape it. You can chase copies you made. You cannot recall a screenshot someone else shared.
  • Captures miss context. A PDF of a page does not show the ad that sent a reader there or the conversation around a post.
  • FTC materials are guidance, and their reach is a legal question. Whether the substantiation policy or the Endorsement Guides apply to your content is for your counsel.
  • Silence in SourceX's documents is not permission. When a claim needs something the terms and the agreement do not say, ask SourceX in writing and file the reply.

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.

Seal a packet for the next claim you publish, register as a partner before any claim describes your participation, point readers to who qualifies rather than restating fit in your own words, and record the program terms version in every packet.

  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

Do SourceX's terms require partners to keep marketing approval records?

No. The published terms contain no rules on partner marketing, and the sample agreement's publicity clause asks only for SourceX's written authorization before you identify it as a partner. The evidence log is your own practice; where the terms are silent on a marketing question, SourceX decides it, so ask and file the answer.

If someone challenges a claim, can we assemble the evidence then?

You can collect documents, but they show what is true on the day you collect them, not what you relied on when the claim went out. SourceX's pages change version by version, so a packet sealed on publication day is the only record of what the source said then.

What happens to the packets when our partner agreement ends?

Claims that describe your participation come down when the agreement ends, and each packet is closed with that date rather than deleted. How long to keep closed packets is a decision for your counsel; nothing in SourceX's published terms sets it.

Sources

  1. refer.sourcex.si/terms
  2. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  3. refer.sourcex.si/who-qualifies
  4. ftc.gov/legal-library/browse/ftc-policy-statement-re…
  5. ecfr.gov/current/title-16/chapter-I/subchapter-B/part…

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