The model allows $5,000 per hire. An employee referral bonus has to fit alongside the hiring work you still need to do. Set the total from that cost comparison, publish its payment conditions before accepting referrals, and use the same hiring standard for referred candidates.
I'd pay the agreed reward in two parts, with a defined start milestone and a later employment milestone. Set both before launch. The referrer introduces a candidate; the hiring manager remains responsible for deciding whether to hire them.
Work Out What the Referral Actually Replaces
The model's $5,000 is an all-in hiring assumption, not an agency invoice. It includes job-board spending and a recruiter share, alongside lost time during onboarding. A referral doesn't remove every part of that work.
Estimate the cost you still expect to incur through the referral route. Include the assessment work and the onboarding time that remain. Then ask payroll for the employer cost of the proposed reward so the comparison isn't limited to the cash amount printed in the announcement.
Use this calculation before choosing the payment:
| Budget Item | What to Enter |
|---|---|
| Comparison cost | The model uses $5,000 per hire; also check your own comparable hiring records |
| Remaining hiring cost | The actual recruiting and onboarding work still needed for a referred hire |
| Total reward cost | The promised bonus plus any associated employer payroll cost |
| Referral-route total | Remaining hiring cost plus total reward cost |
| Difference | Comparison cost less referral-route total |
If you use $5,000 as the comparison, subtract the remaining hiring cost to find the room for the total reward cost. Don't spend the whole difference automatically. Set an amount the owner is willing to fund, and check whether the resulting route remains worthwhile.
That method gives you a budget ceiling from your own costs. It doesn't establish an optimal bonus that will motivate every technician. If there's no room within the comparison, make the extra spending an explicit choice rather than calling the referral cheaper.
Put the Payment Conditions in Writing
Make the reward understandable before someone introduces a candidate. A proposed announcement is: 'For eligible referrals to [named role], we will pay a total gross bonus of [amount]. The first payment is [amount] when [defined start condition] is met. The remaining [amount] is paid when [defined employment milestone] is met.'
Choose the later milestone to match the period your manager needs to assess the hire in the role. Publish an actual date rule or service period, not 'when we're happy.' The model doesn't set a universal referral waiting period, so don't borrow one as though it were a measure of readiness.
Have the person responsible for employment policy check the conditions before launch. Specify what happens if either employee leaves before an unpaid installment becomes due. Don't introduce that condition after the referral has been accepted or assume a generic policy settles the rules for your jurisdiction.
Have payroll determine the treatment of the payment. State the promised gross amount rather than implying that the employee will receive that figure after withholding.
A bonus policy that requires oral history is going to be expensive to explain.
Define an Eligible Introduction
Give employees the role description and its accepted pay range. Explain the work the candidate would need to perform so the referral isn't based only on knowing somebody with an IT job. Ask the candidate's permission before their details are passed into the hiring process.
Record the introduction with its date and the referring employee. Define how you handle a candidate already in the hiring process, and competing referrals for the same person. Resolve that record before the appointment starts rather than after the bonus reaches payroll.
I'd exclude people making the hiring decision from receiving the referral reward for that decision. Put the chosen eligibility rules in the written policy so managers don't improvise exceptions for a colleague. Keep the referring employee informed about the process without sharing private interview notes.
I don't buy 'turn every tech into a talent acquisition engine.' Give people a real vacancy to introduce someone to, then let the hiring manager do the hiring. Another job title won't make the desk's workload disappear.
Keep the Selection Standard the Same
A recommendation from a colleague is a source of candidates. It isn't a substitute for evidence that the person can do the role. Use the same assessment criteria you would use for a candidate from another route, and record the evidence before comparing impressions.
Don't make the reward depend on the referrer supervising the hire. That can blur the buddy assignment and the hiring manager's accountability. If a referred hire needs training, plan and cost it rather than treating the introduction as proof that the training won't be necessary.
The MSP model assumes 20% annual staff turnover for planning. That isn't evidence that your staff will leave at that rate or that a bonus will reduce it. Keep actual departures and reasons separate from the referral count when reviewing the program.
Healthy margins support paying good people well under the model's position. A referral scheme can't repair an offer people won't accept or a job your current staff struggle to sustain. Check those conditions before increasing the reward to compensate for them.
Give Each Administrative Step an Owner
Use a checklist the manager can complete without reconstructing the promise. Keep it with the hiring record and limit access to the people who need it.
- Owner: approves the reward budget and the policy before referrals open.
- Hiring manager: confirms the open role and the consistent selection criteria.
- Hiring administrator: records the eligible introduction and acknowledges it to the referrer.
- Hiring manager: confirms the start milestone against the published condition.
- Payroll owner: checks the approved payment and processes the first installment.
- Hiring manager: confirms the later employment milestone and records the evidence.
- Payroll owner: processes the remaining installment and updates the reward record.
Ask what this does to the board on Monday morning. The assessment work still needs time, and the eventual hire still needs support. If the proposal counts an extra technician's output before you've planned those commitments, revise the capacity plan.
Review Completed Hires and Actual Cost
Count eligible referrals separately from appointments and hires. Record the cost of each completed hire, including the reward already paid and the later installment still committed. An unpaid installment doesn't become a saving just because it falls after the current reporting date.
Compare the route with other hires for the same kind of role, using a consistent cost basis. Review performance through the manager's ordinary records and track continued employment over comparable periods. A small group of referred hires won't establish that the program caused better retention.
Keep the program if it produces candidates you can assess fairly at a cost you accept. Change the amount or conditions prospectively when the records justify it, and preserve promises already made. Before inviting referrals, approve the budget and give payroll the written milestones it will have to honor.
mspoutpost.com/articles/employee-referral-bonus-set-the-cost-and-payment-rules
Written by Megan Friesen
MSP Outpost publishes information, not legal, financial, insurance, tax or compliance advice, and reading it creates no professional relationship. For decisions about your business, talk to a qualified professional.