How to Write a Grant Proposal for a Nonprofit (Step-by-Step)

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 who you are, what problem you're addressing, how you plan to address it, and what the money will be used for.

Most proposals follow a standard structure regardless of the funder. Once you understand each section, writing becomes much faster — especially if you use a tool like FundingDraft that remembers your organization's details across applications.

Grant proposals differ from grant applications in that some funders use online forms with specific fields, while others request a narrative document (the "proposal"). This guide covers the narrative proposal, which is the foundation for nearly all grant writing regardless of format.

Before you write: the Letter of Inquiry (LOI)

Many private foundations require a Letter of Inquiry (LOI) before they will invite a full proposal. An LOI is a short document — typically 1–3 pages — that introduces your organization and project. If the funder is interested, they respond with an invitation to submit a full proposal.

A strong LOI includes:

• Organization overview — who you are, your mission, your track record
• Project summary — what you're proposing to do and for whom
• Funding request — how much you're requesting and for what period
• Alignment with funder priorities — why this funder specifically
• Brief outcome statement — what success looks like

Not all funders require an LOI — federal grants via Grants.gov typically go straight to a full application. Check each funder's guidelines before assuming either format.

The 7 core sections of a grant proposal

A standard grant proposal contains these sections, though the order and naming vary by funder:

1. Executive Summary — 1–2 paragraph overview of the entire proposal
2. Needs Statement (Problem Statement) — the community problem and its scope
3. Goals and Objectives — what you will accomplish and how you'll measure it
4. Program Design / Methods — exactly what you will do
5. Evaluation Plan — how you'll know if it worked
6. Budget and Budget Narrative — how the money will be spent
7. Organizational Capacity — why your organization can do this

Write the executive summary last, even though it appears first. Once you've drafted the other sections, the summary writes itself.

How to write a needs statement

The needs statement (also called the problem statement or community assessment) makes the case that the problem is real, significant, and urgent — and that your organization is positioned to address it.

Use data, and use local data when possible. "1 in 5 children in the United States experiences food insecurity" is less compelling than "23% of children under 12 in Princeton, TX experience food insecurity, compared to a national rate of 18% (Feeding America, 2025)." Funders fund specific communities — local evidence shows you know yours.

A strong needs statement answers four questions:

• Who is affected? Define the population with specificity. Not "food-insecure families" but "food-insecure families with children under 12 in southern Dallas County."
• How many are affected? Quantify the problem with data. Census data, county health department reports, and local government reports are good sources.
• What are the consequences? What happens if this problem goes unaddressed? Connect the immediate problem to downstream outcomes (food insecurity → poor academic performance → reduced lifetime earnings).
• What gap does your program fill? What's currently being done and why isn't it enough? This sets up your program design section.

How to write grant objectives (SMART format)

Goals are broad directional statements ("reduce food insecurity in southern Dallas"). Objectives are specific, measurable, time-bound steps toward that goal. The difference matters because funders use your objectives to evaluate your results at the end of the grant period.

Use the SMART framework for every objective:

• Specific — exactly what will happen, to whom, where
• Measurable — a number you can track (meals served, participants enrolled, test scores)
• Achievable — realistic given your staff and budget
• Relevant — directly connected to the problem in your needs statement
• Time-bound — a specific date by which it will be accomplished

Include both outputs (what you do: meals distributed, participants served, workshops held) and outcomes (what changes: food security scores, employment rates, test results). Outputs are easy to count; outcomes are harder to measure but matter more to funders.

How to write a program design (methods) section

The program design section describes exactly what you will do. The test: if a stranger read this, could they replicate your program? If the answer is no, add more specificity.

Cover these elements:

