How to Write a Winning Grant Proposal

Grants vs Tenders: Understanding the Difference

Before diving into proposal writing, it's worth clarifying what separates a grant from a tender — because the distinction shapes everything about how you write your application.

Grants fund new projects. A funder — whether government, foundation, or international body — provides money for you to do something that wouldn't happen otherwise. Build a community programme. Develop a new technology. Conduct research. Expand access to services in underserved areas. The funder isn't buying a service for themselves; they're investing in an outcome that aligns with their strategic priorities. You propose the project, you deliver it, and you report on results.

Tenders purchase services. A government department or public body has a specific need — maintain a fleet of vehicles, supply IT equipment, deliver training — and issues a tender inviting suppliers to compete for the contract. The buyer defines the scope. You compete on price, quality, and capability. It's a commercial transaction with a clear client-provider relationship.

The practical difference for your application is significant. In a tender response, you're answering prescribed questions and demonstrating that you meet defined specifications. In a grant proposal, you're making a case — persuading a panel that your project deserves funding over dozens or hundreds of competing applications. That requires a different kind of writing: more narrative, more evidence, more vision, and a much deeper understanding of what the funder is trying to achieve.

Many organisations apply for both. A construction company might tender for government building contracts while also applying for innovation grants to develop sustainable building materials. A technology firm might bid on IT service tenders while pursuing R&D grants from Innovate UK or the Australian Research Council. Understanding the difference helps you tailor your approach — and avoid the common mistake of writing a grant proposal that reads like a tender response.

Anatomy of a Grant Proposal

While every funder has their own application form and requirements, nearly all grant proposals contain the same core components. Master these four sections and you'll have a framework that works across most funding programmes.

Writing a Compelling Problem Statement

The problem statement is where most proposals are won or lost. If the panel doesn't feel the urgency of the problem by the end of your opening section, nothing that follows will matter — no matter how elegant your methodology or how reasonable your budget.

Lead with data. Don't open with a general statement about how "many communities face challenges." Open with a number. "In the Western Cape, 43% of small-scale farmers have no access to cold storage within 50 kilometres of their operations, resulting in post-harvest losses averaging 35% of annual yield." That's a problem a funder can see, measure, and feel motivated to solve. Use the most current, most specific data available — government statistics, peer-reviewed research, your own baseline surveys.

Be specific about who is affected. "Underserved communities" is too vague. "Smallholder farmers in three districts of the Western Cape, predominantly women-headed households with average landholdings under 2 hectares" tells the funder exactly who will benefit. Specificity demonstrates that you understand the problem at ground level, not just from a policy document.

Show urgency and trajectory. Is the problem getting worse? Is there a window of opportunity that will close? "Post-harvest losses have increased 12% over the past three years as average temperatures have risen" tells the panel that delay has a cost. "A new agricultural hub opening in the region in 2027 creates a time-limited opportunity to establish cold chain infrastructure before supply patterns are locked in" creates a compelling case for acting now.

Explain why existing solutions fall short. Funders know that problems rarely exist in a vacuum — other organisations, government programmes, and market forces are already at work. You need to acknowledge what's been tried and explain why it hasn't been enough. Perhaps existing cold storage facilities are too far away, too expensive for smallholders, or designed for commercial-scale operations. This isn't about criticising others' work — it's about demonstrating that your approach fills a genuine gap.

The strongest problem statements are concise — typically 300 to 500 words. They paint a vivid picture of a specific problem, backed by evidence, affecting identifiable people, with clear consequences for inaction. Everything in your proposal flows from this section, so invest the time to get it right.

Budget Development: Where Most Proposals Fall Apart

More grant proposals are rejected for budget problems than for any other single reason, including weak methodology. This is because the budget is where abstract plans meet concrete reality — and where reviewers quickly assess whether an applicant truly understands what it takes to deliver the proposed project.

Itemise everything. A budget line that reads "Personnel — $45,000" tells the funder nothing. Break it down: "Project Manager (0.5 FTE x 12 months x $60,000 annual salary = $30,000) + Field Coordinator (1.0 FTE x 6 months x $30,000 pro-rata = $15,000)." This level of detail demonstrates that you've calculated costs from real salary scales and realistic time allocations, not rounded figures plucked from the air.

Justify every line item. Each cost should answer two questions: what is it, and why is it necessary for the project? "Travel — $3,200: 8 field visits to project sites in rural Western Cape, 400km round trip at $0.50/km = $200/visit x 2 staff per visit x 8 visits." The funder can see exactly what you're planning to spend and why. Compare this to "Travel — $3,200" with no explanation — which invites suspicion rather than confidence.

Align the budget with the narrative. Every activity described in your methodology should have a corresponding cost in the budget, and every cost in the budget should relate to an activity in the methodology. If you describe three community workshops in your methodology but your budget only includes costs for two, the reviewer will notice. This cross-referencing is one of the first things experienced evaluators check.

Include in-kind contributions and matched funding. Most funders want to know that you have skin in the game. If your organisation is contributing staff time, office space, equipment, or volunteer hours, quantify these and include them in the budget as in-kind contributions. If you have matched funding from other sources, state it clearly. A budget that shows the grant covering 60% of project costs, with the remaining 40% from your own resources or other funders, is significantly more compelling than one requesting 100% funding.

