In short
To write a grant proposal, read the funder’s guidelines first, define one clear problem with evidence, design a solution with measurable outcomes, plan the activities and timeline, cost every activity in a realistic budget, show how results will last, prove your organisation can deliver, then check everything against the guidelines before submitting.
A grant proposal is a written case for funding. It persuades a funder that a real problem exists, that your project will change it, that the money will be well spent and that your organisation can be trusted to deliver. Strong proposals are not the longest or the most eloquent; they are the clearest and the best evidenced. The ten steps below follow the order in which experienced proposal writers work, which is not the same as the order of the finished document.
Step 1: Read the guidelines and decide whether to apply
Before writing a word, read the call for proposals or funding guidelines from start to finish. Note the eligibility rules, the funder’s priorities, the maximum grant, the deadline, the required sections and attachments, the page or word limits and how proposals will be scored.
Then make an honest go or no-go decision. If your project only fits the funder’s priorities after a lot of reshaping, or you cannot meet a hard requirement such as registration age or audited accounts, it is usually better to spend the time on a funder that fits. If anything is unclear, ask the programme officer before you start, not after.
Step 2: Define the problem with evidence
Write down, in one or two sentences, the specific problem the project will address: who is affected, how many, where, and what happens if nothing changes. Then collect evidence: recent official statistics, research, reports from reputable agencies and your own surveys or needs assessments, each with its source and date.
Describe the problem from the point of view of the people affected, not your organisation. A lack of funding is never the problem; it is the obstacle to solving it.
Step 3: Set a baseline and define who will benefit
Record the starting situation you will measure progress against, broken down by the groups most at risk of being left behind, such as people in poverty, women and girls, persons with disabilities and minority or indigenous communities. Say who will benefit directly and indirectly, how many, and how they will be selected. Funders increasingly expect data that is disaggregated by sex, age and disability.
Step 4: Design the solution and explain why it will work
Describe what you will do, step by step, and link each activity to the problem it solves. Explain why your approach will work better than alternatives: evidence from elsewhere, results of a pilot, local knowledge or a partnership. A simple theory of change, a short explanation of how activities lead to outputs, outcomes and long-term impact, makes the logic visible to reviewers.
Step 5: Write measurable objectives, outputs and outcomes
Turn the solution into objectives that are specific, measurable, achievable, relevant and time-bound (SMART). For each one, separate outputs (what you deliver) from outcomes (the change those outputs cause) and choose one or two indicators you can actually measure, with a source of evidence. Many institutional donors ask for this in a logical framework table.
Step 6: Plan activities, timeline, risks and monitoring
List each main activity with who is responsible and when it starts and ends. Turn the key moments into milestones on a timeline, allowing realistic time for hiring, procurement and permissions. Identify the main risks to delivery, rate their likelihood and impact, and explain how you will prevent or handle each one. Finally, describe how you will monitor progress, evaluate results and report to the funder.
Step 7: Build a realistic budget
Cost every activity in the plan using real prices: supplier quotes, salary scales and published rates. Show the quantity and unit cost for each line so reviewers can check the arithmetic, include overheads only as the funder allows, show any co-funding, and use the funder’s currency and budget template. Add a short budget justification that explains how the largest costs were calculated. The budget and the narrative must tell the same story.
Step 8: Explain sustainability and the exit plan
Say what will continue when the grant ends, who will run and pay for it, and how you will hand over responsibly. Funders want their money to create change that lasts, not a service that stops on the last day of the grant.
Step 9: Prove your organisation can deliver
Introduce your organisation after the project, not before it: your history, vision and mission, track record with numbers, a short success story, governance and financial controls, and legal registration. Attach the documents funders check during due diligence. Then write the executive summary and the covering letter last, when you know exactly what the proposal says.
Step 10: Edit, check and submit
Edit for plain language: short sentences, active verbs, no unexplained acronyms. Check the proposal line by line against the guidelines, make sure every number matches between the letter, summary and budget, and ask someone who has not worked on it to read it. Submit before the deadline, keep proof of submission, and prepare to answer questions quickly.
The structure of a strong grant proposal
If the funder provides a template, use it exactly. If not, the order below follows the way reviewers read: the project first, then the evidence that your organisation can deliver it.
| Part | What it answers |
|---|---|
| Cover page and covering letter | Who is asking, for what, how much and for how long |
| Executive summary | The whole proposal in one page |
| Problem statement and baseline | Why the project is needed, with evidence |
| Beneficiaries and locations | Who will benefit, how many and where |
| Methodology | What you will do and why it will work |
| Outputs, outcomes and indicators | What will change and how you will measure it |
| Implementation plan and timeline | Who does what, and when |
| Risks and mitigation | What could go wrong and how you will handle it |
| Budget and justification | What it costs and why |
| Sustainability and exit plan | What lasts after the grant |
| Organisation profile, governance and legal status | Why you can be trusted to deliver |
| Annexures | The supporting documents |
The most common reasons proposals are rejected
- The project does not match the funder’s priorities or eligibility rules.
- The guidelines, page limits or required format were not followed.
- The problem is described in general terms without local, recent evidence.
- Objectives are vague, so success cannot be measured.
- The budget is unrealistic or does not match the activities in the narrative.
- There is no credible plan for what happens after the grant ends.
- The proposal arrived after the deadline or with missing attachments.
Frequently asked questions
How long does it take to write a grant proposal?
Allow two to eight weeks for a full proposal. Collecting documents, quotes for the budget, letters of support and board approval usually takes longer than the writing itself.
Which part of a grant proposal is most important?
Reviewers usually weigh the problem statement, the logic linking activities to outcomes and the budget most heavily, but the executive summary is read first and often decides whether the rest is read carefully.
Can I write a grant proposal without experience?
Yes. Follow the funder’s guidelines closely, use a clear structure such as the one above, back every claim with evidence and ask an experienced reader to review your draft. The free proposal builder walks you through each section in order.
Written by Gachi Foundation, a non-profit in Jharkhand, India. All proposal-writing resources.