Federal Grants
How to Write a Federal Grant Proposal: Full Guide
Grant Writing Service Editorial Team
June 12, 2026 · 6 min read
Table of contents
Key takeaways
- Build your outline from the NOFO's review criteria and application contents, in their order and with their names, before you write a sentence.
- Spend effort in proportion to points; a criterion worth 30 points deserves far more than one worth 5.
- Every objective needs a number, a population, a date and a data source, and every activity should trace to an objective.
- The budget justification is part of the argument: every cost should map to an activity reviewers have already read about.
To write a federal grant proposal (a government grant proposal to a federal agency), build your outline from the Notice of Funding Opportunity (NOFO): its required sections and, above all, its review criteria, using the same order and headings. Then write each section to earn the points attached to it: a data-backed statement of need, measurable objectives, methods tied to those objectives, an evaluation plan, proof you can manage the award, and a budget justification that connects every dollar to the work. Reviewers score against the criteria one by one, so a proposal that makes each criterion easy to find and easy to score beats a better idea that is hard to follow.
This page is about writing the narrative. For the registration, forms and submission steps around it, see our guide on how to apply for federal grants.
Build the outline from the review criteria
Federal reviewers usually work from a score sheet built on the NOFO's review section. Since the 2024 Uniform Guidance revision, NOFOs must include an "Application Review Information" section with the criteria and, often, their point values. Our explainer on how a NOFO is organized shows where to find it.
Make a crosswalk before you draft. Here is an illustrative one for a fictional community health program:
| Review criterion (points) | Proposal section | Where the evidence will come from |
|---|---|---|
| Need (20) | 1. Statement of Need | County health data, our intake records |
| Approach (30) | 2. Goals, Objectives and Work Plan | Work plan table, logic model attachment |
| Evaluation (20) | 3. Evaluation Plan | Evaluation partner's design, data sources |
| Capacity (20) | 4. Organizational Capacity | Past federal awards, staff resumes, audit history |
| Budget (10) | 5. Budget Justification | SF-424A, cost basis for each line |
Three rules follow from this table. Use the criterion names as your headings. Put the section that carries 30 points where reviewers expect it, with space in proportion. And when the NOFO lists specific sub-questions under a criterion, answer each one under its own subheading, because reviewers look for them one by one.
Agencies differ in how they frame criteria. NSF reviews every proposal on intellectual merit and broader impacts. NIH research grants due on or after January 25, 2025 are reviewed under a simplified framework: importance of the research and rigor and feasibility, each scored, and expertise and resources judged sufficient or not. Program-specific guides for NIH applications, NSF proposals and SBIR proposals go deeper.
The project abstract
The abstract or project summary is the first thing reviewers read and sometimes the only thing agency leadership reads. Write it last and keep it within the stated limit. Cover the problem, who you serve, what you will do, what will change, and over what period. Avoid jargon and acronyms; the abstract is often made public if you are funded.
The statement of need
Establish the problem with evidence, then show why it matters for this program's purpose.
- Lead with recent data from credible sources, such as the Census Bureau, CDC, state agencies or your own records, and cite them.
- Localize it: national figures say the problem exists; local figures say it exists where you work.
- Show the gap: what exists now and why it is not enough.
- End by pointing at your approach, so the reviewer moves from problem to solution without a jump.
Our guide to writing a statement of need has worked examples.
Goals and measurable objectives
One or two goals state the change you want. Objectives make it measurable. A useful test: every objective names how much, for whom, by when, and measured how.
Weak: Improve health outcomes for residents with diabetes.
Stronger (illustrative): By the end of Year 2, 60% of the 300 enrolled adults with type 2 diabetes will reduce their HbA1c by at least one point from baseline, measured through clinic records at intake and every six months.
Reviewers mark down objectives they cannot evaluate. If you cannot collect the data, do not promise the outcome. Our guide to writing SMART objectives for grants covers more patterns.
Methods and work plan
Show how each objective will be achieved: the activities, who does them, when, and with which partners. A work plan table communicates this better than paragraphs:
| Objective | Activity | Lead | Timeline | Output |
|---|---|---|---|---|
| 1 | Recruit and enroll participants through two partner clinics | Program coordinator | Months 1 to 6 | 300 enrolled |
| 1 | Deliver 12-session self-management course | Health educators | Months 3 to 24 | 25 cohorts completed |
Reviewers are judging feasibility: is the plan realistic, is the sequence sensible, and has the applicant thought about risks such as slow recruitment? Name the main risks and your fallback. Where the NOFO asks for evidence-based practices, cite the evidence. A logic model diagram often makes the chain from activities to outcomes clear at a glance, and some agencies require one.
Evaluation plan
Describe what you will measure, how and when you will collect the data, who will analyze it, and how findings will be used to improve the project. Distinguish process measures (did the activities happen as planned) from outcome measures (did they change anything). Name the evaluator, internal or external, and their qualifications. Federal performance reports will draw on these measures later, so promise only what you can report. Our grant evaluation plan guide covers designs and data sources.
Organizational capacity
Reviewers fund applicants they believe can manage public money and deliver. Show:
- Track record with similar work and, ideally, with federal or state awards.
- Key staff and their relevant experience, with time commitments that match the budget.
- Financial management systems that can separate federal funds and track costs by category, as 2 CFR 200 requires.
- Partners, with letters of commitment that say what each partner will actually do.
New organizations can offset a thin track record with experienced staff, strong partners and clear governance.
Budget justification
The budget forms give the numbers; the justification explains them. For each line, show the calculation (for example, 0.5 FTE at $70,000 for 12 months) and connect the cost to an activity the reviewer has already read about. Costs must be allowable, allocable and reasonable under the federal cost principles in 2 CFR 200, and indirect costs must use your negotiated rate or the de minimis rate. The totals must match the SF-424A budget pages to the dollar. Our guide to budget justifications walks through each category.
Two final passes
Compliance. Check every requirement in the NOFO: page limits, font, margins, file names, file types, required attachments and forms, and any sections the notice says must appear in a set order. Some agencies reject non-compliant applications without review, and pages past a limit may simply not be read.
Clarity. Ask someone outside the project to read it cold and explain the approach back to you. Then check that each criterion heading answers its sub-questions directly, that figures and tables are labeled, and that numbers agree across the abstract, narrative, budget and forms.
No proposal can guarantee an award, and federal competitions are demanding. Many funded projects are resubmissions that used reviewer comments to fix a near miss, so keep the score sheet and comments from every attempt.
