Employee referral program template: policy, bonus tiers and rules

An employee referral program template is the written policy that governs how a company pays and administers referral bonuses: who is eligible to refer, which roles qualify, how and when the bonus is paid, and what disqualifies a referral. Without this written down, referral bonuses become a source of disputes — a bonus paid to one employee and not another for what looks like the same kind of referral erodes trust in the program faster than a slow one ever could.

This is the program's policy document, distinct from the emails that actually ask employees to refer people — see referral request email templates for those. Write the policy first; the asks work better once employees know exactly what they are being asked to do and what they get for it.

A policy also protects recruiting from the awkward position of making case-by-case calls under pressure. Without one written down, every disputed referral becomes a negotiation, and the outcome tends to depend on how insistent the employee is rather than on a consistent rule. A one-page policy that new hires see during orientation, and that recruiting can point to without apology, removes most of that friction before it starts.

What the policy has to settle

• Eligibility to refer. Which employees can participate — usually everyone except recruiting/HR staff and, sometimes, the hiring manager for that specific role.
• Eligible roles. All open roles, or only certain levels or departments where the company most needs sourcing help.
• What counts as a valid referral. Submitted before the candidate applies elsewhere in the pipeline, through the official process, with the referrer's name attached.
• Bonus amount and tiers. A flat amount, or one that varies by role difficulty or level.
• Payout timing. Split across the start date and a retention milestone, or paid in full at one point.
• Disqualifying conditions. A candidate already in the pipeline, a rehire situation, or a referral submitted after an offer is already out.

The employee referral program policy template

[Company name] Employee Referral Program

Purpose
We pay a bonus to employees who refer candidates we hire. This program
rewards employees for helping us find great people, not for sourcing on
our behalf as an alternative to recruiting.

Who can refer
All full-time employees, except staff on the recruiting/HR team and
[hiring managers for roles they are directly hiring for, unless they were
not the sole decision-maker].

Eligible roles
[All open roles / roles at level X and below / roles open more than
30 days], posted at [internal careers page link].

How to submit a referral
Submit through [system/form] before the candidate applies on their own.
Referrals submitted after a candidate is already in our pipeline do not
qualify.

Bonus amounts
- [Role tier 1]: $[amount]
- [Role tier 2]: $[amount]
- [Role tier 3, e.g. hard-to-fill or senior]: $[amount]

Payout timing
- $[amount 1] when the referred candidate starts
- $[amount 2] after they complete [X days/months] of employment

Disqualifying conditions
- The candidate was already in our pipeline before the referral
- The referral is a rehire within [X months] of leaving
- The referred candidate does not accept an offer or does not start

Questions
Contact [name/team] with any questions about a specific referral.

A filled example: bonus tiers

An invented company's tier structure, written the way a usable policy reads:

A tiered structure like this rewards the referrals that are genuinely harder to source, rather than paying the same amount whether the role had 200 applicants or two. It also gives recruiting a lever: flagging a stuck role as hard-to-fill for a quarter can meaningfully increase referral volume on exactly the roles where it is needed most.

Payout timing: the arithmetic to check

A worked example with invented numbers. A $2,000 bonus split 40/60 across start date and a 90-day milestone pays $800 on the referred employee's first day and $1,200 after they complete 90 days. If the referred employee leaves in week six, the referrer keeps the $800 already paid and does not receive the remaining $1,200 — a structure that protects the company from paying a full bonus on a hire that did not last, without clawing back money an employee has already spent or budgeted.

Policy gaps that cause disputes

Fairness: referrals alongside other channels

A referral-heavy pipeline tends to reflect the makeup of the current workforce, since employees mostly know people like themselves. That is a reasonable thing for a recruiting leader to watch, not because referrals are a problem on their own, but because a program that becomes the dominant source of hires can quietly narrow who applies over time. Keep referrals as one channel among several rather than the default, track the demographic mix of the referred pool against other sourcing channels if your company already tracks that data for other purposes, and make sure every referred candidate goes through the same evaluation bar as anyone else — the earlier section on disqualifying conditions and equal evaluation exists partly for this reason.

Measuring whether the program is worth its budget

Track cost per hire through the referral channel against your other channels, and track retention separately, since a cheaper hire who leaves within a year is not actually cheaper. A worked example with invented numbers: a company pays $2,000 average per referral bonus and fills 25 roles through the program in a year, a total of $50,000 in bonuses. If those same 25 roles would have cost $6,000 each on average through agency or paid sourcing channels, the program saved roughly $100,000 that year before accounting for recruiter time saved on sourcing. Run the same comparison on retention: if referred hires stay meaningfully longer on average than hires from other channels, that is a second return the raw cost-per-hire number does not show on its own.

Administering the program without becoming a bottleneck

Track every referral in one place — most ATS platforms have a native referral field — rather than in side spreadsheets that different recruiters maintain differently. Confirm eligibility and payout status at each pipeline stage change, not just at hire, so an employee who asks "is my referral still active" gets an answer in minutes rather than requiring someone to reconstruct the history. Route the actual bonus payment through payroll on a fixed schedule (monthly is common) rather than ad hoc, so referrers are not chasing recruiting for a payment that was supposed to happen automatically.

Promoting the program without nagging

A referral program that only gets mentioned once, at new-hire orientation, fades from memory within a quarter. Keep it visible with a short reminder tied to specific open roles — "we're hiring for X, here's the bonus" — rather than a generic "don't forget to refer" message that arrives with no role attached. Recognize referrers publicly when a referral results in a hire, with their permission, since visible proof that the program pays out is more persuasive to the rest of the company than the policy document itself.

Updating the policy without confusing employees

Bonus amounts and eligible roles will need to change as headcount and budget change; do not treat the policy as fixed once published. When you update it, apply the new terms to referrals submitted after the change date and honor the old terms for anything already in the pipeline — changing the deal on an employee mid-referral is the fastest way to make people stop trusting the program's next update. State the effective date on every version, keep a dated changelog even if it is just a short internal note, and tell employees directly when a change affects the bonus amount rather than only updating a page on the intranet and assuming they will notice. A program that quietly changes its terms tends to get talked about far more than one that announces the change plainly, and not in a way that helps the next round of referrals.