Grant Proposal Template: The Structure That Works Across Most Funders

A grant proposal template structured as “about us → our mission → our history → the project” is the wrong template. It organizes information the way organizations think about themselves, not the way reviewers evaluate proposals.

The template that clears rubric thresholds consistently opens with the community problem, moves to the proposed solution and its evidence base, and introduces the applicant’s capacity only after establishing that the problem is real and the solution is credible.

Why Most Grant Proposal Templates Are Wrong

Most downloadable grant proposal templates front-load organizational information: executive summary, about our organization, history and mission, staff bios — then eventually get to the community need.

This structure fails for three reasons. First, program officers reviewing 200 proposals have read the organizational introduction format hundreds of times. Opening with organizational history does not differentiate the applicant. Second, it signals that the applicant is pitching their organization rather than responding to the funder’s priorities. Third, it buries the community need — the problem the funder actually cares about solving — behind marketing copy that reviewers skim.

The template that works opens with the problem. Not “our organization serves low-income families” but “in Hennepin County, 22% of households below 200% of the federal poverty level reported food insecurity in the past 12 months, compared to 14% statewide” (USDA Food Security Survey, 2024 county estimates). The funder funded this program because they care about that number. Give it to them in sentence two.

Universal Sections vs. Funder-Specific Sections

Every competitive grant proposal contains six universal sections regardless of funder type. The weight each section carries varies.

Universal sections — present in every complete proposal:

• Project summary
• Need statement
• Project description (activities, timeline, staff)
• Evaluation plan
• Budget and budget narrative
• Organizational information

Federal-only sections — required by most federal NOFOs:

• SF-424 Application for Federal Assistance (cover page)
• Assurances and certifications (SF-424B or program-specific equivalents)
• Logic model (required by HHS, DOJ, HRSA, SAMHSA; strongly recommended elsewhere)
• Data management plan (NIH, NSF, and some HHS programs)

Foundation-specific sections — vary by funder:

• Theory of change narrative (distinct from logic model at some foundations)
• Sustainability plan (how the program continues after the grant ends)
• Community engagement description (how affected populations participated in program design)

The section weighting shifts by funder type. Federal proposals weight evaluation and organizational capacity heavily — SAMHSA’s NOFO scoring rubrics typically allocate 20–25 points each to project design, evaluation, and organizational capacity. Foundation proposals weight need statement and mission alignment most heavily. Corporate proposals weight organizational visibility and partnership opportunity.

Project Summary: The 300-Word Version That Must Stand Alone

Federal NOFOs specify a project summary length — typically 300–500 words, sometimes called the “abstract” or “project narrative summary.” Foundation applications often request a project summary as the first section of the narrative.

The project summary must work without the full proposal behind it. Senior reviewers, board members, and communications staff at the funder will read the project summary and may not read the full proposal. The project summary is also what gets quoted in press releases if you receive the award.

A complete project summary covers five elements in sequence: (1) the specific problem in the specific geography, with a number; (2) the proposed solution and the evidence that it works; (3) the target population and how many you will serve; (4) the two or three key activities; (5) the measurable outcomes you expect to achieve by the end of the project period.

The project summary should not include organizational history, staff names, or budget amounts unless the funder specifically requests them. It is not a cover letter.

Need Statement: How to Use Local Data Without Fabricating It

The need statement requires local data — not national statistics padded with the phrase “in communities like ours.”

Local data sources that are legitimate and frequently underused:

• Census Bureau American Community Survey (ACS) — 5-year estimates by census tract, available at data.census.gov. Poverty rate, housing cost burden, educational attainment, health insurance coverage, and dozens of other indicators at sub-county geography.
• County Health Rankings — University of Wisconsin Population Health Institute compiles county-level health outcomes and health factor rankings for all 3,000+ US counties annually.
• State child welfare databases — child abuse and neglect rates by county, available from most state health and human services agencies.
• School district report cards — chronic absenteeism rates, graduation rates, and discipline data by school.
• Local needs assessments — your county’s Consolidated Plan (for HUD-funded programs), Community Health Needs Assessment (required of nonprofit hospitals every 3 years under the ACA), or 211 call data.

If local data for your specific program area does not exist, combine the closest available local indicator with a validated relationship to your outcome. “18% of Riverside County adults report no dental care in the past year (BRFSS 2023 state module); untreated dental disease is associated with a 2.7x increased risk of systemic cardiovascular events (AHA, 2022)” is acceptable. “Oral health is important” is not.

Project Description: Activities, Timeline, and Responsible Staff

The project description is where most proposals collapse into vague language. Reviewers score the project description on specificity: are the activities defined precisely enough that a program officer could evaluate whether you did them?

Each activity needs four elements:

