How to Write a Grant Proposal in 2026: Step-by-Step with Free Template

What Is a Grant Proposal?

A grant proposal is a formal written request for funding submitted to a government agency, private foundation, or corporate giving program. It explains what problem your organization will address, how you plan to address it, what outcomes you expect, how much it will cost, and why your organization is qualified to do the work.

Grant proposals differ from loan applications or investor pitches in one fundamental way: you do not repay the funds or give up equity. The funder provides money in exchange for your organization delivering a specific program or project that aligns with the funder's mission. In return, you report on how the money was spent and what results you achieved.

Grants fund nonprofits, small businesses, schools, tribal governments, municipalities, and research institutions. Federal agencies like the Department of Education, EPA, HUD, USDA, and the National Science Foundation collectively distribute over $700 billion annually through grant programs. State governments, private foundations, and corporate giving programs add tens of billions more. The competition for these funds is significant, but organizations that submit well-structured proposals matched to the right funders win consistently.

Types of Grants (and Why It Matters for Your Proposal)

The type of grant you are pursuing shapes the format, length, and requirements of your proposal. Understanding the differences before you start writing saves time and prevents mismatched applications.

Federal Grants

Federal grants come from agencies like USDA, HUD, EPA, the Department of Education, and the National Institutes of Health. They are published on Grants.gov as Notices of Funding Opportunity (NOFOs). Federal proposals are the most structured: they follow strict formatting rules, require specific sections, and are scored against a published rubric. They also require SAM.gov registration, adherence to OMB Uniform Guidance (2 CFR 200), and often specific certifications. Award sizes range from $50,000 to tens of millions depending on the program.

State and Local Government Grants

State agencies run their own grant programs, and many also distribute federal pass-through funding. State grants tend to be less bureaucratic than federal programs, with shorter applications and faster decision timelines. Local governments (cities, counties) run programs like Community Development Block Grant (CDBG) subgrants. If you are a newer organization, state and local grants are often the best place to start building a track record before competing for federal awards.

Foundation Grants

Private foundations (Ford Foundation, Kresge Foundation, local community foundations) have their own priorities and application processes. Foundation proposals are usually shorter than federal applications, sometimes as brief as 3 to 5 pages. Many foundations require a Letter of Inquiry (LOI) before inviting a full proposal. Foundation grants typically range from $5,000 to $500,000, though large national foundations occasionally award more.

Corporate Grants

Corporate giving programs (Walmart Foundation, Google.org, Bank of America Charitable Foundation) fund programs that align with the company's social responsibility priorities. Applications are often submitted through online portals with fixed fields. Corporate grants tend to favor programs with measurable community impact and clear branding opportunities for the funder.

You can filter grants by type on FindGrants to focus your search on federal, state, or foundation programs that match your organization.

Before You Start Writing

The biggest time waster in grant writing is investing weeks in an application you were unlikely to win. Before writing a single sentence, confirm these four things:

• You meet the eligibility requirements. Read the full Notice of Funding Opportunity (NOFO) or grant guidelines, not just the summary. Check organization type (501(c)(3), government entity, tribal nation, small business), geographic requirements, years in operation, and any prior award requirements.
• Your program aligns with the funder's stated priorities. A foundation that funds workforce development will not fund your capital campaign, regardless of how well the proposal is written. Match your program to what the funder actually funds.
• You can meet the deadline. A federal grant that closes in three weeks is not a realistic target if you have not started. Rushed proposals are obvious to reviewers, and they lose.
• You have read the scoring rubric. Most federal grants publish a scoring matrix. If "community engagement" is worth 25 points out of 100, your application needs substantial material on that topic, not a single paragraph.

Use FindGrants to filter opportunities by your organization type, location, and focus area before investing time in proposals where you are not a strong fit.

Grant Proposal Structure: Section-by-Section Breakdown

Every grant proposal follows a similar structure, whether you are applying to a federal agency, state program, or private foundation. The names vary between funders, but the core sections remain consistent. Here is a reference table showing each section, its typical length, and what it covers:

Not every funder uses the same names. Some federal agencies call the program design section "Project Narrative." Some foundations combine the needs statement and program design into a single narrative. Read the specific guidelines for your grant and map your content to their required format.

How to Write Each Section of Your Grant Proposal

Cover Letter

The cover letter is a one-page introduction addressed to the program officer or grants committee. It states the name of the grant program, your organization's name, the amount you are requesting, and a two to three sentence summary of what you propose to do. Include your executive director's signature and the best contact person for questions. Some funders require a cover letter; others do not. When in doubt, include one. It takes 15 minutes to write and creates a professional first impression.

Executive Summary

