What are the main sections of a grant proposal?
A standard grant proposal includes these sections: a cover letter, an executive summary or abstract, a statement of need (the problem you are addressing), project goals and objectives, a methods or approach section (how you will achieve the goals), an evaluation plan (how you will measure success), a budget and budget justification, organizational background, and any required appendices such as.
Grant writing is a specialized skill that directly affects an organization's ability to fund its mission. Whether you represent a nonprofit seeking foundation support, a researcher applying for federal funding, or a community group pursuing a local grant, the proposal is your primary tool for persuasion. A strong proposal translates your vision into a structured, compelling argument that convinces a funder to invest in your work.
The stakes are high. According to the Foundation Center (now Candid), US foundations received over 1.5 million grant proposals annually, with an average success rate between 10 and 20 percent for most funders [1]. That means 80 to 90 percent of proposals are rejected, and the difference between funded and unfunded proposals often comes down to clarity, specificity, and alignment with the funder's priorities -- all factors within your control.
This guide walks you through every section of a standard grant proposal, provides a reusable template structure, and shares the techniques that distinguish successful proposals from the rest.
Before You Write: Essential Preparation
Research the Funder
The most common reason proposals fail is misalignment between the project and the funder's priorities. Before writing a single word:
- Read the funder's mission statement, strategic plan, and funding priorities.
- Review past grants they have awarded (most foundations publish this information).
- Check eligibility requirements (geographic focus, organization type, project type).
- Note formatting requirements (page limits, font, margins, required sections).
- Contact the program officer if the funder allows pre-submission inquiries.
"The number one mistake in grant writing is applying to the wrong funder. No amount of beautiful prose will overcome a fundamental mismatch between your project and the funder's mission." -- Beverly A. Browning, Grant Writing for Dummies, 6th edition [2]
Develop Your Project Before Your Proposal
A proposal documents a project that has already been planned. Do not use the writing process to figure out what you want to do. Before you start writing, you should have:
- A clearly defined problem your project addresses
- Specific, measurable goals and objectives
- A realistic timeline
- A detailed budget
- An evaluation plan
- Letters of support from partners or stakeholders
The Standard Grant Proposal Sections
While every funder has its own format requirements, most proposals follow a standard structure. Here is the section-by-section breakdown:
| Section | Purpose | Typical Length |
|---|---|---|
| Cover Letter | Introduce your organization and project; establish fit with funder | 1 page |
| Executive Summary / Abstract | Summarize the entire proposal | 1/2 to 1 page |
| Statement of Need | Define the problem with data and evidence | 1-3 pages |
| Goals and Objectives | State what you will achieve | 1/2 to 1 page |
| Methods / Approach | Describe how you will achieve your goals | 2-4 pages |
| Evaluation Plan | Explain how you will measure success | 1-2 pages |
| Budget and Justification | Detail all costs and explain each line item | 1-3 pages |
| Organizational Background | Demonstrate your capacity to execute | 1-2 pages |
| Appendices | Supporting documents (letters, resumes, data) | Varies |
Section 1: Cover Letter
The cover letter is a one-page introduction that establishes the relationship between your project and the funder. It should include:
- Your organization name and mission (one sentence).
- The specific grant program you are applying to.
- The amount you are requesting.
- A brief summary of the project (two to three sentences).
- Why your project aligns with the funder's priorities (one to two sentences).
- Contact information for the project director.
Keep it concise. The cover letter is not the place to make your full argument -- that is what the proposal itself is for.
Section 2: Executive Summary / Abstract
The executive summary condenses your entire proposal into roughly 250 to 500 words. Many reviewers read the executive summary first to decide whether to read the full proposal carefully. It should cover:
- The problem you are addressing (one to two sentences).
- Your proposed solution (two to three sentences).
- Your goals and expected outcomes (one to two sentences).
- The total cost and amount requested (one sentence).
- Your organization's qualifications (one sentence).
For tips on writing executive summaries in general, see our guide on executive summaries.
"The abstract is often the most important part of the proposal because it is the only part that every reviewer reads completely. Make it count." -- Robert J. Sternberg, Writing Successful Grant Proposals from the Top Down and Bottom Up [3]
Section 3: Statement of Need
The statement of need (also called the problem statement or needs assessment) is the foundation of your proposal. It answers the question: Why is this project necessary?
How to Write a Compelling Statement of Need
- Lead with data. Use statistics, research findings, and demographic data to establish the scope of the problem.
- Make it local. National statistics provide context, but funders want to know about the specific community or population you serve.
- Use human stories. After establishing the data, include one or two brief examples that put a human face on the problem (with consent).
- Connect need to your project. The statement of need should flow naturally into your proposed solution.
- Cite your sources. Use reputable, recent sources for all data claims.
What to Avoid
- Circular reasoning ("The problem is that we do not have the program we are proposing").
- Presenting your organization's needs as community needs ("We need a new building" vs. "The community lacks accessible health services").
- Using outdated data (more than five years old for most topics).
Section 4: Goals and Objectives
Goals are broad statements of what you intend to achieve. Objectives are specific, measurable steps toward those goals. Use the SMART framework:
| Component | Definition | Example |
|---|---|---|
| Specific | Clearly defined | Increase reading proficiency among 3rd graders |
| Measurable | Quantifiable | By 25 percent as measured by standardized testing |
| Achievable | Realistic given resources | With 10 trained tutors and $50,000 |
| Relevant | Connected to the identified need | In the district with the lowest reading scores |
| Time-bound | Has a deadline | Within 12 months of project launch |
Goal example: Improve early literacy outcomes for underserved children in the Eastside School District.
Objective examples:
- By June 2027, increase the percentage of 3rd graders reading at grade level from 42% to 55%.
- By December 2026, recruit and train 10 volunteer tutors from the local community.
- By March 2027, provide 40 hours of one-on-one tutoring to each of 100 participating students.
Section 5: Methods / Approach
The methods section describes how you will accomplish your objectives. This is where you demonstrate that your plan is realistic, well-organized, and based on evidence or best practices.
Include:
- A detailed description of project activities.
- A timeline showing when each activity will occur.
- Staff roles and responsibilities.
- The rationale for your approach (why this method will work).
- How you will engage participants or the target population.
Sample Timeline
| Quarter | Activities |
|---|---|
| Q1 (Jul-Sep 2026) | Recruit tutors, conduct training, finalize curriculum |
| Q2 (Oct-Dec 2026) | Begin tutoring sessions, establish progress tracking |
| Q3 (Jan-Mar 2027) | Continue sessions, conduct mid-point assessment |
| Q4 (Apr-Jun 2027) | Complete sessions, administer post-assessment, compile results |
Section 6: Evaluation Plan
Funders want to know that you will measure whether your project works. A strong evaluation plan includes:
- Process evaluation: Did you implement the project as planned? (Activities completed, participants served, timeline adherence.)
- Outcome evaluation: Did the project achieve its objectives? (Changes in knowledge, behavior, or conditions.)
- Data collection methods: Surveys, tests, interviews, focus groups, administrative records.
- Data analysis plan: How you will analyze the data and determine success.
- Reporting: How and when you will report results to the funder.
Section 7: Budget and Budget Justification
The budget translates your project plan into numbers. Every line item should be directly connected to an activity described in the methods section.
Sample Budget Format
| Category | Amount | Notes |
|---|---|---|
| Personnel (Project Director, 50% FTE) | $35,000 | Oversees all project activities |
| Personnel (Tutor Coordinator, 100% FTE) | $42,000 | Recruits, trains, and supervises tutors |
| Fringe Benefits (25%) | $19,250 | Health insurance, FICA, retirement |
| Training Materials | $5,000 | Curriculum guides, assessment tools |
| Tutoring Supplies | $3,000 | Books, workbooks, educational materials |
| Technology | $4,500 | Tablets for progress tracking |
| Travel | $2,000 | Mileage for site visits |
| Indirect Costs (10%) | $11,075 | Administrative overhead |
| Total | $121,825 |
Budget Justification
For each line item, explain why it is necessary and how you calculated the amount:
- "Project Director (50% FTE): The Project Director will dedicate 20 hours per week to overseeing curriculum implementation, managing the Tutor Coordinator, liaising with school administrators, and reporting to the funder. Annual salary: $70,000 x 50% = $35,000."
"A well-justified budget demonstrates fiscal responsibility and builds trust. If a reviewer cannot understand why you need a line item, they will question your entire budget." -- Foundation Center / Candid, Guide to Proposal Writing [4]
Section 8: Organizational Background
Demonstrate that your organization has the capacity, experience, and infrastructure to execute the project:
- Mission and history
- Relevant past projects and their outcomes
- Key staff qualifications
- Organizational budget and financial health
- Partnerships and community connections
Grant Proposal Review Checklist
Before submitting any grant proposal, review it against this comprehensive checklist. Many successful grant writers report that the review phase is where proposals are won or lost.
| Section | Check | Common Failure |
|---|---|---|
| Cover letter | Mentions the specific grant program and amount requested | Generic letter that could apply to any funder |
| Executive summary | Covers problem, solution, goals, cost, and qualifications in under 500 words | Summary that restates the need without describing the solution |
| Statement of need | Supported by recent, cited data specific to the target population | Relies on national statistics without local context |
| Goals and objectives | All objectives are SMART (specific, measurable, achievable, relevant, time-bound) | Vague goals like "improve community health" |
| Methods | Every objective has corresponding activities with a timeline | Activities described without connection to objectives |
| Evaluation plan | Includes both process and outcome measures with data collection methods | Evaluation limited to "we will track attendance" |
| Budget | Every line item connects to an activity in the methods section | Budget includes items not described in the narrative |
| Budget justification | Every line item has a calculation and rationale | Round numbers with no explanation |
| Organizational background | Demonstrates capacity with evidence (past successes, staff qualifications) | Mission statement without track record |
| Formatting | Meets all funder requirements (font, margins, page limit, required sections) | Exceeds page limit or uses wrong format |
"The difference between funded and unfunded proposals is rarely the quality of the idea. It is the quality of the writing, the specificity of the plan, and the alignment with the funder's stated priorities. Review your proposal as if you were the program officer reading the fiftieth submission that day." -- Mim Carlson and Tori O'Neal-McElrath, Winning Grants Step by Step, 5th edition [5]
Strengthening Your Statement of Need: Before and After
The statement of need is often the weakest section in rejected proposals. Here is an example of how to transform a vague needs statement into a compelling one.
Before (Weak -- vague, circular, no data)
"Many children in our community are struggling to read. Reading is important for success in school and life. Without reading skills, children fall behind and have difficulty in other subjects. Our organization believes that every child deserves the opportunity to read at grade level. This program will help children improve their reading."
After (Strong -- specific, data-driven, locally anchored)
"In the Eastside School District, only 42 percent of third graders read at grade level, compared to the state average of 61 percent (State Department of Education, 2025). The district serves a predominantly low-income community where 78 percent of families qualify for free or reduced lunch, and access to books outside of school is limited -- the nearest public library branch is 4.2 miles from the district center, and only 23 percent of families report having more than 10 books in the home (Community Needs Assessment, 2025). Research consistently shows that children who are not reading proficiently by the end of third grade are four times more likely to drop out of high school (Annie E. Casey Foundation, 2012). The proposed tutoring program addresses this gap by providing 100 students with 40 hours of one-on-one literacy support from trained community volunteers, targeting the specific phonemic awareness and fluency deficits identified in the district's most recent assessment data."
The strong version is specific, locally grounded, supported by data, and flows directly into the proposed solution. It tells the reviewer exactly what the problem is, how severe it is, and why this project is the right response.
Common Grant Writing Mistakes
- Not following the funder's instructions. If the guidelines say 12-point font, double-spaced, 10-page limit -- follow them exactly. Reviewers reject non-compliant proposals.
- Writing for yourself instead of the reviewer. Avoid jargon and insider language. The reviewer may not be an expert in your specific field.
- Vague objectives. "Improve community health" is not measurable. "Reduce diabetes rates by 15% among adults aged 40-65 within 24 months" is.
- Budget-narrative mismatch. If your methods section describes hiring a coordinator, but the budget does not include coordinator salary, the reviewer will notice.
- Skipping the cover letter. Even when not explicitly required, a professional cover letter frames your proposal.
- Missing the deadline. Submit at least 24 hours early. Technical problems and last-minute errors are not accepted as excuses.
Related Business Writing Guides
- Business Proposal -- general proposal writing techniques
- Executive Summary -- summarizing your project for decision-makers
- Business Plan Outline -- planning documents for organizations
- How to Write Concisely -- tightening your prose for page-limited proposals
- Tone in Professional Writing -- striking the right balance of confidence and humility
Summary
A successful grant proposal combines a compelling statement of need with a clear, realistic plan, measurable objectives, a justified budget, and strong alignment with the funder's priorities. The writing itself must be clear, specific, and free of jargon. Follow the funder's guidelines precisely, invest time in research before you write, and have multiple readers review your draft before submission. Grant writing is a learnable skill, and each proposal you write -- whether funded or not -- builds your capacity for the next one.
How to Write a Complaint Letter Format?
The standard complaint-letter format includes: (1) sender's address block, (2) date, (3) recipient's address block, (4) subject line, (5) formal salutation, (6) three-paragraph body -- problem, evidence, resolution requested, (7) complimentary close ('Sincerely' or 'Yours faithfully'), (8) signature and printed name. The grant-proposal guide's template discipline applies directly to complaint letters -- structure signals credibility. Keep body paragraphs short and factual. Attach supporting documentation (receipts, screenshots, contracts). State a specific resolution with a reasonable deadline, typically 14 days. Send via certified mail or tracked email for proof of delivery. Keep copies of everything, including the envelope's tracking information if the matter escalates to regulators or court.
How to Write a Complaint Letter to Your Boss?
Write a complaint letter to your boss when the issue is internal to your team or role but not something requiring HR escalation. Structure like any formal business letter: clear subject, specific incidents with dates, impact on your work, and the specific request you are making. The grant-proposal guide's template discipline applies -- structured, specific, and solution-oriented letters get results. Keep tone respectful and professional. Lead with the resolution you want, not the grievance: 'I am writing to request a change to [specific thing] because [factual reason].' If the issue is with your boss rather than within your role, the correct recipient is usually HR or your boss's manager, not your boss directly.
References
[1] Candid (formerly Foundation Center). "Key Facts on U.S. Foundations." Candid Research, 2023.
[2] Browning, Beverly A. Grant Writing for Dummies. 6th ed., Wiley, 2022.
[3] Sternberg, Robert J. Writing Successful Grant Proposals from the Top Down and Bottom Up. Sage Publications, 2014.
[4] Geever, Jane C. Guide to Proposal Writing. Foundation Center / Candid, 7th ed., 2019.
[5] Carlson, Mim, and Tori O'Neal-McElrath. Winning Grants Step by Step. 5th ed., Jossey-Bass, 2018.
Frequently Asked Questions
What are the main sections of a grant proposal?
A standard grant proposal includes these sections: a cover letter, an executive summary or abstract, a statement of need (the problem you are addressing), project goals and objectives, a methods or approach section (how you will achieve the goals), an evaluation plan (how you will measure success), a budget and budget justification, organizational background, and any required appendices such as letters of support or staff resumes. The exact format varies by funder, so always check the funder's guidelines before writing.
How long should a grant proposal be?
Length depends entirely on the funder's requirements. Federal grants (such as NIH or NSF) often allow 12 to 15 pages for the narrative plus additional pages for the budget and appendices. Foundation grants may limit proposals to 5 to 10 pages or even require a 2-page letter of inquiry before the full proposal. Some corporate grants use online forms with word or character limits. Never exceed the stated page or word limit -- proposals that violate formatting guidelines are often disqualified without review.
What makes a grant proposal successful?
The most successful grant proposals share four qualities: a compelling and well-documented statement of need backed by data, a clear and realistic plan of action with measurable objectives, a reasonable budget that aligns with the project description, and a strong match between the project and the funder's mission and priorities. Reviewers also look for organizational capacity -- evidence that your team has the experience and resources to execute the plan. Strong writing matters too: clarity, specificity, and logical flow distinguish winning proposals from mediocre ones.