How to check references without wasting everyone's time

The reference check nobody wants to make

You've run three rounds of interviews. The candidate is strong. Your team likes them. You're ready to make an offer. And then someone says, "Did we check references?"

What follows is a ritual everyone dreads. You email the candidate asking for three names. They send contacts who will obviously say nice things. You play phone tag for a week. When you finally connect, you ask vague questions and get vague answers. "Great team player." "Pleasure to work with." "Would definitely rehire."

None of that information changes your decision. It didn't the last time either.

So here's the question every startup founder and hiring manager should be asking: if reference checks rarely surface useful information, why does nearly every company still do them? SHRM data suggests upwards of 90% of employers run some form of reference verification. That's a lot of collective effort for something most people treat as a checkbox.

The problem isn't that references are useless. Schmidt and Hunter's landmark meta-analysis in Psychological Bulletin found that reference checks have a predictive validity of .26 for job performance. That's moderate; lower than structured interviews (.51), but meaningfully above zero. References can tell you things interviews can't. Most people are doing them wrong.

Why most reference checks fail

Three things kill a reference check before it starts.

You're asking the wrong people. When candidates choose their own references, they pick people who will be positive. This is rational behavior, not deception. But it means your "reference check" is closer to a curated testimonial.

You're asking the wrong questions. "Would you rehire this person?" sounds decisive. It isn't. The answer is almost always yes, because saying no feels disloyal and could have legal consequences. Character questions ("Is she reliable?") generate the same thin responses. Research from Campion, Palmer, and Campion published in Personnel Psychology confirms that behavioral and situational questions produce more predictive information than general character assessments. This holds true for reference calls, not only interviews.

You're treating it as confirmation, not investigation. If you've already decided to hire someone and you're checking references to "make sure," you'll hear what you want to hear. Confirmation bias is real, and a five-minute phone call with a friendly contact is the perfect environment for it.

The 15-minute structured reference call

Here's a process that works without consuming your week. It takes 15 minutes per call, two calls per finalist. That's 30 minutes of total investment for information you can't get any other way.

Before the call

Ask the candidate for references, but be specific about who you want. "A direct manager from your last two roles" is better than "three professional references." You want people who observed the candidate's day-to-day work, not former colleagues who happen to be friends.

If a candidate can't provide a direct manager from a recent role, that's worth noting. It's not automatically disqualifying, but it's a data point.

The five questions that work

These questions are structured, behavioral, and hard to answer with platitudes. Ask all five in the same order for every reference call. Consistency is what makes the data comparable across candidates.

1. "What was [name]'s role, and what were they responsible for?"

This is a calibration question. You're checking whether the candidate described their responsibilities accurately. If the reference describes a significantly different scope than the candidate did, that's a signal worth exploring.

2. "Can you walk me through a specific project where [name] did their best work?"

You want a concrete story, not a character summary. If the reference can immediately recall a specific project with details, that tells you the candidate made an impression. If they struggle to name one, that's informative too.

3. "Tell me about a time when [name] struggled or received critical feedback. How did they respond?"

This is the question that separates a useful reference call from a wasted one. Most people will try to soften the answer. Let them. The content of the struggle matters less than how the candidate responded. Did they get defensive? Did they adjust? Did the same issue come up again?

Give the reference permission to be honest by normalizing the question: "Everyone has areas they're developing. I'm trying to understand how [name] handles those moments."

4. "If you were building a team today and needed someone in [this type of role], would [name] be one of the first people you'd call?"

This is different from "Would you rehire them?" That question is binary and loaded. This version asks the reference to rank the candidate against their mental model of strong performers. The distinction matters. Someone can be a competent employee you'd rehire without being someone you'd actively recruit.

Listen for enthusiasm versus politeness. A pause before "yes" tells you more than the word itself.

5. "What kind of environment or management style brings out their best work?"

This question isn't about screening out. It's about setting up the hire for success. If the reference says "she thrives with clear direction and regular check-ins" and your startup is a chaotic environment where nobody checks in on anyone, that's useful to know before day one, not after month three.

After the call

Write down your notes within five minutes. Reference check insights decay fast. Capture direct quotes, not summaries. "He said the candidate 'shut down in group critiques'" is more useful than "communication could be better."

When to skip references (and when you can't)

Not every hire needs a full reference process. Here's the honest breakdown.

Skip or abbreviate when: You're hiring for a junior role with a strong work sample or trial task. The candidate has a public portfolio that demonstrates their work. You're backfilling a role where the skills are commodity and the ramp-up is short.

Do the full process when: The role has high ambiguity and requires self-direction. You don't have strong interview signal and want a second data source. The candidate is a finalist and you're choosing between two strong options. The role involves managing people or handling sensitive decisions.

For early-stage startups, every hire is high-stakes. A five-person team where one person underperforms means 20% of your workforce isn't pulling their weight. The 30 minutes spent on two reference calls is a small price for reducing that risk.

Making it part of your process, not an afterthought

The reason reference checks feel like a waste of time is that most companies bolt them on at the end, after the decision is already made. Move them earlier.

Run reference calls before the final interview, not after. This gives you specific things to probe in the last conversation. If a reference mentioned the candidate struggled with ambiguity, you can design your final interview to test that directly.

Build it into your hiring workflow from the start. When a candidate enters your finalist stage, reference calls should be a scheduled step, not something you remember to do at 9 PM before sending the offer.

If you're using an ATS, create a reference check stage in your pipeline with a template for the five questions. This turns a loose process into a repeatable one. The goal isn't bureaucracy. It's making sure you spend 30 focused minutes getting real information instead of spending a week playing phone tag for platitudes.

The point of all of this

Reference checks have a credibility problem because most people do them badly. Unstructured calls with hand-picked contacts asking vague questions will always be a waste of time.

Structured calls with specific behavioral questions are different. They won't replace a strong interview process, but they fill gaps interviews can't. How someone handles failure when their boss is watching. Whether the scope they described in your interview matches what their manager remembers. What environment makes them thrive versus what makes them shut down.

That's 30 minutes of your time for information that could save you months of a wrong hire.

If your hiring process doesn't have a repeatable structure yet, start there. Bringboard helps startup teams build a hiring workflow that includes every step from application to offer, so nothing falls through the cracks, including reference checks.