Account for indirect costs transparently. Overheads — office rent, utilities, IT infrastructure, management time — are legitimate costs that funders generally accept, typically at 10-20% of direct costs. But state the percentage, explain what it covers, and check the funder's policy on indirect cost recovery. Some funders cap overheads at a specific percentage; others don't fund them at all. Getting this wrong can invalidate your entire application.

The Sustainability Section Most Applicants Skip

Here's a pattern that frustrates funders: an applicant submits a proposal for a two-year project, describes excellent activities and outcomes, presents a solid budget — and then says nothing about what happens in year three. The grant ends. The project ends. The impact evaporates.

Funders don't invest in projects. They invest in change. And change that lasts only as long as the funding isn't change at all — it's a temporary intervention. Your sustainability section needs to answer a simple question: how will the benefits of this project continue after the grant money is spent?

Revenue generation. If your project creates a service, can that service eventually generate its own income? A cold storage facility might charge small fees to cover maintenance. A training programme might certify graduates who pay a nominal fee. Show the funder a path — however gradual — towards financial self-sufficiency.

Institutional embedding. Can the project's outputs be absorbed into existing institutional structures? If you're developing a curriculum, can it be adopted by the education department? If you're creating a database, can a government agency take over hosting and maintenance? Partnerships with institutions that will outlast your project are powerful sustainability signals.

Capacity building. The most sustainable projects are those that build skills and systems within the target community or organisation. If your project trains local technicians to maintain equipment, creates management committees to oversee facilities, or develops policies that become standard practice, the impact continues long after you leave. Document how you'll transfer knowledge and ownership.

Follow-on funding strategy. Being honest about the need for continued funding isn't a weakness — it's realistic. But show that you have a strategy: "Phase 2 funding will be sought from [specific funder] based on Phase 1 results" is much stronger than "We will seek additional funding." Name the funders, explain why your Phase 1 results will make you competitive, and include a timeline.

Required Documentation Checklist

Beyond the proposal narrative and budget, most funders require supporting documentation that validates your organisation's capacity to manage the grant. Missing a single required document is one of the most common reasons for administrative rejection — your proposal may never even reach the review panel.

Financial documentation: Audited financial statements for the past two to three years. These demonstrate your organisation's financial health and its ability to manage grant funds. For newer organisations, management accounts or an accountant's letter may be accepted. Some funders also require a separate audit of any previous grants from the same funding body.

Organisational documents: Certificate of registration or incorporation, tax-exempt status certificates (for non-profits), governance documents (constitution or articles of association), and an organisational chart. These establish that you are a legitimate, properly constituted entity with appropriate governance structures.

Key personnel CVs: Curricula vitae for the project manager and all senior project staff. Funders want to see relevant qualifications, experience with similar projects, and a track record of managing budgets of comparable size. If you're proposing research, include publication records and relevant expertise.

Letters of support: From partner organisations, beneficiary communities, government departments, or other stakeholders who endorse the project. These aren't perfunctory — a strong letter of support from a relevant government official or community leader demonstrates that your project has buy-in and is aligned with local priorities. Give your partners enough time (at least two weeks) to write meaningful letters, and provide them with a brief summary of the project to reference.

Additional requirements vary by funder but commonly include: ethics approval (for research involving human participants), environmental impact assessments (for infrastructure projects), risk registers, monitoring and evaluation frameworks, and logframes (logical frameworks). Check the funder's guidelines carefully and prepare a checklist for each application — the administrative requirements alone can take several weeks to assemble.

"Specificity is what wins grants. Not passion, not vision, not ambition — specificity. The proposals that get funded are the ones where every claim is backed by a number, every activity has a timeline, and every cost has a justification. Vague proposals get vague results: rejection."

Grant Review Panel Member, international development funder

Before You Submit: Final Checks

You've written a compelling problem statement, detailed your methodology, justified every budget line, and assembled your documentation. Before you hit submit, run through these final checks — they catch the mistakes that sink otherwise strong proposals.

Alignment check. Re-read the funder's programme description and priority areas. Does your proposal directly address at least one stated priority? If you have to stretch to make the connection, the reviewers will notice. It's better to not submit than to submit to the wrong programme — it wastes your time and damages your credibility for future applications.

Internal consistency. Does the budget match the methodology? Are the timelines in the work plan consistent with the project duration? Do the objectives in the summary match the detailed objectives in the body? Reviewers frequently find contradictions between sections, and these undermine confidence in the applicant's attention to detail.

Word and page limits. Exceeding limits is an automatic disqualifier with many funders. If the guidelines say 10 pages, submit 10 pages — not 11 with smaller font. Staying within limits demonstrates that you can communicate concisely, which is itself a positive signal about your project management capability.

Eligibility confirmation. Double-check that your organisation meets every stated eligibility criterion. Are you registered in the right jurisdiction? Is your annual turnover within the funder's range? Does your project fall within the eligible activities? Getting rejected on eligibility grounds after investing weeks in a proposal is painful and entirely avoidable.

Peer review. Have someone who wasn't involved in writing the proposal read it through. They'll spot jargon, unclear explanations, logical gaps, and assumptions that seem obvious to you but won't be obvious to a reviewer reading 200 applications. A fresh pair of eyes is the most effective quality control tool you have.

Submission logistics. Know the deadline to the minute — including the time zone. Upload early to avoid portal crashes (most submissions flood in during the final hours). Keep a PDF copy of everything you submitted. Send a confirmation email to the funder if the portal doesn't generate an automatic receipt.