# Member referral feedback that improves fit | SourceX

Canonical: https://refer.sourcex.si/guides/the-member-feedback-loop-that-improves-referral-fit
Last updated: 2026-11-04

Ask the members who took part one optional question about the association's notice, never about their company. Sort every reply into a fixed code, tie each code to a lever the association controls, such as the notice's first line, who receives it or how often it is sent, and change one lever per round. SourceX's criteria, its review and each CEO's decision stay outside the loop, and nothing about a member's records is collected, for SourceX or for the association.

This is for the director of a business association, chamber or member community that tells members about SourceX as a referral partner. It assumes the association already offers the topic on an opt-in basis and wants the next notice to reach the right members with fewer misunderstandings.

## What referral fit means for an association, and what it cannot touch

For an association, fit is not whether a member's company qualifies. That is SourceX's call after review, and the member's CEO decides whether to apply at all. Fit is the match between what the association says and who reads it: members who are clearly not candidates can tell in a sentence, members who might be can see the tests and who decides, and nobody mistakes the note for a recommendation or a promise.

The feedback loop works only on levers the association owns.

| The association can change | The association cannot change |
|---|---|
| The notice's first line and how it states the published screen | SourceX's screening criteria, which vary by program |
| Who receives the notice, by member choice: an opt-in list, a topic preference | A member's eligibility, or SourceX's review outcome |
| How often it writes, and who signs the message | Which partner SourceX credits when two have introduced the same company |
| Where the disclosure of its own possible reward sits | The CEO's decision, at any member company |
| The decline route, the feedback route and the introduction protocol | What SourceX tells a member during review |

Two limits from SourceX's own documents frame the loop. The unsigned sample of the Channel Partner Agreement gives a partner no authority to share a company's inventory, records, raw data or personal information, so the loop has no field for any of them. And neither party may publicly present the other as a partner without written authorization, which is one more reason the notice must never read as an endorsement in either direction.

## The feedback-to-criteria improvement workflow

Four steps per round, borrowed from a well-tested method. The Institute for Healthcare Improvement describes a Plan-Do-Study-Act cycle as a small-scale test of a change in a real setting, run many times in sequence and widened gradually before the change is adopted (our paraphrase), and its worksheet closes each cycle with one of three choices: adapt the change and test again, adopt it at larger scale, or abandon it.

1. **Ask.** One optional question goes to the round's opted-in members a week after the notice: "Which of these best describes your reaction to our note about SourceX?" The first option is "I'd rather not answer", and a free-text box is optional.
2. **Code.** Within five working days a named staff member gives each reply one code from the table below. Free text is deleted once coded. No reply is coded from a guess about the member's company.
3. **Change.** Pick one lever to change. Complaints and misreads come first, whatever their count; otherwise take the most frequent code that maps to a change.
4. **Check.** The next round asks the same question. If the targeted code fell and no complaint rose, adopt the change; if it did not move, adapt it or drop it.

| Code | The reply, in substance | What it says about the notice | The one change it triggers | What never changes in response |
|---|---|---|---|---|
| F1 | Not for us: our full-time headcount never reached 50 | The size test came too late | Put the test in the first line, and offer an education-only version | The association never asks members for headcount |
| F2 | Not for us: most of our records are our clients' material | The ownership test was missing | Add the line on client-owned material | Nobody judges a member's contracts |
| F3 | Unclear who would decide at our company | The authority line was missing | State that the company's CEO decides and nobody else can say yes for it, the association included | No one contacts a CEO around the member who replied |
| F4 | Read it as the association vouching for SourceX, or as a sign we would be accepted | The relationship was described too warmly | Name the association's partner role, its possible reward and that SourceX decides after review | No claim that SourceX vets or favors the association's members |
| F5 | Too many messages, or the wrong sender | The cadence or signature felt like pressure | One notice and at most one reminder, signed by the program lead | No open tracking to choose who gets a reminder |
| F6 | Wanted to know what the association gets | The disclosure sat too low | Move it to the opening paragraph | The disclosure is never softened |
| F7 | Already in touch with SourceX, or an advisor raised it | The notice did not ask first | Add the "already in touch?" question before any introduction | The association does not ask who the advisor is |
| F8 | Useful; decided it is not for us | Nothing; the notice did its job | None | No follow-up to change the member's mind |
| F9 | Useful; our CEO wants to talk | Nothing | The introduction protocol starts | No introduction without the CEO's written request |
| F10 | Wanted detail on privacy, security or rights | A question only SourceX can answer | Link SourceX's published pages | No promise on SourceX's behalf about security or de-identification |

Ten codes are enough. A reply that fits none of them is a sign the code list needs review at the end of the round, not a reason to invent a code mid-round.

## A twelve-member pilot with a decline route at every step

The pilot keeps each round small enough that one change can be traced. Each round invites members to opt in until about twelve have, and every one of them gets the same sequence:

