This is for lawyers, alliance managers, accountants, compliance consultants and other regulated advisers whose clients might license their own records. It owns one question, the format. Which words avoid implying neutrality is covered by the independence language review sheet; what belongs in the company's column and what in yours by the two-column disclosure guide; a full reviewable draft for finance advisers by the twelve-item client disclosure. This page applies no rule to anyone.
Three audiences, three different disclosure questions
A referral relationship here means one thing: SourceX may pay you if the company you introduce licenses data and is paid. Who needs to hear that, and in what form, depends on the audience.
| Audience | What they need to know | Who usually sets the format | Typical channel |
|---|---|---|---|
| The company's CEO, your client or contact | That SourceX may pay you, on what basis, and that the company's amount does not change | Your professional rules, applied by your reviewer | Conversation, introduction email, engagement letter |
| Your employer, firm or fund | That you may receive outside pay | Its own policy, often in its own form | Approval request |
| A group or the public | Your connection, wherever you mention SourceX | Your body's rules on communications, advertising rules where they apply, and SourceX's agreement | Newsletter, post, panel, bio |
The third row carries a contractual step that is easy to miss. Section 4.5 of the sample Channel Partner Agreement reads: "Neither Party may publicly identify the other as a partner or disclose non-public deal details without written authorization, except as legally required." Before a post or a talk names SourceX as your partner, get that authorization in writing.
"In writing" has levels, and rule-makers name them
Rule texts are precise about form in a way conversation is not. The ABA's Model Rule 1.0, in paraphrase of its terminology, says consent "confirmed in writing" can be consent the person gives in writing, or a writing the lawyer promptly sends confirming oral consent, and that where this is not feasible at the time it must follow within a reasonable time. A "writing" includes tangible or electronic records, electronic communications among them, and a "signed" writing includes an electronic sound, symbol or process. The ABA's commentary adds, again in paraphrase, that where a rule needs a writing signed by the client, the rule says so in its own text.
Whether any of those provisions reaches a SourceX referral is a question for your ethics counsel. They are here to show that "put it in writing" is several instructions, not one.
Public messages add a second dimension, the medium. The FTC's Endorsement Guides define the term this way: "'Clear and conspicuous' means that a disclosure is difficult to miss (i.e., easily noticeable) and easily understandable by ordinary consumers." The same section, in paraphrase, places a disclosure in the visual part of a visual message, the audible part of an audible one, and both when the message uses both. Whether the Guides reach a given post is for counsel; the habit of matching the disclosure to the medium is useful either way.
Put together, the forms a reviewer can choose from look like a ladder.
| Step | Form | What it can show later | What it cannot show |
|---|---|---|---|
| 0 | Said aloud, no record | Nothing beyond memory | That the client heard it, or when |
| 1 | Said aloud, then confirmed in a message you send | The date and words of the confirmation | That the client read or accepted it |
| 2 | Written into the introduction message itself | That the disclosure traveled with the ask | Acceptance, unless the client replies |
| 3 | A separate written notice before the introduction | Disclosure before any step was taken | Acceptance |
| 4 | An acknowledgment the client signs, on paper or electronically | Receipt and acceptance, dated | That every term was understood |
| 5 | Shown inside a public message, in the same medium as the mention | That each reader or listener met it | Anything about one client |
The disclosure-format review checklist
Take the checklist to whoever reviews your participation, with one column for each channel you plan to use. Each row asks for a choice, not a general view.
| Item | Question for your reviewer | Choices to record |
|---|---|---|
| F1. Pay first | On these facts, is any pay permitted at all? | Yes, with conditions; or no, and the checklist turns to F10 |
| F2. Form | Which step of the ladder does this channel need? | Step 0 to 5 |
| F3. Moment | When must the disclosure be given? | Before the first mention, before the CEO is asked, before you submit, before the company signs, or again at payment |
| F4. Signature | Must the client reply or sign, and is an electronic signature acceptable? | None, a reply, or a signature |
| F5. Minimum content | What must it say? | Who may pay you; the basis (the greater of $50,000 plus 5% and 15% of Actual Supplier Payout with no cap, payable only when conditions are met); that the company's amount is unchanged; what you will not do |
| F6. Repeat | What calls for a fresh disclosure? | A new matter, a change in your role, a new version of SourceX's terms, a reward becoming payable |
| F7. Record | Where is it kept, and for how long? | Your firm's records policy, named |
| F8. Public naming | Before you name SourceX as your partner in public, is SourceX's written authorization in hand? | Yes, dated; or no public naming |
| F9. Employer | Must your employer receive written notice, in its own form? | Its policy and the date of notice |
| F10. Unpaid route | If you will take no reward, must you say so in writing, and has SourceX confirmed in writing how it treats a declined reward? | The reviewer's answer and SourceX's reply, both dated |
F5 can rest on two sentences of the terms, quoted rather than paraphrased. Section 4: "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation." Section 5: "A lead, meeting or signed agreement alone does not earn a payable reward." No amount belongs in a disclosure, because none is known: the company's payout is fixed only in its own Dataset Deal Confirmation with SourceX.
F10 exists because the published terms do not say what happens when a partner takes no reward. SourceX decides that, so get its answer in writing before a disclosure promises the client anything.
Channel by channel: where the format question bites
| Channel | The format question that usually comes up | What tends to go wrong |
|---|---|---|
| One-to-one conversation | Is spoken disclosure enough, or must a written confirmation follow? | Relying on memory when a payment arrives months later |
| Introduction email | Should the disclosure sit in the email itself, above the ask? | Hiding it in a signature block or behind a link |
| Engagement letter or client agreement | Is a clause the right home, or a separate notice? | A general clause that never names SourceX or the basis of pay |
| Newsletter, client alert or social post | Must it appear inside the post, and is SourceX's written authorization in hand? | A disclosure readers must click to find |
| Panel, webinar or recording | Must it be both spoken and on screen, and does the recording keep it? | One slide at the start of a long recording |
| Partner bio or website | Where does a standing disclosure sit? | A disclosure page nobody reaches |
Recordings raise their own reuse questions, covered in reusing a webinar without misrepresenting live questions.
Confidentiality, conflict and compensation questions behind the format
Format follows substance, so three questions sit underneath the checklist.
- Confidentiality. A written disclosure is itself a record. May it name SourceX before the CEO has agreed to hear about it? Must it avoid any reference to other clients or to what you learned in the engagement? Could a public post let readers infer which client you have in mind?
- Conflict. If you also advise the company on its agreement with SourceX, is notice enough, or does your reviewer require informed consent, and in which form?
- Compensation. Does your rule require the basis of pay, an estimate or neither? Does pay from SourceX need to be offset, shared or reported to anyone?
Three disclosures, three formats (Illustrative)
Generic advisers, invented facts and invented reviewer answers; no outcome implied.
A referral. Outside general counsel to a 180-person logistics company has no matter touching its records. Her reviewer answers F1 yes, with conditions: step 4 before any introduction, plus step 2 in the email itself. The CEO signs an electronic acknowledgment, asks for the conversation, and the company applies itself.
An unpaid introduction. A partner at an accounting firm gets F1 back as no. Under F10 he asks SourceX in writing how it treats a declined reward, then writes the CEO a step 2 email stating that he will take no reward from SourceX and that the company's amount is the same either way. The CEO decides to apply.
No part in promotion. A compliance consultant planned a post naming SourceX as her partner. Her reviewer requires step 5 in the post itself, her firm's policy bars posts promoting vendors, and she never sought SourceX's authorization under section 4.5. She publishes nothing and takes no part in promotion.
| Case | F1 | Form and moment | Open point |
|---|---|---|---|
| Logistics company counsel | Yes, with conditions | Step 4 before the introduction, step 2 in the email | None |
| Accounting firm partner | No | Step 2, after SourceX's written reply | How a declined reward is treated |
| Compliance consultant | Not reached | No post | Firm policy and section 4.5 |
Keep the disclosure line, and go back before switching channels
Keep one line per company: the channel, the step used, the date given, the date of any acknowledgment, the reviewer's reference and the terms version in force. If your reviewer's answer came through a local counsel question pack, file its part D with the line. When you want to change channel, for example from a call to a group email, go back to the reviewer before you send.
Where format stops helping
- A signature does not make pay permitted. If F1 is no, no step of the ladder changes that.
- Format cannot rescue wording. A signed disclosure that calls your view independent still misleads.
- A disclosure does not move the decision. The company's CEO decides whether to talk to SourceX and signs for the company.
- A disclosure does not settle credit. One partner can be credited per company, judged from dated records, and SourceX handles competing claims in duplicate review.
- Disclosures age. SourceX may publish new versions of its terms (section 11); F6 says when yours must be given again.
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.
When your reviewer has filled in F1 to F10 for every channel you will use, register as a partner, compare the CEO's own answers with who qualifies and keep the program terms version you disclosed against; related professional guides are in the guides hub.