How to interview subject matter experts for stronger tender answers

The tender is due next week. Your delivery lead has the knowledge, your bid manager has the questions, and everyone has a calendar that looks mildly hostile.

When you interview subject matter experts, the goal isn’t to collect a long explanation. It’s to capture the facts, proof and delivery detail that help an evaluator award marks.

A well-run discussion produces evidence an evaluator can score.

How do expert interviews strengthen tender answers?

To interview subject matter experts well, give them a short brief before the call, ask questions tied to the tender’s scoring criteria, and request evidence rather than polished prose. The purpose is to gather accurate, relevant evidence that answers the buyer’s question and supports the score available. Its purpose is scoreable evidence.

Subject matter experts own the technical truth. The bid team owns the structure and connection to the buyer’s question. Together, they turn delivery knowledge into evidence an evaluator can score.

Use the process below to prepare, run focused interviews and turn notes into stronger tender content.

Why expert interviews matter in bids

Your team may know the service inside out. That does not mean the evidence is visible in the bid.

Evaluators cannot award marks for background knowledge, good intentions or a claim that someone could explain brilliantly on a call. They score what is in front of them, against the published criteria.

The Procurement Pathway’s evaluation guidance makes this point in practical terms. Assessors judge against relevant criteria and record the reasoning behind their scores. The evaluator is the target audience for your answer, not your internal delivery team.

A good expert interview closes the gap between what your organisation does and what the buyer can see. It makes hidden evidence visible to the buyer.

The best expert input is not a page of impressive technical language. It is a clear account of who does what, when, how risks are controlled and what results prove it works.

This matters for charities, healthcare providers, public bodies and growing businesses alike. You are often bidding alongside delivery, dealing with home life, client work and the usual 4.47pm meeting that could have been an email.

Prepare a short brief around the tender question

Your content brief should fit on one page. It needs the buyer requirement, question, word count, score, deadline and the answer’s key messages.

Also include the exact information you need. Ask for talking points, examples, process steps, performance data, named roles, risks and controls. A 10-point question needs a stronger evidence plan than a five-point question, even when the word limit looks similar.

If the bid needs a clearer story before interviews begin, a bid win theme workshop can help the team agree what makes your offer credible and different.

Share questions in advance

Send the main interview questions 24 to 48 hours before the meeting where possible. This gives the expert time to research and prepare figures and examples before the call.

You are not ruining the surprise. You are giving them the chance to provide a useful answer.

Keep some follow-up questions back. They are there to test assumptions, pull out examples and explore points that only emerge during the conversation.

A good brief makes it easier for an expert to provide useful evidence.

Keep the conversation focused without shutting it down

Use practical interview techniques at the start: explain what the buyer is asking for, what the answer must prove and how long you have. Ten minutes of shared context can save half an hour of talking at cross-purposes.

Tell them you are looking for source material, not bid wording. It is a relief for most experts. They can talk about the work they know, rather than trying to write like a tender writer after a full day.

Open with the delivery reality

Ask them to walk you through what would happen if the contract started tomorrow.

What happens first? Who is responsible? What decisions need approval? Where could delivery wobble? How will the team spot that early?

This gets past vague statements such as “we provide a responsive service”. It gives you a delivery method, named ownership and controls.

Bring answers back to the buyer

Experts can go off on a technical tour. Good communication skills help you guide them back without cutting off useful detail. Use active listening to notice useful evidence, then ask a precise follow-up rather than interrupting.

Try: “That is helpful. For this question, the buyer needs confidence about mobilisation. What would they see in the first 30 days?”

Or: “Which part of that process reduces risk for the client?”

Guide the conversation back to the buyer’s requirement, whilst leaving room for the unexpected detail that could become the strongest line in the answer.

Questions that produce scoreable evidence

Use questions that make broad claims work harder. “Tell me about your experience” usually produces a history lesson. You need evidence an evaluator can recognise and verify.

Ask these questions during the interview process:

