How to Write a Grant Proposal: A Step-by-Step Guide

To write a grant proposal, first confirm you are eligible and that your project fits the funder's priorities, then plan the project before drafting: the problem, the measurable change, the activities, and the cost. Draft the core sections in this order: statement of need, goals and objectives, methods, evaluation plan, organizational capacity, budget and budget narrative, and sustainability. Write the executive summary and cover letter last, size everything to the funder's limits, review it against the guidelines, and submit early.

The rest of this guide covers how to do each of those steps well, where proposals typically break down, and how the process changes for research funders such as NIH and NSF.

Step 1: Confirm fit before you write anything

Funders decline far more requests for poor fit than for weak prose, so the first hours belong to the guidelines, not the draft. For a foundation, that means its published guidelines, recent grants, and typical award size. For a federal program, it means the Notice of Funding Opportunity; our explainer on reading a notice of funding opportunity shows where eligibility, deadlines, and scoring criteria sit.

Answer four questions before committing:

1. Are you eligible? Check organization type, location, and any registration requirements. Federal applicants need an active SAM.gov registration and Unique Entity Identifier, which can take weeks to complete; see registering with SAM.gov and Grants.gov.
2. Does the project match a stated priority? If you cannot explain in one sentence why this funder would care, keep looking. Qualifying funders through prospect research is how you find funders where that sentence comes easily.
3. Is the request the right size? Asking for three times a foundation's largest recent grant usually ends the conversation.
4. How will it be scored? Federal notices publish review criteria, often with point values. Foundations rarely publish rubrics, but their guidelines list what they want to see. These criteria become your structure.

Step 2: Plan the project before drafting prose

A proposal is easier to write when the program is already designed. Before writing paragraphs, settle these on a single page:

• The problem, in one sentence, with the two or three data points that prove it.
• The change you will produce, as numbers with a deadline.
• The activities that produce that change, who runs them, and when.
• The cost, built from those activities.

A logic model is the standard tool for this: it lines up inputs, activities, outputs, and outcomes so every activity connects to a result. If you cannot fill in the logic model, the proposal will have the same gap.

Then work backward from the deadline. Planning dates for internal drafts, budget sign-off, partner letters, and final review prevents the most common failure, which is a strong program described in a rushed document. Ask partners for letters of support at this stage, not the week of submission.

Step 3: Draft the core sections

Unless the funder dictates another order, these sections appear in most proposals. If you want the bare skeleton to fill in, use our section-by-section grant proposal outline; what follows is how to write each part well.

Statement of need

This section proves a specific problem exists for a specific population, using data rather than adjectives. Pair local evidence (your waitlist, intake numbers, county statistics) with a credible outside source, cite both, and frame the need around the people affected, not your organization's budget. Our guide to the statement of need includes worked examples in several fields.

Goals and objectives

A goal states the broad change; an objective states a measurable step toward it. "Improve youth literacy" is a goal. "Raise the share of participating third graders reading at grade level from 38 percent to 55 percent by June 2027" is an objective a reviewer can hold you to. The SMART objectives guide has templates.

Methods or project design

Describe what will happen, who does it, for whom, and when. Reviewers should be able to picture a normal week of the program. A timeline table, with activities by month or quarter, answers most of their questions at a glance. Where a funder asks why your approach should work, add a short theory of change or cite the evidence base behind the model.

Evaluation plan

For each objective, name the indicator, the data source, who collects it, and when. Distinguish tracking progress during the project from judging results at the end. If an objective has no indicator, reviewers assume you cannot show it was met. See how to build the measurement table in our evaluation plan walkthrough.

Organizational background and capacity

Many writers skip this or bury it, yet funders are judging risk: can this organization manage the money and deliver? Keep it to roughly a page and make it specific: mission, years of operation, people served, relevant results from similar work, the qualifications of the staff who will run the project, and your financial controls. For federal awards, capacity also means systems that meet the Uniform Guidance requirements.

Budget and budget narrative

The budget table and the narrative that justifies it must match the methods exactly. Every staff role and activity in the work plan appears in the budget, and nothing appears in the budget that the narrative never described. Show the math (rate times hours, unit cost times quantity). Our grant budget guide covers cost categories, and the budget narrative guide covers the justification.

Sustainability

Funders want to know what happens when the grant ends. Name the specific sources you will pursue or have secured, such as another funder, earned revenue, or a partner absorbing costs, rather than promising to "seek additional funding." The sustainability plan guide lists the approaches reviewers find credible.

Executive summary and cover letter, written last

The executive summary opens the proposal but should be written after everything else, because it compresses what the body actually says: the need, the project, the outcomes, the amount, and why you. See writing the executive summary. The cover letter, where a funder accepts one, is separate: a short letter from your executive director that states the amount and project in the first sentence and connects them to the funder's mission.

Research proposals follow a different shape

Academic and scientific funders score a different argument. An NIH application centers on a one-page Specific Aims page, then Significance, Innovation, and Approach in the Research Strategy; NSF proposals are judged on intellectual merit and broader impacts. The planning discipline above still applies, but the sections and vocabulary differ. Start with writing NIH Specific Aims and our overviews of NIH funding and NSF funding. Small businesses applying for SBIR or STTR awards should follow the SBIR proposal guide instead.

How long the proposal should be

These are common ranges, not rules. The funder's page, word, or character limit always overrides them, and many portals cut off text that runs over. Within the limit, give the most room to the sections that carry the most points, usually the need and the methods.

When a funder wants a short pitch before inviting a full application, write a grant letter of inquiry or a concept paper instead.

Writing so reviewers can score you

Reviewers often read many proposals in one sitting, against a rubric. Make their job easy:

• Use the funder's headings, in the funder's order. If the notice asks for "Project Design and Implementation," do not rename it "Our Approach."
• Answer every question asked. A missing element usually scores zero, however strong the rest is.
• Lead each section with its point. Topic sentences should carry the argument for a reader who skims.
• Cite your sources. Use original sources for statistics, with the year, so a reviewer can verify them.
• Keep numbers consistent. The participant count in the summary, the objectives, the evaluation, and the budget must be identical.

To see these principles applied to a complete document, read our full annotated grant proposal example, or draft against the grant proposal template.

Review and submit

Before submitting, check the draft line by line against the guidelines: eligibility, every required section and attachment, page and formatting limits, signatures, and budget math. Our pre-submission grant proposal checklist lists each item. Have someone who did not write the proposal read it as a reviewer would, then submit at least a day or two early, because portal errors and upload rejections are common close to deadlines. If a proposal is declined, ask for reviewer comments where the funder offers them; the most frequent causes are covered in why grant proposals get rejected.

If you would rather hand the drafting to a team that writes proposals every week, our nonprofit proposal writing service takes it from your program details to a submission-ready document. If you are comparing that with bringing in an independent writer or a staff hire, see how organizations hire grant writers.