Universal · 8 min read

Why Grants Get Rejected: A Triage Guide for Researchers

Most grant rejections are not about the science. Reviewers across funders write similar comments; recognising them helps you triage a decline letter and rebuild faster. Here are the 12 most common reasons good projects get declined — and what to do about each.

1. “Aims unclear”

The aims weren’t set up in a way the reviewer could hold in their head. Either too many, too vague, or stated as “we will study” rather than as testable claims.
Fix: state one central hypothesis in one sentence. Three specific aims, each one sentence.

2. “Lack of innovation”

The reviewer didn’t see what was new. Often the proposal explained the field but not the position relative to it.
Fix: at the end of state-of-the-art, write one sentence that starts “What makes this proposal novel is…”. If you can’t fill it in, the proposal isn’t novel enough.

3. “Methodology insufficient”

The reviewer couldn’t tell exactly what you would do. Method described as a list of techniques, not tied to specific objectives.
Fix: organise methodology by aim, not by technique. Each aim gets methods, expected outcome, and risks.

4. “Feasibility concerns”

The reviewer wasn’t convinced you could pull it off. Either no preliminary data, or the data was tangential.
Fix: at least one figure showing your group has the central method working, ideally with your model system.

5. “Risks not addressed”

Reviewers want to see you’ve thought about what could go wrong. A risk-and-mitigation table that restates the aims fails this test.
Fix: 2–3 concrete technical risks (variability, source availability, ethical approval), each with a real Plan B.

6. “Track record concerns”

Reviewers couldn’t see your independent contribution. Long publication list with most papers dominated by your former PI.
Fix: use the CV section to highlight 5 most-relevant papers and explain, for each, what your contribution was.

7. “Budget unjustified”

The budget didn’t map to the workplan. A postdoc was listed without a corresponding work package; a piece of equipment without a methodology line.
Fix: every budget line ties to a specific aim and specific deliverable. Read the budget and ask: what would I cut if forced?

8. “Impact narrow”

The proposal addressed a niche question without explaining who would care. Common in fundamental-research proposals to applied funders.
Fix: end the impact section with three concrete beneficiary groups and one tangible outcome each.

9. “Wrong panel”

The proposal landed on a panel of reviewers who scored it on the wrong criteria. A clinical-research proposal evaluated by a basic-science panel; a method-development proposal evaluated by an applied panel.
Fix: verify panel choice by reading the panel description carefully. If unsure, ask the funder’s programme officer before submission.

10. “Ethics annex weak”

Late-stage ethics work shows. Boilerplate data-management plan, missing GDPR considerations, no IRB equivalence plan for foreign-component studies.
Fix: 1 full week dedicated to the ethics annex. If working with human data, name-specific consent procedures, retention periods, repositories.

11. “Open-science plan as boilerplate”

Most funders now require open-access and open-data plans. Reviewers explicitly score them. A one-paragraph “we will publish open access” gets a low score.
Fix: name specific repositories, file formats, embargo periods. Explain how the plan aligns with the funder’s open-science policy.

12. “Below the funding line”

Sometimes the proposal scored well but the panel had more strong proposals than budget. The reviewers have nothing critical to say but the proposal didn’t make the cut.
Fix: resubmit. Most agencies allow A1/resubmission with modest revision. Address even the “not weaknesses” reviewers mentioned.

How to recover from a rejection

• Wait 48 hours before reading the report. Reading angry leads to bad decisions.
• Categorise each comment: “real weakness”, “reviewer misunderstood”, “outside our control”.
• Address every real weakness before resubmission. Even if you disagree, reviewers from the same panel may share the misunderstanding — clarify the writing.
• Plan B funder: if the proposal is below-line at one funder, identify two adjacent calls where it fits and adapt for the next deadline.
• Talk to a programme officer. Many funders welcome 15-minute conversations on the decline letter; programme officers know which weaknesses are real and which were panel happenstance.

Find the next opportunity automatically

Grant Radar tracks 24 funders worldwide and ranks every open call against your ORCID profile. The next deadline that fits your project is in your inbox tomorrow. Free during the public beta.