What should I ask on a reference check?

Factual questions rather than performance ones, because they clear liability policies and produce checkable answers. Ask what the person did day to day, what shift they worked, who they reported to, and what the referee relied on them for. The most productive single question is what would you tell their next manager, which reframes the call as helping a colleague rather than assessing a former employee.

Why do employers only confirm dates and job title?

Liability. A former manager who gives a negative reference can be sued, so organizations of any size instruct staff to confirm employment dates and title and nothing further. You will hit this constantly. Asking for the direct supervisor rather than the HR function, and asking factual rather than evaluative questions, gets past it more often than people expect.

Are reference checks actually useful?

Narrowly. They cannot tell you whether someone will succeed in your role under your supervisor. They can tell you whether the job the candidate described is the job they had, which is the mismatch these calls most reliably catch, and that is available even from a dates-only employer. That is worth six minutes on the one or two people you intend to hire.

When in the hiring process should reference checks happen?

Late, on a small number of candidates you genuinely intend to hire, and before the offer rather than after. Running references across a whole shortlist burns the referees' goodwill and produces uniformly positive answers. A reference that raises something material after an offer is accepted leaves no good options.

What does it mean if a reference is hesitant?

Usually that they are working within an instruction rather than that something is wrong. Treat a pause or a redirect as a reason to ask a more specific question or to look harder at one area, not as a verdict. A guarded referee may be following policy, may have had a personality clash, or may simply be busy.

What to Ask on a Reference Check

A reference call takes six minutes. Four of them establish that the candidate worked there between the dates they said, which you could have established from a payslip, and the remaining two produce a warm generality that would fit anybody.

Reference checking has a reputation for uselessness that it has largely earned. But the uselessness is a property of how the call is run, not of the exercise.

Why references have gone quiet

Two things changed and the practice did not adapt.

Many employers now have a policy of confirming employment dates and title only. The reason is liability: a former manager who gives a negative reference can be sued, and organizations of any size instruct people not to take the risk. This policy is real and you will hit it constantly.

And the candidate chose the referee. Nobody nominates someone who will damage them, so the base rate of positive references approaches one, and a positive reference carries almost no information.

Both facts point the same way. The value in a reference call is not the verdict. It is the specifics, and the hesitations.

Get past the policy

When you reach the formal wall, two moves work more often than people expect.

Ask for the direct supervisor rather than HR. A policy of dates-only usually lives in a human resources function; the person who actually managed the candidate is frequently willing to talk, and is the only one who knows anything useful anyway.

Ask questions that are not about performance. "What kind of work did they do day to day" and "what was the shift pattern" are factual, carry no liability, and tell you whether the candidate's description of the job matches somebody else's.

Verifying that the job was what the candidate said it was is worth the call on its own, and it is available even under the strictest policy.

Questions that get a policy answer

Would you rehire them?
How did they perform?
What were their weaknesses?
Were they reliable?
Any concerns we should know about?

Questions people answer

What did they actually do day to day?
What shift did they work?
Who did they report to?
What did you go to them for?
What would you tell their next manager?

The right column is factual, and the last one is the whole call

The questions worth the time

1
What did they do day to day?
Cross-checks the candidate's own account of the job. A material mismatch between the two descriptions is the most common thing a reference call actually catches, and it is available even from a dates-only employer.
Always ask
2
What did you rely on them for?
Positively framed, so it clears the liability instinct, and it forces a specific rather than a grade. An answer with no content is itself an answer.
Highest yield
3
What would you tell their next manager?
The single most productive question in reference checking. It reframes the call as helping a colleague rather than assessing a former employee, and people who will not answer anything else will often answer this.
The real question
4
What did they find hardest about the role?
Asks about difficulty rather than deficiency, which is answerable without risk. It usually surfaces the same information a weakness question would, and it gets answered.
Safe probe
5
Was their attendance what you would expect?
Specific, factual and central to hourly roles. Phrase it as a yes or no and let the pause do the work.
For shift work

