A reference call that actually de-risks the hire
Most reference checks are a rushed formality that confirm nothing. A good one verifies the relationship, probes real performance, and ends with the question that separates strong hires from risky ones. This builder produces a structured call script tailored to the candidate, the role, and the competencies you care about.
Structure of the generated script
The script is built in five sequential sections:
-
Opening and context — a brief introduction explaining your role, that you are conducting references for the candidate’s application, and that the call should take about 10–15 minutes. Sets a professional tone and gives the referee a chance to prepare mentally.
-
Relationship verification — confirms how the referee knows the candidate: their exact reporting relationship, the dates they worked together, and the referee’s current role. This is both administrative (checking the relationship is genuine and relevant) and analytical (a direct manager’s input carries different weight than a peer’s).
-
Job-performance questions — open questions specific to the competencies you selected. For example:
- Leadership: “Can you describe a situation where [Candidate] had to lead others through a difficult period? What did they do, and what was the result?”
- Reliability: “Were there occasions where [Candidate] missed a deadline or commitment? How did they handle it?”
- Communication: “How would you describe the way [Candidate] communicated complex issues to people outside their immediate team?”
-
Culture and working style — questions about how the candidate operates day to day: how they respond to feedback, how they work in a team, how they handle ambiguity.
-
Closing block — a direct closing question: “Would you rehire [Candidate] if you had a suitable opening, and why or why not?” followed by “Is there anything you think I should know before making a decision?”
Why the rehire question is the most important one
The rehire question is the single most predictive question in a reference call. Former managers rarely say explicitly negative things about candidates, but hesitation, qualifications (“it would depend on the role”), or a pivot to listing positives without actually answering “yes” are all meaningful signals. An unambiguous, enthusiastic “Absolutely, I’d take them back tomorrow” is a different data point from “They were fine, I’m sure they’d do well in the right environment.”
Competency-targeted questions
The script changes based on what you toggle:
| Competency | Example question |
|---|---|
| Leadership | Asking about leading others through difficulty or developing direct reports |
| Technical depth | Asking about a technically complex problem they solved or explain to others |
| Reliability | Asking about consistency, deadlines, and ownership of commitments |
| Communication | Asking about how they communicated upward, laterally, and to non-specialists |
| Resilience | Asking about a setback or failure and how they responded |
Narrow the competencies to the two or three most critical for the role — a script that tries to cover ten things covers none of them well.
Practical tips for the call
- Ask open questions and then stay silent. The pause after a question is uncomfortable, but the pause is where genuine, candid answers surface rather than prepared ones.
- Take structured notes against each competency in real time so you can compare two or three referees consistently after the calls.
- Verify the referee independently by reaching them through a company switchboard or a work email you find independently — not via a number or email the candidate supplied.
- Check whether they knew the candidate in a relevant context. A colleague who worked adjacent to the candidate carries less signal than a manager who directly observed their output and decisions.