Grant Writing for African NGOs: The 2026 Guide

Most African NGO and university grant proposals are not rejected because the work is bad. They are rejected because the proposal does not match what the funder is funding this cycle, the logical framework cannot be measured, or the budget signals an inexperienced applicant. Across the thousands of participants Resmob has trained across Africa, those three failures account for the overwhelming majority of screened-out proposals — and all three are fixable in a single proposal cycle.

This is a working guide, not a theoretical one. It is written for two audiences in particular: university grants offices in Kenya and East Africa that are building systematic research-funding capacity, and Kenyan NGOs (national and county-level) that are trying to win bilateral, multilateral, or foundation grants. We touch on corporate philanthropy as a funder type later, but the centre of gravity here is what universities and NGOs need to do differently to start winning consistently.

Resource mobilization is broader than grants — it includes partnerships, secondments, government co-financing, and earned revenue. If you are still working out the strategy layer, start with our resource mobilization guide; this guide picks up at the point where you have decided grants are part of the mix and you need to write one that wins.

What is grant writing — and what does it actually involve?

Grant writing is the structured process of converting a project idea into a fundable proposal across the seven sections that nearly every donor expects: an executive summary, a problem statement, a theory of change, a logical framework, a workplan, a budget, and a monitoring-and-evaluation plan. It involves donor research, internal alignment, narrative drafting, and a peer-review cycle — typically four to eight weeks of focused effort for a major bilateral or multilateral application.

The grant writing job is not "writing prose nicely". It is translating an organizational mission into the donor's language — their priorities, their results frameworks, their compliance constraints — without losing the integrity of what your team will actually do in the field. A good grant writer is half strategist and half technical writer. They know that the executive summary is read by every screener and the budget is read by everyone before the narrative.

Different donors weight the seven sections differently. The European Commission's INTPA programmes lean heavily on the logical framework and indicator quality. USAID activities under a Country Development Cooperation Strategy lean on alignment to the strategy's results framework. UK FCDO programmes weight value-for-money and theory of change. Foundations — Mastercard Foundation, Hewlett, Rockefeller — often de-emphasize logframes and weight the problem statement and organizational track record more. The grant writer's first job is to know which of these weightings applies before they write a single sentence of narrative.

A useful comparison of how the same seven sections get weighted by different funders:

The skill is not memorizing the table. The skill is reading the funder's most recent strategy or call documentation and rebuilding this picture for them, every time.

Why do most African NGO grant proposals get rejected?

The single biggest reason is misalignment with the funder's strategy: the proposal pitches what the NGO wants to do rather than what the funder is funding this cycle. Logical-framework errors and unrealistic budgets are common secondary causes, but they are downstream of the alignment problem.

Donor screeners read for fit before merit. The European Commission's INTPA Directorate publishes its multi-annual indicative programme each cycle — the most recent for Eastern Africa runs 2021–2027 and prioritizes the green deal, digital transformation, and human development. Proposals that do not quote the relevant priority by name typically do not survive the first screening pass. The same dynamic holds for USAID's Country Development Cooperation Strategies and FCDO's country-level operating plans — see the broader index of FCDO country plans for whichever country you are applying in. A grant writer's first hour should be spent reading the funder's most recent strategy document, not drafting a problem statement.

This is the strategy-versus-execution gap, and it shows up in proposal after proposal. As we have argued elsewhere, you don't have a funding problem — you have a strategy problem: if your concept is not visibly anchored in the donor's published priorities, no amount of polished prose recovers it. The fix is mechanical, not creative. Open the funder's strategy document. Find the priority that matches your project. Quote it in the executive summary by name. Then build the rest of the proposal around that anchor.

A second-order failure pattern: proposals submitted by organizations that have never had a screening conversation with the donor. Major bilaterals and most foundations expect a pre-submission conversation — a short call, an unsolicited concept note, a sector-meeting introduction — well before the proposal arrives. A cold full-proposal submission to USAID Kenya or the EU Delegation in Nairobi rarely succeeds. The first concept-note or pre-application step exists precisely so the funder can flag fit problems early, and so you can refine the pitch before you spend three weeks writing.

How do you find the right donor for your project?

Donor mapping is the structured process of categorizing funders into four families — bilateral, multilateral, foundations, and corporate philanthropy — and then narrowing each family by sector match, geography, and active funding cycles. Done well, it produces a ranked list of 8–15 funders whose published priorities visibly overlap your project, which is enough to start two or three pre-submission conversations in parallel.