The executive summary (sometimes called an abstract) is a one-page overview of the entire proposal. Write this section last, after every other section is complete. It should answer six questions: Who is your organization? What problem will you address? What will you do? Who will benefit? How much are you requesting? What outcomes do you expect?

Many reviewers read the executive summary first and form their initial impression before reading the rest. If you are applying to a federal grant that assigns reviewers to panels, the abstract may be the only section every panel member reads in full. Make it specific and concise.

Organization Background and Qualifications

This section establishes your credibility to execute the proposed project. Cover your mission, years of operation, major programs, the population you serve, and any prior experience relevant to this grant.

Quantify your reach: number of clients served annually, geographic footprint (counties, states), annual operating budget, staff size. If you have managed prior grants successfully, name the funders and amounts. For example: "Since 2019, our organization has managed $2.4M in federal and state grants, including a three-year HUD Continuum of Care award for rapid rehousing services."

Keep this section to 1 to 2 pages. Reviewers do not need your full organizational history. They need to be confident you can manage the money and deliver the program.

Statement of Need

The statement of need (also called needs assessment or problem statement) answers: what problem are you solving, and why does it matter? This is where many grant proposals lose points. Strong needs statements have three elements:

• Local data. Use data specific to your service area: census statistics, county health rankings, school performance data, community surveys, crime statistics, unemployment rates. National statistics establish context, but local data establishes urgency. Always cite your sources.
• Human impact. Numbers alone do not persuade. One well-chosen example can make the data tangible. If you are a nonprofit applying for an EPA environmental justice grant, a sentence like "residents of the Southside neighborhood report asthma rates three times the state average, driven by proximity to two industrial facilities" grounds the data in lived experience.
• Connection to your program. The needs statement should naturally set up your program description. The problem you document must be the problem your program addresses. If you spend two pages describing food insecurity but your program is job training, the disconnect will cost you points.

Avoid the "mirror of misery" problem: cataloguing every challenge in your community without connecting them to a clear, focused intervention. The needs statement should make the funder confident that you understand the problem deeply, not that you are overwhelmed by it.

Goals, Objectives, and Methods

This is the core of the proposal. It describes what you will do, in enough detail that a reviewer can visualize your program operating. Understanding the distinction between goals, objectives, and methods is critical:

• Goals are broad statements of what you intend to achieve. Example: "Reduce youth unemployment in Wayne County."
• Objectives are specific, measurable targets. Example: "Place 150 youth ages 16 to 24 in paid employment within 12 months of program enrollment, with 70% retaining employment for at least 90 days."
• Methods are the activities you will undertake to achieve each objective. Example: "Deliver a 6-week workforce readiness curriculum, followed by individualized job placement support and 90 days of post-placement follow-up."

Beyond that framework, your project description should cover:

• Evidence base. Why this approach? Reference research, evidence-based practice models, or your own prior results. Funders want to fund approaches with a credible theory of change. If your after-school tutoring program is based on a model that has peer-reviewed evidence of effectiveness, cite it.
• Target population. Who specifically will you serve? How many? How will you recruit and retain participants? Be specific: "low-income adults ages 25 to 55 in rural Appalachian Ohio" is better than "underserved populations."
• Implementation timeline. What happens in months 1 to 3, 4 to 6, 7 to 12? A simple table or milestone list works well. Reviewers want to see that you have thought through the sequencing of activities.
• Staffing. Who will run the program? What are their qualifications? If you are hiring, describe the position and required qualifications.
• Partners. Name each partner organization and describe what they contribute. Letters of support from partners should be included as attachments.

Evaluation Plan

The evaluation section answers: how will you know if it worked? Many applicants treat this as an afterthought, and reviewers can tell. Strong evaluation plans include:

• Outcomes, not just outputs. Outputs are what you do (served 200 participants, held 12 workshops). Outcomes are what changes (80% of participants gained employment within 90 days, participants reported a 40% increase in financial literacy scores). Funders fund outcomes.
• Measurable indicators. For each outcome, specify what data you will collect. Pre/post surveys? Employment records? Health screenings? Academic assessments? Recidivism data?
• Data collection methods. Who collects the data, at what intervals, and using what tools? How will data be stored and analyzed? If you are using a third-party evaluator, name them.
• Continuous improvement. How will you use evaluation data to adjust the program during the grant period? Describing a quarterly review process signals organizational maturity to reviewers.

Budget and Budget Narrative

The budget is a financial translation of your program design. Every line item should correspond to an activity described in the project section. The budget narrative (also called budget justification) explains each line: what it is, how the cost was calculated, and why it is necessary.

