15 Grant Writing Mistakes That Get You Rejected
Updated 16 official sources
Quick Answer: The 15 most common grant writing mistakes fall into three categories: administrative errors, content mistakes, and strategic errors.
Full answer and how we checked it
Administrative errors disqualify you before review (expired SAM.gov, missed deadlines, wrong format), and content mistakes lower your score (vague needs statements, unrealistic timelines, missing evaluation plans). Strategic errors make funding impossible (wrong funding mechanism, ignoring review criteria). At NIH, 87% of R01 applications weren't funded in FY2025. Most of these grant writing mistakes are preventable with a structured self-review process. This guide is for grant writers, executive directors, program staff, and PIs preparing federal or foundation applications who want to understand what reviewers actually penalize and how to catch fixable errors before submission.
Who this is for: Anyone preparing a grant proposal who wants to understand what reviewers actually penalize, whether you're a beginning grant writer working on your first federal application or an experienced writer looking for a self-review checklist.
Data note: Amounts may shift with annual appropriations.
In this guide
- What Agency Rules Do Not Tell You
- June 2026 Source Check: 7 Rejection Triggers To Verify First
- The Numbers: How Often Grants Get Rejected
- Administrative Mistakes (Pre-Review Failures)
- Needs Statement Mistakes
- Budget Mistakes
- Evaluation Plan Mistakes
- Abstract and Summary Mistakes
- Strategic Mistakes (Structural Problems)
- The Difference Between Fixable Mistakes and Fatal Flaws
- How to Self-Review Before Submitting
- Why Rejected Proposals Miss What Reviewers Score
- If You Missed Out on the Same Award Last Cycle
- What Review Panels Don't Tell You
- Building a Stronger Proposal: Where to Start
- Sources
The same grant writing mistakes appear in application after application. The reasons grants fail aren't mysterious. They're patterns, and once you recognize them, they're mostly avoidable. For the full proposal structure and what each section should accomplish, see our guide to writing a grant proposal first, then come back here to stress-test your draft.
Here's what makes this guide different from generic "tips for grant writing" articles: Grantsights has organized these 15 mistakes by proposal section, explained why reviewers penalize each one, and distinguished between fixable errors (things you can correct in a revision) and fatal flaws (problems that require starting over). Grantsights has also included the statistical context for rejection rates, so you understand the odds you're working against.
According to Grants.gov, applicants should track validation and agency retrieval after submission because a submitted package can still fail processing. According to NIH, R01-equivalent success rates fell to 13.0% in FY2025, and scored review criteria must be stated in the NOFO. According to NSF, proposals can be returned without review when preparation requirements are not met. According to Grants.gov tracking guidance, the tracking tool only confirms 1 thing after retrieval: the agency has the package, not whether the agency will fund it. Our analysis is that grant rejection prevention works best as a pre-submission screen, not a post-mortem. For example, one applicant can fix a weak evaluation plan in review, but a missed deadline, inactive SAM.gov record, or ineligible applicant type is usually fatal.
What Agency Rules Do Not Tell You
Official sources tell applicants where the lines are. Grants.gov tracking guidance (opens in a new tab) tells you to monitor validation and agency retrieval. NIH resubmission policy (opens in a new tab) says A1 applications must respond to prior review concerns. NSF return-without-review rules (opens in a new tab) list format, timing, and fit reasons that can keep a proposal out of review. What those official source pages do not tell you is how to rank mistakes before you rewrite.
| Mistake signal | Official rule | Grantsights decision test |
|---|---|---|
| Missed or late submission | Grants.gov validation and retrieval still matter after submission | Stop treating the proposal as submitted until the status is clean |
| Prior rejection | NIH expects the resubmission to answer the summary statement | Skip cosmetic rewrites and build a response table before editing |
| Format failure | NSF can return noncompliant proposals without review | Do a page-limit, margin, attachment, and file-name checklist before narrative polishing |
| Poor fit | Agency criteria define what reviewers can score | Do not apply if the project cannot earn points under the published criteria |
Looking for your next grant?
About once a week, we email a short list of open grant calls with real deadlines from different funders. It lists open calls only.
No spam. Unsubscribe anytime.
June 2026 Source Check: 7 Rejection Triggers To Verify First
These are the current official-source checks Grantsights would run before line-editing a proposal. The point is to catch rejection triggers that a better narrative cannot repair.
| Trigger | Current source check | What to do before writing |
|---|---|---|
| Application status | Grants.gov tracking (opens in a new tab) confirms only successful agency retrieval, not funding status | Track receipt, validation, retrieval, and agency tracking number separately |
| SAM status | SAM.gov entity registration (opens in a new tab) says registrations must renew every 365 days and can take up to 10 business days to become active | Start renewal 60 days before expiration and verify Active status before submission |
| Grants.gov role | Grants.gov workspace roles (opens in a new tab) distinguish Workspace Manager, Standard AOR, and Expanded AOR permissions | Confirm the actual submitter can submit inside the workspace |
| NIH resubmission | NIH resubmission policy (opens in a new tab) allows one A1 resubmission within 37 months when the opportunity allows resubmissions | Build a response table from the prior summary statement |
| NSF return risk | NSF PAPPG Chapter IV (opens in a new tab) lists return-without-review reasons, including preparation and duplicate-submission problems | Check page limits, formatting, deadline, duplicate risk, and solicitation fit |
| NIH competition level | NIH Data Book (opens in a new tab) shows FY2025 R01-equivalent applications, awards, and success rate | Treat a low success rate as a fit and scoring problem, not a writing-only problem |
| Federal cost rules | 2 CFR Part 200 (opens in a new tab) controls allowability, documentation, and cost treatment for many federal awards | Tie every budget line to an allowable activity and keep backup support |
The Numbers: How Often Grants Get Rejected
Before we get into specific mistakes, let's establish the baseline. Federal grant rejection rates are high and getting higher.
According to NIH data from its success rates reporting (opens in a new tab), R01-equivalent applications remain highly competitive, which is why preventable proposal errors matter so much. According to NSF budget data from its budget reporting page (opens in a new tab), award rates also vary sharply by directorate and year, so a generic proposal quality benchmark is not enough.
| Agency/Program | Success Rate | Rejection Rate |
|---|---|---|
| NIH R01-equivalent (FY2025) | 13.0% | 87.0% |
| NIH R01-equivalent (FY2024) | 18.7% | 81.3% |
Both NIH rows come from NIH's FY2025 by-the-numbers report (opens in a new tab). NSF publishes funding rates by directorate in its budget data, and most other federal agencies don't publish program-level success rates, so check each NOFO's expected number of awards instead.
These numbers mean that even well-written proposals get rejected. Limited budgets ensure that many strong applications go unfunded. But there's a difference between a proposal that scored well but didn't make the funding line and a proposal that scored poorly because of preventable errors. This guide focuses on the preventable errors. If your primary target is NIH, the NIH grants complete guide covers study sections, review scoring, and the specific expectations that NIH reviewers bring to each application section.
For a deeper look at the full spectrum of reasons grants fail, see our guide on common grant rejection reasons.
Administrative Mistakes (Pre-Review Failures)
These grant writing mistakes kill your application before a single reviewer reads it. They're the most frustrating because no amount of strong content can save an administratively ineligible submission.
Mistake 1: Missing the Deadline
Every federal agency enforces hard deadlines. NIH: 5:00 PM local time of the applicant organization. NSF: 5:00 PM submitter's local time. Grants.gov (opens in a new tab): whatever closing time the agency's NOFO sets, which varies (many use 11:59 PM Eastern, others 5:00 PM local time). There are no grace periods, no exceptions for "the system was slow," and no appeals process.
According to Grants.gov status guidance from its tracking page (opens in a new tab), applicants need to monitor validation and agency retrieval after submission. A receipt is not the same as a clean, accepted application.
What makes this a fatal flaw: there is no fix after the fact. Your proposal is dead.
The real problem: Most deadline failures aren't about forgetting the date. They're about underestimating Grants.gov processing time. After you hit "submit," Grants.gov validates your application, which can take up to 48 hours. If validation fails at 11 PM the night before the deadline and you don't check until the next morning, you're out. Submit at least 72 hours early. Check for validation errors at least 48 hours before the deadline.
Mistake 2: Expired or Missing SAM.gov Registration
All federal grant applicants must maintain active SAM.gov registration. Registration expires every 365 days, and SAM.gov says registration can take up to 10 business days to become active. If your SAM.gov registration is expired on the date of submission, most agencies will reject your application administratively.
What makes this a fatal flaw: you can't fix it retroactively. By the time your registration renews, the deadline has passed.
Prevention: Set a calendar reminder 60 days before your SAM.gov expiration date and begin renewal then. Do not wait until the last 10 business days before a federal deadline.
Mistake 3: Wrong Application Format or Missing Components
Federal NOFOs specify exactly what to include: page limits, font requirements, margin sizes, required forms, attachment labels, and file naming conventions. Missing a single required component (like the SF-424 cover page, the project abstract, or a letter of support) can trigger an administrative rejection.
What makes this fixable or fatal: some agencies allow corrections for minor missing items (NSF's "compliance check" process). Others reject outright (NIH won't accept applications with incorrect page limits on research strategy attachments).
Prevention: Create a checklist from the NOFO's application instructions. Check every item before submission.
Needs Statement Mistakes
The needs statement (also called significance or problem statement) is where many proposals start to lose points. Reviewers use this section to decide whether the proposed work is worth doing.
Mistake 4: No Local or Specific Data
"Mental health is a growing problem in America" is not a needs statement. Reviewers want to see specific data about the population you'll serve, in the geography where you'll work. National statistics set context, but local data makes the case.
What reviewers actually penalize: Proposals that use only national statistics without demonstrating that the specific community or population has the need. If you're proposing a substance abuse treatment program in rural Montana, reviewers want Montana-specific prevalence data, county-level treatment gap numbers, and ideally data from your own organization's intake records.
For a full walkthrough of building an evidence-based case, see our guide on how to write a grant needs statement.
Fixable or fatal? Fixable. This is one of the easiest problems to correct in a resubmission. Pull data from your state health department, Census Bureau, and agency-specific data systems (like SAMHSA's NSDUH or CDC WONDER).
Mistake 5: Describing the Solution Instead of the Problem
Some applicants jump straight to describing their program without establishing why it's needed. The needs statement should make the reviewer feel the urgency of the problem before you present your approach. If a reviewer reading your needs statement already knows what your program looks like, you've moved too fast.
Fixable or fatal? Fixable. Restructure the section to lead with problem documentation, then transition to your proposed response in the project narrative section.
Mistake 6: Using Outdated Data
Citing statistics from 2018 in a 2026 application is a red flag. Reviewers interpret outdated data as either laziness (you didn't look for current numbers) or a sign that the problem may no longer exist as you describe it. Use data from the past 3 years whenever possible. If older data is the most recent available (common in some rural areas or for specific populations), acknowledge the date and explain why more recent data isn't available.
Fixable or fatal? Fixable. Update your data sources.
Budget Mistakes
Budget errors are one of the most common categories of grant writing mistakes. They affect scoring, trigger pre-award negotiations, and can disqualify your application entirely.
Mistake 7: Budget Doesn't Align With Project Activities
If your narrative describes hiring six community health workers but your budget funds three, reviewers will question your feasibility. Every activity in your project narrative should have a corresponding cost in your budget, and every budget line item should connect to a described activity.
A proposal might describe a multi-state evaluation design in the narrative but budget only $5,000 for evaluation. That disconnect tells reviewers the applicant either inflated the narrative or didn't think through costs.
For step-by-step budget construction, see our guide on how to write a grant budget. For the written narrative that accompanies it, see how to write a grant budget justification.
Fixable or fatal? Fixable, but it requires revising both the budget and the narrative to align them.
Mistake 8: Math Errors
Column totals that don't add up. Fringe benefit calculations that don't match the stated rate times personnel costs. Year 1 + Year 2 + Year 3 that don't equal the total. These errors make reviewers question your attention to detail across the entire application.
Fixable or fatal? Fixable. Use spreadsheet formulas instead of manual calculations, and have someone else verify every calculation before submission.
Mistake 9: Ignoring the Indirect Cost Rules
Claiming a 45% indirect cost rate when the NOFO caps it at 8%. Using a negotiated rate without attaching the NICRA agreement. Applying indirect costs to the wrong base (total direct costs instead of Modified Total Direct Costs). Indirect cost errors are a common reason budgets get negotiated downward after award.
Fixable or fatal? Fixable if caught before submission. If caught post-submission, the agency may negotiate your budget downward, which could undermine your ability to implement the project.
Evaluation Plan Mistakes
The evaluation section is where technically strong proposals often lose points. Many applicants treat evaluation as an afterthought, writing it last and giving it the least attention.
Mistake 10: No Measurable Outcomes
"We will improve health outcomes for participants" is not an outcome. Reviewers want specific, measurable targets: "We will reduce HbA1c levels by an average of 0.5 percentage points among 200 enrolled participants within 12 months." Without measurable outcomes, there's no way to determine whether the project succeeded.
For detailed guidance on constructing an evaluation framework, see our guide on how to write a grant evaluation plan.
Fixable or fatal? Fixable. Define SMART outcomes (Specific, Measurable, Achievable, Relevant, Time-bound) for each program objective.
Mistake 11: Evaluation Design Doesn't Match the Program
A common error is proposing a randomized controlled trial when your program design makes randomization impossible (you can't ethically withhold services from a control group in a crisis intervention program). Or proposing a simple pre/post survey design when the funder's review criteria explicitly ask for quasi-experimental methods.
Match your evaluation design to what's actually feasible given your program model, ethical constraints, and budget. If you can't do a rigorous design, explain why and describe what you can do.
Fixable or fatal? Fixable. Consult with an evaluator before submitting to ensure the design is appropriate and feasible.
Abstract and Summary Mistakes
The abstract is the first thing reviewers read, and it shapes their expectations for the entire application.
Mistake 12: Abstract That Doesn't Match the Proposal
If your abstract promises to serve 500 participants but your narrative and budget describe serving 200, reviewers notice the discrepancy immediately. Abstracts should be written last, after all other sections are finalized, so the numbers and descriptions are consistent.
Fixable or fatal? Fixable. Rewrite the abstract after completing the full proposal.
Strategic Mistakes (Structural Problems)
These are the hardest mistakes to fix because they're built into the foundation of your proposal.
Mistake 13: Applying to the Wrong Funding Mechanism
Submitting a basic research proposal to a program that funds applied demonstration projects. Proposing a statewide program when the NOFO funds local initiatives. Requesting $2 million from a program that caps awards at $500,000. These aren't writing problems; they're strategy problems.
Before writing anything, read the NOFO's eligibility criteria, funding priorities, and award ceiling/floor. If your project doesn't fit, find a different opportunity. Don't force a square peg into a round hole and hope reviewers won't notice. They will.
At NIH, this mistake often shows up as choosing the wrong parent announcement branch rather than the wrong institute. A clinician-scientist project can have different expectations depending on whether the opportunity allows, requires, or excludes an independent clinical trial. A quantitatively trained investigator crossing into biomedical research faces the same branch-decision problem on career development awards. That branch decision affects eligibility, reviewer expectations, and the language you need in the abstract and research plan. Use the Grantsights federal program search and the official NIH opportunity page together before writing.
Fixable or fatal? Fatal for this submission. You need a different funding opportunity, not a revised proposal.
Mistake 14: Ignoring the Review Criteria
Federal NOFOs publish the exact criteria reviewers will use to score your application, usually with point values. A case in point: SAMHSA's FY2026 CCBHC NOFO (SM-26-014) (opens in a new tab) scores the population of focus and need statement at 10 points (plus up to 5 priority points), implementation at 35, evidence-based practice at 5, organizational experience and staffing at 25, and data collection and performance measurement at 20. Need is one of the smallest sections. Your proposal should allocate space and emphasis in roughly the proportions your NOFO sets.
Consider a proposal that spends 15 pages on the needs statement (worth 10 points in that NOFO) and 2 pages on data collection (worth 20 points). That's a recipe for losing points on data collection, which can move you from fundable to not-discussed.
How reviewers score is explained in detail in our guide on how grant reviewers score applications.
Fixable or fatal? Fixable if the misalignment is about emphasis. Fatal if the entire proposal addresses the wrong criteria.
Mistake 15: No Organizational Track Record Documented
Reviewers need evidence that your organization can do the proposed work. If you've run similar programs, managed previous federal awards, or have staff with relevant expertise, document it. Many proposals describe the program in detail but say almost nothing about why this organization is the right one to implement it.
For newer organizations without extensive track records, demonstrate capacity through staff qualifications, partnerships with experienced organizations, and any pilot data you've collected.
Fixable or fatal? Fixable in most cases. Strengthen the organizational capacity section and include letters of support from partners.
The Difference Between Fixable Mistakes and Fatal Flaws
Not all grant writing mistakes are equal. Here's a quick reference:
| Fixable Mistakes | Fatal Flaws |
|---|---|
| Weak data in needs statement | Wrong funding mechanism |
| Budget math errors | Missed deadline |
| Unclear evaluation outcomes | Expired SAM.gov registration |
| Abstract inconsistencies | Ineligible applicant type |
| Poor writing quality | Project outside funder's mission |
| Missing supporting documents | Exceeds maximum award amount |
| Formatting errors | No organizational capacity |
Fixable mistakes cost you points but can be corrected in a resubmission. Fatal flaws mean this particular proposal, for this particular opportunity, can't be saved. The response to a fatal flaw isn't revision. It's finding the right opportunity and building the right proposal from scratch.
How to Self-Review Before Submitting
Build these review steps into your timeline at least one week before the deadline.
Step 1: The NOFO Compliance Check
Print the NOFO's application checklist and review criteria. For every required component, verify it exists in your application. For every review criterion, verify your proposal addresses it with proportional detail.
Step 2: The Numbers Audit
Verify every number in the application is internally consistent:
- Budget totals match across SF-424, SF-424A, budget narrative, and abstract
- Participant numbers match across needs statement, project narrative, evaluation plan, and budget
- Timeline milestones match between the work plan and the narrative
- Staff effort percentages in the budget match role descriptions in the narrative
Step 3: The Outsider Read
Give your proposal to someone who hasn't been involved in writing it. Ask them to answer three questions after reading:
- What problem is this project trying to solve?
- What exactly will the project do?
- How will you know if it worked?
If they can't answer all three clearly, your proposal needs revision.
Step 4: The Reviewer Simulation
Score your own proposal against the NOFO's review criteria. Be honest. If you'd give yourself a 6/10 on evaluation, that section needs work before submission.
Step 5: The Administrative Final Check
- SAM.gov registration active? Check at SAM.gov (opens in a new tab).
- UEI number correct on all forms?
- All required forms included and signed?
- File names follow the NOFO's conventions?
- Page limits observed?
- Font, margins, and spacing meet requirements?
- Submitted on Grants.gov with at least 48-72 hours to spare?
Why Rejected Proposals Miss What Reviewers Score
A common pattern in rejected applications is a disconnect between what the applicant believes they submitted and what the reviewer actually scored.
For example, a mental health organization could submit a well-written narrative with a clean budget but an evaluation plan that promises to track community-level rates of young adult psychiatric hospitalization for a program serving about 120 people a year. A single program can't demonstrate changes in community-level outcomes, so reviewers are likely to call the plan not feasible. Individual-level outcome measures tied to validated instruments are something the organization can actually deliver.
That pattern, proposing what sounds impressive rather than what you can actually measure and document, is a red flag reviewers catch often.
If You Missed Out on the Same Award Last Cycle
The worst resubmission mistake is sending the same application back with a cleaner cover letter. If you missed out on the same award or a previous project was not selected, reviewers need to see what changed: the fit, the data, the work plan, the budget logic, the evaluator, the partnership structure, or the evidence base.
According to NIH resubmission guidance from the NIH application submission policies (opens in a new tab), a resubmission is expected to respond to prior review concerns rather than simply repeat the original application. The practical version is simple: build a two-column response table before you rewrite. Column one lists every reviewer concern. Column two names the page, paragraph, budget line, or attachment where the fix now appears.
Failure modes to avoid:
- Blaming reviewers instead of fixing the weak section.
- Changing the narrative but leaving the budget, timeline, or evaluation plan inconsistent.
- Addressing only the written comments and ignoring the structural reason the project missed the funding line.
- Treating a fatal fit problem as a writing problem.
The strongest next submission should feel like a better project, not just a more polished document. If the prior application was rejected for fit, use common grant rejection reasons and how grant reviewers score applications to decide whether to rewrite or switch opportunities.
What Review Panels Don't Tell You
The summary statements and panel feedback you receive after a grant decision tell you what the reviewers thought about your proposal. What they don't tell you is how the discussion went.
In a typical NIH study section, each application has three assigned reviewers who write individual critiques. During the meeting, they present preliminary scores and discuss strengths and weaknesses. For research project grants due on or after January 25, 2025, NIH's simplified review framework (opens in a new tab) has reviewers score Factor 1 (Importance of the Research) and Factor 2 (Rigor and Feasibility), rate Factor 3 (Expertise and Resources) as sufficient or insufficient, and give an overall impact score. Other panel members ask questions and can raise concerns the assigned reviewers missed. The final impact score reflects a consensus that emerges from this discussion, not just the average of the three assigned reviewers' scores.
What this means practically: your summary statement captures the assigned reviewers' written critiques, which are drafted before the meeting. For discussed applications, it also includes the Scientific Review Officer's summary of the discussion, so major panel concerns usually appear in writing, but in condensed form. You might see solid factor scores but a weaker overall impact score, and the written feedback may not fully explain the gap.
This is why talking to your program officer after a rejection is so valuable. Program officers attend study section meetings and can share (within limits) what happened during discussion. They can tell you things like "the panel felt the evaluation design wasn't feasible for a community-based program" even if that specific concern isn't in your written feedback. Always request a debrief.
The other thing panels don't tell you is whether your score is likely to be funded. NIH institutes stopped relying on paylines starting with the January 2026 council round, according to NIH's November 2025 funding-strategy notice (opens in a new tab). They now weigh the score against program priorities and budgets, so your program officer is the best source on whether a given score is competitive for your Institute or Center.
Building a Stronger Proposal: Where to Start
If you've identified mistakes in a previous submission, here's the priority order for addressing them:
- Fix fatal flaws first. If you applied to the wrong mechanism or missed eligibility criteria, no amount of polishing will help. Find the right opportunity.
- Address reviewer feedback directly. If you're resubmitting, every concern raised in your summary statement should get a specific response.
- Strengthen your weakest section. Whatever scored lowest in your self-review gets the most attention.
- Improve alignment. Make sure every section references and supports the others. Numbers should be consistent, activities should have budget lines, and outcomes should be measurable.
For a complete guide to building a federal grant proposal from the ground up, start with our guide on how to write a federal grant proposal.
Sources
- NIH Success Rates (opens in a new tab)
- NIH Data Book: R01-Equivalent Success Rates (opens in a new tab)
- NIH Resubmission Applications (opens in a new tab)
- NSF Award Rate Data (opens in a new tab)
- NSF PAPPG Chapter IV: Returned Without Review (opens in a new tab)
- Grants.gov: Search and Apply for Federal Grants (opens in a new tab)
- Grants.gov: Track My Application (opens in a new tab)
- Grants.gov: Workspace Roles (opens in a new tab)
- 2 CFR 200: Uniform Administrative Requirements (opens in a new tab)
- SAM.gov: Entity Registration and Status (opens in a new tab)
Next steps
After a rejection: diagnose, respond and rewrite
These next pages help you move from research into a specific grant choice.
Diagnose rejection reasons
Separate fixable score loss from fatal fit, eligibility, deadline, and registration problems.
Plan the response
Build a reviewer-comment response table before rewriting a declined application.
Check scoring logic
Map every proposed fix to the review criteria, point weights, and evidence reviewers can score.
Rewrite the proposal
Use the federal proposal structure after the prior-review and fit checks are complete.
Find grants that fit you
Free eligibility check: answer 9 questions and see ranked matches with deadlines and fit reasons.
Frequently Asked Questions
What is the most common grant writing mistake?
The single most common grant writing mistake is failing to address the funder's stated priorities. Applicants write about what they want to do rather than what the funder wants to fund. Every Notice of Funding Opportunity lists specific review criteria, priority areas, and sometimes even required program elements. When your proposal doesn't respond directly to these criteria, reviewers can't score it favorably even if your program design is strong. Before writing a single word, map every section of your proposal to the corresponding review criterion in the NOFO.
What percentage of grant applications get rejected?
The majority of federal grant applications are not funded. NIH R01-equivalent success rates fell to about 13% in FY2025, meaning 87% of applications weren't funded. NSF funding rates vary by directorate and year. For federal discretionary programs through agencies like SAMHSA, ED, and DOJ, the odds depend on the program; the NOFO's expected number of awards compared with the likely applicant pool is the best clue. Foundation acceptance rates vary widely, and many large foundations don't publish them. These numbers reflect both competitive quality and limited budgets.
Can I resubmit a grant that was rejected?
Yes, at most agencies. NIH allows one resubmission (A1) within 37 months of the original submission, and resubmitted applications must include an Introduction page addressing reviewer feedback. NSF allows resubmission at any time with no formal limit on attempts. For federal discretionary grants, you can typically reapply in the next funding cycle. Resubmissions that directly address reviewer concerns have historically performed better than new submissions at NIH. The most effective resubmissions don't just fix the problems reviewers identified; they also strengthen areas reviewers didn't comment on.
How do I know if my grant writing mistake is fixable or fatal?
Fixable mistakes are problems with execution: unclear writing, weak data citations, budget math errors, or formatting issues. These can all be corrected in a revision without changing your fundamental approach. Fatal flaws are structural: proposing work that doesn't align with the funder's mission, lacking organizational capacity to do the work, not having the required registrations (SAM.gov, UEI), or missing the deadline. If a reviewer says your approach is 'not responsive to the funding opportunity,' that's often a fatal flaw that requires a completely different proposal, not a revision of the same one.
Should I hire a professional grant writer to avoid mistakes?
It depends on your situation. A professional grant writer brings experience with federal formatting, review criteria, and common pitfalls, but they can't substitute for your organization's subject matter expertise. The most effective approach is collaboration: your program staff provide the content (needs data, program design, evaluation methods) and an experienced grant writer structures it for the funder's requirements. If you're considering hiring a writer, look for someone with a documented track record of funded proposals in your specific field. Avoid anyone who guarantees funding or charges a percentage of the award amount, as both are red flags.
Last updated October 9, 2026. Corrected October 9, 2026: what changed. Published by Grantsights from public sources. See our editorial policy, how we build and check guides, corrections and how we make money.
Related Guides
Complete Guide
Federal Grant Proposal Guide: Sections & Scoring
Federal grant proposals average 50-100 pages. This guide covers every section and scoring criteria for writing a proposal that reviewers score highly.
Grant Writing Guide: How to Start in 2026
Grant writing guide for 2026: how to start grant writing, the 6 proposal parts, budget checks, Grants.gov steps, and first-week checklist.
Grant Writing Glossary: Every Term You Need to Know (2026)
Over 60 grant writing terms defined: NOFA vs FOA, UEI vs DUNS, MTDC, F&A, AOR, payline, NICRA, and every other acronym federal grant applicants encounter.
How to Write a Grant Cover Letter (With Examples)
Many federal programs and most foundations expect a grant cover letter. Learn the 1-page, 4-paragraph format and who should sign it, with 3 examples.
How to Write a Grant Evaluation Plan (With Examples)
Only 3 of 37 open federal NOFOs scored a separate evaluation plan. Write SMART outcomes, baseline plans, and evaluation budgets that reviewers score.
How to Write a Grant Needs Statement That Scores Well
The needs statement is one of the scored criteria in most NOFOs. This guide covers the 4-part structure, data sourcing, and what reviewers look for.