10 Mistakes That Get Proposals Rejected

Most rejected proposals are not rejected for bad ideas — they are rejected for
avoidable, recurring errors that signal a lack of preparation. Reviewers screen
for these patterns within minutes. Here are the ten that sink applications, and
the fix for each.

1. VAGUE BENEFICIARIES — "the community" instead of a counted, disaggregated
group. FIX: name them, count them, break them down by sex and age.

2. NO M&E PLAN — results with no way to measure or verify them. FIX: give every
result an indicator, baseline, target, and source of proof.

3. UNREALISTIC BUDGET — round, unexplained, or mismatched to activities. FIX:
unit costs tied to the logframe, lean overhead, M&E as a line.

4. MISSING CO-FINANCING — asking the donor to carry 100% of the risk. FIX: show
cash or in-kind contribution, however modest.

5. WEAK PROBLEM EVIDENCE — adjectives where data should be. FIX: lead with hard
numbers and the cost of inaction.

6. CONFUSING OUTPUTS WITH OUTCOMES — measuring effort, not change. FIX: push
every output one level further to the result it produces.

7. GENERIC, COPY-PASTE NARRATIVE — a template that ignores this donor's
priorities. FIX: map the proposal to the funder's stated objectives explicitly.

8. NO INSTITUTIONAL CAPACITY — no evidence you can manage the money. FIX: cite
past projects, staff, and a simple governance structure.

9. IGNORING RISKS — pretending nothing can go wrong. FIX: name the top risks and
your mitigation; it signals maturity, not weakness.

10. INCONSISTENT NUMBERS — targets that differ between narrative, logframe, and
budget. FIX: proofread for the "golden thread" — one set of figures everywhere.

A final habit: have someone outside the project read the draft cold. If they
cannot restate the problem, the beneficiaries, and the result in two sentences,
a reviewer will not either.