• What problem did the client have, and how similar is it to this buyer’s requirement?
• What did your team do that another provider may not have done?
• What technical information, controls or system detail would prove that capability?
• Who owned each key part of delivery?
• What happened in the first week, first month and first reporting period?
• What could go wrong, and what control prevents or manages that risk?
• What data, audit result, feedback or case study proves the approach worked?
• What changed for service users, staff, patients, residents or the client?
• What can we commit to in this contract, without stretching the truth?

Follow every broad answer with: “Can you give me an example?” Then ask for scale, date, result and source.

A claim such as “we have extensive experience” is unlikely to earn much on its own. A comparable project, delivery timescale, named role and measurable outcome gives the evaluator something reliable to score.

Specific answers should help the evaluator apply those published criteria and make the evidence reliable to score.

Separate evidence from opinion

Experts often have strong opinions about what good looks like. That can be useful, but a tender answer needs more than a confident view.

Write down the difference as you listen:

What you hear	What the bid needs
“Our team is highly responsive”	Response times, escalation route, named owner and reporting method
“We know this sector well”	Relevant contract example, scale, challenge and outcome
“Our system is secure”	Controls, accreditations, testing, access arrangements and ownership
“We work in partnership”	Meeting cadence, decision-making process, issue management and feedback route

Keep the personality, but turn each promise into something the buyer can assess.

Keep an evidence log with the source, date, owner and approval status for every material claim. If you cannot verify it, remove it or write a more honest proposed commitment.

A well-maintained evidence log protects accuracy, approval and traceability.

When experts have limited time

Some experts are generous with their knowledge but impossible to pin down. Others join calls between operational issues and are already watching the clock.

Plan for reality, not the ideal diary. Adapt your interview techniques to the expert’s availability.

Use a priority question list

Pick the three questions that would leave the biggest holes if unanswered. Ask those first.

A 20-minute call can still give you useful material when it has a clear purpose. You don’t need a perfect life story. You need the proof points that answer this tender question.

Set a stopping time at the beginning. The bid owner can follow up offline on documents, figures and points that need checking.

Use asynchronous input properly

Voice notes, short questionnaires and comments in a shared document can work well when diaries refuse to cooperate.

Keep each request narrow. Ask for one case study, one process or one risk area at a time. A document with 18 open questions isn’t asynchronous working. It’s homework with worse branding.

Give an expert a deadline, a named contact and a simple format for replies. Ask for source documents where relevant, not rough sales copy.

A short, well-prioritised request is more useful than an unrealistic long questionnaire. For teams needing support across several bids, bid consultancy services can offer an outside view while leaving ownership with the people who know the organisation best.

Turn technical language into plain English

Plain language does not mean making an answer basic. It means making it clear.

Technical experts may use internal acronyms or assume a buyer understands every system, process and regulation. Sometimes they do. Often, the evaluator still needs to see what that specialist knowledge means in practice.

Ask for the explanation twice

First, let the expert explain it in their normal terms. Then ask: “How would you explain that to a senior commissioner who does not use this system every day?”

The second answer often gives you the usable version.

The Office for National Statistics style guidance recommends active voice because it makes clear who is doing what. That is exactly what a tender evaluator needs.

Keep the proof, lose the fog

Replace abstract phrases with actions.

Do not write, “We use an integrated quality assurance methodology.”

Write, “Our contract manager checks weekly performance data, records actions in the risk log and reports progress at monthly governance meetings.”

Keep the technical information where it proves capability. Then check the final wording with the SME. They should recognise their process and confirm that the simplification has not changed the meaning. The same principle applies whenever specialist material is simplified for the tender response.

If this is a regular struggle, evaluator-focused bid training helps technical teams see the difference between what they meant to say and what an evaluator can actually score.

The aim is simple: remove the fog, not the evidence.

Use transcripts and AI without handing over judgement

Recording and transcription can save time. They can also create a false sense that every word is correct because it arrived in a neat document.

A transcript captures raw insights, but remains unapproved source material rather than verified evidence.

Get consent and check the data

Tell everyone if a call will be recorded or transcribed. Check where the recording is stored, who can access it and whether it includes client, patient, employee or commercially sensitive information.

The ICO includes meeting recordings, summaries and draft documents amongst AI business-tool use cases. Its AI and data protection guidance is a sensible starting point for UK organisations handling personal data.

Verify every material detail

