Why grant proposals get rejected, and what to do next

Every experienced grant writer has a drawer full of declines. Rejection is part of the work, and it is not always a verdict on your proposal. Funders routinely turn down good requests because they have more good requests than money.

But some declines are self-inflicted, and those are the ones worth studying. Once you understand how reviewers read and score proposals, most of the common reasons for rejection become predictable, and preventable.

How reviewers actually read

Picture the person on the other side. A foundation program officer may be reading dozens of proposals for a single docket while managing current grantees, site visits, and board preparation. A federal peer reviewer may be assigned a stack of applications, each 25 to 50 pages, to read and score against a rubric in a few weeks, often on top of a full-time job.

That reality shapes how proposals are read:

• The first page matters most. Reviewers form an impression from the opening, the executive summary, and the budget total.
• They read against criteria. Federal reviewers literally score each criterion. Foundation staff have their own internal checklists and their board's priorities in mind.
• They look for reasons to trust or doubt. Specific, consistent, well-sourced claims build trust. Vague or contradictory ones erode it fast.
• They have to advocate for you. A program officer usually has to present your request to colleagues or a board. Give them clear, quotable facts.

How federal merit review works

Federal agencies must design and run a merit review process for discretionary awards. Under 2 CFR 200.205, it is "an objective process of evaluating Federal award applications in accordance with the written standards of the Federal agency," and the process must be described in, or incorporated by reference into, the funding notice. That is why every NOFO has a section on review criteria. Read it before you write a word; our guide to reading a NOFO shows where to look.

Typical scoring rubrics

Many federal programs assign points to each criterion. A common pattern looks like this (illustrative only; every NOFO is different):

Reviewers typically score independently, then discuss as a panel, and the agency compiles scores. In many programs, reviewers also write strengths and weaknesses for each criterion, which become the comments you may later receive.

Some agencies use different scales. NIH, for example, uses a 9-point scale where 1 is the best possible score. Starting with January 25, 2025 due dates, NIH moved most research project grant applications to a simplified review framework that focuses reviewers on two key questions: should the proposed research be conducted, and can it be conducted?

Scores are not the whole decision

A high score does not guarantee an award. Agencies weigh merit review results alongside other factors, such as available funds, program balance, geographic distribution, and the agency's priorities stated in the NOFO. Agencies must also conduct a risk review of applicants before making an award under 2 CFR 200.206, considering factors such as financial stability, management systems, history of performance, and audit findings.

Since August 2025, Executive Order 14332 has also required each federal agency to designate a senior appointee to review funding announcements and discretionary awards for consistency with agency priorities and the national interest, and it states that peer review recommendations remain advisory. In practice, a well-scored federal application can still be declined for policy reasons. Keep up with the federal funding landscape for the agencies you apply to.

The top reasons proposals get rejected

These are the reasons practitioners and program officers cite again and again, roughly in order of how often they are avoidable.

1. Poor fit

The single most common avoidable reason. The project is outside the funder's priorities, geography, population, or typical grant size, or it asks for something the funder does not fund (capital, endowment, individuals, general operating support from a project-only funder).

Fix: Do real prospect research before writing. Read the funder's guidelines, recent grants lists, and 990-PF. If fit is a stretch, do not apply. See grant prospecting and our funder fit scorecard.

2. Not following instructions

Exceeding page limits, using the wrong font or margins, missing required attachments, answering a different question than the one asked, submitting late, or uploading the wrong file. In federal competitions, many of these can make an application ineligible before any reviewer reads it.

Fix: Build a compliance matrix from the guidelines or NOFO, listing every requirement, and check each one before submitting. Use the proposal review checklist.

3. A vague or unconvincing need

National statistics with no local data, needs described as a lack of your program ("the community needs our program"), outdated sources, or no clear target population.

Fix: Use current, local, sourced data and describe the problem from the perspective of the people affected. See the statement of need guide.

4. Activities that do not connect to outcomes

The program description lists activities, the objectives list outcomes, and nothing explains how one leads to the other. Or the outcomes are too ambitious for the activities and timeline.

Fix: Build a logic model before you write, and use SMART objectives that your activities can realistically achieve.

5. Weak or missing evaluation

"We will survey participants" with no measures, timeline, or plan for using results.

