Referral Program Template

The referral reward is easy to announce; the earning event needs more thought

A referral program needs an earning event that participants and the office can both recognize. Start with who may refer, what makes an introduction eligible and the point at which the reward is earned. “Refer a friend and get paid” hides decisions the team will eventually have to make about existing leads, duplicate introductions and incomplete jobs.

Use the economics field to examine the proposed reward in the context of the work, while keeping the payment process tied to actual records. A reward triggered by a completed, paid job needs a different verification step from one triggered by an accepted introduction. Do not let the referral announcement wording settle that policy accidentally.

Test the awkward referrals before opening the program

Use three hypothetical cases: two participants introduce the same person, an introduction is already in the pipeline, and an eligible job is cancelled before the stated earning event. The program owner needs an approved rule for each case. If the rule is unclear, the office will be asked to improvise after participants believe they have earned something.

Describe what evidence starts eligibility and what evidence triggers payment. An introduction date, a permitted contact record and a completed paid job are different checkpoints. The reward should follow the program’s actual earning event rather than whichever record is easiest to find.

Give each referral one traceable status

Consider a fictional reward earned after an eligible job is completed and paid. The office first records the introduction and checks eligibility. Completion and collection are later checkpoints, followed by the approved reward payment. Use distinct states for those events so a participant can receive an accurate update and the same introduction does not enter two payment lists.

If the customer cancels before the earning event, apply the approved rule and record the reason. If participants dispute who introduced the customer first, route the actual records to the decision owner through an internal escalation brief. The generator can organize the rule discussion; it cannot settle an ownership dispute without the underlying evidence.

Design administration and announcement together

The office needs enough detail to apply the rules consistently; participants need a short explanation they can understand. Write the operating terms first, then derive the announcement without losing a material condition. If administrators cannot explain a condition plainly, it may need clarification before launch. Track disputed or incomplete referrals separately from payable ones so a count of submissions is not mistaken for a payment obligation. The template helps surface those decisions; the program owner still approves the rules.

Calculate what the reward leaves, not just what it costs

Consider an illustrative job with $1,500 contribution after the direct costs already counted. A proposed $100 referral reward leaves $1,400 before any additional program administration, payment costs or overhead not included in that contribution figure. The reward consumes about 6.7% of the stated contribution. That arithmetic does not establish profit, affordability or a sensible program cap; the missing costs and expected qualifying-job count still matter.

A $100 credit and a $100 cash payment also have different operating implications. A repeat-service business may apply a credit to a later invoice. A roofing customer may not have another invoice soon. Decide whether the reward fits the customer's likely relationship with the company, and write down any expiry or redemption rules before promoting it. The tool organizes your supplied economics; it does not know your actual job margins.

Keep booking, earning and payment separate

Jobber’s referral product illustrates a program that rewards a customer when a referred person books work. That is one possible trigger. If your own proposed program requires completion and collection, a booking has not earned the reward. Staff should be able to point to the approved event rather than importing the trigger from a software default or an advertisement.

Use five distinct ledger stages: submitted, qualified, earned, approved for payment and paid. A cancelled job can stay in the record with its reason and outcome; it should not disappear and later be submitted again as if new. Compare the paid list with the approved list before the next payment run, using the referral ID to detect duplicates.

Reward an introduction without buying a review

A referral program and an online-review campaign have different purposes. Never make the referral reward depend on a positive Google review. Google prohibits review incentives; the FTC’s endorsement guidance also explains when a material connection behind a recommendation needs clear disclosure. Have the responsible reviewer check your actual referral source, terms and jurisdiction before launch, especially for business partners. A planning worksheet is not approval for a professional referral fee.