Grant Proposal Examples: What Actually Wins, Annotated

The single most useful exercise in grant writing education is reading 10 funded proposals from a funder you intend to apply to. More than any course, more than any template, more than any certification. Funded proposals reveal what reviewers actually rewarded — which compromises were tolerated, which formatting choices were ignored, which arguments were considered persuasive enough.

The problem is that most “grant proposal examples” floating around the internet are sanitized fragments, made-up samples, or marketing collateral from grant writing consultants. This guide explains where to find real funded proposals, how to read them productively, and the structure differences between federal and foundation work.

What Counts as a Real Proposal Example

A useful proposal example is:

1. A complete document, not a fragment. Reviewers see the whole package; pieces of one section teach little.
2. From a funder you intend to approach. Federal funders, regional foundations, family foundations, corporate funders, and faith-based funders evaluate against different rubrics. A Gates Foundation proposal teaches almost nothing about applying to a $50K family foundation.
3. Recent. Funder priorities, page limits, and required attachments change. A 2014 federal SAMHSA proposal does not reflect the current Notice of Funding Opportunity.
4. Funded. Reading rejected proposals is also useful but for diagnostic purposes — start with funded examples to understand the bar.

Generic samples that “anyone can adapt” are training-wheel templates. They produce proposals that look like other generic proposals, which is exactly what reviewers stop reading at page two.

Where to Find Real Funded Proposals

Federal grants — public records. Federal grant applications submitted to most agencies are subject to FOIA, with redactions for proprietary information. Many funded applications are available on request. Some agencies — particularly SAMHSA, HRSA, and the Department of Education — proactively publish funded application summaries.

State agency websites. State agencies that pass through federal funds (state HHS departments, state education agencies, state justice and victim services offices) frequently publish lists of awardees and sometimes the funded applications themselves. Public records laws apply at the state level too.

Candid Learning’s funded grants database. Candid (formerly Foundation Center / GuideStar) hosts a searchable database of funded grants by foundation. The database covers grant amounts, dates, and recipients but does not always include full proposals.

Foundation websites. Some foundations publish sample successful proposals to reduce applicant burden — community foundations especially. Search “[foundation name] sample proposal” to surface what is publicly available.

Peer nonprofits. Asking peer organizations to share funded proposals is common practice. Most established nonprofits will share with peers in non-competing geographies or programs. Reciprocity is the norm — share yours when asked.

State and regional grantmaker associations. Some associations curate sample proposals for member nonprofits. The United Philanthropy Forum tracks Common Grant Application formats by region.

Federal Grant Proposal Structure (Annotated)

Federal grant proposals are highly structured. The Notice of Funding Opportunity (NOFO) prescribes content, page limits, and required attachments. Going off-spec is grounds for non-review.

A typical federal application includes:

SF-424 Application for Federal Assistance. The cover form. Includes applicant information, project information, congressional district, federal funds requested, and certifications. Mechanical, not narrative — but errors here can stop the application from being accepted by grants.gov.

Project Abstract / Summary. Usually 1 page. The reviewers’ first impression. State the problem, the population served, the approach, the outcomes, and the dollar amount. Many reviewers form an initial scoring intuition from the abstract before reading the narrative.

Project Narrative — Need. Establishes the problem, supported by quantitative evidence. Reviewers expect cited statistics from authoritative sources (federal agency data, peer-reviewed research, recent state or local data). Anecdote alone is insufficient.

What new writers miss: Need is not “our organization needs funding.” Need is “this population, in this geography, faces this problem at this prevalence, with these consequences.” Lead with the population and problem, not the organization.

Project Narrative — Approach. What you will do, with whom, where, and on what timeline. Includes program model, evidence base for the model, target population, recruitment strategy, key activities, and timeline.

What new writers miss: Reviewers want evidence the model works. “We will provide case management” is not enough; “we will provide case management using the [named model], which has shown [specific outcome] in [cited studies]” is.

Project Narrative — Organizational Capacity. Why your organization can deliver. Includes history with similar work, key personnel qualifications, organizational infrastructure, partnerships, and prior outcomes.

Project Narrative — Evaluation Plan. How you will measure outcomes. Specific measurable indicators tied to outcomes, with data collection methods, frequency, and responsible staff. Federal reviewers expect logic models for most program-services awards.

Budget and Budget Narrative. Personnel, fringe benefits, travel, equipment, supplies, contractual, other, indirect costs. Each line item justified in the narrative. Indirect costs follow the de minimis rate (10% MTDC) or a federally negotiated rate per 2 CFR 200 Subpart E.

What new writers miss: The budget narrative is read as carefully as the project narrative. Round numbers and unjustified line items raise flags. Show your math.

Required Attachments. Indirect cost rate agreement, letters of support, key personnel CVs, audited financial statements, organizational chart, list of current funders, certifications.

The pattern: federal proposals are evidence documents. Every claim is supported by a citation, a number, or a verifiable fact. New writers from the foundation world often produce federal proposals that read as too soft, too narrative, and not specific enough.

Foundation Grant Proposal Structure (Annotated)

Foundation proposals are shorter, more flexible, and more relationship-driven than federal applications. Many follow a Common Grant Application (CGA) format adopted by regional grantmaker associations.

A typical foundation proposal includes:

Cover Letter. 1 page. Personalizes the proposal, references prior contact with the program officer, and states the request amount and purpose.

