Skip to content

Post 10

What a reference check can check, and what it cannot

Nobody argues with a reference check. Somebody who worked with you takes a call and answers a few questions, and the employer writes down what they said. It sits on every process diagram under a box marked checks, and it is the step people mean when they say a company looked into someone.

Ahsan MahmoodAuthor
Published
Last reviewed
About 7 minutesReading time

Do reference checks actually work?

A reference call reaches a manager weeks after the decision is mostly made, and often reaches someone who has moved on. It confirms what nobody was worried about.

That is not a complaint about referees. They give up their own time for somebody else’s benefit, and they are usually generous about it. It is a description of what the question can carry.

What is a reference check actually asking?

A reference check asks one person for their impression of another, with a factual question attached to the front. The factual part, whether you held that job for that long, is the only piece that can be tested against anything. Everything after it is memory and judgement.

Then there is who is answering. You chose them. You picked the person most likely to say a warm thing about you, which is the sensible move and which the employer already assumes you made. So the opinion arrives pre-discounted, in the same way the true lines on your resume do. The reason is the same: the reader has no way to sort the honest ones from the arranged ones.

Why does the timing matter so much?

A call that lands late has one move available to it. It can stop an offer. It cannot shape one, because by then the shape is already there.

It also has to find a person. People move. Teams get renamed, absorbed or dissolved, and the manager who could describe your work from memory now has a new employer, a new inbox and no obligation to anyone. When the call does reach them, they are being asked to recall a specific person across a gap of years, in the middle of a working day, on somebody else’s schedule.

None of that is anybody’s fault. It is just what the design of the step allows.

What can be checked, and what can only be believed?

The title, the company and the dates can be checked. Whether you were good at the job can only be believed. Here is the turn, and it is not the one people expect: the trouble with a reference check is not that referees lie. It is that the call was never a check in the first place.

A check has an answer that does not change with who you ask. Was she good at the job does not have one. Two colleagues who sat either side of you will answer differently and both honestly, and no third thing exists to test either answer against. Did she hold this title at this company between these months does have one, and it is sitting in a payroll record that nobody on the call thought to open.

So the step everyone treats as verification is the step where the least verifiable question gets asked. That is the inversion. The question that could be settled in one lookup is left to the resume, which is the one document in the process with nobody’s name on it but yours.

What does a countersignature ask instead?

One question, in three fields: the job title, the company and the dates.

A former employer answers it from the company’s records, with your claim in front of them and their memory kept out of it. How the request travels, the 7 days it is given and what happens when the two versions differ are told end to end in the countersignature post.

Sending requests is part of Free. No plan gates it. The pricing page carries the current table of what a paid plan does raise.

What comes out is narrow on purpose. A named person at a named company agreed three facts on a date, and the record carries a permanent identifier anyone can look up without an account while your profile is public.

Nobody is asked for an opinion. That is why it can be answered. A verifier who is asked to judge you has to think about what judging you might cost them. A verifier who is asked to read three fields off a record does not.

It also means the person answering never has to remember you. The request goes to whoever at that company handles verification, and you are not told who that is, or when they open it, or how many people there looked. Somebody who joined two years after you left can still answer correctly, because the answer sits in the records rather than in anybody’s head.

What a countersignature cannot do for you

The one thing it will never be is a reference: no field on the form asks whether you were good at the job, and no answer to that question is kept anywhere. Its other limits, and the fact that ClearHire records the company’s answer rather than auditing it, are set out on the same post.

A decline stays private. It is shown to you with the reason given, word for word, and it is published nowhere, to nobody. The note you attach to help a verifier find you reaches that verifier and nobody else, and the privacy policy says what is kept and for how long.

An unanswered request expires, and expired is not declined, because nobody said anything. Sending it again, and what the record keeps of each attempt, is covered on the same post.

So should you still line up references?

Yes. They answer a question no record can.

A countersignature settles whether the job happened. A referee describes what you were like inside it, which is worth hearing and cannot be looked up anywhere. The mistake is asking one source to carry both jobs, because that is how you end up with a process that verifies nothing and an opinion nobody trusts.

Keep the two apart and each gets better at its own half. Ask a referee for your dates and you get their best recollection, and a recollection that disagrees with the record by a month has turned a favour into a discrepancy. Ask a record whether you were good and you get nothing, because no payroll system holds a column for that. That is the split worth keeping: the facts come from the company’s records, and the judgement comes from a person who will stand behind it.

Three things make a referee’s time count.

Pick somebody who saw the work. A senior name who saw you in meetings can confirm that you were in the room, and that is all they can confirm; the person who reviewed what you produced can describe it, and describing is the whole job.

Ask first, then tell them which role and which dates, so they are not reconstructing your history live on a call with a stranger. A referee who knows what is coming can decide what to say about you in their own time, and what they decide in their own time is worth more to you than what they improvise.

Then give them the countersigned record, or your dates, so the factual half of the conversation is settled before the call and the rest of it is about you. A referee who is not being asked when you started can spend the whole call on the part only they know.

One thing neither source settles is the space between two jobs. A referee was not there for it and a record does not cover it, so explaining a gap is a separate job, and a shorter one than people expect.

How a claim moves

A claim moves one way. You claim it, the company is asked, then it is countersigned, declined or expired. Read how employment verification works.

A reference is one person’s opinion of you, and it is worth having. A countersignature is a company’s record of you, and it is the one a stranger can check.

Ahsan Mahmood, a full-stack React and Capacitor developer

Send this to someone

If this was useful to you it is probably useful to someone mid-search. The link goes to the post, not to a signup.

Written by

AM

Ahsan Mahmood

Builds ClearHire. Writes about the parts of hiring that are mechanical rather than mysterious — what a system can actually prove, and what it only appears to.

About ClearHire and how to reach us