Grant Writing Basics: Your First Foundation Application

Every grant proposal answers the same underlying question a funder is asking, whether they say it directly or not: "Why should I invest in this organization over the many others competing for these limited funds?"

Answering that well requires being specific, compelling, and honest. Generic proposals that could describe any organization working in your issue area get rejected, because they give the funder no reason to pick you specifically. Proposals tailored to the funder's stated priorities and grounded in real organizational specificity (actual numbers, actual names, actual outcomes) are what get funded.

Consider two versions of the same claim. The generic version reads: "Our organization is committed to helping children succeed through education, and we have a strong track record." The specific version reads: "In the 2025 to 2026 school year, Second Chance Youth Center served 118 students in grades 3 through 8 at three Title I elementary schools in East Cleveland, and 79 percent of regularly attending students improved at least one reading level by the spring assessment." A program officer reading fifteen proposals in an afternoon will remember the second sentence. The first one could have been written by any of the other fourteen applicants, and reviewers can tell.

Why this framing matters in practice: thinking of a grant application as asking for help leads to vague, hopeful writing that leans on good intentions. Thinking of it as making a case for investment leads to writing that gives the funder exactly what they need in order to say yes: evidence that the problem is real, a specific plan for addressing it, and a credible way to hold the organization accountable for results.

The single most useful thing an applicant can do before writing anything is understand the funder thoroughly, and that means going well past skimming their website.

Start with their stated priorities. Read the funder's website, their most recent annual report, and the actual grant guidelines closely, not skimmed, because guidelines often specify eligibility rules and preferred approaches that a quick scan will miss entirely. Next, look at what they actually funded last year. Most foundations publish a grantee list, sometimes with grant amounts attached. Look specifically for organizations similar in size, issue area, and stage of growth, because a funder's real priorities show up in who they actually wrote checks to, not just in their mission statement. Pay attention to grant size too: most funders make grants within a fairly consistent range, and asking for far more or far less than their typical amount signals that the applicant did not do the homework.

If a pre-application call is offered, take it. A short conversation with a program officer before submitting is one of the most effective things an applicant can do. It lets the applicant tailor the proposal to the funder's real current interests rather than guessing, and it signals to the program officer that this is a serious, prepared applicant rather than someone mass-applying to a long list of foundations without reading any of them closely.

Only apply if the work genuinely fits the funder's priorities. A nonprofit running a job training program that applies to a foundation focused exclusively on environmental conservation is not going to get funded no matter how well the proposal is written, and the wasted writing time is only part of the cost. Program officers remember applicants who clearly did not read the guidelines, and that memory can follow an organization into future cycles even when its actual work would have been a good fit for a different program at the same foundation.

Every funder has their own format, but most applications ask for some version of these seven components. Understanding why each one exists helps in writing it well, not just filling in the blank, and it also explains why reviewers weigh some sections more heavily than others.

1. Executive summary (one paragraph to one page). Often the only section some reviewers read closely before deciding whether to keep reading the rest. Cover who the organization is, what it does, who it serves, what outcomes it achieves, how much is being requested, and what the funds will accomplish. This section earns the reviewer's full attention for everything that follows it, so it should never be written last in a rush. Draft it early, then revise it again after the rest of the proposal is finished, since only then is it clear which specific facts are strong enough to lead with.

2. Organizational background (one to two pages). The organization's history, mission, programs, and key accomplishments. A newer organization without years of track record to point to should lean on its leadership team's relevant experience instead: a founder who ran a similar program at a larger organization for six years is a real credential, and naming that directly is more persuasive than describing the new organization's mission in the abstract. Funders reading this section are assessing execution risk: can this specific team actually deliver what the proposal promises, given who they are and what they have done before.

3. Statement of need (one to two pages). Why this problem matters, and why this particular community needs this particular work. Local data is far more compelling than national statistics here, because it proves the applicant understands the specific gap being filled rather than reciting the general cause. A proposal that opens with "childhood hunger affects one in six children nationally" is weaker than one that opens with "340 students at Lincoln Elementary qualify for free lunch, and the school's only weekend food program currently reaches 60 of them." Describe the beneficiaries' need for services, not the organization's need for funding: those are different arguments, and experienced reviewers can tell within a paragraph which one is actually being made.

4. Program description (two to three pages). What will actually happen with the funds: specific activities and how they are delivered, who delivers them and what qualifies them to (credentials and relevant experience matter here), a timeline, expected participant numbers, and how participants are recruited and selected. Specificity matters more in this section than in any other, because vagueness is the single most common reason funders cite for rejecting an otherwise sympathetic proposal. "We will provide tutoring support" describes nothing a reviewer can evaluate. "Two certified teachers will deliver twice weekly, ninety minute small group tutoring sessions to 40 students in grades 6 through 8, recruited through teacher referral and confirmed by a reading assessment" describes a program a reviewer can actually judge.

5. Evaluation plan (about one page). How the organization will know whether the program worked: specific outcome metrics, how the data will be collected, who is responsible for collecting it, and how results will be reported back to the funder. See the companion lesson on impact measurement for how to build this properly, since a thin evaluation plan is a common weak point even in otherwise strong proposals.

6. Budget (one to two pages). A line item budget for the grant period covering personnel (position, percent of time on this grant, salary, and benefits), non-personnel direct costs, and indirect costs, sometimes called overhead. Most funders allow an indirect cost rate somewhere in the 10 to 20 percent range, and the federal de minimis indirect rate that agencies must accept without further justification currently sits at 15 percent of modified total direct costs. Always include an indirect rate. Leaving it out does not make an organization look lean or efficient. It quietly starves the organization of the money it actually needs to run the program well, since real costs like rent, accounting, and shared administrative staff time do not disappear just because they were not budgeted.

7. Organizational budget. The full annual budget, usually requested as a separate attachment, showing all revenue and expenses. This lets the funder see the requested grant in the context of the organization's whole operation, including how dependent it already is on a small number of funding sources.

Foundation grants are not the only source worth understanding. Many nonprofits also apply for grants from state agencies, county governments, or city departments, and these come with requirements that foundation grants usually do not. Government grant applications tend to be longer, follow a rigid required format down to font size and page margins, and often require formal registration with a state agency before an organization is even eligible to apply, not just before receiving funds.

The registration requirement catches first time applicants off guard more than almost any other part of the process, because it can take weeks to complete and has nothing to do with how good the proposal itself is. Building in time for this step before a government grant deadline, not after deciding to apply, is one of the more overlooked pieces of practical planning in this whole process.

The patterns below repeat across almost every funder in almost every issue area, which is what makes them worth internalizing rather than treating as one time feedback on a single rejected proposal.

If funded, send a thank you promptly, meet every single reporting deadline without exception, and keep building the relationship over the life of the grant. Foundations preferentially renew grants to organizations they already trust and who make their job easy, and a program officer who does not have to chase down a late report is far more likely to advocate for a renewal internally than one who does.

If rejected, ask for feedback. Many program officers will explain why an application was not selected if asked directly and politely, and that input is some of the highest quality free consulting available anywhere in this field. Apply again next cycle if the work still fits the funder's priorities: a no this year is often just not this round, especially at foundations with more strong applicants than they have funds to support.

Set expectations correctly going in. Most community foundation grant pools are oversubscribed three to one or more, so even excellent, well aligned proposals get rejected regularly, and that is not a sign the proposal was written poorly. A roughly 30 percent acceptance rate on genuinely strong proposals is considered good in this field. Treat each rejection as data about how to improve the next application rather than as a verdict on the organization's worth, and keep a simple log of which funders gave feedback and what they said, since that record becomes genuinely valuable after a few grant cycles.