How to Write a Grant Proposal in 2026: Step-by-Step Guide with Template

A strong grant proposal is clear, specific, sourced, on-format, and on-time. Reviewers read dozens of applications per cycle — clarity wins over cleverness, and following the funder's stated structure beats trying to impress.

This guide walks through how to write a competitive proposal in 2026, with the structure most federal and foundation funders expect.

Before you start writing

Confirm the fit

The single biggest reason proposals fail is poor fit with the funder's priorities. Before drafting:

• Read the full Notice of Funding Opportunity (NOFO) or foundation guidelines.
• Confirm your eligibility (organization type, geography, project scope, beneficiary).
• Look at the funder's previously awarded grants — most federal agencies and large foundations publish recent awards. If their portfolio doesn't look like your project, find a better-fit funder.

Gather the boilerplate

You'll need ready-to-paste versions of:

• Mission statement and history (2–3 sizes: 1-paragraph, 1-page, 2-page).
• IRS determination letter (501(c)(3)s).
• Most recent audited financials and IRS Form 990.
• Organization chart.
• Board roster.
• Key staff résumés/biosketches.
• For federal: active SAM.gov registration with Unique Entity ID (UEI).

The proposal structure

Most federal and foundation proposals share this backbone — even when section names vary.

1. Executive summary / cover letter

1 page. State who you are, what you're requesting, the problem, your proposed solution in one sentence, the budget total, and the expected outcomes. Write this last but place it first.

2. Statement of need / problem statement

1–3 pages. The evidence-based case. Use specific, sourced data — prefer .gov and peer-reviewed sources — to quantify the problem and the population. Show why this work matters now, in this place, for these people. Avoid generalities.

3. Goals, objectives, and outcomes

• Goals: broad ambitions (1–3, single sentence each).
• Objectives: SMART milestones — Specific, Measurable, Achievable, Relevant, Time-bound.
• Outcomes: changes in conditions, behaviors, or knowledge that result.

4. Project description / methods

The longest section. What exactly you'll do, in what sequence, by whom, with what tools, over what timeline. Include a workplan or Gantt-style timeline showing milestones tied to the budget periods.

5. Evaluation plan

How you will know it worked. Identify:

• Metrics and data sources (pre/post, surveys, administrative data, etc.).
• Evaluator (internal staff or external consultant).
• Reporting cadence to the funder.

6. Organizational capacity

Why your team is qualified. Past similar projects, relevant credentials, key staff, partnerships, and infrastructure. Match this section to the project — don't list everything you do.

7. Sustainability

For multi-year projects: how the work continues after this grant ends.

8. Budget and budget narrative

• Budget: a line-item spreadsheet by cost category (personnel, fringe, travel, equipment, supplies, contractual, other, indirect) and by year for multi-year projects.
• Budget narrative: 1–3 pages explaining each cost, why it's needed, and how it was calculated.

For federal grants, costs must be allowable, allocable, and reasonable under the Uniform Guidance (2 CFR Part 200). Indirect costs follow your federally-negotiated indirect cost rate or the 15 % de minimis rate (or 10 % MTDC for sub-awards, depending on cycle — confirm the current rate at the time of submission).

9. Attachments

Typically: IRS determination, audited financials, key staff résumés, letters of support, board list, organizational chart, evaluation tools. Follow the funder's required list exactly — extra attachments are often discarded.

A practical workflow

Writing technique

• Write to the rubric. If the funder publishes a scoring rubric, mirror its language and weight in your headings.
• Be specific. Numbers, names, dates, locations. Replace "many" and "various" with counts.
• Lead each paragraph with the conclusion. Reviewers skim; reward them.
• Cite sources for every numeric claim. .gov and peer-reviewed sources are strongest.
• Use plain language. Avoid jargon and acronyms not previously defined.
• Match every budget line to a narrative purpose. Reviewers connect dollars to activities.
• Don't pad to the page limit. A tight 18-page proposal beats a 25-page maximum.

Common reasons proposals fail

1. Poor fit with funder priorities — the most common cause.
2. Did not follow the formatting and submission rules — disqualification with no appeal.
3. Vague project description — reviewer can't tell what will actually happen.
4. Weak or missing evaluation plan — funders increasingly require evidence-based proposals.
5. Unsupported budget — line items don't tie to activities, or numbers look padded.
6. Submitted too late — Grants.gov gets congested at the deadline.

Resources

• Grants.gov Workspace — the federal application system. Free.
• Candid Learning — free and paid grant-writing training; the Foundation Directory is free at many public libraries.
• Grant Professionals Association — membership organization with a national conference and chapter meetings.
• National Council of Nonprofits — Grantseeking basics — short, practical overview.

Common questions

How long should a proposal be? Whatever the funder says. A typical foundation proposal is 5–15 pages; a typical federal proposal is 25–50 pages plus attachments. Going over the page limit can be an automatic disqualification.

Can I copy text from one proposal to another? You can reuse boilerplate (mission, history, capacity sections) freely. The project narrative, budget, and evaluation must be tailored to each funder.

Do I need a grant writer? Helpful for major federal proposals, especially the first one. Not required for small foundation proposals or student aid. Ethical grant writers do not charge a percentage of the awarded grant — federal cost principles generally disallow this anyway.

What if my proposal is rejected? Request reviewer comments (federal agencies typically share them; foundations may not). Use the feedback to revise and apply to the next cycle or a different funder. Most successful organizations are funded on the second or third application to a given funder, not the first.