Five questions, ordered by how reliably they produce something you did not already know

Listen for the pause

The most useful signal in a reference call is not a sentence. It is a hesitation before an otherwise positive one.

Someone who liked working with a person answers immediately and warmly. Someone who is choosing their words carefully, or who redirects to a different topic, or who confirms the dates and offers nothing further when a natural opening exists, is telling you something within the constraints they are working under.

This is a signal to weigh, not a verdict to act on. A reference who is guarded may be following an instruction, may have had a personality clash, or may be having a difficult day. Treat a hesitation as a reason to look harder at something specific rather than as a reason to reject.

Where the call belongs in the process

Late, and before the offer, not after it.

References cost the referee's goodwill as well as your time, so they belong at the point where you have one or two candidates you genuinely intend to hire. Running them across a whole shortlist burns relationships and produces five positive references, which is five pieces of no information.

They also belong before the offer rather than after. A reference that raises something material after an offer has been accepted leaves you with a problem that has no good version. The related timing argument for credentials and clearances is in Credential Verification Checklist.

What a reference cannot do

Worth stating plainly, because reference checking is often asked to carry more weight than it can hold.

A reference cannot tell you whether someone will do well in your role, under your supervisor, on your schedule. It can tell you whether the job they described is the job they had, whether the person who managed them recognizes the account, and occasionally that something specific is worth another question. That is a narrow contribution, and it is worth six minutes for the two candidates you are seriously considering.

Where an automated check is involved, treat its output the same way. Kariaa's own vetting marks each requirement passed or failed on its own with the evidence and a confidence level attached, plus an advisory fraud read, precisely so that a thin signal reads as thin rather than as a verdict. A check that returns a bare yes is hiding the part you needed.

Key takeaways

The candidate chose the referee, so a positive reference carries almost no information. The value is in specifics and hesitations.
Dates-only policies exist for liability reasons and you will hit them constantly. Ask the direct supervisor rather than HR, and ask factual questions rather than performance ones.
What would you tell their next manager is the most productive question in reference checking, because it reframes the call as helping a colleague.
Cross-checking the candidate's description of the job against the referee's is the thing these calls most reliably catch, and it works even under a strict policy.
A hesitation is a reason to look harder at something specific, not a reason to reject. Guardedness usually reflects an instruction.
Run references late, on one or two candidates you intend to hire, and before the offer rather than after.

Common questions

What should I ask on a reference check?: Factual questions rather than performance ones, because they clear liability policies and produce checkable answers. Ask what the person did day to day, what shift they worked, who they reported to, and what the referee relied on them for. The most productive single question is what would you tell their next manager, which reframes the call as helping a colleague rather than assessing a former employee.
Why do employers only confirm dates and job title?: Liability. A former manager who gives a negative reference can be sued, so organizations of any size instruct staff to confirm employment dates and title and nothing further. You will hit this constantly. Asking for the direct supervisor rather than the HR function, and asking factual rather than evaluative questions, gets past it more often than people expect.
Are reference checks actually useful?: Narrowly. They cannot tell you whether someone will succeed in your role under your supervisor. They can tell you whether the job the candidate described is the job they had, which is the mismatch these calls most reliably catch, and that is available even from a dates-only employer. That is worth six minutes on the one or two people you intend to hire.
When in the hiring process should reference checks happen?: Late, on a small number of candidates you genuinely intend to hire, and before the offer rather than after. Running references across a whole shortlist burns the referees' goodwill and produces uniformly positive answers. A reference that raises something material after an offer is accepted leaves no good options.
What does it mean if a reference is hesitant?: Usually that they are working within an instruction rather than that something is wrong. Treat a pause or a redirect as a reason to ask a more specific question or to look harder at one area, not as a verdict. A guarded referee may be following policy, may have had a personality clash, or may simply be busy.

Written by the team at Kariaa. Learn more at www.kariaa.com.