A decline stings more when it arrives after a recommendation from a trusted body. The member heard about SourceX because the association mentioned it, perhaps in its newsletter or at an event, and a no can read as the association's judgment, or worse, as the association having spent the member's time for its own benefit. Most of what decides how that feels was written months earlier, in the first notice.
Why a decline lands on the association's desk
Three things make a member blame the messenger. The first is implied endorsement: if the notice sounded like a recommendation, the decline sounds like the association was wrong. The second is the incentive: a member who later learns the association could have been paid may wonder whose interest the notice served, which is why the newsletter disclosure guide puts the reward in the notice itself. The third is surprise: a member that expected a size check and got a no on something else feels misled.
SourceX's own pages give the association honest language for that third point. Its screening page calls itself screening guidance rather than an eligibility promise and says requirements follow SourceX's current data needs. Its process page says SourceX weighs ten fit signals, not just company size, and that qualifying does not guarantee an offer. A notice that says this plainly before anyone applies has already done most of the work this page describes.
What the association sees, and what stays with the member
What the association can know depends on how the member reached SourceX, and in neither case does it include the reasons for a decline. The terms say partners never receive access to applicant documents, and the partner agreement gives a partner only what it reasonably needs to follow its own referral, in generic stages or reference codes.
| How the member reached SourceX | What the association sees | What it does with it |
|---|---|---|
| The member applied on its own, with no partner | Nothing, unless the member tells it | Waits to be told; never asks members whether they applied |
| The association introduced the member as a registered partner | Generic stages or reference codes for that referral, never applicant documents | Treats any stage as the member's private business and acts on it only as the CEO asked at the yes |
| The member already had contact with SourceX before the association's introduction | That the introduction is not credited | Says nothing to the member about it: the member was not declined, the association simply earns no credit |
Four kinds of no, and one that is not a no
Members say "we were turned down" about very different events, and the association's reply should not depend on knowing which one. Still, the association's own staff should understand the difference, because the last row is a no only for the association.
| What happened | Where the outcome sits | What the association says if the member raises it |
|---|---|---|
| The member decided not to take part | With the member; it was its own choice | Thanks, and confirms the member will not hear about it again unless it asks |
| SourceX did not take the application forward after the fit check | Between SourceX and the company | The reply below, and the published reasons a referral can be declined |
| SourceX's review found a rights or program-fit problem | Between SourceX and the company | The same reply; the reasons a well-documented company can still be declined explain why paperwork alone does not decide |
| A deal did not close | SourceX's no-deal notice, to the company | The same reply; the association does not ask what was offered |
| The association's introduction was a duplicate | With the association alone, because nothing happened to the member | Nothing: the credit question is the association's, not the member's |
The member support response playbook
The playbook has six moments, and the first two happen before any decline exists. The reply lines below are written to be used as they are or adapted, and none of them asks the member for anything.
Complaint handling has its own published guidance. ISO 10002, in our paraphrase of ISO's description, covers complaints about an organization's products and services from planning through improvement, for organizations of any type or size, and leaves out disputes referred outside the organization. The line is a useful one here: a complaint about how the association described the program is the association's to handle and learn from; a disagreement with SourceX's decision belongs to the member and SourceX.
- When a member reports a decline. "Thank you for telling us. The decision and its reasons are between you and SourceX, and we will not pass this on. If anything we said about the program set the wrong expectation, we would like to hear it."
- When a member asks the association to intervene. "We cannot speak for your company or ask SourceX to revisit an application. If you want to pursue it, your CEO can contact SourceX directly."
- When a member is angry with the association. "You heard about this from us, so your view of how we described it matters. Here is how to tell us, and here is who reads it."
- When a member asks whether it will be eligible next time. "SourceX says a company that does not fit one program may fit another later. We cannot predict whether that applies to you."
| Moment | The association does | The association never does | What it records |
|---|---|---|---|
| Before any notice | States that it cannot say who qualifies, that SourceX reviews and each member's CEO decides, that a no can come at several stages, and whether it could be paid | Calls members good candidates, lists sectors as likely fits or calls SourceX its partner without written authorization | The approved notice text and date |
| At a CEO's yes, if the association introduces | Asks how the CEO wants to hear from it after the introduction: never, only if the CEO raises it, or a single check-in | Promises progress, or tells the member a signature or an estimate makes a deal certain | The CEO's dated yes and stated contact preference |
| When a member asks "are we a fit?" | Points to the published screening page and the company's own application | Gives a yes, a likely or a probably | Nothing about the member |
| When a member reports a decline | Sends one reply, keeps it private, offers the feedback route | Asks for the reason, contacts SourceX, compares the member with others | That a reply was sent, with no reason attached |
| When a partner stage changes | Follows the contact preference the CEO gave at the yes | Reaches out first when the CEO asked not to be contacted | Nothing beyond the stage itself |
| When reporting to the board | Counts notices sent, replies, complaints and opt-outs | Names members, applicants or declines | Totals only |
An education path for members who never apply
Some members will want to understand the idea without applying, and a short education session serves them without creating a single decline. It explains what SourceX looks for in its own published words, that a no can come at the fit check, in review or at closing, that the member's CEO decides, and that the association does not see outcomes. It sells nothing and collects nothing. The member education brief gives the association a sentence-by-sentence source map for that session, and the member list guide keeps the invitation itself opt-in.
A small pilot with a decline route and a feedback route
Start with members who ask to hear more, not with the whole roster. Give every message two exits: a one-line way to stop hearing about the program, and a feedback route that goes to a named person at the association and can be used anonymously. After 90 days, read four numbers: complaints about how the association described the program, members who used the stop line, members who said the information helped whatever the outcome, and members who would want the association to keep offering it. A pilot where declined members still say the association was straight with them is working; a pilot where they feel steered is not, whatever the number of introductions. SourceX has not published acceptance or decline rates, and none are given here; the pilot's numbers are the association's own.
If the association is a registered partner, it signs the SourceX Channel Partner Agreement before introducing anyone. Any reward is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, paid by SourceX separately, with nothing taken from the member's compensation.
Where the playbook can still fail
- The first notice was already written. If earlier messages implied that members would qualify, the playbook cannot undo it. Send a corrected notice before the next one.
- Silence can feel like indifference. A member that hears nothing after a decline may decide the association did not care. The contact preference asked at the yes is the guard against that.
- Small networks talk. In a tight trade community, members compare notes. The association cannot stop that, but it can make sure none of the information came from its own staff.
- The incentive shadow. Even a disclosed reward can make a declined member wonder. An association that never registers, leaving members to apply on their own, removes the question; whether a registered partner can turn its reward down is not settled in the published terms and goes to SourceX in writing.
- Program changes. SourceX's criteria follow its current programs, so a reply that was accurate last quarter may need rechecking against the screening page.
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 the association's next notice goes out, register if it will introduce members, quote the screening facts on who qualifies rather than paraphrasing a promise, and keep the program terms beside the response playbook.