The Reference Call You're Not Preparing For

The reference call rarely fails the way candidates expect. UK law requires that any reference an employer chooses to give must be truthful, fair and not misleading, which is why former managers almost never volunteer anything sharp on the phone. The risk is the opposite: a referee who liked you, who genuinely wanted to help, but who hadn’t been told what the call was actually for — and who, asked to describe your strengths cold, produces a description that could have applied to almost anyone. Lukewarm references are the silent killer of the late-stage offer.

This piece is about the short, specific brief that turns a generic reference into a useful one. It is the part of the offer process candidates most reliably leave to chance, and the part that has the cleanest fix.

What the reference call is actually testing

The hiring manager has already decided they want to hire you by the time references are run. The call is not assessing whether you’re a strong candidate in the abstract. It’s testing two narrower things:

• Specificity. Can your referee describe a concrete moment where they watched you do the thing the role requires? Or do they speak in adjectives?
• Warmth. Does the referee sound, on the phone, like they actively want you to get the role? Or do they sound like they're filling out a form?

Both of those things depend almost entirely on whether the referee has been briefed. A talented former manager who has been given no context will default to generic praise, because that’s the safe move when you don’t know what’s being asked. The same person, told what the role is, what the company cares about, and which stories to draw on, will sound like they spent the morning preparing — because they did.

The contrast is stark in practice. The weakest reference calls a hiring manager takes tend to lean entirely on generic adjectives — “team player,” “smart,” “well-liked” — and nothing else. The strongest are the ones that contain a specific moment a hiring manager can picture. “I’d hire her again tomorrow” lands because it commits the referee to a concrete claim. It is not a stronger truth than “she was a real team player.” It is a more useful one.

The silent-killer warning

This is the part candidates rarely internalise. You’re not just preparing your referee to say good things. You’re preparing them to say specific things, with the right level of energy, in answer to questions they haven’t seen yet.

The three-bullet brief

The whole job of preparing a referee fits in a short email. Three bullets. Send it twenty-four to forty-eight hours before the call. Any longer in advance and they’ll forget; any later and they won’t have time to read it.

• Bullet one — the role and what the company says they care about, kept brief. Two sentences maximum. "It's a Head of Growth role at a Series B fintech. They've told me the three things they want are someone who's run paid acquisition at scale, someone who can hold a CFO conversation about LTV, and someone who can rebuild the team after a churn event."
• Bullet two — the specific story you'd love them to tell if it comes up. The X project where you did Y. Not a request to lie; a reminder of which true story matches the role. "If they ask about a hard call you saw me make, the obvious one is the decision to kill the paid social channel in 2024 — you were the one I came to before I did it."
• Bullet three — how you'd describe your biggest growth area, with the explicit caveat that their version is more credible than yours. "On growth areas — I'd say my instinct is to under-delegate when the stakes are high. But your version is more credible than mine, and I'd rather you spoke honestly than parroted my framing."

That third bullet is the one that surprises candidates. The instinct is to keep growth areas off the agenda. Don’t. Reference checkers will ask the question regardless, and the answer that lands well is one your referee has prepared for, in your voice, with permission to be honest. The answer that lands badly is the one they invent on the spot.

Vague reference, briefed reference

To make this concrete, here’s what the same referee might say about the same candidate, before and after a brief. The candidate is a senior product manager. The role is a Director of Product position.

The “before” reference is positive. It’s also doing nothing. A hiring manager hearing it will come off the call uncertain, because every candidate’s former manager says some version of this. The “after” is the same referee, the same truthful underlying view, transformed by the fact that they were briefed on what the role asks and which story to lead with.

What to send your referee twenty-four hours before the call

The brief above is the substance. The mechanics matter too. Send your referee a short message, ideally by email so they can re-read it before the call, the day before the call is scheduled. Keep it to three things:

• The role and the company, with one sentence on what the panel said they're scoring most heavily. Give them the language to mirror. If the company keeps using the phrase "commercial instinct," your referee should hear that phrase before the call.
• The two or three projects that map most cleanly to the role. Don't tell them what to say about each one. Just remind them which ones exist. Memories are imperfect; this is permission to skip the irrelevant ones.
• The name of the person calling, the day and time of the call, and how long it will take. If your referee is a senior person with twenty things on their plate, the prep that decides the call is whether they were in a quiet room for it.

The whole message should be under a hundred and fifty words. Any longer and you’re managing them, which is the wrong dynamic. The point is to give them the rails. They’ll do the talking.

Choosing the referee in the first place

A briefed weak referee will still underperform an unbriefed strong one. So the chain of decisions starts further back than the brief itself.

The strongest reference, in almost every case, is a former line manager who has watched you operate in the function the new role requires. The second strongest is a senior peer who relied on your work to do theirs. The weakest, and the one candidates lean on far too often, is a former colleague who liked you personally. Hiring managers can usually tell within the first minute or two which category they’re talking to.

If the choice is between a senior name who barely knew you and a more junior name who saw you do the work, take the junior name every time. Specificity beats title in reference calls, by a wide margin.

It is also worth remembering that UK reference law shapes what the conversation can cover. Employers are not required to give references unless contract or sector regulation specifies it, and any reference they do give must avoid information related to protected characteristics, absences, or spent convictions unless objectively relevant. That is why most reference calls feel guarded. It is also why a briefed referee, sticking to specific work, can stand out so cleanly: they are giving the hiring manager the one thing the legal frame still allows in full — a concrete account of what you did.

The thank-you afterwards

One last move that costs nothing. After the call, send your referee a short message thanking them and telling them what happened — including if it didn’t go your way. The reason is partly courtesy and partly self-interest. The next time you need them, they’ll remember that you closed the loop, and they’ll pick up the phone again.

If you’re preparing for the offer stage more generally, the follow-up-after-interview piece handles the same window from the candidate side, and the recruiter-silence guide covers what the silence between verbal and signed actually means. For the wider arc of late-stage offers, the salary-band piece is the companion to this one.