Referral eligibility and qualification

Eligibility rules should tell a referrer, before submission, whether the person and referral can enter the program. Qualification decides whether the submission is useful, while the reward rule identifies the later event that earns payment or recognition. Keep the decisions separate so a complete referral is not confused with a successful outcome. Reward design should trigger the act of referring, while the qualification gate protects the program from weak submissions.¹ The strongest rule is one a reviewer can apply from the record without guessing.

Set the eligibility boundary

Start with the people and situations your program accepts. Write this boundary before deciding how to score a referral or release a reward.

Choose the eligible referrer group explicitly. Referral programs have been run exclusively for employees' friends and family, valued customers, or successful referrers.² State whether the referred person may already be known to you, whether a previous referral blocks entry, and whether the referrer must make an introduction.

Exclude anyone who has already used someone else's referral code or earned a referral reward. Also exclude a sign-up made through a link or code shared by someone else.^{3, 4} If your program has a reward cap, publish the threshold plainly. One referral rule requires the referrer to have earned fewer than 100 referral rewards.⁵

Ask these questions before accepting a submission:

• Who may refer?
• Who may be referred?
• What previous action makes the person ineligible?
• Does the referral need to be new to the program, new to the company, or both?
• What must the referrer do beyond sending a name?

Put the answers in the public rules and the form. Referrers should be able to screen their own submissions without asking your team to interpret an unwritten exception.

Define a valid referral

Eligibility sets who may enter. Validity checks whether the submission has enough information for review and meets every required condition.

A referral is eligible only when it meets all listed criteria.⁶ Write each condition as a checkable field or decision, so the reviewer can mark what failed instead of rejecting a vague submission.

Build the form around identity, need, and scope. In a treatment referral, the record includes the person's name, symptoms or diagnosis, and the number of treatment services requested.^{7, 8, 9} The same structure works for a commercial referral: identify the person, describe the problem or need, and state what kind of help or conversation is requested.

Describe fit in terms a referrer can recognize. Good referrals have been described as high quality, a good fit, and clients the business enjoys working with.^{10, 11} Give referral sources that description before they submit. Clearer information about what counts as a good referral helps them make better referrals.¹²

Use a short intake checklist:

• Is the person identifiable?
• Is there a stated need or reason for the referral?
• Is the requested next step clear?
• Does the submission match the published fit rules?
• Has the referrer supplied the action your rules require?

Send the submission to qualification only when the record answers those questions. If a missing field prevents a decision, return it for completion and record what is missing.

Run the qualification check

Qualification begins after the form passes the entry rules. Give the reviewer a defined decision, a routing path, and a place to record the result.

The team receiving the referrals should own the criteria. Each receiving unit is responsible for defining its criteria for screening and routing productive referrals.¹³ That owner decides what counts as sufficient fit, who receives the referral, and what happens when a submission falls outside the criteria.

Use a named reviewer to assess potential and record whether the referral was selected.¹⁴ Have the reviewer read the structured selections and written explanation together. One referral process specifically requires reviewing the checkbox and narrative sections together to avoid destroying valid referrals.¹⁵

If qualification depends on cooperation after the introduction, include that obligation in the rule. One agreement requires the qualified referral customer to reasonably support sales efforts when requested.¹⁶ Define what cooperation means in your process, such as responding to the introduction or taking part in the agreed next step.

When the reviewer cannot decide from the record, use an escalation path. In a clinical eligibility process, the treating professional is directed to contact the referring practitioner when unsure.¹⁷ Your equivalent should name a person or team, set a response expectation, and record the decision. Uncertainty should not become automatic approval or an invisible rejection.

Choose the reward trigger

After qualification, define the event that makes the reward due. The trigger should be visible in the record and separate from the submission date.

Choose the event according to the behavior you want to encourage. Referral commission programs may attach additional bonuses to scheduling a discovery call, completing a demo, or converting a lead to a deal.¹⁸ Each event creates a different qualification burden, so state which event counts and who verifies it.

If revenue is the trigger, define the commercial artifact and the time window. One referral agreement defines referral revenue around revenue collected from a customer that signs a binding agreement or purchase order within one year of the referral submission.¹⁹ If hiring is the outcome, successful referral status can require an accepted offer, cleared onboarding, and a start in the new role.²⁰

Keep preapproval and outcome rules separate when both apply. A referral fee arrangement may require the company to pre-approve the potential client,²¹ and the partner may qualify for a fee only when a specified scenario occurs.²² Put each gate in the rules, then record the approval and later event independently.

The reward record should show what was submitted, when it became qualified, which trigger was selected, what evidence shows that the trigger occurred, and who approved the reward. If any part is missing, hold the reward decision until the record is complete.

Review exceptions and close the loop

A referral program needs an exception path for edge cases and a record of what happened after intake. Timing, duplicate submissions, or validation status can complicate the normal path.

Create an exception path for referrals whose registration is still in progress or whose validation team has already made a decision.²³ State who may request the exception, what can be changed, and whether the original submission date stays attached to the record.

Record the outcome after review: selected, declined, returned for information, or routed elsewhere. This distinguishes a weak referral from one that was never reviewed and protects both the referrer and the receiving team.

Review the rules when recurring edge cases appear. A policy can begin as a pilot and return for revisions after lessons are learned.^{24, 25} Keep the active rule version attached to each referral so a later change does not rewrite an earlier eligibility decision.

What not to do

Use these checks to keep the operating process consistent.

• Review the narrative with the checkbox; a checkbox alone is not enough.¹⁵
• Require every listed condition before calling a submission qualified.⁶
• Exclude anyone who has already used another referral path or earned a referral reward.³
• Reject a second claim on a sign-up when someone else supplied the referral link or code.⁴
• Give referrers clear guidance about what a good referral looks like, because clearer guidance improves the referrals they make.¹²
• Release a reward only after recording the agreement, onboarding event, call, demo, deal, or other written trigger that makes it due.^{19, 20, 18}
• Escalate an ambiguous case to the referring practitioner or the equivalent escalation owner.¹⁷