How to Write a Reference Check Policy (Free Template)

Most teams run references from a recruiter’s inbox and call it policy. That habit breaks the first time two managers use different questions, a referee complains, or a candidate asks who saw the notes. A written reference check policy template gives hiring managers one standard: who you contact, what you ask, when you start, and how long you keep the file.

This guide shows how to write a company reference check policy, convert it into a reference check SOP people actually follow, and copy a free template you can paste into your handbook. Pair it with practical habits hiring managers can apply on the next file and the intake-to-archive sequence for a single check.

Why you need a written policy, not a shared email

Unwritten rules live in the person who “usually does references.” When that person is on leave, the process improvises. Improvisation is how questions drift into family status, how consent is skipped, and how an offer goes out on one glowing peer note.

A Chicago warehouse team that let each supervisor phone “someone who knows them” produced files that could not be compared. A Leeds product team that froze a short template for the requisition could explain every decline with job-related notes. The difference was not software. It was a policy people could open.

Write the policy for the roles you actually hire. An executive search firm and a 20-person clinic need the same building blocks, with different referee counts and approval paths.

What a company reference check policy must include

Every company reference check policy should name these items in plain language:

1. Purpose. What decision the check supports (hire, promotion, contractor conversion).
2. Scope. Which roles require a check, and which exceptions exist.
3. Consent. Written candidate permission before contact, plus what you tell them you will ask.
4. Referee rules. Who counts (former managers preferred), how many, and when peers or clients are allowed.
5. Questions. A versioned library tied to job duties. No protected-class probes.
6. Timing. Start while final interviews run. No signed offer until the defined minimum is complete.
7. Verification. Confirm employer, title, and a sane contact path before you treat praise as evidence.
8. Records. Where notes live, who can open them, and how long you keep them.
9. Escalation. What happens on a negative reference, a fake-contact flag, or an incomplete set.
10. Owner and review. Named role, review date, and how managers request a change.

If a section is missing, hiring managers will fill the gap in Slack. That gap is the policy failure.

How to write it in one afternoon

Step 1: Map the current path

List who sends invites, who approves questions, where PDFs sit, and what “done” means today. A Vancouver scale-up often finds three answers to “done.” Pick one.

Step 2: Freeze the minimum for each job family

State a default, then exceptions. Example: two independent former managers for individual contributors; three contacts including one skip-level or client for people leaders. Write the numbers in the policy so recruiters do not invent them under offer pressure.

Step 3: Attach the question library by role family

Do not paste 40 questions into the policy. Point to a dated template ID. The policy says “use the current library.” The library holds the prompts.

Step 4: Name systems and access

If notes live in an ATS, say so. If they live in a reference platform, say who has admin rights. A Munich employer that left reports in a shared drive learned that “everyone in hiring” was too wide after a contractor left with access.

Step 5: Legal review for the countries you hire into

The template below is operational, not legal advice. US consumer-report rules, UK and EU privacy duties, and Canadian and Australian employment norms differ. Send the draft to counsel for the locations on your org chart, then lock version 1.0.

Free reference check policy template

Copy this reference check policy template, replace bracketed text, and store it with a version and date.

Document title: Reference checking policy
Owner: [Head of People / HR Manager]
Version: 1.0
Effective date: [YYYY-MM-DD]
Next review: [12 months from effective date]
Applies to: All employees and hiring managers who request or review employment references for [Company]

1. Purpose
[Company] collects employment references to inform hiring and promotion decisions for a named role. References are job-related evidence, not a character test and not a substitute for interviews or right-to-work checks.

2. Scope
A reference check is required before a signed offer for [list role families, e.g. all permanent hires above intern]. Interns and casual staff follow [lighter path or same path]. Contingent workers follow this policy when the assignment exceeds [N] months or includes [systems / clients / safety duties].

3. Consent and candidate notice
Do not contact referees until the candidate has given written consent for this employer and this role. Share a short summary of topics, expected timing, and how long notes are kept. The candidate should warn referees before the first invite.

4. Referee selection
Default: two independent people who supervised the candidate’s work in the last [five] years. Prefer former managers over peers. Peers and clients may supplement; they do not replace a manager except where the candidate has no manager history (documented). If two contacts share one personal inbox domain and the same narrow story, pause and widen the set.

5. Questions
Use the current question library for the role family ([template ID]). Questions must map to duties in the job description. Do not ask about age, health, family, religion, race, union activity, or other protected characteristics. If a referee volunteers that detail, exclude it from the decision note.

6. Timing and completion
Start consent and referee intake no later than the final interview. A signed offer does not leave until the minimum set in section 4 is complete, or [People / hiring committee] records a written exception. Incomplete files are not “close enough.”

7. Verification
Confirm employer name, reported title, and a work-email pattern or published switchboard before relying on the content. Treat stacked contact-path problems as a pause, not an automatic reject.

8. Documentation, access, and retention
Store invites, answers, timestamps, and the decision note in [system]. Access is limited to people who need the file for this decision. Retain records for [period aligned to local employment-file rules], then delete or anonymize per [records schedule]. Do not forward full reports to group inboxes.

9. Negative or conflicting references
A single negative note is a signal. Verify facts, seek a second independent referee, and document job-related reasons for the outcome. Do not ghost the candidate while the file is open.

10. Exceptions
Only [named role] may waive or reduce the minimum. Record the reason, the remaining evidence, and who approved. Exceptions are reviewed in the next policy cycle.

11. Training and SOP
Hiring managers complete a short briefing before they send their first check. Day-to-day steps live in the reference check SOP attached to this policy.

Turn the policy into a reference check SOP

A policy states rules. A reference check SOP states clicks and owners.

Write a one-page SOP with:

• Trigger (ATS stage name)
• Who sends the consent form
• Who reviews questions before send
• Reminder cadence (for example day 1, day 3, day 5)
• Who closes a stuck referee and requests a substitute
• Where the report is attached
• Who records the hire/no-hire note

A Wellington retailer that published the policy in the handbook but never wrote the SOP still had store managers phoning friends. The SOP is what changes Friday-afternoon behavior.

Keep the SOP in the same folder as the reference check policy template so version numbers stay aligned. When you change the question library, bump the SOP “library ID” line, not the whole policy, unless a rule changed.

Rollout without stalling hires

Pilot on one job family for two weeks. Collect where managers skipped a step. Fix the SOP, then expand.

Train with a live file, not a slide. Walk through consent, a stuck referee, and a volunteered medical comment so people see the rule applied.

Publish the completion definition in the ATS stage, not only in a PDF. If the stage says “references in progress” with no number, coordinators will guess.

Review quarterly: exception log, time-to-complete, and any question that attracted a complaint. A Sydney professional-services firm that reviewed exceptions every quarter found most waivers were “the candidate starts Monday,” which is a timing failure, not a policy exception.

FAQ

Can we use this template in every country we hire?

Use it as the operational skeleton. Confirm consent, retention, and screening overlays with local counsel. Do not treat a US-written form as automatic cover for EU or UK processing.

Do we need a separate policy for promotions?

Only if the rules differ. If the same consent, referee, and record rules apply, one policy with a promotions paragraph is enough.

Should the policy name a vendor?

Name the system of record. If you change vendors, update that line and the SOP. The rules (consent, minimum referees, job-related questions) should survive a tool change.

Who owns question wording?

People or Talent owns the library. Hiring managers may request a role-specific add-on. They may not send a private questionnaire that skips the filter in section 5.

Implement your policy with HiveRef

Implement your policy with HiveRef. Structured invites, a shared question library, and a stored report make the SOP the default path instead of another PDF. See HiveRef or compare plans when you are ready to run the policy on live checks.