AI tools can help organise notes, identify possible themes and suggest follow-up questions, but they cannot know whether a figure is current, a case study is approved or a proposed commitment can be delivered.

Check names, dates, percentages, accreditations, outcomes and technical statements against the source. Keep the expert involved where the wording carries contractual weight.

A useful prompt is not “write the answer”. It is “using only these approved notes, list the evidence gaps and follow-up questions”. You remain responsible for the judgement.

Recording saves time only when a responsible person checks every material fact.

Turn interview notes into a stronger answer

An expert interview is only useful when its information reaches the right question, in the right shape.

The scoring criteria should decide what survives. Don’t paste a transcript into a draft and hope it sorts itself out. It will mostly repeat itself, with good points buried among interesting but irrelevant ones.

Map notes to the scoring criteria

Start with the tender question and mark scheme. Pull out the buyer’s required elements, then place each useful insight against one of them.

A simple structure works:

• Answer the requirement directly.
• Explain the method, including roles and timescales.
• Add evidence beside the relevant claim.
• Show the benefit for this buyer.

This content strategy links the buyer’s requirement to the evidence and final structure. It keeps the answer focused and makes the benefit for the buyer clear. It also shows where the interview left a gap, before you are staring at a blank section on the final afternoon.

Review the answer like an evaluator

Ask someone who did not write it to read the answer against the question.

Can they find the commitment in the first paragraph? Can they see proof near the claim? Does the evidence actually match the buyer’s requirement? Does the price and delivery model support what you are promising?

An independent bid review can test those points before submission. It can identify unclear commitments, unsupported claims and gaps between the proposed delivery model and the evidence provided.

If you’d value an external perspective, explore the available support before submission. Mapped evidence is more valuable than a complete transcript.

Common mistakes to avoid

A strong interview can still lead to a weak answer when the process slips.

Avoid these familiar problems:

• Asking for “thoughts” instead of asking for facts, examples and documents.
• Inviting too many people to one call without a clear role for each person.
• Letting the expert rewrite tender prose when they should be confirming delivery detail.
• Treating old case studies as current proof without checking what has changed.
• Assuming a buyer understands internal jargon or acronyms.
• Relying on a compelling thought leadership story that doesn’t answer the scored question.
• Leaving approval of key commitments until the last day.

A repeatable interview process protects bid quality and the people delivering the work. It also gives your team a stronger evidence base for the next bid.

FAQs

Should we interview every subject matter expert live?

No. Use a live call when the subject is complex, the answer needs probing or several teams need to agree a position. Use written questions or voice notes for focused evidence requests, document checks and straightforward follow-up.

How long should an SME interview last?

Most tender interviews work well in 20 to 45 minutes. The right length depends on the question, not the number of people invited. Send a clear agenda and cover priority questions first.

Should subject matter experts approve the final tender answer?

They should approve factual, technical and contractual details that sit within their responsibility. The bid owner should approve the final answer as a whole, including its fit with the tender question and evaluation criteria.

What if an expert gives us no useful evidence?

Be honest about the gap. Ask for documents, another relevant contact or a proposed delivery commitment with a named owner, timeframe and measure. Do not turn a vague claim into a confident-sounding fact.

Key takeaways

• Brief experts on the score, question, deadline and evidence needed.
• Ask for delivery detail and proof, not polished tender wording.
• Keep interviews short, focused and tied to buyer requirements.
• Translate jargon into clear actions, responsibilities and outcomes.
• Verify every figure, claim and commitment before it reaches the final draft.
• Review answers through evaluator eyes before submission.

Protect the quality, and the people doing the work

A good SME interview gives your bid team material they can use. A great one leaves the expert feeling heard, the delivery reality accurately represented and the evaluator with less work to do.

An independent red-team can reduce the emotional load when deadlines tighten.

Outside support complements your delivery team’s knowledge. It doesn’t replace the people doing the work. It gives them a clearer, more objective view of what may be missing or unclear.

If your team needs a clearer process across future bids, consider a bid review retainer. You can also Book a free fit call to talk through what is costing you marks and what support would genuinely help.

A practical review gives your team a clearer view of what is missing, unclear or difficult for an evaluator to score.