1. What — the specific activity (not “case management” but “weekly 45-minute individual counseling sessions using CBT protocol with each enrolled participant”)
2. Who — the staff title (not name, unless you have a named PI) responsible for delivering it
3. When — month or quarter in the project period when it occurs
4. How many — the output (number of sessions, participants, hours, materials distributed)

The timeline is typically presented as a Gantt chart or month-by-month table. Reviewers use it to verify that the proposed scope is achievable within the project period and that activities are sequenced logically (hiring before program launch, training before direct service).

Staff descriptions belong in the project description section, not the organizational capacity section. Name the position, the required qualifications, and the FTE allocation to this project. If the position is filled, note the incumbent’s relevant experience in one sentence.

Evaluation Plan: What “Measurable Outcomes” Actually Requires

An evaluation plan that lists outputs (“we will train 200 community health workers”) does not meet the standard of a measurable outcomes plan. The measurable outcome is what changes in the participants, community, or system as a result of the training.

Write outcomes in the format: “[X%] of [population] will [demonstrate measurable change] by [timepoint] as measured by [instrument].” Example: “80% of enrolled community health workers will achieve a passing score (≥70%) on the CHW competency assessment administered at 90-day post-training follow-up.”

Data collection methods must be realistic given the organization’s capacity. A community health organization applying for a $150,000 two-year foundation grant should not propose a randomized controlled trial. Acceptable methods for that grant size: pre/post surveys with a validated instrument, administrative data pulls from the organization’s case management system, or follow-up interviews with a 30% sample.

For federal programs that require “rigorous evaluation design,” check the NOFO’s specific language. OJJDP and HRSA programs often require adherence to the What Works Clearinghouse evidence standards or a specific evaluation tier (Tier 1–5 on the HHS evidence scale). See the evaluation plan guide for full detail on meeting those requirements.

Budget and Budget Narrative: The Section Reviewers Trust Most

The budget is the only section that cannot be written around factual gaps. Every inconsistency between the narrative and the budget is visible.

A complete budget narrative justifies every line item:

Personnel: “Project Director (1.0 FTE, annual salary $72,000, fringe rate 28%): $72,000 salary + $20,160 fringe = $92,160. The Project Director will provide overall program management, staff supervision, funder communication, and data reporting for the full 24-month project period.”

Fringe benefits: State the rate and what it covers. “28% fringe rate covers FICA (7.65%), health insurance (12.3%), retirement match (5%), workers’ compensation (1.1%), and unemployment insurance (1.95%), consistent with organizational payroll documentation.”

Indirect costs: “Indirect costs calculated at 12% of Modified Total Direct Costs (MTDC) per our federally negotiated indirect cost rate agreement with HHS, Rate Agreement dated March 2025, effective through FY2027.”

For foundation proposals that discourage or limit indirect costs, note which costs are excluded from MTDC and how you are absorbing overhead.

Organizational Information: What to Include and What to Cut

The organizational information section is not a marketing section. It is the evidence section that answers: can this organization actually execute this project?

Include:

• Years in operation and core programs (one sentence)
• Relevant prior grants: funder name, award amount, award period, program description, performance outcome (one line per award)
• Financial health: most recent audit result, operating budget size, months of cash reserves
• Staff credentials: relevant degrees, licensures, certifications for key project staff
• Facilities: if the project requires specific facilities, confirm they exist and are available

Cut:

• Mission statements that don’t connect to the specific project
• Lists of board members without explaining why that governance structure is relevant
• Testimonials or anecdotes not tied to program performance data
• Any language that begins with “we are passionate about” or “we are committed to”

The organizational information section should make the reviewer confident, not impressed. Confidence comes from evidence.

DEFINITION

Budget narrative

The written justification accompanying a grant budget that explains why each line item is necessary, how costs were calculated, and how they connect to proposed activities. Federal grants under 2 CFR 200 require that all costs be allowable, allocable, and reasonable — the budget narrative documents all three. It is distinct from the budget spreadsheet, which shows numbers; the narrative explains them.

DEFINITION

Project summary

A 300-word (or funder-specified length) standalone description of the proposed project — problem statement, proposed solution, target population, key activities, and expected outcomes. The project summary is often read first and sometimes read alone by senior reviewers who use it to understand the proposal before scoring begins. It must be self-contained and accurate to the full proposal.

DEFINITION

Indirect cost rate

A rate applied to a direct cost base (typically Modified Total Direct Costs, or MTDC) to recover organizational overhead expenses — rent, utilities, HR, finance — that support the project but cannot be directly attributed to it. Organizations with federally negotiated indirect cost rate agreements (NICRA) apply that rate. Organizations without a negotiated rate may claim the 10% de minimis rate under 2 CFR 200.414.