The four families behave differently. Bilateral donors — USAID, FCDO, GIZ, JICA, SIDA, Danida — fund through country-level strategies and structured calls. Multilateral donors — the European Commission's Eastern Africa MIP 2021–2027, the World Bank, UN agencies — fund through programmatic instruments tied to country compacts. Private foundations — Mastercard Foundation, the Hewlett Foundation, the Rockefeller Foundation, Ford, Open Society — fund along thematic priorities set by their boards. And corporate foundations — Safaricom Foundation, Equity Group Foundation, KCB Foundation — typically fund within tightly scoped CSR themes anchored to the parent company's commercial geography. Corporate philanthropy is rarely a major share of an African NGO's funding stack, but it is worth mapping when your work overlaps a corporate's host community or core market.

Most NGOs we train start their donor mapping with three high-leverage moves. First, they sign up to receive published calls from the major donors operating in Kenya — USAID Kenya, the EU Delegation, FCDO, GIZ, the AfDB. Second, they keep a live database of active grants — the funding-opportunities feed on this site is one such resource — and triage every new entry against their thematic focus. Third, they identify the two or three funders whose strategy documents most closely mirror their work, and they invest in a relationship cadence with those funders that does not depend on a specific proposal cycle. That third move is what separates organizations that win consistently from organizations that win occasionally.

Donor mapping is a one-week investment that pays for itself across every subsequent proposal. Do it once, do it well, and revisit it every six months as published strategies refresh.

What is a Theory of Change — and why do donors require it?

A Theory of Change is a causal map showing how project activities lead to outputs, outcomes, and long-term impact. Donors require it because it forces the proposal to articulate every assumption between activity and impact — and to name the assumptions that, if they fail, will derail the project before it finishes. Without an explicit Theory of Change, neither the donor nor the implementer can tell whether a missed result is a design failure or an execution failure.

The methodology behind Theory of Change is grounded in results-based management as developed by the OECD-DAC and now standardized across most major donors. The structure has four levels: activities (what we do), outputs (what we produce), outcomes (what changes for participants in the medium term), and impact (the long-term societal change). Each level connects to the next through one or more assumptions — testable statements like "if young women complete the training, they will apply for the available jobs" or "if county officers receive the planning template, they will use it in the next budget cycle". The Theory of Change is exactly as detailed as it needs to be to make every assumption visible.

A worked example, lightly adapted from a Kenyan youth-livelihoods project we have advised on:

Activity:    Deliver a 6-week digital-skills curriculum to 500 unemployed youth
                        ↓ (assumption: participants complete the curriculum)
Output:      400 young people certified in digital marketing and freelance work
                        ↓ (assumption: certified youth pursue digital work)
Outcome:     280 young people earning freelance income within 6 months of
             certification
                        ↓ (assumption: freelance income is stable enough to
                                        compound)
Impact:      A measurable reduction in youth unemployment and outmigration
             in two target counties over 36 months

The diagram is short. The narrative around it does the heavy lifting: each downward arrow is one or two paragraphs unpacking why we believe the assumption holds, what evidence we have, and what we would do if it fails. The result is a proposal that is auditable in advance — the donor can see exactly where the project would break, and decide whether the risk is acceptable. That is the entire point.

The most common Theory of Change failures we see in African NGO proposals are: a diagram with no assumptions named, a diagram that ends at "output" without any plausible link to outcome, and assumptions that are obvious truisms ("if we train people, they will be more skilled") rather than testable hypotheses. Each is fixable in an hour with a peer-review pass.

How do you write a Logical Framework that survives screening?

A Logical Framework — or logframe — is a 4×4 matrix linking the goal, outcomes, outputs, and activities of a project to indicators, baselines, targets, and means of verification. Whether your logframe survives screening depends almost entirely on whether each indicator is SMART (specific, measurable, achievable, relevant, time-bound) and whether each assumption is genuinely testable.

The logical framework approach was formalized by USAID in the 1970s and has since been adapted by the World Bank, the EU, the UK, and most major bilaterals. The structure is consistent across donors even where the column labels differ slightly: the first column states the result level, the second states one or more SMART indicators, the third states the baseline value and target value (with dates), and the fourth states how the indicator will be verified. A typical logframe row for a Kenyan health project might read:

