The Nine Sections of a Winning Grant Proposal (and How to Write Each One)

Almost every full grant proposal — foundation or federal — has the same skeleton. Nine sections, in roughly the same order, doing roughly the same job. Funders don't coordinate on this; the structure converged because each section answers a question reviewers actually have. Once you can name the question each section answers, you can write to the question instead of free-associating into a Word doc and hoping.

This is the working anatomy of a grant proposal. We'll walk through what each section is for, what good and bad versions look like, and the order to actually write them in (which is not the order they appear).

The nine sections, in the order they appear

1. Cover letter or executive summary
2. Statement of need
3. Project description (goals and objectives)
4. Methodology, activities, and timeline
5. Evaluation plan
6. Organizational capacity
7. Budget and budget narrative
8. Sustainability plan
9. Attachments and appendices

Specific funders rename or merge these — some federal NOFOs use ten section headings, some foundation applications collapse them into five — but the underlying logic of what reviewers want at each step is the same. If you've answered the question that section is supposed to answer, you can rearrange or rename to fit any application form.

1. Cover letter or executive summary

The question: Why should I read this and what are you asking for?

One page, three paragraphs at most. Names the funder by their priority in the first sentence, names the problem and the population in the second, names the dollar amount and what it pays for in the third. End with one signed name and contact info.

This section is closely related to a Letter of Inquiry — in fact, a strong LOI is essentially a tightly written executive summary plus a sign-off. If the funder asked for an LOI first and accepted it, the executive summary in your full proposal usually doesn't need to add much.

2. Statement of need

The question: Is this a real problem, and is it a problem worth fixing?

Two pieces of evidence: a number that establishes scale, and a specific, local example that establishes texture. Cite federal data, peer-reviewed research, or your own program data. Vague claims (“many young people in our community face barriers to opportunity”) read as bluster.

Bad: “Literacy is a major issue in Philadelphia.”

Good: “Forty-three percent of K–5 students in the School District of Philadelphia read below grade level (NAEP, 2024). At Hancock Elementary, where we tutor 120 students a year, the rate is 67%. Two of our current third-graders entered the program reading at a kindergarten level.”

3. Project description (goals and objectives)

The question: What specifically will you do with this money?

Distinguish goals from objectives. Goals are broad, directional, often non-measurable (“raise reading proficiency in our service area”). Objectives are specific, measurable, time-bound (“by spring 2027, 60% of program participants will read at or above grade level, up from a baseline of 28%”).

Reviewers want to see two or three goals and three to five objectives. Don't list ten goals; it signals you're trying to hit whatever priority happens to land. Pick the ones that match the funder's rubric and stop.

4. Methodology, activities, and timeline

The question: Are you going to actually pull this off, and how do I know?

Describe the program model concretely — what staff will do, what participants will do, where it happens, on what schedule. If your approach is evidence-based, name the model and cite the evidence (“our reading curriculum is grounded in the Orton- Gillingham approach, which has been validated in randomized controlled trials including [citation]”). If it's innovative, explain why innovation is justified given existing evidence.

Include a timeline. Federal NOFOs typically require a Gantt chart or timeline table; foundations don't always require one but it makes the section much stronger. Show specific start dates, key milestones, and the period of performance you're proposing.

Many proposals also benefit from a logic model diagram showing inputs → activities → outputs → outcomes. Include it as a visual in this section or as an attachment.

5. Evaluation plan

The question: How will we know if this worked?

Specify four things: indicators (what you'll measure), methods (how you'll measure them), timing (when measurements happen), and ownership (who runs the evaluation).

Distinguish outputs, outcomes, and impact. Reviewers know the difference and notice when applicants conflate them. Outputs are what you do (“200 students tutored, 50 sessions per student”). Outcomes are the changes you cause (“participants gained an average of 1.2 grade levels”). Impact is the broader change you contribute to (“the literacy gap in our service area narrowed”).

Federal grants increasingly distinguish formative evaluation (used to improve the work in progress) from summative evaluation (used to judge whether it worked). If your evaluation plan only mentions end-of-year reports, you've likely missed the formative half.

6. Organizational capacity

The question: Can your organization actually do this work, and have you done it before?

Three things establish capacity: relevant track record, current infrastructure, and key personnel.

