Anatomy of a grant proposal: every section, explained

A grant proposal is not a collection of essays. It is one argument told in sections: here is a problem that matters to you, here is a credible plan to change it, here is how we will know it worked, here is why we are the right people, and here is what it costs. Each section has a job in that argument, and reviewers read for whether the pieces connect.

This guide walks through every standard section of a foundation proposal, then shows how federal applications package the same content differently. Each section links to a deep-dive page when you are ready to write it.

The core logic every proposal must carry

Before you write a word, you should be able to fill in this sentence:

Every section of the proposal expands one bracket of that sentence. If you cannot fill a bracket, the proposal is not ready, and no amount of polished writing will cover the gap. Reviewers are very good at finding the empty bracket.

The standard sections of a foundation proposal

Private and community foundations vary widely in what they ask for. Some want a two-page letter; some use online portals with a dozen questions and character limits; some accept a full narrative in any format. Candid's guidance on proposal writing lists the same core elements most practitioners use: executive summary, need statement, project description, goals and objectives, organizational information, and budget, plus a plan for sustaining the work beyond the grant.

Here is the full set, in the conventional order, with what each one does.

1. Cover letter

A one-page letter on your letterhead, signed by the executive director or board chair, that introduces the request, names the amount, and connects it to the funder's priorities. It is a courtesy and a signal of organizational commitment, not a place to repeat the proposal. Many online portals have no place for one; if there is no upload slot, skip it.

Deep dive: cover letter and the cover letter template.

2. Executive summary (or abstract)

A half page to one page that states the need, the project, the expected results, your qualifications, and the amount requested. It is often the only section every decision-maker reads, especially board members who approve a docket of grants. Write it last, place it first.

Deep dive: executive summary.

3. Statement of need (problem statement)

The evidence that a specific problem affects specific people in a specific place, why it persists, and why now. Strong need statements use local data, cite sources, and describe the community's need, not the organization's need for money.

Deep dive: statement of need and the statement of need template.

4. Goals and objectives

The goal is the broad change you are working toward. Objectives are the specific, measurable results this grant will produce within the grant period. This is the section reviewers use to judge whether your ambitions are realistic and whether you will be accountable for anything concrete.

Deep dive: goals and objectives, and try the SMART objective builder.

5. Program design (methods, approach, activities)

What you will actually do: who you will serve, how you will recruit them, what they will experience, how often, delivered by whom, on what timeline. This section should show why your approach is likely to work, ideally citing evidence or your own track record.

Deep dive: program design.

6. Logic model

A one-page picture of how resources and activities lead to outputs and then to short-, intermediate-, and long-term outcomes. Some funders require one; many do not ask but are glad to see it as an attachment. Even when it is not submitted, building one first makes every other section easier to write.

Deep dive: logic models and the logic model template.

7. Evaluation plan

How you will know whether you did what you said (process evaluation) and whether it made the difference you predicted (outcome evaluation): indicators, data sources, tools, who collects data, when, and how you will use what you learn.

Deep dive: evaluation plan.

8. Organizational capacity (background and qualifications)

Why your organization can deliver: mission and history, relevant results, key staff and their qualifications, board oversight, financial management, and partners. Letters of support or memoranda of understanding usually live here or in the attachments.

Deep dive: organizational capacity.

9. Sustainability plan

How the work, or its benefits, will continue after this grant ends. Funders are not asking for a guarantee; they are asking whether you have thought past the grant period and have a realistic, diversified plan.

Deep dive: sustainability plan.

10. Budget and budget justification

A line-item budget for the project, plus a narrative explaining how each cost was calculated and why it is necessary. The budget is the proposal translated into numbers; reviewers check that every activity in the narrative has a cost and every cost has an activity. Include a fair share of indirect costs where the funder allows.

Deep dives: grant budget, indirect costs, the budget justification template, and the budget builder tool.

11. Attachments

Commonly requested: IRS determination letter, board list with affiliations, current organizational budget, most recent audit or financial statements, Form 990, key staff résumés, letters of support, and sometimes a logic model or evaluation instruments. Funders who ask for these are checking legitimacy and financial health. Send exactly what is asked, labeled the way they ask.

Typical length norms

There is no universal standard; the funder's instructions always govern. That said, these ranges reflect common practice for a full foundation proposal when the funder gives you room.

Online portals are increasingly common and often use character limits instead of pages. A 2,000-character limit is roughly 300 words. Draft in a word processor, count characters including spaces, and paste in; never write directly into a portal that may time out.

How federal applications differ

Federal applications contain the same intellectual content as a foundation proposal, but packaged differently and judged differently. If you have only written foundation proposals, three shifts matter most.

1. Standard forms carry much of the administrative content

Most federal discretionary grant applications submitted through Grants.gov use forms from the SF-424 family. The exact package varies by agency and program, and the application package for each opportunity lists what is required. Common components include:

HHS's grants guidance for applicants lists the SF-424, SF-424A, SF-LLL, and Project Abstract Summary as standard components, with additional forms included in the application package when a program requires them. Research applications often use the separate R&R (Research and Related) form family instead.

Assurances and certifications have also shifted. Under 2 CFR 200.209, agencies may require annual certifications and representations, which most applicants complete through their SAM.gov registration; the separate SF-424B assurance form is called for when a recipient has an exception from SAM registration requirements. Follow your application package: if a form is in it, complete it.

For the mechanics of registration and submission, see the Grants.gov guide and SAM.gov registration.

2. The project narrative is the primary basis for scoring

