Most rejected proposals are not rejected on their ideas. They are rejected before anyone reads the ideas.
The first round of elimination is compliance: submission deadline, page limit, font specification, required annexes. Reviewers working through a large pile apply those rules first because the rules let them reduce the pile without reading. A proposal that misses one of them never reaches the section where the programme design sits.
That is the part organisations find hardest to accept. Twenty-five years of reviewing and writing proposals across Kenya, the East African Community and international NGOs has produced a consistent pattern: the technical quality of the work and the success rate of the proposals describing it are only loosely related.
What follows is the rejection list as it appears in practice, ordered by how early it kills an application.
Stage one: rejected before review
Late submission. Grant deadlines are administrative, not editorial. A minute past the close is a disqualification, and no relationship with the programme officer reverses it. Work backwards from the deadline in daily increments rather than reserving the final week.
Format non-compliance. Page count, font, margin, file format, annex order. These read as trivial. They are the cheapest possible filter for a reviewer with 200 submissions, which is exactly why they get applied first.
Budget above the ceiling. Where a call states a maximum, exceeding it ends the application. It is a competition, so there is no revision round. This one is worth stating plainly because organisations routinely assume a strong proposal earns a negotiation. It does not.
Stage two: rejected on the financials
Most donors score in two passes, technical soundness and then financials. A proposal can pass the first and fail the second.
Administrative costs above 20% of the budget carry a materially higher rejection rate. If your overhead line crosses that threshold, either restructure what sits in it or justify it explicitly in the budget narrative. Do not leave a reviewer to draw their own conclusion.
No co-financing shown. Very few donors intend to fund 100% of anything. A budget that requests the full amount without showing other contributions, including in-kind and staff time, signals an organisation with no other funders. That reads as risk.
No budget narrative. Unit costs without explanation force the reviewer to guess whether a figure is reasonable. Reviewers who guess, guess unfavourably.
Inconsistency between narrative and budget. If the proposal describes six field visits and the budget funds four, the reviewer stops trusting both documents.
Stage three: rejected on substance
Misalignment with the funder's objectives. The most common substantive failure. A proposal advancing your mission rather than theirs will lose to a weaker programme that advances theirs. Before writing, answer in writing: what does this funder say its priorities are, in its own published language, and which of my objectives moves them?
No clear solution path. Donors fund solutions to identified problems. Where a proposal describes a problem and requests resources without demonstrating the mechanism connecting the two, it does not persuade.
Beneficiaries unquantified. "People living with HIV" is a category. "1,400 people living with HIV, of whom 820 are women and 130 have a disability" is a beneficiary count. The second can be verified, budgeted against, and reported on. The first cannot.
No evidence of how the need was identified, or by whom. Assessments, community consultation, baseline data. Absent these, the need is an assertion.
Duplication with existing programmes. A proposal that shows no awareness of who else works in the area invites the assumption that the work is already funded.
Sustainability not demonstrated. What happens when the grant closes is a scored question in most frameworks, and it is frequently answered with a sentence.
Weak executive summary. In many review processes the executive summary is the only section every panel member reads in full. It is written last and treated as a formality more often than any other section.
Stage four: rejected on craft
Unreadable formatting. Long unbroken paragraphs, dense fonts, no headings. A busy reviewer scanning quickly should be able to locate the problem statement, the objectives, the beneficiary numbers and the budget total without hunting.
Grammatical errors. These are read as a proxy for the care an organisation will apply to the grant itself.
Recycled text from a previous bid. Reusing sections is fine and efficient. Leaving in a previous funder's name, or language aimed at a different priority, is a signal that the organisation applies a single template to every donor.
Excessive jargon. Technical density intimidates non-specialist panel members, who are frequently the ones scoring.
No references or testimonials. Evidence from people who have already received your work is more persuasive than any claim you make about it.
The compressed version
In summary, the mistakes that most often end an application:
- Ambiguity about what is actually being funded
- Duplication, and no linkage to other programmes
- Beneficiaries not identified or quantified
- No explanation of how the need was identified
- No logical link between problem, objectives and activities
- Unrealistic timeframes
- Sustainability not demonstrated
- Inconsistent budget, no narrative
- Poor packaging, weak writing, grammatical errors
- A weak executive summary
What to do with a rejection
Request the reviewer feedback where the funder provides it, and read it against this list rather than against your own view of the proposal. Most organisations that raise their win rate do so by fixing three or four recurring items, not by writing better prose.
The diagnosis of each failure, the worked examples, and the seven section checklists sit in The Art and Science of Proposal Writing — available here.
For the surrounding method, see our complete guide to grant writing. If the pattern in your organisation is that strong proposals keep losing, the cause is usually upstream of the proposal: read you don't have a funding problem, you have a strategy problem. We teach the full process in our resource mobilization training.