7 Checks You MUST Make Before Submitting an EU Proposal

Picture two proposals failing on the same day. Both are hypothetical. One is declared ineligible because a mandatory requirement in the call was missed. The other passes every threshold, scores well and is still never funded.

Both teams believed their proposals were finished. They needed completely different checks.

Some checks below prevent rejection. Others decide where you rank. Knowing which is which tells you what cannot be skipped when time runs short.

1. Fit with the topic and its expected outcomes

Type: ranking, with a rejection risk.

Inspect: each expected outcome in the topic text, and where the proposal answers it.

Warning sign: an outcome addressed only in the introduction, or not at all.

Action: check that each expected outcome maps to an objective, a work package and an indicator. Close the gaps or explain them.

A weak fit costs points. A clear mismatch costs more: in Horizon Europe, a proposal whose content does not correspond, wholly or in part, to the topic description is ineligible.

2. Eligibility, admissibility and submission requirements

Type: rejection risk. Non-negotiable.

Inspect: mandatory sections, template version, minimum consortium composition, call-specific conditions and page limits. (In Horizon Europe, pages beyond the limit are made invisible to evaluators.) Rules vary by programme, action type and work programme, so check the current call documents, not last year’s habits.

Warning sign: someone says, “We checked that on the last bid.”

Action: draw up a compliance checklist from the call text itself, with one named owner. Submit a complete version early. On the Funding & Tenders Portal you can submit several times before the deadline; each submission overwrites the previous one.

3. A clear, evidenced intervention logic and methodology

Type: ranking.

Inspect: the chain from problem to objectives, activities, outputs and outcomes.

Warning sign: objectives that restate the topic, or a methodology that describes what you will study but not how.

Action: ask a reviewer to draw the logic from the text alone. Wherever they have to guess, rewrite.

4. Partner roles, capacity and complementary expertise

Type: ranking.

Inspect: what each partner does, why they are the right organisation to do it, and where that is evidenced.

Warning sign: partners described by reputation rather than by task, or two partners doing the same job.

Action: check that each partner has at least one task they are uniquely placed to deliver.

5. Consistency between tasks, resources, budget and timetable

Type: ranking, and credibility.

Inspect: work package descriptions against the Gantt chart, person-months, deliverables and budget.

Warning sign: a task led by a partner with almost no effort allocated to it.

Action: run a dedicated consistency pass, ideally by someone who did not write the work plan.

For example (hypothetical): work package 3 says the pilot runs from month 10 to month 24. The Gantt chart shows months 14 to 30. The pilot lead has two person-months. None of these errors is fatal alone. Together, they tell an evaluator the plan has not been checked.

6. Credible impact pathways, indicators and uptake responsibilities

Type: ranking.

Inspect: who will use the results, how they will get them, and what will be measured.

Warning sign: indicators with no baseline, or exploitation described as “partners will disseminate widely”.

Action: name the users, the route to them and the partner responsible for each step. Give each key indicator a baseline and a source.

7. An independent challenge and final submission readiness

Type: both.

Inspect: whether anyone outside the writing team has read the whole proposal against the evaluation criteria.

Warning sign: the only reviewers are the people who wrote it.

Action: schedule an independent review early enough to act on. Then complete the mechanics: final PDF, page count, every partner’s details confirmed, submission by the owner with time to spare.

Rejection versus ranking. Check 2, the scope question in check 1 and the mechanical half of check 7 can end a proposal outright. Everything else decides your position. Clearing a threshold only earns you a place in the ranking; in competitive calls, proposals above threshold compete for a limited budget, and many go unfunded.

Before you submit. Polish is visible from across the room. Inconsistency is visible only to the person checking the Gantt chart against the budget, and that is precisely what an evaluator does.

Put these seven checks on the agenda of your final readiness meeting, with a named owner for each. Better still, run them a fortnight earlier as well, while there is still time to act on what you find.