In a federal application, the project narrative holds the need, approach, objectives, evaluation, and capacity content. HHS's applicant guidance says plainly that the project narrative is the most important part of the application because reviewers use it as the primary basis to determine whether a project merits an award. The budget narrative must justify the overall cost and the cost per activity or service.

The narrative's headings should usually mirror the review criteria in the Notice of Funding Opportunity (NOFO), in the same order and with the same names. Reviewers score with the criteria in front of them. Make it easy for them to find each element.

3. Merit review against published, weighted criteria

Federal regulations require agencies to run a merit review process for discretionary awards unless a statute prohibits it, and to describe that process in the funding notice (2 CFR 200.205). The NOFO's Application Review Information section must describe each criterion and sub-criterion and, if criteria differ in importance, give their relative weights or points (2 CFR Part 200, Appendix I). Since the 2024 revisions to the Uniform Guidance, NOFOs are also required to follow a standard structure with sections including Basic Information, Eligibility, Program Description, Application Contents and Format, Submission Requirements and Deadlines, Application Review Information, Award Notices, and Post-Award Requirements and Administration.

Many NOFOs also apply a responsiveness or threshold review before merit review: missing a required element, exceeding a funding cap, or being an ineligible entity type can remove an application before any reviewer scores it. Federal agencies also conduct a risk review of applicants before making an award.

For a full walkthrough, see how to read a NOFO and Uniform Guidance essentials.

The federal review process is in flux (as of October 2026)

Federal grantmaking has changed significantly since 2025. Executive Order 14332 (August 7, 2025) directed each agency to designate a senior appointee to review new funding opportunity announcements and discretionary grants for consistency with agency priorities, and called for announcements written in plain language that minimize the need for legal or technical expertise to apply. In May 2026, OMB and 41 grantmaking agencies proposed a "Regulation for Federal Financial Assistance" that would replace the current Uniform Guidance. According to the Congressional Research Service, it would among other things require senior appointees to use independent judgment rather than defer to peer review, and federal appropriations law signed in September 2026 bars OMB from finalizing it on or before December 11, 2026.

The practical effect for writers: read every NOFO closely for new priorities, required certifications, and changed review procedures, and do not assume a program works the way it did in a prior cycle. See the federal funding landscape for current developments.

Foundation vs. federal at a glance

How the sections connect

Reviewers read proposals for consistency. The fastest way to lose credibility is for one section to quietly contradict another: the need statement describes teenagers, but the program serves elementary students; the objective says 120 participants, but the budget pays for one part-time staff member. Use this chain to check alignment:

1. Need → Objectives. Every objective should address a problem documented in the need statement. If the need statement says 41% of third graders read below grade level, an objective should move that number for the students you serve.
2. Objectives → Program design. Every objective should have activities that plausibly produce it. If you promise improved reading scores, the program must include enough reading instruction to make that realistic.
3. Program design → Logic model. The logic model is the program design compressed to one page. They should use the same activity names and the same numbers.
4. Objectives → Evaluation. Every objective needs an indicator, a data source, and a collection schedule in the evaluation plan.
5. Program design → Organizational capacity. Every role named in the design should appear in staffing, with qualifications.
6. Everything → Budget. Every person, activity, material, and evaluation cost appears in the budget, and nothing appears in the budget that the narrative does not explain.
7. Budget → Sustainability. If the budget relies on this grant for a core position, the sustainability plan should say how that position is funded afterward.

What reviewers check in each section

This table maps each section to the questions reviewers ask while reading it. Use it as a self-review rubric.

For a deeper look at how reviewers score and what to do after a decline, see why proposals get rejected.

A worked example: one project, every section

Notice how the same numbers (three schools, 120 students, grades 2–4) recur in every section. That repetition is not redundancy; it is proof of a coherent plan.

How to sequence the writing

The order you write sections is not the order you present them. This sequence prevents rework:

1. Read the guidelines or NOFO twice and make a compliance checklist of every required element, limit, and attachment.
2. Confirm fit. Check eligibility, priorities, and grant size against your project. The funder fit scorecard helps you decide quickly.
3. Build the logic model first. It forces agreement on activities and outcomes before anyone writes prose.
4. Draft the need statement, gathering local data.
5. Write objectives, then program design, then evaluation, keeping numbers consistent.
6. Build the budget alongside the program design, not after it, so the two stay matched.
7. Write organizational capacity and sustainability.
8. Write the executive summary and cover letter last.
9. Run a full review, ideally by someone who has not seen the draft. Check alignment, limits, and attachments.

Common mistakes across the whole proposal

• Writing to your organization's needs instead of the funder's priorities. Funders fund outcomes that advance their mission. Show the overlap explicitly.
• Inconsistent numbers. The participant count changes between sections, or the budget total on the cover letter differs from the budget form.
• Jargon and acronyms. Write for a smart reader outside your field. Define every acronym on first use.
• Burying the ask. State the amount and purpose in the first paragraph of the executive summary and the cover letter.
• Ignoring instructions. Use the funder's headings, order, limits, and file formats. This is the single most avoidable failure.
• Promising too much. Over-ambitious objectives make you look naive or put you on the hook for results you cannot deliver in reports. See grant reporting.

Before you submit

Run the proposal review checklist, confirm every attachment is current, and submit early: online systems slow down near deadlines, and federal submissions can be rejected for registration or validation problems you cannot fix in the final hour. Then log the submission and follow-up dates in your grant tracker.

If you are newer to grants, the readiness assessment can tell you which foundations (financial systems, board oversight, data) to shore up before you apply.