Most reference checks happen after the decision is already made. The offer is drafted, the hiring manager is excited, and someone calls two people the candidate hand-picked to say nice things. Everyone spends twenty minutes confirming what they already believe.
That is not a check. That is a ritual.
Done well, a reference call is one of the cheapest signals available to a hiring team. It is the only part of your process where you hear from someone who watched the candidate work for months instead of for an hour. The problem is not the tool. It is how most teams use it.
Why the standard call produces nothing
Three habits drain the value out of reference checks.
The first is timing. If you call references after you have emotionally committed, you will read every hedge as modesty and every pause as a bad connection. Confirmation bias does the rest.
The second is the question set. "Was she a good employee?" and "Would you hire him again?" invite a yes. References want to be helpful, and a vague question gets a vague, generous answer.
The third is who you call. Candidates choose references who like them. That is rational behavior and you should expect it. A curated list is not useless, but treating it as an independent audit is a mistake.
Call before you fall in love
Move reference calls earlier, ideally right after the final interview and before the debrief converges on a decision. You want the information while your mind is still open.
This also changes the tone of the call. When you are still deciding, you ask better questions, because the answers actually matter to you.
Tell the candidate what you are doing and why. Most people are fine with it when the timeline is clear.
Ask about the work, not the person
Character questions produce character answers, and character answers are almost always positive. Work questions produce specifics.
Instead of asking whether someone is a strong communicator, ask what they were working on, who they had to convince, and what happened. You are looking for detail, not adjectives. A reference who cannot describe the actual work either did not see it closely or is being careful, and both are worth noting.
Anchor your questions to the role you are hiring for. If the job involves owning a roadmap with no direct authority, ask about a time the candidate had to move a project through a team that did not report to them.
Five questions that earn their twenty minutes
1. What was he actually responsible for, and what did the rest of the team own?
Scope inflation is the most common resume distortion. This question separates contribution from proximity without accusing anyone of anything.
2. Walk me through a project of hers that did not go well. What happened?
Every good employee has one. A reference who claims otherwise is not being useful. Listen for whether the candidate saw it coming, said something, and adjusted.
3. What kind of manager or environment gets the best out of him?
The most practical question on the list. It gives you something to act on whether you hire him or not, and it tends to get honest answers because it sounds like a favor rather than an interrogation.
4. Where did she need the most support?
Softer than asking about weaknesses, and it usually gets a real answer. Everyone needed support somewhere.
5. Who else saw this work closely?
The backdoor question. It often surfaces a second reference the candidate did not choose, and those calls tend to be the most informative ones you make.
Learn to hear a lukewarm reference
References rarely say anything negative outright. They signal it.
Watch for short answers where you expected stories. Watch for praise that stays in the safe zone: reliable, pleasant, always on time, never caused problems. Watch for a long pause before "yes, I would hire him again."
The strongest tell is an enthusiasm mismatch. Someone who genuinely rates a person interrupts you to add examples. Someone who does not answers exactly the question asked, then waits.
A tepid reference is not a rejection. It is a prompt. Take what you heard back into the process and probe it in a follow-up conversation with the candidate rather than quietly downgrading them without ever telling them why.
Write it down like any other interview
Reference calls tend to live in a hiring manager's memory and nowhere else. That makes them impossible to weigh fairly against the rest of your evidence.
Use the same scorecard structure you use for interviews. Note the question, the answer, and your read of it. If the reference raised a concern, log it as a concern rather than as a feeling.
This does two things. It stops one person's opinion from carrying more weight than it deserves, and it stops a vague bad impression from sinking a candidate with nothing written down to support it.
What to skip
Do not ask about salary history. In many places it is illegal, and everywhere it is irrelevant. Do not ask about health, family plans, or anything you would not ask the candidate directly.
Do not hand the call to someone who has never read the job description. The value comes from the follow-up question, and only someone who understands the role knows what to follow up on.
And do not run reference checks on some finalists and not others. Inconsistency is where bias quietly enters a process.
The point
A reference check should be able to change your mind. If it cannot, you are not running one.
Ask about the work. Ask early. Ask for one more name. Write down what you hear. Twenty minutes of that is worth more than an entire extra interview round.