Fix: Name your measures, data sources, collection schedule, who analyzes the data, and how findings will improve the program. See evaluation plans.

6. A budget that does not match the narrative

Staff mentioned in the narrative but missing from the budget, unexplained lump sums, math errors, unallowable costs, or a request out of proportion to the organization's size.

Fix: Follow the grant budget guide and do a trace test between narrative and budget.

7. Doubts about capacity

A new organization proposing a large expansion with no new staff, key positions unfilled with no hiring plan, no evidence of past results, financial red flags in the 990 or audit, or partners described without commitments.

Fix: Show named staff, real systems, and documented partner commitments. See organizational capacity.

8. No sustainability plan

The funder cannot see what happens when the grant ends, especially for new programs or staff positions.

Fix: Show a realistic path to continued funding. See the sustainability plan guide.

9. Hard to read

Jargon, dense paragraphs, no headings, acronyms never defined, or writing that buries the main point. Reviewers who have to work to understand you will not give you the benefit of the doubt.

Fix: Short paragraphs, headings that mirror the funder's criteria, plain language, and a cold read by someone outside your organization.

10. Too much competition, not enough money

Sometimes everything was strong and the funder still said no. This is common in federal programs and popular foundation programs.

Fix: This one is not about your writing. Keep building the relationship, diversify your prospects, and ask whether a future cycle might be a better fit.

How to ask for feedback

Asking for feedback is normal, professional, and one of the most useful things you can do after a decline. Most program officers respect it, and many will give more candid advice in a phone call than in writing.

With foundations

1. Wait a few days after the decline so your note is calm and gracious.
2. Send a short email to the program officer thanking them for their consideration.
3. Ask a specific, open question. For example, whether they would be willing to share any feedback, and whether the project might be a better fit in a future cycle or a different program.
4. Offer a short call, and make it easy to say no.
5. Listen, do not argue. Take notes. Thank them again.

With federal agencies

Federal processes vary by agency and program. Some agencies send reviewer comments or scores with every decision; others provide them only on request, and some programs offer formal debriefs. The NOFO or your notification will often explain the process. If not, contact the agency contact listed in the NOFO and ask what feedback is available.

At NIH, for example, applicants can see their score in eRA Commons within about three business days after review and their summary statement, which contains the reviewers' critiques, within about 30 days. NIH encourages applicants to discuss next steps with the program official named on the summary statement.

Reading reviewer comments

Reviewer comments can sting. Read them twice, a day apart. Then sort them:

If one reviewer misunderstood you, others probably will too. Treat confusion as a writing problem.

Reapplying

Should you reapply?

Reapply when the funder allows it, the feedback suggests the idea fits, and you can genuinely address the concerns. Do not reapply if the feedback says the work falls outside the funder's priorities; find a better-fit funder instead.

How to reapply well

1. Start from the feedback. List every concern and decide how you will address each one.
2. Revise substantively. A light edit of the same proposal is unlikely to change the result.
3. Add new evidence. Pilot results, new partner commitments, a stronger evaluation design, updated data.
4. Explain what changed, when allowed. Some funders welcome a short note; some federal programs require a specific format.
5. Keep the relationship warm. Send a brief update before the next cycle if you have meaningful news, and invite the program officer to see the work.

Formal federal resubmission rules

Some agencies have specific resubmission policies. NIH, for example, accepts only a single resubmission (A1) of a new, renewal, or revision application. The applicant must have received the summary statement from the previous review, must resubmit within 37 months, and must include an introduction of one page or less (unless the funding opportunity says otherwise) that summarizes substantial changes and responds to the reviewers' criticisms. After an unsuccessful resubmission, the idea may be submitted as a new application.

Other agencies treat each competition separately; you simply apply again in the next cycle. Read the NOFO for any resubmission or prior-applicant guidance.

Build a learning system

Declines are data. Keep a simple log in your grant tracker with the funder, request, decision, feedback received, and what you changed. Over a year, patterns emerge: maybe your evaluation sections are consistently weak, or you keep applying to funders with marginal fit. Fix the pattern, and your success rate will follow.

And remember the funders who said no for budget reasons. Steward those relationships: thank them, share updates, and invite them to events. A decline today is often the first step toward a grant next year. Our guide to funder relationships covers how.