A strong nonprofit grant proposal tells a funder exactly what problem you’ll solve, how you’ll solve it, what it will cost, and how you’ll prove it worked. While every funder has its own application format, nearly all proposals share the same core sections: an executive summary, a statement of need, a project description, a budget, and an evaluation plan. Getting each of these right, and having your supporting documents ready before you start writing, is what separates funded proposals from rejected ones.
Gather Your Documents First
Before you write a single sentence, assemble the paperwork that most funders will require alongside your narrative. Missing a document can disqualify your application outright, and tracking these down mid-draft slows the whole process. At minimum, you’ll typically need your IRS 501(c)(3) determination letter, your most recent IRS Form 990 filing, audited or reviewed financial statements, a list of board members with their affiliations and contact information, and your organization’s annual report or a summary of recent activities.
Federal grants have additional requirements. You’ll need a Unique Entity Identifier (UEI), an active registration on SAM.gov (which can take several weeks to process if you’re registering for the first time), and potentially an indirect cost rate agreement. State grants often require proof of good standing and letters of support from community partners. Foundation grants tend to be less paperwork-heavy but may ask for a strategic plan or logic model. Check the funder’s guidelines early so you know exactly what’s expected.
Write a Focused Executive Summary
The executive summary (sometimes called a project summary) is a one-page overview of your entire proposal. Many reviewers read dozens of proposals in a sitting, and the summary is often what determines whether they engage deeply with yours or skim through it. Write it last, after you’ve finished every other section, so it accurately reflects the final version of your project.
In roughly three to four paragraphs, cover who you are, the problem you’re addressing, what you plan to do about it, how much it will cost, and what success looks like. Be specific. Instead of “We will serve underserved youth,” write “We will provide after-school tutoring to 200 middle school students in low-income neighborhoods, with the goal of improving math proficiency scores by 15% within one academic year.” Concrete numbers give reviewers something to evaluate and remember.
Build a Compelling Statement of Need
The statement of need (also called a needs assessment or problem statement) makes the case that the issue you’re tackling is real, urgent, and worth funding. This section answers one question for the reviewer: why does this matter?
Ground your argument in data. Use census figures, public health statistics, school district reports, or community surveys to show the scope of the problem. Then narrow the lens to your specific community or population. National statistics establish context, but local data shows the funder that you understand the people you intend to serve. If 12% of households in your service area are food insecure compared to 8% nationally, that contrast tells a clear story.
Avoid making the statement of need about your organization. This section is about the community, not about your budget shortfall or operational challenges. Funders want to invest in solving problems, not in sustaining organizations. Frame the need from the perspective of the people who will benefit.
Describe Your Project in Detail
The project description is the heart of your proposal. It explains what you will do, how you will do it, and why your approach will work. Think of it as answering five questions in sequence: What activities will you carry out? Who will carry them out? Where and when will the work happen? What resources do you need? And why is this approach more likely to succeed than alternatives?
Break the project into clear phases or components. If you’re proposing a job training program, for example, describe the recruitment process, the curriculum, the training schedule, any wraparound services like transportation or childcare, and the job placement support that follows. Reviewers need to see that you’ve thought through the logistics, not just the vision.
Include a realistic timeline. A simple table or list showing major milestones by month or quarter helps reviewers see that your plan is feasible within the grant period. One of the most common reasons proposals are rejected is that reviewers have concerns about feasibility, so be honest about what you can accomplish in the time and budget you’re requesting.
If your organization has successfully run similar programs before, say so here. Past performance is one of the strongest arguments you can make. Include specific results: “Our 2023 pilot served 85 participants, and 72% secured employment within 90 days of completing the program.”
Create a Realistic Budget
Your budget translates your project description into dollars. Every activity you described in the narrative should have a corresponding line item, and every line item should trace back to something in the narrative. Reviewers look for this alignment closely, and a mismatch between what you say you’ll do and what you’re budgeting for raises red flags.
Most budgets are organized into two categories. Direct costs are expenses tied specifically to the project: staff salaries and benefits for people working on the grant, supplies and materials, travel, equipment, consultant fees, and any other costs you can attribute directly to the proposed work. List each person by role with their base salary and the percentage of time they’ll dedicate to the project. For equipment, note anything with an acquisition cost of $5,000 or more separately, as funders often have specific rules about equipment purchases.
Indirect costs (sometimes called facilities and administrative costs) cover expenses that support the project but aren’t exclusive to it: rent, utilities, general office supplies, IT support, and administrative staff time. Many funders cap indirect costs at a set percentage of direct costs, often between 10% and 25% for foundation grants. Federal funders may accept a negotiated indirect cost rate that your organization has established. If you don’t have one, some federal programs allow a de minimis rate of 10%.
Accompany the budget with a brief narrative justification explaining why each cost is necessary. Don’t just list “$4,000 for travel.” Write “$4,000 for travel: two staff members attending four regional partner meetings at an estimated $500 per trip, covering mileage, lodging, and meals.” This level of detail shows funders you’ve done the math, not just estimated a round number.
Define How You’ll Measure Success
The evaluation plan tells funders how you’ll know whether your project worked. This is where many proposals fall short, either by being too vague (“we will track participant satisfaction”) or by promising measurements they don’t have the capacity to collect.
Start by distinguishing between outputs and outcomes. Outputs are the direct products of your activities: the number of workshops held, meals served, or students enrolled. Outcomes are the changes those activities produce: improved test scores, reduced hunger, or higher employment rates. Funders care about both, but outcomes carry more weight because they demonstrate impact rather than just activity.
For each outcome, specify what you’ll measure, how you’ll measure it, and when. If your program aims to reduce school absenteeism, explain that you’ll collect attendance records from partnering schools at baseline, at the midpoint, and at the end of the program year. If you’re measuring something harder to quantify, like confidence or community engagement, describe the survey instrument or assessment tool you’ll use. Reviewers want to see that you’ve thought carefully about measurement, especially for outcomes where multiple approaches are possible.
Be honest about what your evaluation can and can’t tell you. A small program serving 50 people probably can’t demonstrate community-wide change, but it can show meaningful individual-level results. Matching your evaluation claims to your project’s actual scale builds credibility.
Align With the Funder’s Priorities
Misalignment with funding priorities is one of the most common reasons proposals are rejected. Before you begin writing, read the funder’s guidelines, mission statement, and any published strategic priorities carefully. Look at what they’ve funded in the past. Many foundations publish lists of recent grantees on their websites, giving you a clear picture of the types of projects and organizations they support.
Tailor your language to reflect the funder’s stated goals. If a foundation emphasizes “community-driven solutions,” make sure your proposal highlights how community members shaped your program design. If a federal agency’s funding announcement prioritizes “evidence-based interventions,” cite the research supporting your approach. This isn’t about being disingenuous. It’s about showing reviewers that you’ve read their priorities and that your project genuinely fits.
Many funders also require or welcome a letter of intent before the full proposal. This is a brief one-to-two-page document summarizing your project concept. Submitting a strong letter of intent gives you an early signal about whether your project aligns with the funder’s interests, saving you weeks of work if it doesn’t.
Polish and Submit
Give yourself at least two weeks between finishing your draft and the submission deadline. Use that time to have someone outside the project read the proposal. A fresh pair of eyes catches jargon, logical gaps, and unclear passages that you’ve become blind to after weeks of drafting. Ideally, ask someone unfamiliar with your program to read the project description and tell you, in their own words, what they think you’re proposing. If their summary doesn’t match your intent, revise.
Check every number in your budget. Make sure line items add up correctly, that the budget total matches the amount stated in your executive summary, and that your indirect cost rate falls within the funder’s limits. Arithmetic errors signal carelessness, and reviewers notice.
Follow formatting instructions precisely. If the funder specifies 12-point font, one-inch margins, and a 10-page limit, those aren’t suggestions. Many online submission portals will reject uploads that exceed page limits, and reviewers are instructed to stop reading at the cutoff even when submissions arrive by mail. Attach all required documents in the order specified, label files according to any naming conventions provided, and submit at least a day early to account for technical problems with upload systems.