A strong budget narrative demonstrates three things: you understand the true cost of delivering the program, you are fiscally responsible, and every dollar is tied to a specific activity. Reviewers use the budget to check whether your program design is realistic. If your project description calls for five staff members but your budget only funds two, that inconsistency will raise questions.

Here is an example of proper budget line-item justification:

• Weak: "Supplies: $5,000"
• Strong: "Educational materials and supplies for 200 participants at $25/participant: $5,000. Includes workbooks ($15 each) and career assessment kits ($10 each), sourced from ABC Publishing."

Common budget mistakes that cost applicants points:

Sustainability Plan

Funders do not want to create permanent dependency. The sustainability section explains how the program continues after the grant period ends. Acceptable sustainability sources include:

• Earned revenue (fees for service, Medicaid billing, service contracts)
• Other grants already secured or in the pipeline
• Integration into your organization's base operating budget
• Government contracts or formula funding
• Social enterprise revenue or fundraising capacity

Be specific. "We will seek additional grant funding" is not a sustainability plan. "We will use outcome data from this grant period to pursue Medicaid reimbursement for our counseling services, which would generate approximately $180,000 annually and cover 85% of program costs" is credible because it ties a specific revenue source to a specific dollar amount.

Federal vs. Foundation Proposals: Key Differences

Government grant proposals and foundation grant proposals follow similar structures, but the execution differs in important ways:

• Length and format. Federal applications (USDA, HUD, EPA, Department of Education) follow strict page limits, formatting rules (font size, margins, spacing), and required sections. Foundation proposals are usually shorter and more flexible.
• Scoring. Federal grants publish scoring rubrics. You can see exactly how many points each section is worth. Use the rubric to allocate space proportionally. Foundation proposals are reviewed holistically, often by board members rather than trained peer reviewers.
• Compliance requirements. Federal grants require SAM.gov registration (allow 4 to 6 weeks), a Unique Entity Identifier (UEI), adherence to 2 CFR 200, and often specific certifications. Foundation proposals rarely require any of this.
• Budget detail. Federal budgets require line-item justification with calculation methods. Foundation budgets are often a simple one-page summary.
• Reporting. Federal grants require quarterly or semi-annual performance and financial reports (SF-425, SF-PPR). Foundation reporting requirements vary but are usually lighter.
• Timeline. Federal grant cycles are predictable and published months in advance. Foundation deadlines vary; some accept proposals on a rolling basis.

If you are new to grant writing, starting with smaller foundation grants or local government subgrants builds your track record before you compete for larger federal awards. Search grants by type on FindGrants to filter by federal, state, or foundation programs.

Common Grant Proposal Mistakes

The same mistakes appear in unsuccessful proposals regardless of funder type. Avoiding these puts your application ahead of the majority of submissions:

Grant Writing Tips That Improve Your Win Rate

These patterns appear consistently in proposals that win funding:

• Lead with outcomes, not activities. Instead of "We will hold 12 workshops," write "240 participants will complete financial literacy training, with 70% demonstrating improved budgeting skills on post-program assessments." Activities support outcomes, not the other way around.
• Use the funder's language. If the NOFO says "health equity," use that exact phrase in your proposal. Do not substitute a synonym. Reviewers scan for alignment with the stated priorities, sometimes using keyword searches.
• Quantify everything possible. Number of people served, percentage improvement, dollar amounts, timelines. Specific numbers build credibility. Vague language erodes it.
• Show organizational capacity with specifics. Instead of "our staff is highly qualified," write "our Program Director has 12 years of experience managing HUD-funded programs totaling $3.2M, with zero audit findings." Specifics replace assertions.
• Build a logic model. Connect your needs statement to your activities to your outputs to your outcomes. When a reviewer can trace the logic from problem to solution to measurable result, the proposal is persuasive. Many federal NOFOs explicitly request a logic model as an attachment.
• Start early. A competitive federal grant proposal takes 4 to 8 weeks to write well, especially if you need to secure letters of support, finalize partner agreements, or collect local data. Block the time as soon as the NOFO is published.
• Get reviewer feedback on losses. If you are declined, request reviewer comments. Most federal programs and many foundations will provide them. Reviewer feedback is the clearest guide to improving your next application.

A Step-by-Step Process for First-Time Grant Writers

If you have never written a grant proposal before, the process can seem overwhelming. Here is a concrete sequence to follow:

