Most concept notes are rejected in the first three minutes, before a single budget line is checked. Reviewers reading a stack of proposals are not looking for reasons to say yes; they are looking for reasons to set yours aside. The patterns that survive that first pass are consistent enough to list.
1. A problem stated as evidence, not adjectives
“Many smallholder women remain marginalised” is an adjective in search of a fact. A problem statement that survives review names the population, the behaviour or condition, and the source: who is affected, what is happening to them, and where the number comes from. Evidence can be challenged, verified and built on. Adjectives cannot.
2. Outcomes that are plausible this year
Funders read proposed outcomes for credibility, not ambition. An outcome that promises transformed livelihoods across a county in twelve months tells the reviewer you have not costed your own theory of change. Outcomes that are specific, time-bound and proportional to the budget signal an implementer who has done this before.
3. A logic chain that closes
Activities lead to outputs, outputs to outcomes, outcomes to the goal. When a proposal lists trainings but the outcome depends on market access the project never funds, the chain snaps, and with it the reviewer’s confidence. Trace the chain yourself before submission and count the missing links.
4. A budget that explains itself
Honest budgets are specific budgets. Line items that match the narrative, unit costs that look like local prices, and a share of personnel time that matches the work described all read as care. A budget where 80 percent sits in “other” reads as a wish list. Reviewers fund documents they can defend to their own board.
5. A problem the funder is actually trying to solve
The strongest paragraph in many rejected notes is the one that would have opened a better submission: a clear line connecting the proposal to the funder’s stated priority. Fit is not flattery; it is the reviewer’s easiest signal that this application belongs in their portfolio rather than their forwarding pile.
A checklist before you send
- Problem statement has a source and a population, not just adjectives.
- Outcomes are time-bound and proportional to the budget.
- Every activity can be traced to an outcome in the same document.
- Budget lines match narrative lines, with unit costs you could defend aloud.
- The first paragraph names the funder’s priority in their own words.
- Someone outside the team has read it and found no missing links.
Proposals are not won by the flashiest theory of change. They are won by documents a reviewer can defend without calling you for clarification. Write for that reader and the stack gets shorter.