The most common reasons logframes get screened out are diagnostic, not creative. Indicators with no baseline value (so the donor cannot tell whether the target represents progress). Targets with no date (so the donor cannot tell when achievement is expected). Means of verification that point to a data source the implementer does not actually control. Assumptions phrased as wishes rather than testable hypotheses. The fix for each is mechanical: rewrite each indicator with a number, a baseline year, a target value, and a target date, and stress-test each assumption with the question "what would falsify this assumption, and what would we do then?". A weak logframe rewritten this way takes one afternoon and lifts a proposal out of the screening reject pile.

A second discipline that separates winning logframes: alignment with the donor's own results framework. If you are applying under USAID's Kenya CDCS, your outcomes should map cleanly to one of the CDCS Development Objectives. If you are applying under EU INTPA Eastern Africa MIP 2021–2027, your outcomes should map to a priority area in the MIP. The exercise of cross-walking your logframe to the donor's strategy is the highest-leverage hour you will spend in the entire proposal — and it is the single biggest tell that separates a serious applicant from one the screener will not recommend forward.

What does a strong grant budget look like in 2026?

A strong 2026 grant budget combines direct programme costs, indirect costs (typically 7–15% under a NICRA-style arrangement), co-funding contributions from your organization or partners, and clear treatment of VAT and statutory obligations under Kenyan tax law. Critically, every budget line must reconcile back to a workplan activity — donors that scan the budget first (which is most of them) check this reconciliation before they read the narrative.

Direct costs are the items spent specifically on delivering the project: personnel time charged to the project, project travel, materials, training delivery costs, M&E expenses. Indirect costs are the share of organizational overheads — finance team, office rent, IT, leadership time — that supports the project but is not exclusive to it. Most reputable donors expect indirect costs at 7–15% of direct costs, and several use a Negotiated Indirect Cost Rate Agreement (NICRA) framework where the rate is established once and applied across grants. Skipping indirect costs entirely is a tell of an inexperienced applicant; padding them above donor norms gets the budget flagged. The right move is to know your organization's indirect-cost rate before you start budgeting and apply it consistently.

Co-funding — the portion of the project budget your organization or your partners contribute in cash or in kind — is often required by EU and FCDO programmes and is a signal of organizational commitment to others. In-kind contributions (volunteer time, donated equipment, office space) can typically be valued at fair-market rates and counted toward co-funding, provided the methodology is transparent in the budget notes.

VAT and statutory deductions in Kenya deserve their own column in any budget submitted to a Kenyan NGO. Donor-funded projects can sometimes claim VAT exemption under Kenya Revenue Authority rules, but the exemption process takes time and is project-specific; assume VAT is payable unless your finance team has confirmed exemption status. Withholding tax on consultant fees, NSSF and SHIF contributions on staff costs, and pay-as-you-earn obligations all need to be correctly handled in the budget — donors do not enjoy reading proposals where the implementer has obviously not budgeted for statutory costs.

Three quick budget red flags we routinely see screeners react to: round numbers everywhere (suggests no real costing exercise was done), no contingency line (most donors expect 5–10%), and unit costs that diverge sharply from prevailing market rates without explanation. Each is fixable in a half-day budget review.

How do you respond to an RFP without missing eligibility?

RFP response starts with an eligibility-and-compliance checklist — if any "shall" clause in the RFP is unmet, the proposal is disqualified before content is read. The discipline is to extract every mandatory requirement from the RFP into a single tracked list before any narrative is drafted, and to assign a name to each requirement so nothing falls through the cracks.

Major donors publish detailed compliance guidance precisely so applicants do not waste their time. The European Commission's PRAG (Practical Guide) governs procurement and grant procedures across most EU external-action funding. Each donor's eligibility rules tend to cluster around four themes: organizational eligibility (legal status, registration, audit history), partnership requirements (consortium composition, lead-applicant rules, mandatory partners), financial eligibility (turnover thresholds, audit history, co-funding minimums), and compliance attestations (anti-fraud, safeguarding, environmental, conflict-of-interest declarations).

The screening phase happens before evaluation. Screeners run a checklist against your submission and disqualify anything that fails. Common screening killers: missing a mandatory annex (audited accounts, organizational registration certificate, signed declarations), missing a mandatory partner type, exceeding the page limit, submitting after the deadline, using the wrong template version. None of these is a content failure; all of them are process failures. The fix is the same as for any other complex compliance task: a checklist, owned by one person on the team, signed off before submission.

