Handle Employee Referrals Without Assuming Candidate Consent

Start here

Five rules for a safe first handoff

Start from an authenticated source event.
Keep working fields separate from the controlling record.
Send decisions and exceptions to the employer recruiting, privacy, HR, finance, legal, and hiring owners.
Use named access and the minimum necessary data.
Require recruiting records the candidate-authorized next step and the program owner separately records the referral and any later reward decision before closure.

Task map

Split admin work from owner decisions

Work lane	Philippines team	Company owner	Useful check
Open	Preserve the source, received time, case identity, due date, and assigned owner.	Confirm that the case belongs in this workflow and define the permitted task.	The original source remains retrievable
Prepare	Check the approved field list and identify missing or conflicting information without resolving it.	Answer exceptions and approve any consequential instruction.	Submitted, source, and approved values stay distinct
Route	Pause when candidate consent, source ownership, relationship, duplicate submission, reward eligibility, conflict, protected information, or selection treatment is unclear. Send one bounded question through the restricted channel.	Make the required decision and return a dated instruction.	The decision has a person, time, and source
Close	Apply only the approved administrative step and attach destination evidence.	Review the result and authorize closure.	recruiting records the candidate-authorized next step and the program owner separately records the referral and any later reward decision

Example pilot board

Use small numbers for the first review

1Source recordKeep the controlling evidence intact

5Test pathsRoutine, missing, conflict, sensitive, failed destination

18Pilot casesReview every early case

2Owner checksDecision and closeout

Minimize referral intake

A referral begins with an employee introduction but cannot manufacture candidate permission or selection priority. Design the intake form to collect only what recruiting may use before candidate contact. A referrer’s endorsement, personal history, protected information, or private résumé copy should not become an uncontrolled candidate record. For employee referral consent intake, record the source event, responsible owner, effective time, and present state in language that another reviewer can reconstruct. Use an employee uploads a former colleague’s résumé without asking them and requests a referral bonus before recruiting makes contact as a redacted tabletop case, then identify the first fact that prevents routine processing. That fact determines the handoff; queue age or convenience does not.

Turn this checkpoint into a working control by naming the permitted preparation, the evidence the coordinator may compare, and the decision reserved for the employer recruiting, privacy, HR, finance, legal, and hiring owners. The item must pause when candidate consent, source ownership, relationship, duplicate submission, reward eligibility, conflict, protected information, or selection treatment is unclear. Preserve both the observed value and the requested outcome, send a bounded question through the approved channel, and keep the next deadline visible. Completion requires that recruiting records the candidate-authorized next step and the program owner separately records the referral and any later reward decision; a sent reminder, updated spreadsheet, or successful login is not equivalent evidence.

Wait for candidate direction

A referral begins with an employee introduction but cannot manufacture candidate permission or selection priority. Record the introduction separately from the candidate’s response. The referral event can exist while the candidate is uncontacted, declines, requests deletion, chooses another channel, or authorizes a limited recruiting conversation. For employee referral consent intake, record the source event, responsible owner, effective time, and present state in language that another reviewer can reconstruct. Use an employee uploads a former colleague’s résumé without asking them and requests a referral bonus before recruiting makes contact as a redacted tabletop case, then identify the first fact that prevents routine processing. That fact determines the handoff; queue age or convenience does not.

Resolve source conflicts neutrally

A referral begins with an employee introduction but cannot manufacture candidate permission or selection priority. Resolve duplicate-source evidence without changing candidate treatment. Timestamps, prior applications, agency submissions, event lists, and employee referrals may affect internal ownership or rewards, not selection merit. For employee referral consent intake, record the source event, responsible owner, effective time, and present state in language that another reviewer can reconstruct. Use an employee uploads a former colleague’s résumé without asking them and requests a referral bonus before recruiting makes contact as a redacted tabletop case, then identify the first fact that prevents routine processing. That fact determines the handoff; queue age or convenience does not.

