Five Mistakes That Sink Federal Grant Proposals

Every year I read federal proposals that clearly come from teams doing meaningful work — and every year I watch some of them fall apart on the page. The idea is right. The people are qualified. The scoring is unforgiving. Here are the five mistakes I see most often, and how to avoid them.

First, telling instead of showing. Reviewers are asked to score against criteria; they are not asked to be inspired. A proposal that describes a program without evidence of need, design fidelity, or measurable outcomes reads like a brochure. Every claim earns its keep by pointing to data, precedent, or a specific plan.

Second, ignoring the scoring rubric. The scoring rubric is the assignment. When a section is worth 20 points and 10 of them hinge on evaluation, the evaluation plan cannot be two paragraphs at the end. Structure the narrative to mirror how it will be read.

Third, weak logic between need, activities, and outcomes. Federal reviewers are trained to look for coherence. If the need statement describes one problem and the activities solve a different one, the proposal loses trust — even when each section is well written on its own.

Fourth, a budget that doesn't tell the same story as the narrative. A stunning program described in the narrative but under-resourced in the budget signals inexperience. A budget that funds staff the narrative never mentions signals worse. Line by line, the budget should be the narrative in numbers.

Fifth, submitting without a full internal review. The most avoidable losses I see come from proposals that no one outside the writing team read before submission. A fresh reader catches the missing appendix, the confused paragraph, the acronym used before it's defined. Build that review time into the timeline before the deadline exists.

Winning proposals are rarely the flashiest. They're the ones that respect the reviewer's job and make it easy to award the points.