How to Run a Mock Grant Interview: A 45-Minute Panel Simulation

A useful mock grant interview is not a friendly discussion followed by “you sounded confident”. It is a controlled test of whether your funding case survives time pressure, generalist questions, specialist challenge and requests for evidence. It should reveal which uncertainty could still stop a panel from recommending your application.

This guide is for research grants and fellowships. Funding processes differ: some schemes use an applicant interview, some use a presentation and panel questions, and others rely on written peer review without interviewing the applicant. Your current invitation, assessment criteria and funder guidance always control the real format.

Start with the funder's actual decision system

Do not begin with a generic list of difficult questions. Begin with the current documents for your scheme: the interview invitation, assessment criteria, proposal, reviewer comments, applicant response, budget, work plan and any presentation instructions. These documents define the claims the panel can test.

For example, UKRI's Future Leaders Fellowships Round 8 guidance allocated 50 minutes per candidate, including a five-minute presentation and separate questioning blocks on the programme of work, leadership and impact, and candidate development and fellowship management. That format is useful evidence for that scheme and round, not a universal template. NIH's current simplified peer review framework instead groups many research project grant judgements around importance, rigor and feasibility, and expertise and resources. Use these official structures as examples of how funders organise uncertainty, then map your rehearsal to your own scheme.

Prepare a one-page mock panel brief

Give the mock panel a concise evidence pack at least two days before the session:

• the scheme name, round and official interview format;
• the published assessment and scoring criteria;
• your proposal summary, aims, work packages and budget;
• reviewer strengths, weaknesses and unresolved questions;
• your response to reviewers, if one exists;
• the three claims you believe are most vulnerable; and
• instructions to record evidence gaps rather than general impressions.

Keep the full application available for reference, but do not force every mock panellist to reread it line by line. The one-page brief helps them spend their limited preparation time on the decisions that could change the outcome.

Choose a panel that creates useful disagreement

A three-person mock panel is usually enough. Ask a subject specialist to test novelty, method and technical feasibility. Ask an informed generalist to test whether the case remains intelligible and important outside the immediate niche. Ask a third person to focus on delivery, risk, leadership, impact, environment or funder fit, depending on the scheme.

The strongest mock panel is not necessarily the most senior. Choose people who will read the brief, interrupt long answers, request evidence and distinguish a repairable answer problem from a genuine proposal weakness. Avoid using only close collaborators who already know the missing context.

A 45-minute mock grant interview schedule

Replace this schedule with the official timing when you have it. Otherwise, use the following compact rehearsal to test the complete decision chain.

Use questions that expose decision risk

Build the first question in each block from an unresolved uncertainty in the actual application. For example:

• What would remain unsolved if this project were not funded?
• Which result would make you abandon or redesign the central approach?
• Why is the strongest alternative method insufficient for this aim?
• What evidence supports the most ambitious claim in the proposal?
• Which dependency is outside your direct control, and what is the fallback?
• What expertise is missing from the current team?
• Why does this work require this scheme, duration and budget?
• What will a specific beneficiary be able to decide or do more safely?
• What would you remove first if the award were reduced?
• Which reviewer concern has not yet been fully resolved?

Follow-up questions matter more than volume. If the candidate says a risk is low, ask for the evidence, trigger and fallback. If the candidate claims impact, ask who changes behaviour, through what route and how that change will be observed. If the candidate claims novelty, ask for the strongest existing alternative.

Score evidence, not confidence

Use the scheme's published scoring system where possible. If the scheme does not provide a usable applicant scorecard, assess six dimensions from one to four. A score of one means the answer did not resolve the panel's concern; two means partially resolved; three means resolved with credible evidence; and four means resolved with clear evidence, limits and control.

• Importance: Is the problem specific, consequential and timely?
• Distinctiveness: Is the contribution clear relative to the strongest alternative?
• Approach and feasibility: Do the method, evidence, work plan and fallbacks support delivery?
• People and environment: Are the expertise, leadership, support and resources credible?
• Impact and value: Are the beneficiaries, route to use and observable outcomes specific?
• Answer control: Does the candidate answer directly, support claims and state boundaries?

Each score must include one observed sentence or omission. “Needs confidence” is not usable evidence. “Did not identify the data-access trigger or fallback after two follow-up questions” is usable because it identifies a repair target.

Separate answer repair from proposal repair

After independent scoring, classify every weakness. An answer problem exists when the evidence is in the proposal but the candidate did not retrieve or explain it. A proposal problem exists when the necessary evidence, decision or control is absent. A format problem exists when the answer is sound but too long, indirect or inaccessible to a generalist.

This distinction prevents rehearsal from becoming cosmetic. Shortening an answer cannot repair an unsupported feasibility claim. Rewriting the proposal cannot help if the candidate cannot explain its main contribution in the allotted time.

Run a repair session within seven days

Select the three weaknesses with the highest decision risk. For each one, create a repair card containing the panel question, the missing evidence, a direct first sentence, the supporting evidence, the boundary or fallback and the next likely follow-up. Then run a 20-minute second session using changed wording.

The second session should test transfer, not memory. Pass a repair only when the candidate can answer a rephrased question directly, provide relevant evidence and control the limitation without relying on a memorised script.

Common mock grant interview mistakes

Copying a generic question list

Generic questions can warm up the candidate, but the highest-value questions come from the specific scheme, proposal and reviewer concerns.

Using only specialists

A specialist-only panel may overlook whether the importance, impact and delivery case make sense to informed generalists who participate in real funding decisions.

Giving feedback during the answer

Unless the real format permits coaching, save feedback until after independent scoring. Otherwise the rehearsal measures how well the candidate follows hints.

Rewarding fluency without evidence

A smooth answer can still leave the panel uncertain. Require a claim, evidence, decision logic and control where the question demands them.

Running several full mocks without repair

One diagnostic session and one targeted retest usually produce more learning than repeated full interviews that preserve the same weaknesses.

Frequently asked questions

How long should a mock grant interview be?

Use the timing in your official invitation when available. Otherwise, a focused 45-minute rehearsal can test a short presentation, panel questioning, follow-up challenges and immediate scoring without pretending to reproduce every funder's process.

Who should be on a mock grant interview panel?

Use two or three people who test different uncertainties: a close specialist, an informed generalist and, where relevant, someone focused on delivery, impact, leadership or the funding scheme.

Should mock panel questions be shared in advance?

Share the assessment areas but keep the exact wording and follow-up questions private. Prepare evidence and decision logic rather than memorising scripts.

How should a mock grant interview be scored?

Score observable evidence against the current criteria for the scheme. Separate importance, approach and feasibility, people and resources, impact, and answer control instead of giving one vague confidence score.