The Credible Witness: A Referee Briefing Method for Late-Stage UK Bids

By the time a UK buyer asks for references, the written proposal has usually done its work. The shortlist is small, the commercial shape is understood, and the remaining question is not whether the supplier can describe good practice but whether someone else will confirm it. That is why the reference call deserves more preparation than it typically receives.

Why the reference call has moved to the centre

Procurement teams have become more cautious about written claims. A proposal can be polished until every risk sounds managed and every delay sounds instructive. A reference call introduces a different kind of evidence: a past client speaking without the supplier's editorial control. Buyers know this, which is why the call often sits late in the process, after the technical and commercial reviews have narrowed the field. It is less a courtesy than a final check on whether the project story holds up under questioning.

The practical consequence is uncomfortable. Suppliers spend weeks preparing their own team for the bid, then ask a former client to take a call with little more than a diary invitation. The referee may be willing, experienced and well disposed, but they are not prepared for the specific shape of a procurement interview. They may talk about the relationship when the buyer wants evidence on change control. They may praise the team when the buyer is testing whether the final invoice matched the quote.

What buyers actually ask

The questions tend to cluster around three perspectives, and each has its own logic.

Procurement

Procurement reviewers are usually testing contractual discipline. They may ask whether commitments were met, whether changes were raised early, how delays were handled, and whether the supplier was transparent about cost. A common question is whether the referee would appoint the supplier again. That question is rarely about affection. It is a proxy for whether the experience was predictable enough to repeat.

Technical leads

Technical reviewers want to know how the supplier behaved when the work became specific. Did they understand the legacy estate? Did they work well with in-house engineers? Were defects handled without defensiveness? Was the documentation usable after the team left? These questions are less about capability in the abstract and more about whether the supplier can operate inside an existing technical culture.

Finance

Finance reviewers often ask the plainest questions. Did the final invoice match the quoted figure? Were variations explained before they were incurred? Were there surprises in the payment schedule? A referee who can answer these questions with specifics is worth more than one who offers general praise.

Briefing is not scripting

The temptation, once a supplier understands these question areas, is to write the answers. That is a mistake. A referee who sounds coached will be discounted, and a referee who is asked to repeat a corporate message will often resist. The aim is not to put words in the client's mouth but to help them recall the evidence that matters.

A useful distinction is between briefing and scripting. Briefing gives the referee context: the project scope, the buyer's likely concerns, the names and roles of the people they may speak to, and the areas where their testimony will carry most weight. Scripting tells them what to say. The first preserves credibility. The second destroys it.

A good referee should also feel free to acknowledge difficulty. If a project had a tense fortnight, the buyer may already suspect it. A referee who says the issue was raised early and resolved without drama is more persuasive than one who claims nothing ever went wrong. Credible testimony includes boundaries. It does not require a flawless narrative.

A one-page referee brief

The most effective preparation is usually a single page, sent in advance and discussed briefly by phone. It should include:

• The project name, dates and scope, in plain terms.
• The referee's role and the parts of the work they saw directly.
• Two or three specific outcomes they can speak to, with enough detail to jog memory.
• The likely question areas, grouped under procurement, technical and finance.
• Any confidentiality limits or topics they should not discuss.
• A reminder that they may say they do not know, rather than speculate.

This is not a dossier. It is a memory aid and a boundary document. It respects the referee's time while making clear why the call matters.

Rehearsing the awkward answers

A short rehearsal is often worthwhile, particularly for referees who have not taken a procurement call before. The supplier should not supply answers, but can ask the referee to practise two or three responses in their own words. The most useful rehearsal question is usually some version of: what would you say if we asked whether the project was good value? Another is: how would you describe the one moment when the project was under pressure?

These are not traps. They are the questions that separate a useful reference from a pleasant one. A referee who has thought about them in advance will sound measured rather than surprised.

Closing the loop

After the call, the supplier should thank the referee and, where appropriate, ask whether there is anything they would like handled differently in future. This is not only manners. It keeps the reference relationship alive and gives the referee a reason to take the next call seriously. A reference call is not a character witness. It is the last piece of project evidence. Treat it with the same discipline as any other evidence, and the testimony will be stronger for it.