Not Reading the NOFO — or Reading It Only Once
Every federal NOFO specifies exactly what reviewers are looking for — the review criteria are published with their point values. Applicants who write a strong program description but ignore the stated criteria lose points on every section. The fix: print the review criteria, weight each section by point value, and treat the application as answering an exam — not telling your organization's story.
Describing Activities Instead of Outcomes
The most common narrative failure: proposals that describe what the organization will do without specifying what will change as a result. Reviewers want to see measurable outcomes — not program descriptions. "We will provide training to 50 people" scores lower than "50 participants will achieve 80%+ on post-training assessments demonstrating proficiency in X."
Vague Need Statement Without Local Data
Saying "substance abuse is a serious problem in our community" scores poorly. Reviewers see 100+ proposals saying the same thing. What scores points: specific, local data that demonstrates your community's need exceeds comparable communities, tied to your proposed service area specifically.
Budget Doesn't Match the Narrative
Reviewers read the budget and the narrative simultaneously. If your narrative mentions hiring a program coordinator but the budget shows only $20,000 for personnel, reviewers will question your capacity to implement. Budget-narrative discrepancies trigger a loss of confidence in your entire proposal.
Additional Critical Errors
Not Addressing Sustainability
Federal reviewers ask: what happens when the grant ends? If your answer is "we'll apply for more grants," that scores poorly. Reviewers want earned revenue plans, institutional partnerships, and diversified funding strategies.
Weak or Missing Evaluation Plan
Evaluation is a scored criterion in virtually every federal grant. "We will collect participant surveys" is not a credible evaluation plan. You need a logic model, pre/post measurement instruments, and a data collection timeline tied to your performance measures.
Letters of Support That Say Nothing
Generic letters ("We support this organization's work") add nothing. Reviewers value letters that specify the partner's concrete contribution — funding committed, staff time, referrals, facilities — with specific numbers and a signature from the organization's executive.
Timeline That Doesn't Reflect Reality
Back-loading all activities to the last quarter signals poor planning. Reviewers expect to see hiring in month 1–2, early implementation milestones, and continuous data collection — not a "ramp-up phase" that runs 6 months.
Exceeding the Page Limit
This sounds obvious, but reviewers report it often. Page limits are hard requirements — some programs disqualify applications that exceed them. Count pages after formatting, not before. Appendices have their own limits.
Unqualified Key Personnel
Reviewer criterion: does the team have the qualifications to implement this program? Key personnel resumes/CVs must show direct relevant experience. If you're filling positions, show you've hired for similar roles before and describe your hiring strategy.
Not Using Evidence-Based Practices
Many federal programs explicitly require or prefer evidence-based models. If there's an established evidence-based curriculum or intervention model in your field, name it, cite the research behind it, and explain how you're adapting it to your population.
Submitting Without Requesting Reviewer Comments
After a rejection, most federal programs will provide reviewer score sheets on request. This is free intelligence — read every reviewer comment, identify which criteria scored lowest, and treat it as a revision roadmap before reapplying in the next cycle.
Pre-Submission Checklist
- Read the review criteria once more and confirm every criterion is addressed explicitly in the narrative
- Cross-reference every activity in the narrative with a corresponding line in the budget and work plan
- Verify the need statement contains local, specific, sourced data — not general national statistics
- Confirm all key personnel have resumes attached and qualifications match the roles described
- Count pages and verify compliance with all attachment requirements
- Submit through Grants.gov at least 2 business days before the deadline — system outages happen
◆ Primary Sources & Further Reading
Related Articles
Frequently Asked Questions
What is the most common reason grant applications get rejected?
Not following the instructions in the funding announcement — missing required sections, exceeding page limits, ignoring formatting rules, or failing eligibility screening. Agencies reject these applications administratively before any reviewer scores the content.
How early should I start a federal grant application?
At minimum 6 to 8 weeks before the deadline, and registrations come first: SAM.gov registration (required for all federal grants) can take 2 to 4 weeks alone. Starting after the notice drops with only 30 days left forces the rushed errors reviewers spot instantly.
Why do well-written proposals still lose?
Common silent killers include budgets misaligned with the narrative, vague outcomes that cannot be measured, no evidence base for the proposed approach, weak evaluation plans, and failure to address the funder's specific priorities. Reviewers score against the published criteria, not general quality.
Should I contact the program officer before applying?
Yes, in nearly every case. Program officers can confirm fit before you invest weeks of work, clarify ambiguous requirements, and sometimes share what review panels prioritized in past cycles. A short, specific email with one or two questions is the professional norm.