Employee Referral Apps: Which Recruitment Milestones Earn Recognition?

An employee referral feature should explain which recruitment milestones earn recognition without turning the referring employee into an interviewer or exposing private hiring notes. Decide who gets credit for an introduction, which events count and what the employee may see. A candidate moving along the pipeline is not the same as a reward being available.

This guide is for teams specifying an internal referral app. Reward eligibility, employment terms, tax treatment and candidate privacy require the responsible advisers; the software should implement an approved programme rather than invent one.

Attach the introduction to a specific application

Start with a fictional example: an employee introduces a designer, who applies for two different roles. Is credit attached to the person, each application or only the role for which the introduction was accepted? Write that rule before adding a referral link.

Also decide what happens when two employees introduce the same person or the applicant was already in the recruitment system. A timestamp can supply evidence, but it does not settle your policy. Give a responsible recruiter a review route and preserve the reason for any correction. Do not silently replace the original referrer when an applicant's record is edited.

The Odoo 19 referral points guide shows a concrete product example: referral cards identify the applicant, application title, job position, recruiter and earned points. Use that as a prompt to define the relationship your app must preserve, not proof that the provider resolves every attribution dispute.

Award milestones, not repeated movements

Odoo assigns referral points to recruitment stages, and documents the same earning structure across job positions. That is its product model. Your programme may need different eligibility, but differences should be explicit rather than hidden in a stage name.

Specify which event qualifies: first entry into an interview stage, a completed interview or another approved milestone. These are different requirements. If an application moves backwards and then forwards again, should it earn the milestone twice? Usually the brief should require a single recognisable award for the agreed application and milestone, with separately authorised corrections. That is a recommendation to implement and test, not a guarantee supplied by a progress bar.

A renamed or removed recruitment stage also needs a migration decision. Avoid rewriting historical recognition merely because the team reorganises its pipeline. Show the rule used when recognition was recorded and explain later adjustments.

Give the referrer useful but limited visibility

An employee may need to know that an introduction is still active without seeing interview comments, salary discussions or another applicant's details. Define the referrer view separately from the recruiter view. Do not copy the full applicant screen and hide a few buttons.

Odoo's documented referral card includes recruitment context and points. Its existence does not establish the right privacy policy for your organisation. Choose appropriate status labels with HR and privacy reviewers, and test direct record links, notifications and exports as well as the dashboard. A person who stops being an eligible referrer should not retain access simply because an old link still works.

Explain earned recognition and available rewards separately

The Odoo dashboard distinguishes total points earned from points available to spend. In your brief, decide what those labels mean and whether a reward requires review. Do not label an in-progress introduction as a hired candidate, or an earned milestone as money already paid.

Keep this decision separate from building a shop-style loyalty wallet. The important referral questions are why this employee receives credit, what hiring milestone supports it and what recruitment information is disclosed. Redemption mechanics can be scoped later if your approved programme actually needs them.

Demonstrate the programme before accepting it

Use synthetic employees and applicants in your acceptance tests. Include two referrals for one person, two vacancies, an existing applicant, a repeated stage, a revised stage structure and an employee who loses access. Inspect both the recruiter's explanation and the employee's restricted view.

Bring a written referral policy to a discussion about an internal business app. A successful demonstration should explain one person's recognition from the introduction and milestone history without revealing material they are not authorised to read.