Writing Grant Proposals That Get Funded: A Step-by-Step Framework

Most NGOs do not lose funding because their work is unimportant. They lose it because their grant proposals fail to show, quickly and convincingly, that a clearly defined problem will be solved by a well-designed project run by a capable team at a reasonable cost. Reviewers often read dozens of applications against a scoring grid, and the proposals that rise to the top are rarely the most eloquent. They are the most coherent. This article sets out a step-by-step framework you can use for any call, whether it is a small foundation grant or a multi-year institutional programme.

Why a framework beats inspiration

Grant writing is often treated as a creative sprint: someone senior blocks out a week, writes furiously and submits at midnight. The result is usually a document that reads well in places but contradicts itself elsewhere, with a budget that does not match the activities and indicators that do not match the objectives. A repeatable framework protects you from this. It turns the proposal into a small project with its own scope, schedule, roles and quality checks, which is exactly how you would run any other piece of work. If your team would benefit from a refresher on running work this way, our Project Management Fundamentals workshop covers scoping, planning and governance in an NGO context.

Step 1: Decide whether to apply at all

The cheapest proposal is the one you do not write. Before anyone opens a template, run a short go/no-go review with the people who will deliver the project, not just the fundraising team.

If you answer “no” or “not sure” to two or more of these, think hard before proceeding. Saying no to a poor fit frees time for a stronger application elsewhere.

Step 2: Read the call like a reviewer

Print the call text, the guidelines and the evaluation grid, and read them together. Highlight every “must”, “should” and “will be assessed on”. Then build a compliance matrix: a simple table that lists each requirement and where in your proposal you will address it. This becomes your writing map and your final checklist.

Requirement from the call	Weight / criterion	Where we address it	Owner
Demonstrate involvement of target groups in design	Relevance	Section 2.3, Annex B consultation summary	Programme lead
Gender-sensitive indicators	Quality of design	Logframe, Section 4.2	M&E officer
Sustainability after funding ends	Sustainability	Section 6	Director
Maximum 15 pages, font size 11	Admissibility	Whole document	Editor

Notice which criteria carry the most weight. If “relevance” and “design” make up most of the score, they deserve most of your words and your best evidence.

Step 3: Define the problem before the project

Weak proposals start with the activities the organisation already wants to run. Strong proposals start with the problem and work forward. Use a problem tree: write the core problem in the middle, its causes below and its effects above. Then check each cause: is it supported by evidence you can cite (your own needs assessment, government data, published research, consultations with the community)?

A good problem statement is specific about who is affected, where, how, and why existing efforts have not solved it. Avoid sweeping claims such as “poverty is a global challenge”. Instead, describe the particular gap your project fills.

Hypothetical example: “In the three districts we serve, young women who leave school early have few routes into paid work. Local vocational courses are held in the daytime, far from where they live, and do not offer childcare. Our consultations with 40 participants in previous programmes identified time, travel and childcare as the main barriers.”

Note how the example points to its own source of evidence. If you cite numbers, make sure you can back them up if asked.

Step 4: Build the logic, then write

Turn the problem tree into an objective tree by rewriting each negative statement as a positive change. This gives you the backbone of a results chain or Logical Framework: overall objective (impact), specific objective (outcome), outputs and activities. Many institutional funders require a logframe; even when they do not, building one keeps your narrative honest.

Test the logic from the bottom up with “if… then…” statements. If we deliver evening training with on-site childcare, then more young women complete the course. If more complete the course and we broker work placements, then more move into paid work. Each “then” depends on assumptions (for example, that local employers will take placements), and those assumptions belong in your risk section.

Write objectives reviewers can score

• One overall objective that the project contributes to, not one it achieves alone.
• One (occasionally two) specific objectives describing the change the project is accountable for.
• A small number of outputs: tangible things the project delivers.
• SMART indicators for each level, with baselines and targets where possible. Our guide to monitoring and evaluation on the NGO Training blog goes deeper on indicator design.

Step 5: Draft section by section

Most templates follow a similar pattern. The table below summarises what each section needs to do and the most common failing.

