Notes on EU evaluation

Proposal Readiness Audit Before Submission

← All articles

A proposal can be technically sound, led by credible organisations and still lose marks because an evaluator cannot verify a claim from the text in front of them. That is the purpose of a proposal readiness audit: to test the submitted document against the applicable evaluation form before the real panel sees it. Not to confirm that the team has worked hard, but to identify where the evidence required for a score is absent, vague, inconsistent or buried.

For Horizon Europe, Digital Europe and Erasmus+ applicants, this matters late in the process because a deadline closes more than a document. It closes the opportunity to repair an unconvincing impact pathway, reconcile a work package with its deliverables, or show why a consortium is capable of doing what it promises. You only get one chance to submit.

What a proposal readiness audit is testing

A readiness audit is not a general review for grammar, style or plausibility. Those can matter, but they are not the primary question. The central question is whether the proposal gives an evaluator sufficient, located evidence to award marks under the published award criteria and their sub-criteria.

That distinction is material. An internal team may know that a partner owns a key facility, has access to a pilot site or has delivered comparable work before. An evaluator can only score the evidence presented in the proposal and annexes permitted by the call. A claim that depends on knowledge outside the document is not a strength in the evaluation room.

The audit should also separate admissibility and eligibility from quality. Page limits, submission format, participant conditions, country requirements and call-specific eligibility rules can disqualify a proposal or make parts of it ineligible. They are not normally remedied by a higher Excellence score. Once those checks are clear, the audit turns to the award criteria, the weighting and any thresholds specified for that action.

Read the draft through evaluator seats

A credible proposal readiness audit uses distinct readings rather than one broad impression. Evaluation panels do not reward a document for being generally persuasive. They assess defined criteria, often under time pressure, using the evaluator brief and scoring descriptors attached to the call.

Excellence: can the evaluator follow the logic?

The Excellence reading examines whether objectives are clear, measurable and proportionate to the action; whether the methodology is credible; and whether relevant state of the art, interdisciplinarity, open science or other call-specific elements are properly addressed. The precise sub-criteria vary by programme and type of action, which is why a generic checklist is unreliable.

Frequent losses occur where objectives are aspirations rather than testable outcomes. “Develop an innovative platform” is not an objective unless the proposal establishes what the platform will do, how performance will be assessed, against what baseline and at which stage. The same applies to methodology. A diagram of work packages is not methodological justification if it does not explain why the approach will answer the research or implementation question.

An audit should quote the passage on which a concern rests. “Methodology is weak” is not an actionable finding. “Task 2.3 promises validation, but specifies no sample, comparator, success criterion or responsible beneficiary” is.

Impact: is there a causal route to the claimed result?

Impact is commonly where internally coherent proposals become overconfident. A market estimate, policy ambition or statement that stakeholders are interested does not by itself demonstrate a credible pathway to outcomes and impacts.

The evaluator needs to see the chain: outputs, users or adopters, uptake activity, assumptions, barriers, timing and indicators. Exploitation, dissemination and communication should be proportionate to the action and connected to named results. A list of conferences, publications and social media activity may show effort, but it does not show who will use which result or why that use is likely.

This is also where inconsistencies become expensive. If the impact section forecasts adoption in three Member States, but the pilot work only involves one site and the budget contains no credible replication activity, an evaluator can reasonably treat the claimed scale as unsupported. The audit should test such joins across sections, not read each section in isolation.

Implementation: can the plan actually deliver?

Implementation scrutiny begins with the work plan, but does not end there. Evaluators look for logical work package structure, realistic effort, dependencies, milestones, deliverables, risk management, governance and the allocation of resources. They compare them against the technical ambition already claimed under Excellence and the benefits promised under Impact.

A common significant weakness is a plan that names risks without explaining triggers, likelihood, mitigation ownership or the consequence of failure. Another is a milestone that merely repeats a deliverable title. A milestone should help management decide whether the project can proceed, redirect effort or escalate a problem.

Budgets and person-months are part of the evidence. A proposal that assigns minimal effort to a data-intensive validation exercise, extensive stakeholder engagement or complex coordination invites questions about feasibility. It may still be viable, but the draft must explain the operating model well enough to support that conclusion.

Consortium capacity: do the named partners cover the critical work?

Consortium quality is not established by prestige alone. The relevant question is whether the participants collectively possess the expertise, infrastructure, networks and operational capacity needed for the tasks assigned to them.

An audit compares partner descriptions with task ownership. Where a small organisation is responsible for a technically central work package, the proposal should make its capacity visible. Where two partners appear to perform similar roles, the governance and division of labour must explain why both are necessary. Gaps are often found not in CV-style descriptions but at the handover points between work packages, countries and disciplines.

Why disagreement is useful evidence

Two competent evaluators can read the same paragraph differently. That is not merely noise. In a competitive call, it can be a signal that the wording permits more than one interpretation, or that supporting evidence is too weak for an unambiguous score.

A useful audit preserves that disagreement rather than averaging it away. If one reader sees a credible exploitation plan and another sees a list of promotional activities, the team should inspect the cited passages and resolve the ambiguity. The aim is not artificial consensus. It is to remove avoidable grounds for a lower reading before submission.

This matters particularly where a draft sits near a score-band boundary. EU forms commonly use a 0-5 scale, and some procedures permit half-point scoring, but thresholds, weighting and score-band descriptors must always be checked against the published form for the call. A proposal can meet an individual threshold and still be uncompetitive once weighted scores and ranking are applied. No readiness review can predict the quality of the competing field.

A practical audit sequence before the deadline

The most useful review is conducted when the team still has authority to make substantive changes. Running it on the final evening may identify defects, but it cannot create time for partners to reconcile KPIs, revise task allocations or approve a changed impact narrative.

First, fix the applicable evaluation form and version. Map every criterion and sub-criterion to the relevant proposal passages. This prevents the familiar mistake of reviewing a Research and Innovation Action as if it were an Innovation Action, or carrying assumptions from an earlier call into a new one.

Second, score each criterion independently against the descriptors and record the evidence used. The score is less valuable than the audit trail behind it. A defensible finding identifies the criterion, the passage, the reason it does or does not meet the descriptor, and the consequence for the likely score.

Third, test cross-document consistency. Objectives should reappear as work package outputs, milestones, KPIs, resources and impact indicators. Named end users should appear in engagement plans and, where appropriate, consortium roles. Risks should correspond to actual dependencies. Contradictions are often more damaging than missing polish because they make an evaluator doubt the underlying plan.

Fourth, prioritise corrections by score effect and repairability. A missing evidence base for a central impact claim may justify immediate rewriting. A minor stylistic inconsistency may not. This is a commercial decision as well as an editorial one: use the remaining time where it can materially improve the evaluator’s reading.

BidShark applies this logic through independent automated readings against a marking scheme transcribed from the published form for the relevant action, followed by evidence-based adjudication where scores materially differ. Its automated report is not a human verdict. The Evaluation + Expert Q&A package is the point at which a person who evaluates EU proposals reads the report and answers fifteen written questions.

Do not wait for a perfect draft to subject it to sceptical reading. Wait too long, and the audit becomes a post-mortem conducted before submission. Run it while a weakness can still become a decision, a task, a budget line or a sentence an evaluator can actually score.

About 15 minutes · before the panel

Evaluate
before you
submit

One proposal. One deadline. One opportunity to improve it before submission. Upload your proposal and the call, and get the score, the reasons and what to fix.

Start
Chat with us on WhatsApp