Common Reasons Federal Grant Applications Are Rejected

Many federal grant applications never reach reviewers. Agencies return them without review for compliance problems they publish in advance: missing the deadline, not responding to the funding opportunity, breaking page limits or formatting rules, leaving out a required section, or failing to complete or renew required registrations. Each of these is preventable with a checklist built from the funding notice and registrations finished weeks ahead.

This guide covers the reasons agencies themselves list, with links to the official policies from NSF, NIH and Grants.gov guidance. It separates compliance failures, which stop an application before review, from scoring problems, which happen when reviewers read it and rank it lower than others. Agency policies vary, so always check the funding notice for the specific rules that apply.

Two kinds of "no"

It helps to separate two outcomes:

• Not accepted or returned without review. The application fails a compliance or eligibility check. Reviewers never score it.
• Reviewed but not funded. The application is compliant and scored, but it ranks below the funding line, or the agency chooses other applications for program reasons.

The first kind is almost entirely within your control. The second is about competition and quality. This guide focuses mostly on the first, with a section on scoring at the end.

What NSF lists

NSF publishes its rules in the Proposal and Award Policies and Procedures Guide. Chapter IV of the 24-1 edition lists the reasons a proposal will not be accepted or will be returned without review. A proposal is not accepted or is returned if it:

1. Is inappropriate for NSF funding.
2. Poses a potential research security risk based on credible information of a national security concern, which NSF expects to be rare.
3. Is submitted with insufficient lead time before the activity's scheduled start.
4. Is a full proposal from a submitter who received a "not invited" response to a preliminary proposal.
5. Duplicates or is substantially similar to a proposal already under consideration from the same submitter.
6. Does not meet NSF proposal preparation requirements, such as page limits, formatting instructions and electronic submission.
7. Is not responsive to the NSF funding opportunity.
8. Does not meet an announced proposal deadline.
9. Was previously reviewed and declined and has not been substantially revised.
10. Duplicates a proposal NSF has already awarded.
11. Does not contain each of the required sections.

Most of these apply in spirit at other agencies too. Check the latest edition of the PAPPG for NSF submissions, because NSF updates it regularly.

Registration problems

Registrations are a common reason an otherwise finished application cannot be submitted on time.

Expired or incomplete SAM.gov registration

Every applicant organization needs an active SAM.gov registration, renewed every 365 days. Agencies do not treat registration delays as a reason to accept late applications. NIH notice NOT-OD-23-153 revoked an earlier exception and states that the NIH Late Application Policy does not allow late submissions due to failure to complete or renew required registrations.

Grants.gov advises allowing up to 10 business days for a SAM.gov registration to become active, and validation problems can take longer. Our SAM.gov registration guide covers how to avoid delays.

Mismatched identifiers

Your Unique Entity ID must be the same everywhere. NIH guidance in NOT-OD-22-162 requires the UEI on the application to match the one in the organization's eRA Commons profile and in SAM.gov. NIH also requires a valid eRA Commons ID for the program director or principal investigator, and a missing one prevents successful electronic submission.

No one with submission authority

On Grants.gov, only a user with the Authorized Organization Representative (AOR) role can submit for an organization. If the role was never assigned, or the person who held it left, nobody can submit. Confirm roles early, as described in our Grants.gov guide.

Submission and system problems

Missing the deadline

Deadlines are strict. The Grants.gov timestamp on your submission is the official submission time, according to agency guidance such as the HRSA Grants.gov overview. Agency guides, such as the USDA AMS application guide, recommend submitting at least 24 to 48 hours early so there is time to correct errors.

Grants.gov rejection

After you submit, Grants.gov sends a validation email or a rejection email that describes the errors. A rejected package is not received by the agency. Fix the errors and resubmit before the deadline.

Passing Grants.gov but failing the agency check

Grants.gov validation only confirms that certain parts of the package were submitted. Agency guidance notes that it does not mean the agency has accepted the application as complete. The USDA AMS guide also states that Grants.gov does not check for the agency's required attachments. An application can be validated by Grants.gov and still be returned by the agency.

Content and format problems

Not responsive to the notice

An application that proposes work outside the program's purpose is likely to be returned or scored poorly. Read the Program Description section of the notice and make sure your project answers it directly. Our guide to reading a NOFO explains each section.

Missing required sections

NSF returns proposals that do not contain each required section. Other agencies do the same with missing narratives, budget justifications or required forms. Build your checklist from the notice's Application Contents and Format section, which 2 CFR 200 Appendix I requires every NOFO to include.

Page limits and formatting

Exceeding page limits or ignoring font, margin and file format rules is a listed reason for return at NSF. Many agencies remove pages beyond the limit before review, or return the application. Check the final PDF, not the word processing file, because conversion can change page counts.

Ineligible applicant

If your organization type is not listed in the notice's Eligibility section, the application will not be reviewed. Check eligibility before you start, using the categories on the Grants.gov eligibility page.

Duplicate or unrevised resubmissions

NSF does not accept a proposal that duplicates one under consideration, or one previously declined without substantial revision. If you resubmit, show what changed in response to the earlier reviews.

Scoring problems: reviewed but not funded

When an application is compliant but not funded, the reasons usually come back to the review criteria in the notice. Patterns to watch for:

• Criteria not answered clearly. Reviewers score against the criteria in Application Review Information. If they cannot find your answer to a criterion, they score it low. Use the criteria as headings.
• Weak link between need and approach. Show why the problem matters, with sourced data, and how each activity addresses it.
• Vague outcomes. Measurable objectives and an evaluation plan show reviewers how you will know the project worked.
• A budget that does not match the narrative. Costs with no clear purpose, or activities with no cost, raise questions. See our budget guide.
• Unclear capacity. Reviewers want to see that your team and organization can carry out the work and manage federal funds.

Many agencies share reviewer comments with applicants. Read them, ask the program officer about them if the agency allows, and use them to improve a resubmission.

A prevention checklist

1. Eligibility confirmed against the notice before any writing starts.
2. SAM.gov active with at least 60 days before expiration, and UEI identical in every system.
3. Grants.gov and agency system accounts active, with the AOR and PI roles confirmed.
4. Every required section and attachment on a checklist built from the notice.
5. Page limits and formatting checked on the final PDFs.
6. Narrative organized around the review criteria.
7. Budget totals matching the justification and the forms.
8. Submitted at least 24 to 48 hours before the deadline, with the tracking number saved.
9. Validation email received, and agency retrieval confirmed.

Our Federal Grant Readiness Checklist and Application Timeline Planner help you work through these steps on schedule.

Building an internal review

The simplest way to avoid compliance failures is a review by someone who did not write the application. Give the reviewer the notice and your checklist, and ask them to check:

• Every required section and attachment is present, named and formatted as instructed.
• Page counts are within limits in the final PDFs.
• Budget totals agree across the forms, the justification and the narrative.
• Each review criterion has a clearly labeled answer.
• Names, identifiers and dates are consistent throughout.

Schedule this review at least a week before the deadline so there is time to fix what it finds.

After a rejection

If your application was returned without review, find out exactly why. Agencies usually say which requirement was not met. Fix the process that caused it, not just the document, so the same problem does not happen again. If your application was reviewed but not funded, read the reviewer comments, talk to the program officer if the agency allows it, and decide whether a revised application would be competitive in the next cycle.

Keep a record of what went wrong

Keep a short log of every compliance problem your team finds, whether an agency caught it or your own review did. Over a few application cycles the log shows patterns, such as registrations that keep lapsing or attachments that keep getting missed. Fixing the pattern, for example by assigning registrations to one owner or adding a step to your checklist, prevents far more problems than fixing each application on its own.