Track record means concrete prior results, not aspirations. “Founded in 2008, served 4,800 students, last year 71% of participants read at or above grade level by year-end” is track record. “Committed to making a difference” is not.

Infrastructure means financial-management systems, audit compliance, technology, and operations. For federal grants this section should explicitly address your readiness for OMB Uniform Guidance compliance. For foundation grants, it's lighter — recent audited financials and a clean board are usually sufficient. Personnel: name the key people, their roles, and one line on each of their relevant experience.

7. Budget and budget narrative

The question: Are these numbers realistic, allowable, and tied to the work?

The budget table itself is line items. The budget narrative is the prose that justifies each line: what each cost is for, how it was calculated (“0.5 FTE program coordinator at $52,000/year”), and why it's necessary.

Reviewers read budget narratives more carefully than almost any other section. Round numbers without explanation (“$25,000 for materials”) signal you didn't do the homework. Show the math: how many participants, what supplies per participant, what unit costs.

Federal budgets need an indirect cost section. Use your NICRA if you have one, or the 10% de minimis rate if you don't. Our free Indirect Cost Calculator handles the MTDC math automatically.

8. Sustainability plan

The question: What happens after this grant ends?

Funders ask because they don't want to fund work that collapses on day 366. Honest sustainability plans name specificrevenue sources and a timeline. “We will pursue diversified funding” is the answer of someone who hasn't thought about it.

Stronger: “In year one, this grant covers 70% of program costs. We have committed to growing individual giving from $84,000 to $150,000 by year three (we increased it 28% last year). Our state Department of Education has expressed interest in the methodology and we plan to pursue a formal partnership in year two. By year four, no single funder will represent more than 35% of the program.”

9. Attachments and appendices

The question: Can I verify what you said?

Standard attachments: IRS determination letter (proof of 501(c)(3) status), most recent audited financial statements (or review for smaller orgs), most recent Form 990, board roster, organizational chart, current operating budget, letters of support, and a logic model if you didn't include one in section 4.

Federal applications add: NICRA agreement (or de minimis declaration), SF-424 family forms, key personnel CVs in the agency's preferred format. Read the NOFO checklist; missing attachments are a common and avoidable rejection reason.

The order to actually write them in

The order they appear is not the order to write them. Most successful proposal writers work in roughly this sequence:

1. Project description (3) and methodology (4) first. Pin down what you're proposing before describing why it matters or how you'll measure it.
2. Evaluation plan (5). Once the project is concrete, define how you'll measure it. Often the evaluation plan reveals that an objective is too vague, so you fold corrections back into section 3.
3. Budget and budget narrative (7). The budget forces you to confront whether the proposed work is actually feasible at the dollar amount you're asking for. You may discover you need a smaller scope or a bigger ask.
4. Statement of need (2) and organizational capacity (6). Now that the project, measurement, and budget are settled, write the framing sections. The need is shaped by what you're proposing to do; capacity is shaped by what staff and infrastructure the budget assumes.
5. Sustainability plan (8). Specifics from the budget shape what realistic post-grant funding looks like.
6. Cover letter / executive summary (1). Last. Now that you know what the proposal actually says, you can summarize it.
7. Attachments (9). Pulled together at the end against the funder's checklist.

Where most proposals fall apart

• Sections that don't talk to each other. The need section says one thing; the project description proposes something different; the evaluation measures something else. This is the single most common reason proposals score badly.
• Vague objectives. “Improve outcomes for participants” is not an objective. “Increase the percentage of participants reading at grade level from 28% to 60% by spring 2027” is.
• Budget that doesn't match the work. The activities section describes a year-round program but the budget covers nine months. The methodology requires three full-time staff but the budget funds 1.5 FTE. Reviewers spot these instantly.
• Generic capacity prose. Capacity sections that read like marketing copy — “a dynamic, mission-driven organization” — don't give the reviewer any actual evidence. Track record numbers do.
• Sustainability plans written last and skipped. A weak sustainability section is sometimes the one thing that drops a strong application out of the funded range.

The bottom line

A grant proposal is nine answers to nine questions. The format varies by funder; the questions are constant. When sections contradict each other, when objectives are vague, when budgets don't match the work, the proposal scores badly — not because the writing was bad, but because the underlying coherence wasn't there.

Write the project, the evaluation, and the budget first — before the framing sections, before the cover letter. By the time you write the executive summary, the proposal will have written itself.