How to Write a Better Grant Proposal: Step-by-Step

Writing a grant proposal is part storytelling, part budgeting, and part project management. A strong proposal clearly explains a real problem, presents a logical solution, and convinces the funder that your team is the right one to carry it out. This guide walks you through the entire process, from reading the guidelines to submitting a polished package. By following these steps, you’ll avoid common pitfalls, save time, and significantly increase your chances of getting funded.

What You’ll Need

• The funder’s grant guidelines or request for proposals (RFP)
• A clear project idea or program you want funded
• Basic financial information (budget, expenses, revenue)
• Organizational documents (mission statement, IRS determination letter if nonprofit, board list)
• Resumes or CVs of key personnel
• Any supporting data or research about the problem you’re addressing
• A word processor or Google Docs
• A calendar to track deadlines

Step-by-Step

1. Read the guidelines thoroughly. Before writing a single word, read the RFP or guidelines twice. Highlight eligibility requirements, page limits, formatting rules, and the funder’s stated priorities. If anything is unclear, contact the program officer with specific questions. Missing a detail like a font size or a required attachment can disqualify you.
2. Understand your audience. Who reviews your proposal? It might be a board of scientists, a community foundation staff, or a corporate giving committee. Tailor your language accordingly. Avoid jargon unless it’s appropriate for the audience. Always write in plain, active language that anyone can understand.
3. Plan your project before you write. A proposal is only as good as the project behind it. Define your project’s goal, objectives, activities, timeline, and expected outcomes. Use the SMART framework: Specific, Measurable, Achievable, Relevant, and Time-bound. If you can’t explain your project in one sentence, refine it before writing.
4. Create a proposal outline. Most grant proposals follow a standard structure: summary, problem statement, goals and objectives, methods, evaluation, budget, and organizational capacity. Write a rough outline with bullet points under each section. This will keep you organized and ensure you cover everything.
5. Write the executive summary last. The executive summary (or project abstract) is the first thing reviewers read, but it’s easiest to write after you’ve completed the rest of the proposal. It should be a one-paragraph overview that includes the problem, your solution, the target population, the funding amount, and expected outcomes. Make it compelling—reviewers often decide based on this section alone.
6. Craft a compelling problem statement. Describe the issue you’re addressing in concrete terms. Use data, stories, or examples to show why this problem matters and why it’s urgent. Avoid vague statements like “poverty is bad.” Instead, say “In our county, 32% of families with children under five live below the poverty line, and only 1 in 10 have access to affordable childcare.”
7. Define clear goals and objectives. Goals are broad statements (e.g., “Improve literacy among third graders”). Objectives are specific, measurable outcomes (e.g., “Increase the percentage of third graders reading at grade level from 40% to 60% within 18 months”). Make sure each objective is tied to an activity and a timeline.
8. Describe your methods or approach. Explain exactly what you will do to achieve your objectives. Break it down into phases or activities. Include who will do the work, when, and with what resources. If you’re using a specific evidence-based model, name it and cite it briefly. Reviewers want to see that your approach is realistic and grounded in best practices.
9. Include an evaluation plan. Funders want to know how you’ll measure success. Describe both process evaluation (did you do what you said?) and outcome evaluation (did it make a difference?). If you have the budget, hire an external evaluator. If not, explain how you’ll collect and analyze data internally.
10. Build a realistic budget. Your budget should align exactly with your project description. Include personnel salaries, fringe benefits, equipment, supplies, travel, and indirect costs. Be sure to check if the funder allows indirect costs. Justify each line item—reviewers will question expenses that seem inflated or unrelated. If you have in-kind contributions or other funding, list them as well.
11. Write about your organization’s capacity. Show that your team has the skills and experience to carry out the project. Include a brief history of your organization, its mission, and key accomplishments. Attach resumes of key personnel and a list of your board of directors. If you’re a new organization, emphasize your partners and any relevant experience.
12. Review and edit ruthlessly. Once you have a full draft, set it aside for a day, then read it with fresh eyes. Cut unnecessary words, fix typos, and check that every paragraph supports your main argument. Ask a colleague who is not familiar with your project to read it and tell you if anything is confusing.
13. Format and submit according to instructions. Follow the funder’s submission method exactly—whether it’s an online portal, email, or mail. Convert to PDF if required. Double-check page counts, margins, and font size. Submit before the deadline; don’t wait until the last minute in case of technical issues.

