# Employee referral program: launch decisions

Metix AI editorial worksheet. Replace every bracket with a company-approved decision before sharing an invitation. This is a workflow draft, not an adopted employment policy. No account is needed to use it.

## One program version

- Program owner and backup: [names or team routes]
- Approved version and effective date: [version, date]
- Who approves changes and records exceptions: [owner and decision record]
- Roles included, status and hiring brief version: [role IDs and brief links]
- Where employees see the current role list: [company-owned location]
- Participating groups and any exclusions/conflicts: [company-approved rules]
- Accepted referral channel and minimum information: [form or responsible contact]
- How the candidate's permission to share details/contact is confirmed: [actual process and owner]
- What happens when a role closes or the candidate prefers another role: [owner and next step]

## Handoff and access

- Who receives each submission: [owner and backup]
- Acknowledgement target chosen by the company: [target and calendar/timezone]
- Where the next follow-up date is recorded: [system and field]
- What the employee may see: [approved status only]
- What remains in restricted hiring records: [assessment notes and other restricted material]
- Who corrects an identity match or submitted detail: [authorized contact]
- Record access, retention and deletion responsibility: [actual company process]
- Hiring criteria and evidence used for every candidate: [brief/assessment version]

## Decisions to resolve before incentives are announced

- Is there an incentive? [yes/no; approved details]
- Reward type, amount/currency, eligibility and qualifying event: [approved terms]
- Payment conditions, timing, payroll owner and required reviews: [approved terms]
- Existing candidate/application rule and any lookback period: [approved rule]
- Same candidate, same role, two referrers: [approved rule; adjudicator]
- Same candidate, another role or later reopening: [approved rule; adjudicator]
- Ties, incomplete submissions, withdrawn candidates and disputed records: [decision route]
- Referrer changes role or leaves before a qualifying event: [approved rule]
- Which policy version applies when the program changes: [transition rule]
- How employees receive the final terms and corrections: [communication owner]

Leave unresolved items visibly pending. A timestamp, a software source label or the earliest row does not approve a reward. Do not announce a payment or eligibility promise that the responsible company reviewers have not approved.

## Internal announcement to adapt

We are inviting referrals for [approved roles and brief links]. Please use [submission channel] and confirm [the company's permission-to-share process] before sharing anyone's details. Include [minimum role-related information]. [Owner] will acknowledge receipt under [company target] and record the next check. The approved program terms are [version/location]; questions and disputed submissions go to [decision owner]. Please avoid circulating candidates' private information in group channels.

## Receipt to adapt

We received submission [ID] for [role]. [Owner] will check [the next task] by [date/timezone]. This message confirms receipt. Any referral eligibility or reward decision follows [approved policy version] and is handled by [decision owner]. We can share [approved status]; hiring assessment notes remain in the appropriate restricted record.

## Review the first handoff

Test a normal submission, two referrers for the same person and role, a different role for the same person, a candidate already in the record system, missing or declined permission, a missing owner and a missed follow-up. Confirm who sees each message and who records the decision. Keep the original submissions and link corrections instead of silently overwriting them.