The mistakes that repeat
What are the most common mistakes in grant proposals?
Two are fatal before scoring begins: missing a stated requirement, and submitting late or in the wrong format. Both make a proposal non-responsive, and no amount of quality survives that. After those, the repeat offenders are describing need instead of solution, giving outputs where outcomes were asked for, a budget that does not match the narrative, and answering "how will this continue after the grant?" with "we will apply for more grants".
Last reviewed 6 August 2026.
The two that end it before scoring
- A requirement you did not notice
- A missing attachment, an unsigned certification, a page limit exceeded, a required font ignored, a letter that had to be on letterhead. Compliance screening happens before evaluation, and a screened-out proposal is not read. This is exactly what a requirements checklist exists to prevent, and it is why the boring feature is the important one.
- Late, or in the wrong place
- Portals close at a stated time in a stated time zone and do not care. Grants.gov submissions can also be rejected after upload for validation errors, which means submitting an hour before the deadline is not the same as submitting on time.
The ones that cost points
- A need statement where a solution should be
- Three pages establishing that the problem is serious, and half a page on what you will do about it. Reviewers already believe the problem is serious, which is why the program exists. They are choosing between approaches.
- Outputs presented as outcomes
- "We will serve 400 people" is an output. What changed for them is the outcome, and the criterion almost always asks for the second one.
- A budget that contradicts the narrative
- The narrative promises a full-time coordinator and the budget carries 0.4 FTE. Reviewers check, and the discrepancy costs more than the number would have.
- Sustainability answered with more grants
- Every applicant says this. Earned revenue, a public funding stream, a partner absorbing the work, or an honest statement that the intervention is time-limited by design all score better than the universal answer.
- Jargon standing in for specificity
- "Leverage synergies across stakeholder ecosystems" survives because nobody can disagree with it, and it also tells the reviewer nothing. Specific beats safe, even when specific can be argued with.
- Ignoring what the funder said they care about
- The announcement names priorities. A proposal that never uses that language reads as a general proposal sent to whoever was open, which is usually exactly what it is.
The mistake underneath the mistakes
Writing about your organization instead of about the funder's problem. You applied because you need money for something you believe in, and that is a completely legitimate reason that is not the reason anyone funds you.
The funder has a stated intention and a limited budget. The proposal that wins is the one that most clearly advances that stated intention. Everything on this list is a version of forgetting that.
Who asks this most
The answer above is the same whoever you are. What Quillify does about it is not.
Related
- How a reviewer actually reads your proposalHow do grant reviewers actually read proposals?
- What a rejection is actually telling youWhy was my grant proposal rejected and should I reapply?
- How to read a funding announcementHow do I read a NOFO or funding announcement properly?
All guides, or the glossary.
Stop researching and see what you are eligible for.
Browsing and keyword search are free, and there is no card required.