How to Write a Grant Proposal: A Step-by-Step Guide

Writing a grant proposal means moving through a clear arc: research the funder, prove the problem with a statement of need, set measurable goals and objectives, describe your methods, plan how you will evaluate results, justify the budget, and show how the work will sustain itself after the grant ends. Each section builds on the one before it, and every claim ties back to the need you established. Done well, the proposal reads as a single argument that your organization can solve a defined problem with the funder's money.

This guide walks through every section in order, links to deeper how-to articles for the hardest parts, and points out where proposals most often fall apart.

Before you write: research the funder

The work that decides most proposals happens before the writing starts. Funders reject far more applications for poor fit than for poor prose, so your first job is to confirm alignment. Read the Notice of Funding Opportunity (NOFO) or foundation guidelines line by line, then confirm three things: you are eligible, your project matches the funder's stated priorities, and you can meet the deadline and format limits.

Next, study the funder itself. Review their past awards, typical grant size, and the kinds of organizations they back. Foundations publish this in annual reports and in databases such as Candid's Foundation Directory (2026); federal patterns live on Grants.gov and agency sites. If you are still deciding which sections a particular opportunity requires, start with a grant proposal outline so the structure is settled before you draft. Read our guide to building a grant proposal outline to map the sections to the funder's requirements.

A good rule from the field: if you cannot explain in one sentence why this funder would care about this project, you are not ready to write.

Section 1: Executive summary

The executive summary is a one-paragraph to one-page snapshot of the entire request. It names your organization, the problem, your proposed solution, the population served, the outcomes you expect, and the amount you are asking for. Reviewers often read it first and skim the rest, so it has to stand alone.

Write it last. You cannot summarize an argument you have not finished making. When you do write it, mirror the order of the full proposal so a reader who only reads the summary still understands the logic. Keep it concrete: name real numbers, a real timeframe, and a real population rather than vague mission language. For a deeper treatment of this single page, see our guide to the executive summary of a grant proposal.

Section 2: Statement of need

The statement of need proves a specific problem exists for a specific group, using data, not adjectives. This is the foundation of the whole proposal; if reviewers do not believe the problem is real and urgent, nothing downstream matters. Pair local evidence (your waitlist, your service-area statistics) with credible external sources to show both scale and proximity.

Avoid the most common trap, which is describing your organization's need for money instead of the community's need for change. The need is about the target population, not your budget. For the full method, including how to balance statistics with story, see our statement of need writing guide.

Section 3: Goals and SMART objectives

Goals state the broad change you seek; objectives state the specific, measurable steps that get you there. The strongest objectives follow the SMART framework: specific, measurable, achievable, relevant, and time-bound. "Improve youth literacy" is a goal. "Raise third-grade reading proficiency from 40 percent to 60 percent at two schools by June 2027" is a SMART objective.

Reviewers reward measurability because it tells them exactly what success looks like and how they will hold you accountable. Vague objectives signal a vague program. For templates and worked examples, read how to write SMART goals and objectives that map cleanly to your evaluation plan.

Section 4: Methods and the logic model

The methods section, sometimes called the project design or work plan, explains exactly what you will do, who will do it, and when. List the activities, the timeline, the staff responsible, and the participants served. Reviewers should be able to picture the program running day to day.

This is where a logic model earns its place. A logic model is a one-page visual that links your inputs (resources), activities, outputs (countable products), outcomes (changes in participants), and long-term impact. It forces every activity to connect to a result, which is exactly the discipline reviewers look for.

Some funders also ask for the deeper reasoning behind that chain, a theory of change that explains why your activities should produce the outcomes you claim. The two tools complement each other: the logic model shows the what, the theory shows the why. Learn how to build a logic model for grants and pair it with a clear theory of change before you finalize methods. You can also start from our logic model template to keep the columns aligned.

Section 5: Evaluation plan

The evaluation plan describes how you will measure whether the project worked. Strong plans name outcomes, the indicators you will track for each, the data collection methods, who collects the data, and when. Distinguish formative evaluation (tracking progress so you can adjust mid-stream) from summative evaluation (judging results at the end).

Funders increasingly fund evidence, not effort, so a credible evaluation plan can lift an average application. Tie every indicator directly back to a SMART objective; if an outcome has no indicator, reviewers assume you cannot prove it. Our grant evaluation plan walkthrough shows how to build the measurement table funders expect.

Section 6: Budget and budget narrative

The budget is a table of costs; the budget narrative is the prose that justifies each line. Together they must match the methods exactly. Every staff role, supply, and activity in your work plan should appear in the budget, and nothing should appear in the budget that the narrative did not describe.

Keep the math clean and the assumptions visible. Show how you calculated each figure (rate times hours, unit cost times quantity) so a reviewer can follow it without guessing. Federal applicants must also handle direct versus indirect costs correctly. For the full treatment of cost categories, justification, and common errors, see our grant budget guide.

Section 7: Sustainability

The sustainability plan answers the question every funder asks: what happens when our money runs out? Few funders want to be a program's only lifeline forever, so they look for a realistic path to continued funding, earned revenue, partnerships, or institutional support.

Be honest rather than aspirational. A specific plan to diversify funding across two or three sources reads better than a vague promise to "seek additional grants." For the full set of strategies funders find credible, read how to write a grant sustainability plan.

See it assembled: a worked example

Reading the sections in isolation only goes so far. To see how a needs statement, objectives, methods, and budget fit together into one coherent document, study an annotated grant proposal example and adapt its structure to your funder. You can also download our fill-in-the-blank grant proposal template to draft against the structure above.

Common reasons proposals get rejected

Most rejections trace to a handful of avoidable mistakes:

• Poor funder fit. The single biggest cause; the project does not match the funder's stated priorities.
• A weak statement of need. No data, or need framed around the organization instead of the population.
• Unmeasurable objectives. Goals with no numbers and no deadline.
• A budget that does not match the methods. Costs appear with no matching activity, or activities appear with no funding.
• Ignoring the guidelines. Exceeding page limits, missing required attachments, or skipping a mandatory form such as the SF-424 on a federal application.
• No evaluation or sustainability plan. Reviewers read this as a program that cannot prove results or survive.

Many applications also require attachments that strengthen your case, and the most common is a letter of support from a partner or the community you serve. Smaller funders sometimes start with a shorter ask first. If your target wants a brief pitch before a full application, learn how to write a grant letter of inquiry or a grant concept paper to open the door.

Write each section as part of one argument, follow the funder's rules exactly, and ground every claim in the need you proved up front. When the stakes are high or the deadline is tight, you do not have to do it alone; our certified grant writing team handles the full proposal with you.