Most grant proposal templates fail in one of two ways: they are a bare list of headings that tells you nothing about what a reviewer needs from each section, or they are a finished sample whose polished sentences fit someone else’s facts. This nonprofit grant proposal template takes the third path. It gives you the structure, the burden of proof each section carries, and the space each deserves, and then it makes you write your own program into it. A template earns its keep by stopping you from forgetting a section a reviewer expects and by telling you when a section is actually done. It does not write the proposal.
One boundary stated plainly: a clean structure improves review readiness, but it cannot guarantee an award, an invitation, or any funder decision. What it can do is remove the self-inflicted rejections, and those are more common than most teams admit.
The template, complete and copyable
Copy the skeleton below straight into your working document, or download the same structure as a Markdown file. This is a free grant proposal template in the plainest sense: the whole thing is on the page, the download adds per-section writing prompts and failure checks, and neither asks for an email address. Length shares assume a ten-page narrative; scale them proportionally for shorter limits, and use the funder’s lengths whenever they specify their own.
# [Organization name]: proposal to [funder] for [program name]
## 1. Executive summary (half a page, written last)
Who you are, the documented need, the program that answers it,
the amount requested, and the intended, measurable result.
## 2. Organizational background (one page)
Capacity relevant to THIS program: current work, staffing,
one or two verifiable results with dates. Legal status,
service area, and annual budget stated once.
## 3. Statement of need (1.5 to 2 pages)
Population, condition, consequence, and your relevance, in
that order. A source and data year on every figure.
## 4. Program description (three pages)
Who does what, for whom, when, where, at what capacity.
The participant's path from intake to exit. Staff roles,
partner commitments, and a timeline with owners.
## 5. Objectives and outcomes (half a page)
Each objective checkable later: who changes, in what way,
by how much, by when. Outputs separated from outcomes.
## 6. Evaluation plan (1 to 1.5 pages)
The questions you will answer, the indicators, the data
sources, who collects what and when, and how results
will be reported and used.
## 7. Budget and budget narrative (per funder format)
Every line with unit, quantity, rate, and source, traced
to an activity. Narrative explains basis and purpose.
## 8. Sustainability (half a page to one page)
What continues after the grant, what ends, and what future
decisions depend on. No vague pledge to find other funders.
## 9. Attachments (per funder list)
Only what the funder requests, current, signed, and in the
requested file format.
All nine sections with per-section writing prompts, length shares for a ten-page narrative, a named failure check for each section, and a compact letter-proposal variant for small foundations. Reorder freely to match any funder’s format.
Markdown templateWhat each section must prove
Think of every section as answering a skeptical question, not filling a slot. The table gives the question, the space it deserves in a ten-page narrative, and the failure mode that shows up in weak submissions. Together, the table and the skeleton form a complete proposal template map: the skeleton tells you what to write, the table tells you when each section can be called done.
| Section | Must prove | Share of 10 pages | Common failure |
|---|---|---|---|
| Executive summary | The whole request coheres in half a page | 0.5 | Written first, matches nothing |
| Organizational background | Capacity relevant to this program | 1 | Full-history recitation |
| Statement of need | A documented gap for a defined population | 1.5 to 2 | Circular need, orphan statistics |
| Program description | Who does what, for whom, when, at what scale | 3 | Aspirations without operations |
| Objectives and outcomes | Change that could be checked later | 0.5 | Outputs dressed as outcomes |
| Evaluation plan | You will know whether it worked | 1 to 1.5 | Method-free survey promises |
| Budget and narrative | Money matches activities, both directions | Per funder format | Numbers disagree with prose |
| Sustainability | A plausible path past the grant | 0.5 to 1 | “We will seek other funders” |
| Attachments | Compliance, current and signed | n/a | Expired documents on deadline day |
Three of these deserve expansion because they carry most of the weight.
The statement of need must establish population, condition, consequence, and your relevance, in that order, with a source and data year on every figure. It is the section most often written backward, starting from the program and reverse-engineering a need. The full method, with a worksheet, is in the needs statement template.
The program description is the largest section because it is the one a reviewer cannot reconstruct from anywhere else. Your background can be verified, your need can be checked against public data, but only you can explain the operating model. If a stranger cannot sketch a participant’s week from this section, it is not finished.
The budget must reconcile with the narrative line by line: every budget line traces to an activity, every staffed activity to a budget line. The grant budget template covers the formulas and reconciliation checks; the evaluation plan template and logic model template do the same for the measurement sections.
Weak versus strong, on the page
The fastest way to calibrate is to see the same content written both ways. Everything below uses Cedar Bend Youth Alliance, a fictional nonprofit invented for worked examples on this site, with illustrative figures. Two companion pages extend this section: a complete annotated sample proposal assembled end to end from the same fictional case, and seven more weak-and-strong passage pairs covering every major section.
Worked example
Statement of need: two openings from a fictional applicant
The fictional Cedar Bend Youth Alliance is requesting funds for an after-school reading program. All figures are illustrative placeholders.
Weak: “Literacy is a growing crisis in our community. Studies show that reading is critical to student success. Cedar Bend Youth Alliance urgently needs funding to continue its vital work helping struggling readers.”
Every sentence fails a different way. The first claims a trend with no data. The second cites “studies” without a source. The third commits the classic circular need: the applicant’s funding gap presented as the community’s problem.
Strong: “In the Cedar Bend school district, 41 percent of third graders scored below proficient on the 2025 state reading assessment, against 33 percent statewide (state education department, 2025). The district’s two elementary schools ended their own after-school tutoring in 2024 when a federal grant lapsed. Students who are not reading proficiently by the end of third grade face documented long-term academic risk, and no other structured literacy program currently operates in the district.”
Population, local figure with comparison and source, a specific gap in services, and a consequence. The organization has not appeared yet, which is correct: the need belongs to the community, not the applicant.
Worked example
Executive summary: the same fictional request, twice
Weak: “Cedar Bend Youth Alliance is a dynamic, community-driven organization dedicated to empowering youth. We respectfully request support for our innovative programming, which transforms lives every day.”
No amount, no program, no population, no result. A reviewer reading only this paragraph could not describe the request.
Strong: “Cedar Bend Youth Alliance requests $48,000 to operate a structured after-school reading program for 60 third and fourth graders at two elementary schools in the Cedar Bend district during the 2027 school year. The program provides four hours weekly of small-group instruction from two certified teachers, targeting the 41 percent of district third graders below reading proficiency. We will measure progress with fall and spring benchmark assessments and report results to the funder within 60 days of the school year’s end.”
Amount, program, population, place, dose, staffing, the need in one clause, and a measurable commitment. Six sentences of the full proposal, compressed honestly. This is why the summary is written last. The full drafting method for this section, with a reconciliation table that catches number drift before it reaches the reviewer, is in the executive summary template.
Grant proposal format: how to present the document
The format questions that stall teams have short answers, because the governing rule is always the same: the funder’s current instructions control the format, and the template adapts to them, never the reverse.
Section order. Use the order in the skeleton when the funder does not specify one. When they do, their order wins, even when it splits sections this template joins. The vocabulary rule matches: if the funder says “problem statement” where you say “statement of need,” their term goes on the heading.
Page and word limits. Treat limits as hard. Count them the way the funder counts them, because a portal’s character count usually includes spaces while a word processor’s may not, and apply the length shares from the table inside whatever total the funder allows.
Cover page. Add one only when the funder requests or permits it, and then include exactly the fields they ask for. An unrequested cover page spends a page of a reviewer’s attention on information the application form already carries.
Files and delivery. Deliver in the requested file type, follow the funder’s naming rules exactly, and keep one source file for every number so the narrative, budget, and attachments cannot drift apart during final edits. The submission checklist runs these format checks as a gate before the portal’s final screen.
Federal applications. These are not a formatting variant of the foundation structure; the notice of funding opportunity mandates its own forms, sections, and limits. Build federal applications from the notice itself, using Grants.gov’s applicant resources as the entry point.
The letter proposal: a foundation template variant
Many smaller foundations, family foundations especially, ask for a short letter rather than a full narrative. When they do, the letter is not a cover note for a proposal; it is the funding proposal, complete in three pages or fewer. The same nine burdens of proof apply, compressed into a foundation proposal template you can hold in one sitting:
- The request, first paragraph. Organization, amount, program, population, and period. The strong executive summary above, at half its length.
- The need, one to two paragraphs. The strongest local figure with its source and year, the service gap, and the consequence.
- The program, two to three paragraphs. What happens, who delivers it, at what capacity, and the one or two objectives you will measure.
- Capacity and budget, one paragraph each. The result that proves you can run this program, then the total budget, the amount requested, and the other confirmed sources.
- The close. Contact, offer of a full proposal or site visit, and the signature of the person accountable.
A letter proposal is a different document from a letter of inquiry, which asks whether a full application is welcome rather than making the complete request; the letter of inquiry template covers that one-page screening build, and the skeleton download includes this letter variant alongside the full structure.
Allocate length before you draft
Length allocation is a decision, not an accident. Teams that draft without shares end up with the sections that were easiest to write, usually background and mission language, crowding out the sections reviewers weight most, usually program design and evaluation.
The practical method: take the funder’s page or word limit, apply the shares from the table above, and write the target at the top of each section of your working file before drafting a sentence. When a section runs over, the overage must be argued for, not defaulted into. Half a page of trimmed organizational history buys you half a page of staffing detail in the program description, and that is almost always the better trade.
Two allocation rules hold across formats. First, the need and program sections together should consume at least half of any narrative; if they do not, the proposal is describing the applicant more than the work. Second, no section should be padded to hit its share. A tight three-quarter page evaluation plan beats a stretched page and a half.
Assemble per funder, in this order
The template is the stable half of the system. The other half is a per-funder assembly sequence, and the order matters because each step can end the work before you spend the next step’s hours.
- Eligibility before anything. Confirm geography, program fit, applicant type, and grant size range against the funder’s current guidelines. A fail-closed eligibility matrix makes this a gate instead of a vibe.
- Map the funder’s requirements. List every question, limit, format rule, and attachment from the live instructions. This map is the working grant application template for that funder: it, not the generic structure, controls the final document’s order and vocabulary.
- Pull from your core narrative. Reuse approved facts, not recycled prose. The core grant narrative template separates the facts that stay stable from the decisions you must remake per funder.
- Draft to the map, using the section standards above. Write need and program first, budget alongside program, evaluation against objectives, background against what this funder cares about, summary last.
- Reconcile and package. Check every number across narrative, budget, and attachments, then run the submission checklist before the portal opens its final screen.
For a first-time applicant, structure is necessary but not sufficient; readiness comes before persuasion, and it is worth confirming you can operate and report on a grant before polishing prose about one.
Frequently asked questions
What sections does a grant proposal template include?
The stable working structure has nine sections: executive summary, organizational background, statement of need, program description, objectives and outcomes, evaluation plan, budget with narrative, sustainability, and attachments. Each section answers a skeptical reviewer question rather than filling a slot. The funder's own instructions always override the template, and federal applications follow their own mandated formats, so start those from the notice itself.
How do you format a grant proposal?
Follow the funder's current instructions first: their section order, section names, page or word limits, file types, and naming rules override any template. When no format is specified, use the nine-section order shown here, count limits the way the funder counts them, and add a cover page only when one is requested. Federal applications follow the format their notice of funding opportunity mandates, so build those from the notice itself.
How long should each section of a grant proposal be?
Allocate length before drafting. In a ten-page narrative, the program description deserves about three pages, the statement of need one and a half to two, the evaluation plan one to one and a half, and the executive summary half a page. Need and program together should consume at least half of any narrative, no section should be padded to hit its share, and the shares scale proportionally for shorter limits.
Does a strong template guarantee a grant award?
No. A clean structure improves review readiness, but it cannot guarantee an award, an invitation, or any funder decision. What it removes are the self-inflicted rejections: forgotten sections, circular need statements, budgets that disagree with the narrative, and expired attachments on deadline day. Structure is necessary but not sufficient, so confirm you can operate and report on a grant before polishing prose about one.