NEWRecognition module — recognise hard work and the people going above and beyond
AgencyOptixRecruitment software
Right to Work & Checks9 February 2026 · 4 min read · Updated 27 September 2026

Reference checks: what a recruitment agency should actually be verifying

Reference checking isn't a statutory requirement in the way a right to work check is, but for most placements it's still a genuine part of due diligence — and it's one of the easier steps to do badly without anyone noticing, because a thin reference still looks, on paper, like a completed step.

What a reference check is actually for

A reference check exists to verify what's been said about a candidate's employment history is accurate, and to surface anything relevant a CV or interview wouldn't reveal — a pattern of short tenures, a conduct issue, a mismatch between the role claimed and the role actually performed. A check that only confirms start and end dates accomplishes the first of these and nothing else, which is a much weaker check than it looks.

What good practice actually covers

  • Confirming employment dates and job title against what the candidate provided, not just accepting the candidate's version at face value.
  • Asking specifically about the nature of the role and day-to-day responsibilities, to catch a meaningful mismatch with what's been claimed.
  • Where the role justifies it, asking direct questions about reliability, conduct and, for roles involving vulnerable people, any known safeguarding concerns.
  • Following up a vague or evasive answer rather than treating a completed call as equivalent to a genuinely informative one.

Why this matters more for some roles than others

For a low-risk commercial or industrial placement, a light-touch reference check is a reasonable, proportionate approach. For a role working with children, vulnerable adults, or in a position of financial trust, a thin reference process sits uncomfortably alongside the more rigorous DBS check the role likely also requires — the two are meant to work together, and a strong DBS result doesn't compensate for a reference check that never asked a meaningful question.

Handling a reference that raises a concern

A reference that raises something genuinely concerning needs a considered response, not an automatic rejection or an automatic dismissal of the concern as unreliable gossip from a disgruntled former employer. The safest practice is recording what was actually said, following up directly with the candidate to give them a chance to respond, and making a documented decision either way — rather than quietly not proceeding without ever writing down why, which leaves the agency with no defensible record if the decision is later questioned.

Building reference checks into a sequenced onboarding process

Reference checking fits naturally alongside the other sequenced onboarding steps — ideally completed, or at minimum initiated, before an assignment start date is confirmed, rather than run in parallel with a worker already on site. A reference that comes back after someone has already started isn't worthless, but it's a much weaker safeguard than one completed as a genuine gate.

What to do when a previous employer won't give more than dates

Many employers, on legal advice, will only confirm dates and job title regardless of what's asked — that's a real constraint, not a failure of the checking process. In that situation, the honest response is documenting that a fuller reference wasn't obtainable, rather than quietly treating a bare-dates confirmation as if it were a fuller check that simply came back clean. For higher-risk roles, this might mean leaning more heavily on the DBS result and a more thorough interview process to compensate for a reference that couldn't say much.

The reference that verifies nothing

A reference obtained through contact details supplied by the candidate, confirming employment the candidate described, has independently established very little — and it is the commonest form a reference takes, because it is the easiest to obtain and looks identical in the file to one that was properly verified.

What separates a reference that holds up is independence: contact details obtained separately, confirmation that the organisation exists, a record of how the referee's position was established, and all of it noted at the time rather than reconstructed when a client audits the file.

Common mistakes

  • Contacting referees only through details the candidate provided
  • No record of how the referee's authenticity was established
  • Verbal references with no contemporaneous note
  • Inconsistent standards between consultants or branches
  • Filing the reference without recording who obtained it and when
  • Accepting a reference that confirms dates but not conduct or role

Key takeaways

  • A reference check that only confirms dates is a weak check, even though it looks complete.
  • Ask about role responsibilities and conduct specifically, not just employment dates.
  • Higher-risk roles — working with vulnerable people or in positions of trust — need a more rigorous reference process, not the same light-touch check as any other placement.
  • Document a concerning reference and the decision made in response, rather than quietly declining to proceed without a record.
  • Treat reference checking as a sequenced onboarding step completed before a start date, not a parallel task running after someone's already working.

The AgencyOptix team

Written by people who work daily with recruitment agencies on right-to-work checks, AWR compliance and the records that hold up under an EAS inspection.