Application rejected: how to read donor feedback

Everything has been written about how to submit an application. Almost nothing about what to do with a rejection. Yet rejection is the standard outcome, because most calls approve a minority of what they receive, so a team that cannot work with feedback spends years repeating the same mistakes.

The volume of feedback differs by an order of magnitude between donors. EU programmes deliver a formal report with a score for every criterion plus a list of strengths and weaknesses. Private foundations often stop at one paragraph. Some donors write nothing at all, although they would answer a direct request.

So this guide covers how to identify the type of rejection, how to read an evaluators report, what you can appeal and within what deadline, and how to turn feedback into a resubmission plan.

Start by identifying the type of rejection

Three different rejections look almost identical in the letter while meaning opposite things. Until you know which one is yours, any work on the application amounts to guessing.

The proposal missed the score thresholds

This is a rejection on merit. Evaluators scored below the threshold on at least one criterion, so the ranking no longer matters. The content needs rewriting: methodology, impact justification, implementation plan.

In this case the most useful signal is the distribution of scores across criteria. A proposal with a high score on excellence and a low one on implementation has different problems from a proposal with evenly middling scores.

Scores above threshold, but outside the call budget

The most common situation in large programmes, and also the most frequently misread. The proposal passed evaluation and entered the ranked list, although the topic budget ran out above your position.

Here the content may be fine. Rewriting everything from scratch actively hurts, since you risk breaking the parts that earned high scores. Instead the work sits in a difference of a few tenths of a point, in choosing a topic with lower competition, and in the timing of submission.

A practical benchmark: if your score sits tenths of a point from the funding line, resubmitting nearly the same proposal in the next round is a rational strategy. If the gap runs to several points, that is a rejection on merit.

Screened out before evaluation

The third type, the most annoying and the cheapest to fix. Nobody read the proposal at all, because it failed the eligibility checks: the wrong type of applicant, a missing mandatory document, a format breach, a mismatch with the call conditions.

EU programmes call these two checks admissibility and eligibility, and they happen before a single expert sees the proposal. Ukrainian state calls follow the same logic. The NRFU handbook for competition commissions describes the mechanics plainly: when an application fails the formal screening, the system automatically emails the project supervisor with a comment on the reason.

How much feedback each type of donor gives

Before asking for feedback, it pays to know what the call conditions entitle you to.

EU programmes: a full report with scores

The most detailed level. An applicant receives an evaluation result letter together with a summary report from evaluators, carrying a score per criterion and text comments on strengths and weaknesses. For single-stage calls that arrives roughly 5 months after the deadline, and for two-stage calls approximately 3 months after stage one and 5 after stage two.

One detail about the score structure matters. The official briefing materials for experts state directly that from the 2026-2027 work programme the evaluation of impact is simplified, and the scale and significance of contributions are no longer considered separately. So comments written to older templates no longer match the current criteria.

Ukrainian state programmes with points-based scoring

The Ukrainian Cultural Foundation and the National Research Foundation both work with points and report the outcome with a comment. Vlasna Sprava adds points-based scoring from 1 September 2026, which changes the nature of rejection: an application used to either meet the conditions or fail them, and now applications compete against each other.

For an applicant that means a new type of rejection in the Ukrainian context: everything is formally correct, although somebody else scored higher. Looking for an error in the paperwork then makes no sense, because the work belongs in the quality of the business plan or the project logic.

Donor projects and private foundations

The range here is widest. Some programmes send a structured assessment, while others stop at a notification of the decision. In programmes where a local team or partner organisation decides, feedback is often available on request, although you have to ask for it separately.

One special case involves schemes where rejection remains possible after you have already spent money. In cashback mechanisms a refund may be declined after the loan has been drawn, and the reasons there are far more concrete than evaluation comments: failing the criteria, buying assets outside the eligible list, spending off-purpose, or an incomplete document package.

When there is no feedback at all

Three routes work. Send a debriefing request with specific questions instead of asking someone to explain the rejection. Contact the national contact point for your thematic area, because the list of NCPs in Ukraine is public and the consultation costs nothing. And compare your proposal with the descriptions of funded projects that most donors publish, since that supplies the feedback nobody wrote for you.

How to read the report without deceiving yourself