- **The notice**, with the published screen in plain words, the disclosure that the association may earn a reward, which SourceX pays separately and never takes out of a company's compensation, and a line saying that one reply of "stop" ends all messages on the topic.
- **An optional brief or a 30-minute briefing**, with no attendance list kept beyond a headcount.
- **The one-question feedback form**, with "I'd rather not answer" listed first.
- **An introduction only on request.** If a member's CEO asks in writing, the association first asks whether the company has already been in touch with SourceX or been offered an introduction, because only one partner can be credited and SourceX decides overlapping claims in duplicate review. Then it introduces that one company under its signed Channel Partner Agreement, and the CEO takes it from there.

Two routes stay open throughout. The decline route: "stop" is honored on every channel the association runs, and the member's name goes on a do-not-contact note, not into a report. The feedback route: complaints go to a named board member who has no stake in any reward, not to the staff member who runs the program.

What the association may say about fit is fixed before round one. It publishes SourceX's screen in plain words: a peak of at least 50 full-time employees (contractors excluded), several years of records the company created itself, the right to license them and a CEO who agrees to the discussion. 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. Members check themselves, for instance with the [company fit checker](/tools/company-fit-checker); whether the records suit a current program stays unknown until SourceX reviews them, and SourceX notes that a company outside one program may fit another later.

## Three rounds, read through the codes (Illustrative)

Illustrative. An invented association, invented members and invented counts.

| Round | Opted in | Replied | Codes received | Change made after the round |
|---|---|---|---|---|
| 1 | 12 | 9 | F1 3, F2 1, F4 2, F8 2, F9 1 | F4 first, because misreads outrank volume: the opening now names the association's partner role and says SourceX decides after review |
| 2 | 12 | 10 | F1 3, F5 1, F8 4, F9 1, F10 1 | F4 fell from 2 to 0, so the change was adopted; next, F1: the size test moved into the first line |
| 3 | 12 | 9 | F1 1, F5 2, F8 4, F9 2 | F1 fell from 3 to 1 and was adopted; F5 rose to 2, so the reminder was dropped for round four |

Three things in the log matter more than any count. The misread code disappeared after one wording change, which is the clearest gain in the pilot. Useful-but-not-for-us answers (F8) doubled from 2 to 4, and that is success: members who could not be candidates found out quickly and said so without complaint. And F9 never rose above two per round, which is the right expectation for an opt-in topic; the loop improves the notice, not the number of introductions. Each CEO who asked was introduced individually, after the earlier-contact question.

## Negative feedback first: complaints, misreads and silence

- **Complaints pause the loop.** Any complaint that the association pressed a member, or acted as if it could decide for one, stops the next round until the cause is fixed and the board member who handles complaints signs off.
- **Misreads outrank volume.** One member who thought the association was vouching for SourceX, or that attending meant acceptance, is a wording failure even if eleven others read it correctly.
- **Silence is not a code.** Members who do not reply are never counted as satisfied or opposed, and nobody follows up to find out why.
- **Small numbers stay small.** Report counts, not percentages, and never a breakdown that could identify a member.
- **Report the change log, not a funnel.** The board needs to know what changed and whether it worked. For measuring member benefit itself, a separate opt-in dashboard is described in [measuring a partner benefit without counting every member](/guides/how-to-measure-a-partner-benefit-without-counting-every-member), and a neutral way to survey members is in the [association member survey questions](/resources/association-member-survey-questions).

## Where this loop can mislead

- **Respondents choose themselves.** The members who reply are the most engaged ones, so a code that falls among them may not have fallen among everyone else who read the notice.
- **Codes flatten nuance.** A member's reply is reduced to one code by design. Read the free text once before deleting it, and revise the code list between rounds if several replies fit poorly.
- **One change per round is slow.** It is also the only way to know which change worked. Changing three things at once produces a better notice and no learning.
- **SourceX's criteria move.** SourceX applies each program's own requirements and can change them. Date every notice and reread the published screen before each round.
- **The association has a stake.** If it can earn a reward, whoever codes the replies has an interest in reading them kindly. A second reader without that interest should check a sample each round.
- **A feedback request can itself feel like pressure.** Ask once, make declining the first option, and never chase. Guidance on writing a no that costs nothing is in [making a referral ask easy to decline](/guides/how-to-make-a-referral-ask-easy-to-decline).

This loop concerns the association's own messages. It is unrelated to the human feedback records some companies hold, which SourceX describes on its page about [human-in-the-loop data](/proof/what-is-human-in-the-loop-data). More association guidance sits in the [industry associations overview](/for/industry-associations), the guide to [explaining the program to members](/guides/how-industry-associations-can-explain-a-company-referral-program-to-members), the [vendor endorsement policy question](/questions/association-endorsement-policy-vendor) and the [guides library](/guides).

## 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 round one, [register the association as a partner](/register) and sign the agreement, so a CEO who asks is never kept waiting; keep [who qualifies](/who-qualifies) as the only screen the notice repeats, and give the board the [program terms](/terms) version each round was written against.

## 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.ihi.org/library/model-for-improvement/testing-changes
- https://www.ihi.org/sites/default/files/QIToolkit_PDSAWorksheet.pdf