What new writers miss: The cover letter is the single most-read page of a foundation application. A weak cover letter — generic, addressed to the wrong person, missing the requested amount — undermines an otherwise strong proposal.

Executive Summary. 1 page. The proposal in miniature: problem, response, organization, outcomes, request. Some foundations require this; even when not required, including one helps.

Statement of Need. 1 page. Same purpose as the federal “Need” section but typically shorter and more accessible. Foundation reviewers — often program officers and trustees rather than peer-reviewer panels — appreciate clear writing over dense citation.

Project Description. 1–2 pages. What the work is, who it serves, where, and on what timeline.

Evaluation. Half a page to one page. What measurable outcomes you commit to and how you will report on them. Foundations care less about logic models than federal reviewers but care a lot about whether you will actually report.

Organizational Capacity. Half a page. Brief, focused on relevant prior work.

Sustainability. Half a page. How the work continues after the grant. A common drop-off section that distinguishes thoughtful applicants from boilerplate.

Budget. Often a single page including project budget and organizational budget. Less detailed than federal budgets — most foundations want a clear cost picture, not line-item justification.

Attachments. 501(c)(3) determination letter, recent audited financials, IRS Form 990, board list, organizational budget, project budget.

The pattern: foundation proposals are persuasion documents. Tight, evidenced, but written for a generalist program officer who reads many proposals quickly. Federal proposers writing their first foundation proposal often write something that reads as too long, too compliance-heavy, and not personal enough.

Letter of Inquiry (LOI) Structure

Many foundations require an LOI before a full proposal. A typical LOI is 1–3 pages and includes:

• 1 paragraph: organization snapshot.
• 2–3 paragraphs: problem statement and proposed work.
• 1 paragraph: requested amount, purpose, and timeline.
• 1 paragraph: invitation to submit a full proposal.

LOIs are filtering documents. The funder uses them to decide who to invite to a full proposal. Treat them as carefully as full proposals — most rejections happen here.

Common Drafting Mistakes Across Both Types

1. Leading with the organization. Reviewers care about the problem and population first. Lead with the world the work will change, not your founding date.

2. Vague outcomes. “Improve outcomes for at-risk youth” is not measurable. “Increase 9th-grade attendance from 78% to 88% across 240 youth in three high schools” is.

3. Mismatched budget and narrative. The narrative describes a program with three case managers; the budget funds two. This kills proposals more often than weak writing does.

4. Skipped evaluation plans. Or evaluation plans that promise to “measure success” without naming who collects what data when. Reviewers read evaluation as a proxy for organizational seriousness.

5. Generic letters of support. Ten letters that all say the same thing because the applicant drafted them all. Reviewers notice.

6. Going over page limits. Federal reviewers stop reading at the limit; over-limit material is not considered. Foundation reviewers notice and judge accordingly.

7. Submitting without internal review. A second pair of eyes — ideally an experienced grants manager — catches errors the writer cannot see.

For the full step-by-step on drafting a proposal, see our grant proposal writing guide. For the full lifecycle from prospect identification through closeout, see grant lifecycle guide.

How to Read a Funded Proposal Productively

When you find a real funded proposal, do not just skim it. Read it three times:

First read — structure. What sections did the funder require? What’s the order? What’s the page allocation? Note any sections that surprised you.

Second read — evidence. What sources did the writer cite? How recent? Public agency data, peer-reviewed research, internal program data? How specific are the claims?

Third read — voice. Where does the writer get specific? Where do they generalize? Where does the budget narrative justify costs vs. assert them? What does the proposal not say that you would have said?

This is more useful than any course, including the courses we cover in our grant writing courses guide.

A Note on AI-Generated Proposal Examples

A growing volume of “grant proposal examples” online are AI-generated content marketing — produced by software vendors and grant writing consultants to capture search traffic. These are not real proposals. They were never submitted. They were never funded. They reflect what AI thinks a proposal should look like, which is what other AI-generated proposals look like.

If you cannot identify the funder, the year, the awarded amount, and the recipient organization, you are looking at marketing copy, not an example. Move on.

Frequently Asked Questions

Are federal grant proposals public? Funded federal grant applications are generally subject to FOIA, with redactions for proprietary or personally identifying information. Submit FOIA requests to the funding agency. Some agencies publish funded applications proactively.

How long does it take to write a grant proposal? A federal proposal of moderate complexity typically requires 80–200 staff hours, including budget development, partner coordination, attachment collection, and review cycles. A foundation proposal of 5 pages typically requires 15–40 hours. LOIs typically 5–15 hours.

Do I need to follow the funder’s exact section headings? Yes, when the funder specifies them. Reviewers use a scoring rubric tied to the prescribed sections. Renaming or reordering sections makes scoring harder and reflects poorly on the applicant.

Should I include charts and graphics in proposals? Federal proposals: only if the NOFO permits. Many do not, and any unauthorized graphics are excluded. Foundation proposals: a single relevant chart often strengthens a needs statement, but most foundation proposals are text-heavy and graphics-light.

Can I reuse sections of a funded proposal for new applications? Organizational capacity sections, evaluation frameworks, and standard partner descriptions can be reused with light editing. Need statements and project descriptions should be rewritten for each funder — reviewers can detect copy-paste, and funder priorities differ.