• Activities — what will actually happen, in sequence. Not "we will provide food assistance" but "our mobile pantry will visit each ZIP code twice weekly; intake volunteers will register new participants using our online system; each registered family receives a pre-packed box tailored to household size."
• Timeline — when each activity starts and ends. A simple table or Gantt chart works. Month 1: hire coordinator. Month 2: procure van route permits. Month 3: begin operations. This shows you've thought through execution.
• Staffing — who does what. Name positions (not individuals unless they're already hired), list hours, and explain qualifications.
• Partners — who else is involved and what they contribute. Letters of support from partners strengthen this section significantly.
• Evidence base — if your program model has research support ("our model is based on the USDA's Supplemental Nutrition Assistance Program education framework"), say so.

If you've run a pilot or similar program before, describe the results here. Prior results are the most credible evidence that your program will work.

How to write an evaluation plan

The evaluation plan explains how you'll know whether the program worked. Even small organizations need one — it signals to funders that you're serious about outcomes and will be accountable for the investment.

A basic evaluation plan addresses:

• What will you measure? List each objective from the previous section and the specific data point that will tell you whether you achieved it.
• How will you collect data? Intake forms, participant surveys, pre/post assessments, administrative records, third-party data (school records, hospital admissions). Be specific.
• Who is responsible? Name the position responsible for data collection and analysis. Even if it's "program coordinator," naming the role shows accountability.
• When will you report? Quarterly check-ins? Final report? What will you share with the funder?

Many small nonprofits worry that their evaluation capacity isn't sophisticated enough. It doesn't need to be. A participant satisfaction survey, attendance records, and a 90-day follow-up call can constitute a meaningful evaluation for a small-scale program. What matters is that you've thought through the question: how will we know this worked?

How to write a budget and budget narrative

The budget is a line-item breakdown of how you'll spend the grant funds. The budget narrative explains each line in plain language — what it costs, how you calculated it, and why it's needed.

Standard budget categories for nonprofit grants:

• Personnel — salaries and wages for staff working on the project (listed by position, FTE, and annual rate)
• Fringe benefits — employer share of FICA, health insurance, retirement (typically 20–30% of salaries)
• Consultants and contractors — outside experts or service providers
• Supplies and materials — consumable items needed for the project
• Equipment — items over a certain dollar threshold (varies by funder) that will be capitalized
• Travel — mileage, lodging, per diem for program activities
• Indirect costs / overhead — your organization's indirect cost rate (negotiated with a federal agency or a flat percentage)

Cost sharing / match: Most funders want to see that the grant covers a portion of a larger project budget — not 100% of the cost. Even informal in-kind contributions (donated space, volunteer hours at fair market value) can serve as your match. Document them in the budget.

Allowable vs. unallowable costs: Each funder has rules about what their money can pay for. Federal grants typically prohibit using grant funds for lobbying, fundraising, entertainment, and certain equipment. Read the Funding Opportunity Announcement carefully.

How to write an organizational capacity section

This section answers the question: why should the funder trust you to execute this project? Even the best program design is worthless if reviewers aren't convinced you can deliver.

Include:

• Organization history and track record — when founded, how many people served, notable milestones, growth over time
• Relevant prior grants — grants you've received and fulfilled, especially from the same agency or similar funders. Include grant amounts if significant.
• Key staff qualifications — the executive director's background, the program staff's credentials. This is not the place for modesty — lead with the most impressive credentials relevant to this project.
• Financial stability — your annual budget, primary revenue sources, and any notable financial health indicators (full reserve fund, clean audit)
• Partnerships and community ties — who else in the community works with you and vouches for your capacity

For newer organizations without an extensive track record: focus on the individual expertise of your leadership team. A founder with 20 years of direct service experience in the field carries weight even if the organization is two years old.

Common mistakes that get proposals rejected

• Not following the funder's guidelines. If they ask for 5 pages, don't submit 8. If they want Arial 11pt, don't use Times New Roman 12pt. Reviewers flag format violations as evidence that applicants can't follow instructions — which raises questions about whether they can follow grant reporting requirements.
• Generic proposals. Copying the same narrative across applications without tailoring it to each funder's priorities is easy to spot and rarely funded. Funders read the same vague language in hundreds of proposals. Specific, local, funder-aligned proposals stand out.
• Vague objectives. "We will serve more people" is not a measurable objective. Reviewers need to know how many people, by when, and how you'll measure it.
• Budget mismatches. If your narrative says you'll hire 2 staff but the budget only funds 1, reviewers will catch it. Your budget and narrative must match exactly.
• Missing attachments. 501(c)(3) determination letter, board of directors list, most recent financial statements, audit — these are commonly required and commonly forgotten. Create a checklist (see our grant writing checklist) before every submission.
• Not reading the Funding Opportunity Announcement. This is the single most common reason applications are rejected before review. Read it twice. Then check your application against every requirement.
• Applying to grants you're not eligible for. If a grant requires a 501(c)(3) status and you're a fiscal sponsee, or requires US citizenship and your participants include undocumented individuals, you may be ineligible. Verify before investing time in an application.
• Submitting at the deadline. Technical failures at submission time — Grants.gov outages, file size errors, browser compatibility issues — are common. Submit 48–72 hours early and have backups ready.

How long does it take to write a grant proposal?

A first-time proposal for a new grant typically takes 20–40 hours spread across several weeks. This includes researching the funder, reading the FOA, drafting each section, gathering attachments, and reviewing.

Once you have a strong organizational profile and a library of prior proposals, you can reuse and adapt sections — cutting that down to 5–10 hours per new application. An experienced grant writer can work faster still.

The breakdown by section (rough estimates for a first draft):

• Funder research and FOA reading: 2–4 hours
• Needs statement: 3–5 hours (includes data gathering)
• Goals and objectives: 1–2 hours
• Program design: 4–6 hours
• Evaluation plan: 2–3 hours
• Budget and narrative: 3–5 hours
• Organizational capacity: 1–2 hours
• Executive summary: 1 hour
• Review, revision, attachments: 3–5 hours

AI tools like FundingDraft significantly compress the drafting time. After entering your organizational profile once, FundingDraft can generate a tailored first draft of any section in under 2 minutes. You still spend time on funder research, refinement, and review — but the blank-page hours disappear. See how it works at FundingDraft for Nonprofits.

Using AI for grant writing

AI tools have made grant writing significantly faster, but they work best when used as a drafting accelerator — not a replacement for research and judgment.

What AI does well:

• Generating first drafts of standard sections (needs statement, goals, program design)
• Rewriting sections to match a different funder's tone or word limit
• Structuring an evaluation plan from bullet points you provide
• Writing a budget narrative from a spreadsheet of line items
• Summarizing a long narrative into an executive summary

What AI cannot do:

• Tell you which grants you're eligible for (without grant discovery built in)
• Know your organization's true impact without you providing it
• Research the specific funder's priorities and recent grantees
• Replace the judgment of someone who knows your community

Tools like FundingDraft are built specifically for grant writing — they maintain your organizational profile, search Grants.gov for matching opportunities, and structure output around the criteria reviewers actually score. A general-purpose tool like ChatGPT can help too, but requires more setup per application. See our comparison: FundingDraft vs ChatGPT for grant writing.

Frequently asked questions