Two typical mistakes at this stage: reading only the total score, and treating every comment as a verdict.

A criterion score and a comment are different data

A comment describes what the evaluator saw. A score shows how much that affected the decision. A weakness mentioned in the text but paired with a high score on the same criterion is a suggestion. The same weakness paired with a score at the threshold is the reason for rejection.

So read the report in reverse order: the score table first, then the comments on the lowest criterion, and only then the rest of the text.

Why the same proposal receives different scores

This is worth knowing so that you do not overweight a single comment. At least three independent experts evaluate a proposal, then a consensus procedure follows, then a panel that levels the assessments and builds the ranking. Because the composition of experts differs in every round, the same proposal can receive noticeably different scores across rounds.

The practical conclusion follows. A single low score on a criterion that no other comment flags as a problem may reflect one particular evaluator. A conclusion repeated across several comments points to a systemic problem in the proposal.

Appeals: what they deliver and what they do not

The procedure exists, although it is narrower than most applicants assume.

What you can actually appeal

The European Commission Online Manual sets out the means of redress: a request for an admissibility, eligibility or evaluation review goes in within 30 days of receiving the letter. For decisions by EU executive agencies a request for review of legality under Article 22 of Regulation 58/2003 is also available.

The key limitation. Complaints must focus on aspects of the evaluation: admissibility or eligibility checks, the evaluation procedure and similar matters. They do not concern the merits of the proposal, and the review procedure does not question the scientific or technical judgement of appropriately qualified experts.

In practice that means disagreement with the evaluators conclusions is no basis for a complaint. A procedural breach is: a conflict of interest, assessment against criteria absent from the call conditions, an arithmetic error, or treating a proposal as ineligible without grounds.

The trap that lets the deadline pass unnoticed

This is the single most important detail in the whole procedure. Under the portal terms and conditions, notifications not opened within 10 days of sending count as accessed, and the deadlines run from opening or access.

So a postponed email does not stop the clock. A team that received a rejection before a holiday and opened the letter three weeks later may find that 9 of the 30 days remain. Open the letter immediately, even when reading it holds no appeal.

ERC and system failures: separate deadlines

The ERC rules of submission and evaluation set 30 calendar days from receipt of the agency notification, and a complaint must contain at least the call name, the proposal number, the project title and a description of the circumstances.

A separate and much shorter deadline covers technical failures. An applicant who could not submit because of a fault in the electronic system has 4 calendar days after call closure to send a complaint explaining the circumstances, attaching a copy of all parts of the proposal. Such cases get examined against the logs of operations running up to the deadline.

Rebuttal: when you can respond before the decision

Selected schemes, notably EIC Pathfinder, are piloting a rebuttal process. An applicant responds to the comments of individual evaluators before consensus is reached, and that reaction is taken into account during the consensus procedure.

This is a fundamentally different situation from appealing after rejection, because here you influence the decision itself. So in schemes with a rebuttal stage, decide in advance who on the team prepares the response and within what timeframe.

From feedback to a resubmission

What to rewrite and what to keep

A sequence that works. Write every comment into a three-column table: criterion, the specific remark, your action. Then mark which remarks repeat across different comments, because those are the systemic ones. Only after that decide how much rewriting the proposal needs.

The typical mistake is rewriting the proposal completely. Sections that earned high scores are working, so a new version should preserve them. Most often the systemic problem sits in one of two places: the impact justification or the realism of the implementation plan.

Signs the project sits in the wrong programme

Several signs indicate that a project simply sits in the wrong programme. Comments point to a mismatch with the thematic focus of the round. The action type does not fit the content, meaning you submitted a research project to a coordination and support call or the reverse. Your role does not match the requirements, for example you apply as coordinator where the conditions place a different type of entity in that seat.

In such cases reworking the proposal will not help, so the time belongs to finding a programme with the right focus.

Institutional memory

Last in order and first in consequences. An evaluators report is the most valuable training material your organisation receives for free, and within a year it usually becomes impossible to find.

A minimum practice: one folder holding the reports for every submitted proposal, a one-page summary for each, and a named person who reads those summaries before the next application goes out. That single procedure separates an organisation applying for the sixth time from one applying for the sixth time with accumulated experience.