Administer rewards downstream

A referral begins with an employee introduction but cannot manufacture candidate permission or selection priority. Keep reward administration downstream. Eligibility conditions, exclusions, employment status, payment timing, tax handling, and disputes belong to the program and finance owners after the defined hiring event occurs. For employee referral consent intake, record the source event, responsible owner, effective time, and present state in language that another reviewer can reconstruct. Use an employee uploads a former colleague’s résumé without asking them and requests a referral bonus before recruiting makes contact as a redacted tabletop case, then identify the first fact that prevents routine processing. That fact determines the handoff; queue age or convenience does not.

Copy-ready scripts

Make the stop points easy to say

Owner escalation"I paused this employee referral consent intake item because candidate consent, source ownership, relationship, duplicate submission, reward eligibility, conflict, protected information, or selection treatment is unclear. The source and conflicting or missing fields remain unchanged. Please provide the controlling instruction and effective date."

Closeout check"Before closure, please confirm that recruiting records the candidate-authorized next step and the program owner separately records the referral and any later reward decision. I will keep the case pending until that evidence is attached or you approve another disposition."

Let candidates correct the record

A referral begins with an employee introduction but cannot manufacture candidate permission or selection priority. Give candidates a clean correction path. They should be able to clarify contact details, source, consent, and interest without asking the referring employee to edit recruiting records on their behalf. For employee referral consent intake, record the source event, responsible owner, effective time, and present state in language that another reviewer can reconstruct. Use an employee uploads a former colleague’s résumé without asking them and requests a referral bonus before recruiting makes contact as a redacted tabletop case, then identify the first fact that prevents routine processing. That fact determines the handoff; queue age or convenience does not.

Launch path

A five-step HR outsourcing workflow

01
Receive
Preserve the source, received time, case ID, owner, and deadline.
02
Check
Compare the approved field list without deciding conflicts.
03
Escalate
Send one bounded question to the authorized company owner.
04
Apply
Perform only the dated administrative instruction.
05
Verify
Confirm the destination, attach evidence, and complete owner review.

Measure responsible routing

A referral begins with an employee introduction but cannot manufacture candidate permission or selection priority. Measure the lane with consent and routing outcomes rather than referral volume alone. Useful checks include unauthorized uploads, duplicates, declined contact, wrong destinations, delayed acknowledgment, and unresolved program-owner decisions. For employee referral consent intake, record the source event, responsible owner, effective time, and present state in language that another reviewer can reconstruct. Use an employee uploads a former colleague’s résumé without asking them and requests a referral bonus before recruiting makes contact as a redacted tabletop case, then identify the first fact that prevents routine processing. That fact determines the handoff; queue age or convenience does not.

Buyer FAQ

HR outsourcing questions

Can an outsourced HR coordinator own employee referral consent intake?

The coordinator can own the documented administrative queue, completeness checks, reminders, and evidence collection. The company must retain legal, policy, employment, pay, benefits, safety, privacy, contract, and exception decisions.

What should be kept in the shared tracker?

Use a case ID, status, assigned owner, deadline, waiting reason, next action, and source link. Keep sensitive documents and narratives in the approved restricted system.

What happens when information conflicts?

Preserve both values and their sources, then route the decision to the employer recruiting, privacy, HR, finance, legal, and hiring owners. Do not overwrite one value to make the queue look complete.

What proves the task is complete?

Require this result: recruiting records the candidate-authorized next step and the program owner separately records the referral and any later reward decision. A sent email, reminder, or checked box does not by itself prove the authoritative destination changed.

How should the first month be reviewed?

Review every early case, classify defects, inspect access and messages, and revise the written boundary before increasing volume or reducing review.

Sources

Source notes

EEOC Recordkeeping RequirementsOfficial EEOC overview of employment recordkeeping requirements.
NIST Privacy FrameworkOfficial voluntary framework for managing privacy risk and accountable data processing.