Grant Rejection: Why It Happened and What to Do Next

A grant rejection means the funder decided not to fund your proposal in this cycle, and it usually happens for one of three reasons: the application was screened out before review for a compliance or eligibility problem, it scored lower than funded proposals because reviewers found weaknesses, or it scored well but missed the funding line because the money ran out. Your next step depends on which of those happened, so start by working that out.

Read the decline for clues

Decline letters are often brief, but the wording and anything attached tell you a lot.

• "Did not meet eligibility requirements," "not reviewed," or "returned without review." The proposal was screened out. Nobody judged the project; something administrative failed.
• Reviewer comments, scores, or a summary statement attached. It was reviewed and scored. The comments are the most valuable thing you will get from this cycle.
• "Highly meritorious but unable to fund," or a score close to past funding lines. It came close. Small, targeted revisions may be enough.
• A form letter with no detail. Common at foundations. You will need to ask.

Reasons proposals are declined, by stage

Screened out before review

These are the most avoidable, and the most painful, because a strong project never gets read.

• Applicant type or location outside the eligibility rules.
• Missing required forms, attachments, or letters.
• Page limits, font, margin, or file-format rules ignored.
• Expired or missing registrations (for federal grants, SAM.gov and Grants.gov; see our guide to keeping federal registrations active).
• Submitted after the deadline, even by minutes.

Building a grant proposal checklist straight from the funding announcement prevents nearly all of these. For federal opportunities, our explainer on what a notice of funding opportunity contains shows where the requirements sit.

Reviewed and scored low

Reviewers score against criteria, so weaknesses in specific sections cost specific points.

• Weak fit. The project is worthwhile but outside the funder's current priorities, population, or geography.
• Unconvincing need. Assertions instead of data, or a description of the organization's needs rather than the community's. Our guide to writing the statement of need covers the fix.
• Vague outcomes. Activities described as results ("we will provide services") instead of measurable change. Tightening your measurable objectives and pairing them with a credible evaluation plan addresses the most common reviewer complaint.
• Budget mismatch. Costs for activities the narrative never mentions, staffing that does not match the work plan, or arithmetic errors. See our grant budget guide.
• Capacity doubts. No evidence the organization has run something similar, or no named staff with relevant experience.
• Unclear writing. Reviewers read many proposals; if they cannot find your answer to a criterion quickly, they score it as missing.

Scored well, not funded

Some competitions receive far more fundable proposals than they can pay for. A well-scored decline is a reason to resubmit with modest changes, not to start over.

What to do in the first two weeks

1. Send a short thank-you. Two or three sentences to the program officer or foundation contact. Thank them for the consideration and ask whether feedback is available.
2. Ask for feedback specifically. Useful questions: "Were there areas of the proposal reviewers found weakest?" "Was the project a good fit for your current priorities?" "Would you welcome a future application, and when?" Keep it brief and never dispute the decision.
3. Collect what federal agencies provide. NIH applicants receive a summary statement with reviewer critiques, and scored applications show an overall impact score. NSF provides reviewer comments and, for panel-reviewed proposals, a panel summary; NSF also allows a written request for reconsideration within 90 days of the decline, but only after you have sought clarification from the program officer, and a reconsideration is a review of whether the process was fair, not a second chance to revise.
4. Log everything. Date, funder, amount requested, score if any, comments, and the contact's response. Patterns across several declines tell you more than any single one.

Deciding whether to resubmit

Resubmit when the feedback names fixable weaknesses and the funder's priorities still match. Look elsewhere when the core issue is fit, because no rewrite fixes a project the funder does not fund. Our prospect research overview explains how to find funders whose priorities genuinely match.

Rules differ by funder:

• NIH generally allows one resubmission of an unfunded application, labeled A1. It must include an Introduction, usually one page, that summarizes changes and responds to the critiques in the summary statement. After an unsuccessful A1, the same idea may be submitted as a new application.
• NSF has no formal resubmission category. A revised proposal is submitted as a new proposal and goes through standard review again.
• Foundations set their own rules. Many state a waiting period before reapplying; some invite a revised proposal in the next cycle. Check the guidelines and ask the program officer.

Revising so the next version is different

Treat every reviewer comment as a fact about how your proposal read, even if you disagree with it. If a reviewer missed something, it was not easy enough to find.

• Group comments by theme and fix the root cause, not just the sentence a reviewer quoted.
• Where the funder allows it, explain what changed and why, briefly and without defensiveness.
• Re-check the current funding announcement; criteria, deadlines, and forms change between cycles.
• Have someone outside the project read it cold against the scoring criteria before you submit.

That outside read is what our grant review and editing service does: we score a declined or draft proposal against the funder's criteria and the reviewer comments, then revise it.