Reference Checking Questions for Recruiters: A Structured Question Bank
A reference call is only as useful as the questions you bring to it.
Ask the same themes in the same order across referees and you can compare answers; improvise each call and you get anecdotes you cannot weigh. This guide gives you a question bank grouped by what it tests, a short process for running the calls, and a way to read the results without letting one comment decide the hire.
Before you dial: seven practices that make the answers usable
- Decide what the check must prove. Write down the two or three things you need confirmed — for example, whether the candidate's stated responsibilities match reality, or whether their working style suits your team. Everything else is secondary.
- Get the candidate's permission and say plainly why you are calling. Transparency keeps the relationship intact and keeps the process on the right side of legal and ethical expectations.
- Choose referees who actually saw the work. Past supervisors, close collaborators and clients can speak to performance; personal referees can speak to character but are weak predictors of how someone performs on the job.
- Use a prepared question set. A fixed structure is what lets you compare two referees objectively and spot where their accounts diverge. Adjust the wording to the role and the skills you need to confirm, but keep the spine.
- Be respectful of the referee's time. Referees tend to be positive by default; a courteous, focused call is more likely to produce a detailed and honest answer than a rushed one.
- Write down what was said, not what you think it means. Record facts and examples; leave your interpretations out of the notes so bias does not creep in at the recording stage.
- Read across referees, not within one. A single criticism is not decisive. A theme that recurs across several referees is.
The question bank, grouped by what each theme tests
Use the groups below as a running order. Not every role needs every question — pick the groups that map to your shortlist criteria and keep the same set for every referee on that role.
General performance and work ethics. Confirm job title, employment dates and main responsibilities first; that anchors everything else. Then ask for an overall performance rating on a 1–10 scale, the candidate's main strengths and development areas, how they coped with deadlines and pressure, a 1–10 rating for punctuality and reliability, an example of following instructions beyond what was expected, whether they respected company policies (yes/no), and a 1–10 rating for time management and organisation.
Teamwork and interpersonal skills. Ask how well the candidate collaborated and cooperated, whether they resolved conflicts when they arose (yes/no), how you would describe their communication style with colleagues and clients (effective, neutral or ineffective), how receptive they were to correction and criticism, what their leadership behaviours looked like where relevant, and whether they worked more independently or as part of a team.
Problem-solving and decision-making. Ask for a concrete example of a problem the candidate solved, how they handled unexpected challenges or workplace change, and how their work contributed to the company's strategic goals.
Job-specific skills and competencies. Ask about the technical skills that matter for the role, how the candidate demonstrated specific knowledge in the area, whether any weakness kept them from excelling, how quickly they picked up new skills, tools or technologies, and what the referee sees as the key strengths and weaknesses from their vantage point.
Cultural fit and values. Ask for a 1–10 rating of how well the candidate matched the organisation's culture, the positive impact they had on the working environment, a 1–10 rating of alignment with values and mission, whether the referee would rehire them (yes/no), and their impression of the candidate's work habits and attitude.
Closing questions. Ask why the candidate left, whether any area needs training or support, and whether the referee would offer them this position (yes/no).
Worked example: one comment versus a pattern
Suppose three referees are asked about a candidate's leadership. The first says the candidate "kept the team steady through a difficult quarter" and names a specific project. The second describes how the candidate ran weekly planning and resolved a dispute between two team members. The third mentions the candidate's calm handling of a client escalation. Three independent referees, three concrete examples, one theme: leadership under pressure. That is a pattern worth weighting.
Now suppose one of those referees adds that the candidate "could be slow to delegate." On its own, that is a single data point. If a second referee independently raises the same delegation issue, it becomes a pattern — and a question worth putting to the candidate before an offer. The rule is not "ignore criticism"; it is "weigh criticism by how often it recurs and how specific it is."
Reading the results in five steps
- Compare with the interviews. Look for where the reference accounts match what the candidate said in interview and where they diverge. Agreement supports claimed strengths; divergence is a prompt for a follow-up conversation.
- Identify patterns. Praise or concern that appears in more than one reference is the signal. A single mention is a note; a repeated mention is information.
- Assess cultural fit. Compare the candidate's past working environments with your own. Referees' descriptions of how the candidate operated in their previous team are more useful than generic statements about "fit".
- Evaluate specificity. Vague positive or negative remarks are hard to act on. Concrete examples of conduct and outcomes are what you can weigh.
- Make an informed decision. Reference data is one input, not the verdict. Combine it with interview performance, skills evidence and any other assessments before deciding.
A field map for the reference-call record
Keep one record per referee so the comparison is mechanical rather than memory-based. The fields below cover everything the question bank asks for.
When the check is complete — and when it is not
A reference check is complete when you have spoken to the planned number of referees, asked the same core question set to each, recorded facts and examples rather than impressions, and can state in one sentence what the references confirmed and what they left open. It is inconclusive when the referees could not speak to the role's core skills, when answers were too vague to test, or when the accounts conflict in a way interviews cannot resolve. In that case, the next step is a targeted follow-up with the candidate, not a decision made on thin evidence.
| Question theme | Evidence it should produce | Failure mode if the answer stays vague |
|---|---|---|
| Job title, dates, responsibilities | A factual baseline to test the CV against | Referee cannot confirm the basics — treat the CV claim as unverified |
| Overall performance rating (1–10) | A comparable number across referees | A rating with no example behind it |
| Strengths and development areas | Named strengths and named gaps | Generic praise that could apply to anyone |
| Deadlines and pressure | A specific situation and how it was handled | Adjectives without a story |
| Punctuality and reliability (1–10) | A comparable number across referees | Rating given without context |
| Following instructions beyond expectations | A concrete example | No example offered |
| Respect for company policies (yes/no) | A direct confirmation | Hedged answer — ask for the specific policy |
| Time management and organisation (1–10) | A comparable number across referees | Rating given without context |
| Collaboration and cooperation | A description of how the candidate worked with others | Only general statements about being 'a team player' |
| Conflict resolution (yes/no) | A direct confirmation plus an example | Yes with no example |
| Communication style (effective / neutral / ineffective) | A comparable category across referees | Category chosen without explanation |
| Receptiveness to correction and criticism | A described reaction to feedback | No example of feedback received |
| Leadership behaviours (where relevant) | Described activities, attitudes and behaviours | Leadership asserted without evidence |
| Independent vs team working | A description of the candidate's actual mode of work | Both claimed without distinction |
| Problem-solving example | A specific problem and the resolution | Abstract description of 'good problem solver' |
| Handling unexpected change | A specific situation and response | No example |
| Contribution to strategic goals | A described contribution | Claim without evidence |
| Technical skills for the role | Specific skills confirmed or not | Skills listed without demonstration |
| Demonstrated area knowledge | An example of knowledge in use | Assertion only |
| Weaknesses that limited excellence | A named limitation | No weakness offered — probe further |
| Learning rate for new skills, tools, technologies | An example of picking something up quickly | No example |
| Key strengths and weaknesses from the referee's position | A summary grounded in the referee's vantage point | Summary that repeats the CV |
| Cultural match (1–10) | A comparable number across referees | Rating without context |
| Positive impact on the work environment | A described impact | Generic statement |
| Alignment with values and mission (1–10) | A comparable number across referees | Rating without context |
| Would rehire (yes/no) | A direct signal | Hedged answer — ask why |
| Impression of work habits and attitude | A described impression | Impression with no example |
| Reason for turnover | A stated reason | Reason that conflicts with the candidate's account |
| Training or support needed | A named area | No area identified |
| Would offer this position (yes/no) | A direct signal | Hedged answer — ask why |
Question wording and rating scales are the reference set used in this guide; adapt wording to the role while keeping the same themes and scales so referees remain comparable.
| Field | What goes in it | Why it matters |
|---|---|---|
| Referee name and relationship | Who they are and how they worked with the candidate | Establishes the vantage point behind every answer |
| Employment facts confirmed | Job title, dates, responsibilities as stated by the referee | Tests the CV baseline |
| Ratings | Performance, punctuality, time management, cultural match, values alignment — each on its stated scale | Comparable across referees |
| Examples given | The concrete situations the referee described | The evidence behind any rating |
| Named strengths | What the referee said the candidate does well | Feeds the pattern check |
| Named development areas | What the referee said the candidate should improve | Feeds the pattern check |
| Rehire and offer signals | Yes/no answers to the rehire and offer questions | Direct signals to weigh |
| Open questions | Anything the referee could not answer or left vague | Drives the follow-up with the candidate |
The record is a working document for the recruiter; it is not a substitute for the interview record and should be read alongside it.
Frequently asked questions
How many references should I contact?
Three to five is the usual range. Mix past supervisors, peers and clients so you get a balanced view rather than three versions of the same perspective.
Can a candidate refuse to give references?
They can decline, and that is their right — but a refusal is worth understanding. Ask why, and look for other ways to verify their credentials and abilities before deciding how to proceed.
What if a reference gives negative feedback?
Put it in context. Look for whether the same theme appears across several referees, and weigh the specifics of the criticism against the candidate's overall background. One unfavourable remark does not rule a candidate out; a recurring pattern does.
Should I contact references not listed by the candidate?
Generally no, unless the candidate has given permission. Staying within the referees they named protects their privacy and keeps the hiring process open and above board.
Should I use the same questions for every referee?
Yes for the core set — that is what makes the answers comparable. You can add role-specific questions on top, but keep the spine identical so you can see where referees agree and where they diverge.
How should I record the answers?
Record facts and examples, not your interpretations. Leave your own opinions out of the notes so the comparison between referees stays as neutral as possible.