An executive director once sent me a rejected proposal and asked, almost angrily, what the funder could possibly have found wrong with it. The programming was solid. The organisation had a real track record. I read it twice before I saw it. The proposal answered every question the organisation wanted to talk about and almost none of the questions the funder had actually asked in the call for proposals. That single gap, more than weak writing or a thin budget, is the reason most grant proposals get rejected, and almost nobody tells founders this directly.
You Are Answering Your Own Priorities, Not the Funder’s
Every funder publishes, somewhere in their guidelines, exactly what they care about this cycle. Sometimes it is explicit, a clearly stated theme or geographic focus. Sometimes it is buried in the language of previous grants they have awarded. Organisations often write the proposal they wish the funder wanted, built around their own existing program, rather than the proposal the funder actually described. A reviewer reading fifty submissions in a week does not have the patience to translate your priorities into theirs. State clearly, in your first paragraph, how your project directly answers what they said they are funding this cycle.
Your Problem Statement Is Generic
“Poverty is a major challenge in Nigeria” is true and useless. It tells a reviewer nothing they did not already know, and it fails to prove you understand your specific community better than the fifty other applicants describing the same broad continent. Replace generic statements with specific, local, evidenced ones. “In the three wards we work in across Kaduna state, our own needs assessment conducted in March found that sixty two percent of households reported skipping at least one meal weekly in the past year” does more work in one sentence than three paragraphs of general poverty statistics.
Your Theory of Change Does Not Actually Connect
Reviewers are trained to check whether your activities logically lead to your outcomes. A proposal that lists training workshops as an activity and “reduced poverty” as the outcome, without any explanation of the steps between those two things, reads as wishful rather than strategic. Walk the reviewer through the chain deliberately. Training leads to specific new skills. Skills, applied consistently, lead to increased income. Increased income, sustained over the grant period, contributes to the broader outcome you are claiming. Each link should be explicit, not assumed.
Your Budget Does Not Match Your Narrative
I have written about this at length elsewhere, but it deserves repeating here because it causes so many rejections. If your narrative describes reaching two thousand beneficiaries and your budget only accounts for enough materials, staff time, and transport to realistically reach three hundred, an experienced reviewer notices the mismatch immediately, and it damages trust in every other number on the page.
You Ignored the Word Count and Formatting Rules
This sounds minor until you have sat on a review panel yourself. Many funders, particularly larger institutional ones, use formatting compliance as an early filter simply because volume makes full review of every submission impossible. A proposal that exceeds the page limit, uses the wrong font size, or skips a required section gets set aside before anyone even evaluates the quality of the actual programming. Follow the instructions exactly, even the ones that feel bureaucratic and unnecessary.
Your Organisation’s Capacity Section Is Thin
Funders are not only evaluating your idea. They are evaluating whether your specific organisation can deliver it. A common rejection cause is a strong program idea paired with a weak organisational capacity section that fails to demonstrate relevant past experience, adequate staffing, or financial systems capable of managing the requested grant size. If your organisation is smaller or newer, address this directly rather than hoping the reviewer will not notice. Explain your specific plan for building the capacity the project requires, including any partnerships that fill gaps in your current team.
You Submitted the Same Proposal to Every Funder
Reviewers who have worked in this sector for years can often recognise a proposal that was written for a different funder and lightly edited. Generic language, misaligned priorities, and a tone that does not match the actual funder’s stated values are common tells. Every proposal deserves at least one full read specifically checking that it speaks to this funder, using this funder’s language, addressing this funder’s stated priorities, not the priorities of whoever you last applied to.
The Bigger Picture on Why Grant Proposals Get Rejected
I want to say this plainly because I have watched good organisations lose heart entirely after a string of rejections. A rejected proposal is not a verdict on whether your mission matters. It is usually a verdict on whether this specific document, submitted to this specific funder, made the connection clear enough for a stranger with fifty other applications to see it too. That is a solvable, fixable problem, not a referendum on your organisation’s worth.
If your proposals keep coming back with silence or generic rejection letters and you cannot tell exactly why, an outside read often catches what you can no longer see after living inside the document for weeks. Fresh eyes notice the gap between what you meant to say and what the page actually says, and that gap is usually smaller and more fixable than it feels after a third rejection in a row.
Send me your next proposal before you submit it and let us find the gap together while there is still time to fix it.