The reference check is usually the shortest step in a hiring process and the one that takes the longest. Everything else has a date on it. The interviews were scheduled, the panel met, the decision was made. Then the offer sits unsent while a recruiter leaves a third voicemail for a former manager in a different time zone who has no particular reason to call back.
Meanwhile the candidate is waiting, and candidates who wait accept other offers.
Moving references to a form is the obvious response, and it is usually done badly, because the form gets built as a survey. A survey asks anonymous people for opinions. A reference check asks a specific named person about a specific named candidate, keeps a record of who said what, and has to hold up if the hire is ever disputed. Those are different requirements, and they change what the form needs to be.
Why the call is the bottleneck
It is worth naming the actual failure, because a form only fixes some of it.
Both people have to be free at once. A call needs a slot in two calendars, one of which belongs to someone with no stake in the outcome. Across time zones this alone adds days.
Nothing is recorded. Notes are written afterwards from memory, filtered by whoever took the call. If a hiring decision is later questioned, what exists is one person's summary, not what the referee said.
Every call is different. Conversations drift. One referee is asked about reliability and another about teamwork, and the two candidates are then compared as though the same ground was covered. Unstructured reference conversations are also the easiest place in a process for irrelevant personal information to surface, which is a risk to the decision and to the organisation.
Referees are increasingly not allowed to say much. Many employers have policies restricting what a former manager may confirm, often limited to dates of employment and job title. A twenty minute call that produces two facts is a twenty minute call that could have been a two minute form.
A form fixes the scheduling, the record and the consistency. It does not make a restricted referee say more, and any process that depends on candid personal assessment from a large employer should be designed with that in mind.
What a reference form needs that a survey does not
Four requirements separate this from an ordinary questionnaire.
It has to know which candidate it is about. A form that asks the referee to type the candidate's name produces spelling variants, nicknames and mismatches that then have to be reconciled by hand. The candidate should be carried by the link, so the response arrives already attached.
It has to establish who the referee is. Name, job title, organisation, and the relationship to the candidate, including the period they worked together and whether they managed them directly. A reference from a peer and a reference from a line manager answer different questions, and the difference has to be recorded rather than assumed.
It has to be handled confidentially. Reference responses are among the most sensitive records a hiring process creates. They should not sit in a spreadsheet shared across a company, or in an email thread that gets forwarded. Tools that offer view-only roles and per-workspace separation let a hiring manager read a reference without the response becoming generally available, and it is worth checking what the access model actually allows rather than assuming a link is private because it is unlisted.
It has to leave an audit trail. Who was asked, when, what came back, and what was done with it. If a hire is challenged, or a candidate later asks what was collected about them, the answer needs to be retrievable rather than reconstructed.
The questions worth asking
Split the form into a verification block and an assessment block. The first is factual and almost always answerable. The second is judgement and will sometimes be declined.
| Block | Question | Why it earns its place |
|---|---|---|
| Verification | Dates the candidate worked there | The single most common discrepancy in applications |
| Verification | Job title held at the end | Titles drift upward between the CV and reality |
| Verification | Relationship and reporting line | Determines how much weight the rest of the answers carry |
| Assessment | What the candidate was responsible for | Confirms or contradicts what the interviews established |
| Assessment | How they handled a difficult situation | Behaviour rather than personality |
| Assessment | Anything the role description should account for | An open door without inviting personal commentary |
| Closing | Would the referee work with them again | A single question that correlates with everything else |
Two rules about the wording. Ask about the job, not the person. Questions about attitude, health, personal circumstances or anything protected are both unreliable and a liability, and a written form makes them permanent in a way a call does not. And keep rating scales attached to something concrete. A one to five score for communication means nothing without a definition, while a question asking whether the candidate wrote documentation others relied on can actually be answered.
Eight to ten questions is a reasonable ceiling. The referee is doing an unpaid favour for a former colleague, and every additional question reduces the chance of getting any of them answered.
Consent, and what the candidate is told
Contacting a former employer about someone is processing personal data about both the candidate and the referee, and the rules differ by jurisdiction. Some require the candidate's written consent before any approach is made. Most good practice converges on the same shape regardless.
Get consent explicitly, as a separate step, and record it with a timestamp. Let the candidate nominate the referees rather than approaching people they did not list, particularly a current employer, since an unannounced call to a current manager can cost the candidate their existing job. State how long the reference will be kept and what it will be used for. And tell the referee, on the form itself, who will see their answers, because a referee who assumes anonymity and later learns otherwise has a legitimate complaint.
Retention is the part most often skipped. References collected for a candidate who was not hired have no ongoing purpose, and keeping them indefinitely in a shared drive is the kind of quiet accumulation that becomes a problem only when someone asks. Deciding the period in advance, and being able to export and delete by candidate, is easier than reconstructing it later.
One link for everyone, or one link per candidate
This is the decision that determines how much manual reconciliation the process creates, and it is usually made by accident.
A single public form, sent to every referee, is the easy build. It also means the referee has to identify the candidate themselves, and the answers arrive in one undifferentiated list that someone then sorts. Names get misspelled, two candidates with similar names get confused, and a response that omits the candidate's name entirely has to be traced back through the email that prompted it.
Carrying the candidate in the link removes all of that. The same form is used, with the candidate's identity supplied as a parameter, so the response arrives already attached to the right person. Where a tool supports it, the referee's own details can be carried the same way, which shortens the form and stops a referee being asked to retype information the recruiter already has.
The alternative some teams reach for is requiring the referee to sign in, which guarantees identity and costs far more than it looks. It is worth knowing how this behaves on the platforms people default to. Google's documentation for the file upload question type states that responders need to sign in to a Google Account to answer it, that files land in a folder on the form owner's Drive, and that the question cannot be used when the form lives in a shared drive. A senior former manager asked to create an account before answering a favour for an ex-colleague will frequently just not do it.
The workable middle ground is no account, a unique link per request, and the referee's identity captured as questions on the form rather than enforced by a login. That is enough to keep the record straight without adding a barrier at the exact moment goodwill is thinnest.
Getting referees to actually reply
A form removes the scheduling problem and introduces a new one. An email that can be ignored gets ignored.
Make the ask short and specific. Say who the candidate is, that they nominated this person, roughly how long it takes, and when a reply is useful by. A deadline turns an open request into a task.
Make it work on a phone. Referees answer these between other things. A long single page on a small screen gets abandoned partway through, while one question per screen with a progress bar tends to get finished.
Send reminders, but know whether the first message arrived. Chasing someone who never received the request is wasted effort, and so is chasing someone who is halfway through it. Tools that record whether an email was opened and whether the link was pressed turn a guess into a decision about who actually needs a nudge.
Make the candidate part of the chase. A short note from the candidate to their own referee moves things faster than a third reminder from an unknown recruiter.
Where the responses should live
The common ending is a form that works, feeding a spreadsheet nobody owns. References arrive as rows, the recruiter matches them to candidates by hand, and the hiring manager asks in a meeting whether the second reference came back yet.
What the step actually needs is a record per candidate that carries a state. Requested, opened, returned, reviewed. An owner, so it is clear whose job the chase is. A place for the recruiter's own note after reading it, separate from what the referee wrote, so the assessment and the source stay distinguishable. And the two or three references for one candidate grouped together rather than scattered across a sheet in submission order.
Tools built around response handling rather than form building carry those properties natively, including stages, an assigned owner and internal fields the team fills in after the response arrives. The way different intakes are structured is worth reading before building this on top of a spreadsheet, because the reference step is one where a lost or misfiled response has consequences beyond inconvenience.
What to change first
Write the questions down once, as a fixed list, and stop asking them by phone. Put consent and retention in writing before the first request goes out. Then check whether the tool holding the answers can tell you which references are outstanding without anyone reading a spreadsheet, and if it cannot, try the same process on one that can, such as Halict.
Q1. How many references should be requested for one candidate?
Two is the common standard, and the more important variable is who they are rather than how many. One direct line manager is worth more than three peers, because the manager can speak to responsibility and performance while a peer usually cannot. Asking for more than three rarely adds information and lengthens the step.
Q2. Can a current employer be contacted without telling the candidate?
It should never happen. An unannounced approach to a current manager can end the candidate's existing job before a new offer is signed, and in several jurisdictions contacting a referee without consent is itself a problem. Let the candidate nominate who may be contacted and when, and hold current employer checks until an offer is accepted.
Q3. What should be done when a referee refuses to answer anything beyond dates and title?
Treat it as a company policy rather than a signal about the candidate, because that is usually what it is. Record what was confirmed, note that the policy limited the response, and put the weight on the other reference. Designing the form so the verification block can stand alone means a restricted reply still produces something usable.
Q4. Is a written reference form acceptable as evidence if a hire is disputed?
A written response is generally stronger evidence than notes taken from a call, because it shows what was asked and what was answered rather than one person's summary. The value depends on the record being complete and unaltered, which means keeping the original response, the timestamp and the consent record together rather than copying conclusions into a document.
Q5. How long should reference responses be kept?
Decide the period before collecting them and apply it consistently, particularly for candidates who were not hired, since those records have no ongoing purpose. The practical requirement is being able to find and remove everything relating to one candidate on request, which is difficult in a shared spreadsheet and straightforward in a tool that keeps responses grouped per person.