Back to the blog

Recruitment operations · 21 September 2026

Candidate reference checks: a staffing agency workflow

Plan candidate reference checks with agreed contact timing, focused questions, clear CRM states and human review of incomplete or conflicting information.

Recruiter making a reference-check phone call while reviewing a folder in a quiet office

Turn insight into action

Need this fixed inside your staffing workflow?

We help staffing teams tighten intake, follow-up, CRM structure, and recruiter handoff without adding a heavy system.

  • Fewer lost candidates
  • Clearer recruiter next steps
  • Better pipeline visibility

A candidate reference check workflow should establish why a reference is needed, when the named person may be contacted, what questions are relevant and who will review the answer. Track the request separately from the recruitment decision. Received is an administrative state; reviewed means a recruiter has considered the evidence and recorded the next step.

When a start date approaches, an unanswered reference request can create pressure. Silence is not an adverse reference, and a factual reply does not confirm every skill on a CV. Keep both gaps visible.

Agree the purpose before contacting anyone

Start with the client brief. Identify the specific employment information the reference should help establish and whether the request is an agreed requirement for this vacancy. Record which stage depends on its review and who can decide how to handle an unavailable reference. Do not create an identical reference hurdle for every candidate simply because the CRM has a checkbox.

The recruiter should be able to explain the purpose to the candidate in ordinary language. For example, the desk might want to clarify duties in a previous warehouse assignment that are relevant to a new role. That is a narrower request than asking a former manager to provide a general verdict on the person's character.

Keep this work separate from initial candidate qualification. A reference adds information from another source. It does not replace the agency's own conversation about skills, availability or the actual vacancy.

Establish a contact boundary with the candidate

Before sending anything, confirm the referee's name, organization, relationship to the candidate, contact route and agreed contact timing. Be especially careful with a current employer: a reference request can reveal a job search. Record the candidate's contact agreement and any restriction, such as using a previous supervisor first.

UK guidance from Acas on requesting references recommends final-stage timing and applicant permission before approaching a current employer. That is a UK reference point, not a statement of Dutch, Polish or Spanish law. For cross-border recruitment, establish the applicable local process with the person responsible for employment and privacy requirements before configuring it.

An operational contact agreement also does not settle every data-protection question. Keep the workflow within the agency's approved access, sharing and retention rules. The useful design decision here is to stop a request from being sent merely because someone entered a telephone number.

Create one request record for each reference

Attach the request to the relevant candidate application, with a link back to the candidate record. Include its purpose, owner, permitted contact timing, sent date, expected follow-up date, response location and review outcome. If the same person has two live applications, the scope of one reference should not silently expand to the other.

Use states that distinguish the work still needed:

  • ready to request: purpose and contact details agreed;
  • requested: sent through the approved route;
  • awaiting clarification: a reply needs a focused question;
  • received, awaiting review: information is available but not assessed;
  • reviewed: the reviewer has documented what it establishes;
  • unavailable: the agreed attempt process ended without usable information.

Keep the candidate's overall application status separate. A request can be unavailable while the hiring decision remains under review. Likewise, an automated delivery confirmation only shows that a message reached a technical destination; it does not show that the referee answered.

Ask questions the recipient can actually answer

A short request should explain who is asking, identify the candidate appropriately and specify the relevant employment period or working relationship. Use the agency's approved communication route and share only what is needed for that purpose. Offer a practical way to say that the recipient is not the right person.

Useful questions can include:

  • In what role and period did you work with the candidate?
  • Which relevant duties did you directly observe?
  • Can you clarify the particular responsibility we have described?
  • Are there limits to the information you can provide?

Keep questions tied to the vacancy and direct knowledge. Avoid fishing for medical information, family circumstances or unrelated personal opinions. A recipient who can confirm dates but not duties has provided a limited reference, not necessarily a poor one.

For a Polish-speaking former supervisor supporting a Dutch placement, agree the language and explain unfamiliar job terms. Preserve meaningful wording when translating the response. If a phrase could describe different responsibilities, ask a clarifying question rather than choosing the interpretation most convenient for the vacancy.

Review evidence without turning uncertainty into rejection

Consider a hypothetical candidate whose CV describes order-picking work, while a former supervisor confirms employment in the packing team. The recruiter should check whether duties changed during the assignment, whether the reference covers the same period and whether the person answering observed the work directly.

Record the source statement and the recruiter's interpretation separately. Give the candidate a chance to clarify a material discrepancy through the appropriate process before treating it as settled. A statement from a referee is evidence to assess in context, not a substitute for human judgement.

If the reference is unavailable, use the agreed exception route. The responsible reviewer can decide what alternative evidence is appropriate and what remains unresolved. Do not automatically clear a mandatory condition, and do not automatically reject the candidate because the referee did not respond. The decision and its basis belong in the application record.

Automate reminders around the decision

A proposed recruitment CRM workflow can be assessed for request tasks, owner reminders and a queue of received responses awaiting review. Confirm those capabilities in the actual setup. Stop reminders when a reply arrives or a restriction changes, and make reassignment visible if the owner is absent.

Keep decisions about conflicting or incomplete information with a named person. AI-generated summaries, if evaluated, should retain a route to the original response and be checked for omitted qualifications. A summary saying confirmed must not hide that the referee only confirmed dates.

Track the delay by stage: waiting for permission, waiting for the referee, or waiting for internal review. These require different actions. Measuring only the total age of the request can blame an external contact for a response that has been sitting unread inside the agency.

Common mistakes and desk checklist

The costly mistakes are sending too early, repeating requests after a reply, treating no response as negative evidence and copying sensitive reference detail into broad client updates. Another is marking the whole candidate approved when only one requested fact has been confirmed.

Before closing a reference task, check:

  • the purpose and contact boundary were recorded;
  • the recipient and working relationship were established;
  • the response is distinguishable from the reviewer's interpretation;
  • limited or conflicting information has a next action;
  • the application decision has a named reviewer;
  • reminders and unnecessary access have been handled under the approved process.

If reference requests are disappearing between email and recruiter decisions, contact AI JOB AGENCY to map the handoff using an anonymized example. Start with the request and review states before adding more automated messages.

FAQ

Should references be requested during the first intake?

First decide the vacancy's requirements and appropriate timing. Collecting a contact detail is not authorization to approach that person immediately. A current employer requires particular care because contact may disclose the candidate's job search.

What if the referee does not reply?

Follow the agreed reminder limit and exception route. Record the reference as unavailable when appropriate, with a reviewer deciding the next step. Do not turn silence into a negative judgement about the candidate.

Can one reference cover several applications?

Possibly, but review its purpose, age, relevance and approved sharing scope for each application. A reference about one set of duties may not establish the requirements of another vacancy. Avoid automatic reuse without that check.

Is an employment-date confirmation enough?

It is enough only for a requirement that it actually addresses. Record what was confirmed and what was not. A factual reply should not be summarized as proof of skills that the recipient never discussed.

Can AI make the reference decision?

Keep the substantive review with a responsible person. Automation can be considered for administration and carefully checked summaries, but missing context and ambiguous wording make an unexplained automated pass or fail unsuitable for this workflow.

Turn insight into action

Need this fixed inside your staffing workflow?

We help staffing teams tighten intake, follow-up, CRM structure, and recruiter handoff without adding a heavy system.

  • Fewer lost candidates
  • Clearer recruiter next steps
  • Better pipeline visibility