Two practical disciplines that separate organizations that consistently pass screening. First, a 72-hour buffer before deadline, used for compliance review only — no narrative editing, just verifying every requirement. Second, a peer-screen by someone outside the writing team who reads the RFP cold and the proposal cold, and flags every "shall" clause they cannot find evidence of in the proposal. Either discipline alone catches most screening failures; both together catch nearly all of them.

What's the #1 grant-proposal mistake — and how do you fix it?

The single most common mistake is leading the executive summary with what your organization does instead of with the problem the donor is trying to solve. Proposals get screened out in the first 90 seconds when the executive summary fails the funder-relevance test — and most do.

We have written about this at length in the #1 grant-proposal mistake costing African organizations millions. The pattern is universal: the proposal opens with the implementing organization's history, mission, and capabilities, and only gets to the donor's priority three or four paragraphs in. By that point the screener has lost interest. Across the thousands of participants Resmob has trained across Africa, this is the single most common failure pattern we see — and it is the easiest to fix.

The fix has three parts. First, the executive summary's opening sentence must name the donor's strategic priority, by name, in the donor's own language. Second, the second sentence must connect that priority to a specific population, place, and timeframe — not the donor's geography in general but exactly where this project will operate. Third, the third sentence must state, in one line, what the project will achieve and what it costs. The implementer's history goes into the organizational capacity section later, where it belongs.

Rewriting an executive summary along these lines takes about 90 minutes and is the single highest-leverage edit in the entire proposal. We have seen the same proposal go from the screening reject pile to the technical evaluation stage on the strength of a rewritten executive summary alone, with no other content changes.

How do university grants offices win research funding consistently?

University grants offices that win consistently run a centralized operation with a 90-day rolling pipeline, an internal peer-review screen before submission, and a relationship cadence with funders that does not depend on individual researchers. Universities that leave grants development to individual academics, with no central coordination and no peer-review function, win occasionally and struggle to compound the wins.

The case study we point to most often is JKUAT's grants office case study — Jomo Kenyatta University of Agriculture and Technology built a centralized grants function with three operating disciplines that we now see across every consistently winning university grants office in East Africa. First, every active proposal is tracked on a single pipeline view, with dates, donors, principal investigators, status, and submission deadlines visible to the whole office. Second, every proposal goes through an internal peer-review screen before submission — typically two reviewers with subject-matter knowledge plus one with funder-relations experience — and the screen kills proposals that would not survive donor screening anyway. Third, the office maintains a relationship cadence with priority funders (donor agency country offices, major foundations) that is independent of any specific call — quarterly check-ins, sector-meeting attendance, hosted events.

The same operating model translates directly to NGOs that run a programme-development function. The principle is centralization-with-quality-control: one team owns the pipeline, one team owns the peer-review screen, one team owns funder relationships. Where universities have an advantage is that academic departments can be incentivized to submit through the central office rather than around it, because the office handles the compliance overhead they would otherwise carry alone.

For universities and academic institutions in particular, see our playbook for university grants offices — it is the operational companion to the strategic content in this guide. The free university grants office playbook covers the operating model, donor-engagement cadence, and proposal-screening framework in detail; it is the single artefact most university grants leaders we work with use when they are setting up or upgrading their function.

What's the next step?

Pick one move from this guide and ship it this week — most of the discipline gap between organizations that win consistently and organizations that win occasionally is a series of small, mechanical improvements applied repeatedly, not a single strategic insight.

For university grants offices, the highest-leverage starting move is the free university grants office playbook — it gives you the operating model, the proposal-screening framework, and the funder-engagement cadence in one document. For NGOs that need a deeper structural intervention, our 3-day Grant Writing & Proposal Development program covers the full set of disciplines this guide outlines, with hands-on work on a real proposal you bring to the room. Both options exist precisely because different organizations need different things — a playbook to run the practice you already have, or training to build the practice you do not yet have.

If you are not sure which fits, book a training enquiry at no fee. Bring a recent proposal we can review together; we will map the bottleneck and recommend the shortest path. The shortest path may or may not involve us. Either way, you leave with a clearer picture of where to spend the next month of effort.