1. Identify the right grants. Do not write a proposal until you have confirmed your organization is eligible and the grant aligns with your work. Use FindGrants to match your organization's profile to available funding opportunities, or browse by category on the grants directory.
2. Read the full NOFO or guidelines. Read every page, including the appendices. Note required sections, page limits, formatting rules, scoring criteria, required attachments, and the submission deadline.
3. Build an outline mapped to the funder's requirements. Create a document with section headers matching the NOFO. Under each header, note the point value (for federal grants) and what the funder says they want to see.
4. Gather your data. Collect the local statistics, organizational data, and evidence base citations you will need for the needs statement and program design. This step often takes longer than the writing itself.
5. Draft the needs statement and program design first. These are the most substantive sections. Get them right before writing the executive summary, budget, or evaluation plan.
6. Build the budget from the program design. Every activity in the narrative should have a corresponding budget line. Calculate costs from the bottom up: salary x FTE x months, unit cost x quantity, contractor rates x hours.
7. Write the evaluation plan. For each objective, define the outcome, the indicator, the data source, and the collection schedule.
8. Draft the executive summary last. It should be a condensed version of the completed proposal, not a preview written before the details are finalized.
9. Internal review. Have at least one person who was not involved in writing read the entire proposal. Ask them to identify any section where the logic is unclear or the language is vague.
10. Submit 24 to 48 hours early. Portal crashes and upload errors happen on deadline day. Submitting early eliminates this risk.

Letters of Inquiry: Your First Step with Foundations

Many foundations require a Letter of Inquiry (LOI) before accepting a full proposal. An LOI is 1 to 3 pages that covers: who you are, what problem you are addressing, what you will do, who you will serve, and how much you are requesting. Its only purpose is to get invited to submit a full proposal.

An effective LOI covers four things in about 500 words:

• The problem. State the issue with one or two data points that establish scale or urgency.
• Your solution. Describe the program in concrete terms: how many people, what activities, over what timeframe.
• Why your organization. What makes you the right entity to do this work? Prior experience, community relationships, a proven model.
• The ask. State the amount and what it funds. "$40,000 to fund one program coordinator and materials for 120 participants over 12 months" is more useful than "$40,000 for general program support."

Follow the funder's specific LOI format requirements exactly. If they ask for two pages, do not submit three.

The Revision Process

The difference between a funded proposal and an unfunded one is often editing, not content. Strong proposals go through multiple revision rounds:

• Reviewer perspective check. Read each section and ask: does this clearly answer the question the funder is asking? If a section heading says "Statement of Need," does the content demonstrate a need, or does it describe your organization?
• Cut aggressively. Grant reviewers read under time pressure, sometimes evaluating 15 to 20 proposals in a single session. Every sentence that does not serve the argument dilutes the ones that do.
• Clarity test. Have someone unfamiliar with your program read the needs statement and program description. If they can explain your program back to you accurately, your writing is clear enough.
• Cross-reference. Check that every outcome in your evaluation section corresponds to an activity in your program description, every activity has a budget line, and the budget totals match across all forms.
• Compliance check. Verify page limits, font requirements, margin widths, file naming conventions, and required signatures. Technical noncompliance can disqualify your application before a reviewer reads a word.

How to Find Grants to Apply For

Writing a strong proposal matters only if you are applying to the right grants. The most efficient approach is to match your organization's characteristics to funder criteria before investing time in writing. Key sources for finding grants include:

• Grants.gov for all federal grant opportunities from 26+ agencies.
• Your state's grants portal for state-funded programs (search "[your state] grants portal").
• Candid (Foundation Directory Online) for private foundation grants, with searchable histories of past awards.
• Community foundations in your metro area for local funding with streamlined applications.
• FindGrants to match your organization profile (type, focus areas, location, budget) against 57,000+ grants from federal, state, and foundation sources, ranked by fit. Instead of checking multiple databases, you get a scored list of opportunities where you are most competitive.

Organizations that focus on 8 to 12 well-matched grants per year win more total funding than those that submit 30 to 40 marginally aligned applications. Targeting the right opportunities is as important as writing well.

After Submission

After submitting, do three things. First, note the expected decision date in your calendar. Second, confirm receipt with the program officer or through the submission portal. Third, begin planning your next application while the current one is under review.

If you are declined, request reviewer comments. Most federal programs provide detailed reviewer scores and feedback. Many foundations will share general reasons for the decision. This feedback is the most direct path to improving your next proposal.

If you are funded, read the award terms carefully before spending. Federal grants include specific reporting requirements, prior approval rules for budget changes, and restrictions on certain expenses. Successful grant management starts with understanding your obligations from day one.

Start With the Right Grant

A well-written proposal submitted to the wrong funder is wasted effort. Before you begin writing, make sure you are pursuing grants where your organization is genuinely competitive. FindGrants matches your organization's profile to thousands of federal, state, and foundation grants, ranked by alignment score. You can also browse all 57,000+ grants or search by keyword to find specific programs. Finding the right opportunities first is the highest-leverage step in any grants strategy.