An employee referral program works best when employees can understand it in a few minutes and recruiters can administer it without detective work. I build the program around clear ownership, a simple submission form, consistent status updates, and written reward rules. A referral is not a promise to interview or hire someone. It is a useful introduction that still needs the same fair selection process as any other candidate.
Policy template
I start with a one-page policy that answers these questions:
- Who can refer: Define whether full-time employees, part-time employees, contractors, interns, and former employees are eligible.
- Who cannot receive a reward: Common exclusions include recruiters working on the role, hiring managers for their own openings, and anyone involved in approving the hire. Confirm these rules with HR and payroll.
- What counts as a referral: Require the employee to submit the candidate before the company has an active application or documented contact.
- Which roles qualify: List eligible departments, employment types, locations, and any roles excluded from the reward.
- When the reward is earned: State whether payment follows the start date, a retention milestone, or another approved condition.
- How conflicts are handled: Explain what happens when two employees refer the same candidate and who decides ownership.
I include a sentence that referrals are reviewed against the same job-related criteria as all applicants. That protects the candidate experience and keeps the program from becoming a private hiring lane.
Referral form template
The form should collect enough context to start a review without asking the employee to perform a recruiter screen. My standard fields are:
Referrer: name, work email, department, manager, and relationship to the candidate.
Candidate: full name, personal email, phone number if the candidate has agreed to share it, resume or profile link, location, work authorization details when relevant to the role, and preferred contact method.
Role fit: target role, relevant skills, recent experience, reason the employee believes the candidate may be interested, and whether the candidate has consented to be contacted.
Administration: submission date, source, owner, duplicate check, candidate record ID, and employee acknowledgment of the policy.
Tracker fields and workflow
I use one row per referral and keep the status vocabulary small: Submitted, Duplicate, Contacted, Screened, Interviewing, Offer, Hired, Not selected, Withdrawn, and Reward paid. The tracker also has columns for role, referrer, recruiter, referral date, candidate ID, last action date, next action, hire date, milestone date, payout date, reward amount, and exception notes.
The workflow is straightforward. I review new submissions, check for an existing candidate record, confirm consent, assign the recruiter, and send the referrer a receipt. The recruiter owns candidate communication. Payroll or HR owns payment approval. I reconcile hires and milestone dates monthly so rewards do not depend on an employee asking for an update.
Announcement email template
Subject: Help us meet our next [Role] teammate
Hi team,
We are hiring for [role names or link to open roles]. If you know someone who may be a strong fit, submit the referral here: [form link]. Please include the candidate's contact details only with their permission.
Eligible referrals follow the attached program rules. A reward of [amount or reward description] is paid after [approved condition]. If more than one employee refers the same person, the first complete submission in our tracker determines ownership.
Thank you for helping us meet thoughtful candidates. Questions can go to [contact].
Best, [Program owner]
Operating rules I keep visible
I publish the policy, form link, status definitions, and payment timeline in the same place. I review whether the program is reaching different teams and locations rather than relying on the loudest internal networks. I also give referrers a status update without exposing private candidate information.
The program should make a good introduction easier, not make hiring less consistent. Clear rules, prompt acknowledgment, and dependable tracking are the foundation.