Section	What it must achieve	Common failing
Summary	State problem, solution, beneficiaries, results and cost in under a page	Written first and never updated; vague
Context and need	Show evidence of a specific, current problem	Generic statistics unconnected to the target group
Objectives and results	Clear, measurable change the project will cause	Activities disguised as objectives
Methodology and activities	Explain how and why the approach works	Lists of activities with no rationale
Work plan	Realistic sequence and timing	Everything starts in month one
Monitoring and evaluation	How progress will be tracked and lessons used	One paragraph promising an “external evaluation”
Risks and assumptions	Credible risks with mitigation	Only external risks; nothing about the organisation itself
Organisational capacity	Why your team can deliver	A copy of the website’s “About us” page
Sustainability	What continues after funding ends, and how	“We will seek further funding”
Budget and justification	Costs that match activities and are reasonable	Round numbers, unexplained lines, hidden overheads

Writing techniques that help reviewers

• Mirror the funder’s language. If the call talks about “resilience” and “inclusion”, use those terms (honestly) so reviewers can find what they are scoring.
• Lead with the point. Put the main claim in the first sentence of each paragraph, then support it.
• Use headings that match the evaluation grid. Make it easy for a tired reviewer to tick the box.
• Prefer concrete detail to adjectives. “Weekly mentoring sessions in two community centres” beats “innovative, holistic support”.
• Show, don’t assert, capacity. Describe comparable projects you have delivered and what you learnt from them.

Step 6: Build a budget that tells the same story

Reviewers read the budget to check whether the narrative is real. Every activity in your work plan should have a cost, and every significant cost should trace back to an activity. Build the budget bottom-up from unit costs (number of sessions × cost per session) rather than top-down from the maximum grant amount.

1. List all activities from the work plan and logframe.
2. Identify the inputs each needs: staff time, travel, venues, equipment, materials, subcontracts.
3. Estimate quantities and unit costs, using quotes or past actuals where available.
4. Apply the funder’s rules on eligible costs, indirect costs and co-financing.
5. Write a budget justification that explains any line a reviewer might question.
6. Reconcile: check that totals, percentages and staff allocations match the narrative.

Estimating durations and costs with confidence is a skill in its own right; the Advanced Project Management Tools & Techniques workshop covers estimating, budgeting and tracking in detail.

Step 7: Review, polish and submit early

Schedule at least two review rounds. In the first, a colleague who has not been involved reads the proposal against the evaluation grid and scores it honestly. In the second, someone checks consistency: numbers, dates, names, beneficiary figures and indicators must be identical everywhere they appear.

A hypothetical walk-through

Imagine a small environmental NGO responding to a foundation call on urban biodiversity. Its first instinct is to propose the tree-planting days it already runs. Working through the framework, the team realises the call’s main criterion is long-term community ownership, which its planting days do not address. Its problem analysis shows that newly planted areas decline because no one is responsible for maintenance. The redesigned project trains neighbourhood volunteer groups to adopt and care for green spaces, with a light-touch agreement with the municipality. The budget now includes training, simple tools and a coordinator’s time, and the indicators measure how many sites are actively maintained a year later rather than how many trees were planted. The proposal is shorter than the first draft, but far more persuasive.

Common mistakes to avoid

• Bending the mission to fit the money. Reviewers can usually spot a project invented for the call.
• Confusing activities with results. “Hold ten workshops” is an activity; “participants apply new skills in their jobs” is a result.
• Overpromising. Ambitious targets with no baseline undermine credibility.
• Ignoring the evaluation grid. If a criterion carries points, give it a clear, signposted answer.
• Inconsistent numbers. A beneficiary figure that changes between sections suggests a careless team.
• Writing for yourself. Internal jargon and acronyms slow reviewers down.
• Treating rejection as the end. Feedback and reusable content are valuable assets.

Make winning grant proposals a team habit

Organisations that win funding consistently treat grant proposals as an organisational process rather than a heroic individual effort. Keep a content library of approved text (organisational description, safeguarding policy summaries, past results, staff profiles), maintain a calendar of relevant funders, and hold short debriefs after every submission. Positioning your organisation clearly, segmenting funders like any other audience and communicating results well are all marketing skills; our Mastering Marketing workshop looks at fundraising communications from that angle.

Want your team to write stronger proposals and run the funded projects with confidence? NGO Training offers practical one-day workshops in Brussels, and we can bring the material to your office through in-house training tailored to your funders and projects. Get in touch to discuss what your team needs.