Common Mistakes

• Not following guidelines. Ignoring page limits, font requirements, or missing attachments is an instant red flag.
• Being too vague. Saying “we will help the community” is not enough. Be specific about who, what, when, and how.
• Focusing on your needs instead of the funder’s priorities. Frame your project in terms of the funder’s mission, not just your organization’s needs.
• Overpromising. Setting unrealistic goals or timelines can make your proposal seem naive. Be ambitious but honest.
• Ignoring the budget narrative. A budget with no explanation is hard to evaluate. Always justify major expenses.
• Submitting a one-size-fits-all proposal. Each funder is different. Tailor every proposal to the specific funder and their priorities.

Tips

• Start early—ideally 4-6 weeks before the deadline.
• Use headings and bullet points to make your proposal easy to scan.
• Write in the active voice: “We will train 50 teachers” instead of “Training will be provided.”
• Include a logic model or a simple table linking activities to outcomes.
• If the funder allows it, call them to discuss your idea before writing. They often give valuable feedback.
• Keep a template of your organization’s standard information (history, mission, etc.) so you don’t have to rewrite it each time.

Template

Troubleshooting

What if you get rejected? First, don’t take it personally. Many funders receive dozens or hundreds of proposals. Ask for feedback—many will provide a summary of why they declined. Use that feedback to improve your next proposal. Also, consider whether the funder was a good fit; sometimes it’s just a mismatch. Reapply to the same funder in the next cycle if they encourage it, or look for other funders with similar priorities.

What if you’re running out of time? Prioritize the sections that carry the most weight: the executive summary, problem statement, and budget. Even if you can’t perfect every section, make sure those are strong. Submit a complete but imperfect proposal rather than missing the deadline entirely.

What if you have no experience writing grants? Look for free resources online, such as grant writing guides from nonprofit associations. Consider taking a short online course. You can also partner with an experienced grant writer or ask a mentor to review your draft. Many communities have grant writing workshops or volunteer programs.

What if your project is too large for one funder? Break your project into smaller phases or components and apply to multiple funders for each part. Be transparent about your other funding sources—funders often like to see a diversified funding base.

Frequently Asked Questions

Q: How long should a grant proposal be?
A: It varies widely. Some funders want 2 pages, others 20. Always follow the guidelines exactly. If no length is specified, aim for 5-10 pages for a standard project grant.

Q: Can I reuse the same proposal for different funders?
A: You can reuse sections, but you must tailor each proposal to the specific funder’s priorities and requirements. A generic proposal is easy to spot and often rejected.

Q: What if I don’t have a formal evaluation plan?
A: Start simple. Even a basic plan—like tracking attendance and using pre/post surveys—is better than none. Funders want to see that you’ll measure your impact, not that you have a PhD in statistics.

Q: Should I include my organization’s financial statements?
A: Only if the funder asks for them. If they do, include audited financials if you have them, otherwise provide a budget and a profit/loss statement.

Q: How do I find grant opportunities?
A: Start with your local community foundation, state agencies, and corporate giving programs. Online databases like Grants.gov (for federal grants) and Foundation Directory are also useful, but many require a subscription.

Q: What is an indirect cost rate?
A: It’s a percentage of your direct costs that covers overhead like rent and utilities. Some funders allow it, others don’t. If you’re a nonprofit, you may have a federally negotiated rate. If not, you can often request a de minimis rate of 10% of modified total direct costs.

Related

• Grievance Coordinator Job Description & Duties
• Food Beverage Inventory Controller Job Description
• HR Training Coordinator: Job Description & Duties