Expert Q&A Proposal Feedback Before Submission
A proposal team can spend six months building a consortium, refining the intervention logic and reconciling partner contributions, then lose points because a claimed outcome is not evidenced where an evaluator expects to find it. Expert Q&A proposal feedback is useful at precisely this point: after an evidence-based assessment has identified the weaknesses, but before the submission deadline turns every unresolved judgement into a permanent feature of the application.
This is not a substitute for reading the call, checking admissibility and eligibility, or writing a coherent proposal. It is a way to test difficult decisions against someone who understands how EU evaluators distinguish an ambitious claim from a credible one. The value depends on the questions asked, the quality of the underlying assessment and the time left to act on the answers.
A score tells you where to investigate. Q&A tells you what to change.
An evaluation report should first establish the problem under the applicable award criteria. For Horizon Europe, that commonly means Excellence, Impact and Quality and Efficiency of the Implementation, assessed through the specific sub-criteria set out in the call documentation and evaluator brief. Digital Europe and Erasmus+ use their own forms, thresholds, weightings and descriptors. These are not interchangeable.
A score of 3.5 or 4 is not a drafting instruction. It signals that the criterion is good, but that one or more shortcomings prevent it reaching the next score band. The useful next question is not, “How do we increase the score?” It is, “Which assertion, omission or inconsistency caused an evaluator to withhold the higher score, and what evidence would resolve it?”
That distinction matters because a lower score can arise from very different defects. An Impact section may have credible KPIs but no baseline, a persuasive exploitation route but no owner for each route, or a convincing European-scale ambition that is not matched by dissemination resources. An Implementation score may be limited by an underdeveloped critical path, unclear decision rights, an implausible person-month allocation or risk mitigation that merely restates the risk.
The report identifies passages and applies the relevant marking scheme. Expert Q&A then allows the proposal lead to test the proposed remedy with a person who has evaluated EU proposals and has read that report. It is a narrower and more valuable intervention than generic comments on style.
What a real evaluator can clarify
The questions worth asking are those on which an internal team has competing views, or where the assessment has revealed a material ambiguity. Fifteen written questions is enough to resolve priority decisions if they are disciplined. It is not enough to ask for a wholesale rewrite of a complex application, nor should it be treated as an informal promise of how a real panel will score the final version.
Excellence: is the method convincing on the page?
Questions under Excellence should test whether the claimed advance is intelligible, evidenced and proportionate to the work proposed. For example: does the state-of-the-art comparison establish a genuine gap, or does it list prior work without showing what remains unsolved? Is the methodology sufficiently specific to demonstrate feasibility, or has the team confused technical detail with a credible research design?
An evaluator can distinguish between a section that needs sharper signposting and one where a fundamental methodological dependency has not been addressed. That difference determines whether the remedy is a redraft of two paragraphs or a change to a work package, partner role or validation plan.
Impact: are the pathways owned and measurable?
Impact is often where confident internal language meets the evaluator’s demand for causality. A question may concern whether a pathway from project output to uptake is sufficiently credible, whether a target user has a defined route into validation, or whether expected outcomes and wider impacts have been separated rather than blended into a single benefits list.
The answer should be tied to the proposal’s actual claims. If a draft says it will influence standards, procurement or policy, the issue is not whether that sounds desirable. It is who will do the work, through which mechanism, when, with what resource and what evidence of progress. Where a KPI measures activity rather than adoption, an evaluator can say so plainly.
Implementation: is the plan capable of carrying the promise?
Implementation questions are often the most commercially useful because they expose tensions between ambition and delivery. A consortium may ask whether the governance model is adequate for a cross-border pilot, whether the risk register is a credible management tool, or whether effort is visibly aligned with the work plan.
The answer cannot replace a detailed budget review or legal eligibility check. It can, however, identify when a proposal’s implementation narrative contradicts its Gantt chart, when a work package lead lacks the authority implied by their role, or when a milestone records activity rather than a decision-ready result.
Ask questions that permit an evaluative answer
Vague questions produce vague value. “Is the Impact section strong enough?” asks an evaluator to repeat the report. A better question identifies the contested claim, names the relevant sub-criterion and presents the available options.
For instance: “The report identifies insufficient evidence that our pilot sites can support the stated scale-up pathway. Is a letter of commitment and a revised task on replication likely to address the weakness, or does the application need a different exploitation structure?” This gives the expert something concrete to assess.
Likewise, if two independent readings diverged on a criterion, use the Q&A to interrogate that disagreement. A difference of more than a point is not noise to average away. It usually indicates that the section permits more than one defensible interpretation. Ask what led to the less favourable reading, whether the issue is evidence, structure or terminology, and what a revised passage must make unambiguous.
Avoid spending questions on matters already answered by published call documents. Admissibility, eligibility, page limits, mandatory annexes and conditions of participation should be checked directly against the call. Expert judgement is most valuable where the rules leave room for evaluative judgement.
The controlled sequence matters
The order of operations protects against superficial advice. First, the proposal is assessed against the hand-transcribed evaluation form for the relevant type of action and version. Specialist readings examine Excellence, Impact, Implementation, consortium capacity, unsupported claims and sector-specific issues independently. Where materially different readings emerge, evidence is exchanged and the score is adjudicated on the official 0-5 scale.
Only then should an expert receive the report and answer the team’s questions. Without that foundation, Q&A can become a conversation driven by the loudest concern in the room rather than the most costly weakness in the evaluation summary report.
BidShark’s Evaluation + Expert Q&A package follows this division deliberately. The scoring and report production are automated; fifteen written answers are provided by a person who evaluates proposals for EU programmes and has read the report. It does not represent a human panel review of the whole draft, and it does not predict the final outcome. It creates a documented opportunity to challenge and refine the decisions that the assessment has made visible.
Use the answers to make decisions, not decorate the draft
After the responses arrive, assign each answer to an owner and a location in the proposal. Decide whether the change affects a claim, an evidence source, a work package, a KPI, a budget allocation or the consistency between sections. Then check the amended text against the original finding. If the change improves one criterion while creating an inconsistency elsewhere, resolve that before submission.
Do not respond to every finding with more text. An evaluator has limited time and reads against defined sub-criteria. Sometimes the correct remedy is to remove an unsupported assertion, narrow an overextended impact claim or turn a vague deliverable into a verifiable output. A shorter, evidenced statement is usually safer than a grander one that the proposal cannot carry.
You only get one submitted version. The disciplined use of expert Q&A proposal feedback is not to seek reassurance that the proposal is good. It is to force the remaining uncertainties into explicit questions while there is still time to make defensible changes.