The short version
An executive summary is a half-page to one-page overview of your entire proposal: who you are, the need, what you will do, the results you expect, and exactly how much you are requesting. Write it last, put it first, and make it able to stand alone, because it is often the only section every decision-maker reads.
The executive summary is the most-read part of most proposals. A program officer reads it to decide how carefully to read the rest. A board or grants committee approving a docket may read little else. In a federal application, the project abstract is often what reviewers read first, and some agencies make abstracts of funded projects public.
That makes it the highest-leverage half page you will write. It needs to be clear, specific, and complete enough to stand on its own.
What an executive summary must do
A good summary answers six questions in a few short paragraphs. Candid's proposal guidance lists the core contents as the problem or need, a brief description of the project with its goals and objectives, information about the organization's experience with the need, and the amount requested. Practitioners add a sixth element: the results you expect.
| Question | What to include | Typical length |
|---|---|---|
| Who are you? | Legal name, location, mission in one line, years of relevant work | 1–2 sentences |
| What is the need? | One or two of your strongest local data points, and who is affected | 2–3 sentences |
| What will you do? | The project's name, core activities, who and how many you will serve, where, and over what period | 2–4 sentences |
| What will change? | Your one to three most important measurable outcomes | 1–3 sentences |
| Why you? | One proof point of capacity: results, expertise, partnerships | 1–2 sentences |
| What are you asking for? | Exact amount, grant period, and what it pays for; total project cost if different | 1–2 sentences |
Executive summary vs. project abstract vs. cover letter
These three are easy to confuse. They overlap but do different jobs.
| Executive summary | Federal project abstract | Cover letter | |
|---|---|---|---|
| Purpose | Persuasive overview of the whole proposal | Neutral, descriptive overview for reviewers and the public | Formal introduction and signal of organizational commitment |
| Where it goes | First page of the proposal | A dedicated form or attachment (often the Project Abstract Summary form in Grants.gov packages) | Separate letter on letterhead |
| Voice | "We will..." | Often third person or neutral; plain language | Signed by the ED or board chair |
| Length | ½–1 page | Set by the NOFO or form | 1 page |
| May be published? | No | Some agencies publish abstracts of funded projects (NIH does, through RePORTER) | No |
HHS lists the Project Abstract Summary among the standard forms in its application packages. Each NOFO's Application Contents and Format section states the abstract's content and limits, and 2 CFR Part 200, Appendix I requires agencies to spell out page limits and formatting rules there. Read that section before drafting, because some programs require specific elements in the abstract, such as the number of people to be served or the geographic area.
For the cover letter, see how to write a grant cover letter.
A fill-in structure you can adapt
Use this as a starting skeleton, then rewrite in your own voice. Each bracket corresponds to a section of your full proposal.
A full worked example
That example runs about 220 words. Notice what it does not include: organizational history beyond one clause, a list of every activity, or adjectives like "innovative" and "comprehensive." Every sentence carries a fact.
How to write it, step by step
- Finish the rest of the proposal first. Lock the objectives, participant numbers, timeline, and budget total.
- Pull one sentence from each major section. Copy your strongest sentence from the need statement, program design, objectives, capacity, and budget into a blank document.
- Rewrite for flow. Turn those fragments into four short paragraphs using the structure above.
- Match the funder's language. If the funder's priority is "kindergarten readiness" or "economic mobility," use those exact words where they truthfully apply.
- Cut every adjective you can. Replace "a highly successful, innovative program" with the result that proves it.
- Check every number against the full proposal. The amount, participant count, dates, and outcomes must match exactly.
- Test it cold. Give it to someone who knows nothing about the project. Ask them to explain back what you will do, for whom, and for how much. If they cannot, revise.
Common mistakes
- Opening with history. "Founded in 1987 by a group of concerned parents..." delays the point. Lead with the request and purpose; history belongs in organizational capacity.
- Leaving out the amount. This is the most common omission and the most frustrating for readers.
- Describing activities without outcomes. "We will provide tutoring" says what you will do, not what will change. Include at least one measurable outcome. See goals and objectives.
- Using national statistics only. One sharp local figure beats three national ones. See the statement of need guide for local data sources.
- Numbers that don't match. The summary says 150 students; the program design says 120. Reviewers notice, and it makes the whole proposal look careless.
- Exceeding the limit. If the abstract form or NOFO sets a limit, a summary that runs over may be truncated or flagged as noncompliant.
- Copying the same summary across funders. The core facts can stay, but the framing should connect to each funder's priorities.
Before and after: rewriting a weak summary
Most weak summaries share the same problems: they open with history, describe activities in general terms, and leave the reader to guess the amount and results.
The "before" version runs more than 60 words yet contains no facts a reviewer could act on: no amount, no number served, no place, no measurable result. The "after" version is barely longer and answers every question a program officer would ask.
Tailoring the summary for different readers
The core facts in your summary should not change from one funder to the next, but the emphasis should.
| Funder type | What to foreground |
|---|---|
| Community foundation | Local need, local partners, and benefit to the specific geography it serves |
| Private foundation with a narrow focus | The direct link to its stated priority, using its language |
| Corporate funder | Community benefit in its operating area; any employee volunteer or partnership angle |
| Federal agency | The NOFO's required abstract elements, in the order listed, in plain, neutral language |
| Capacity-building funder | How the grant strengthens the organization and leads to better program results |
Executive summaries in online portals
Many foundation portals ask for a "project summary" or "brief description" with a character limit, sometimes as low as 500 or 1,000 characters. For those:
- Lead with the ask and purpose in one sentence.
- Keep one need data point, the core activity, and the primary outcome.
- Drop capacity and sustainability; other portal questions usually cover them.
- Count characters including spaces before pasting.
Final check
Before you submit, confirm the summary:
- States the organization, amount, period, and purpose in the first paragraph
- Includes at least one sourced local need data point
- Names the number of people served and where
- Includes at least one measurable outcome with a date
- Matches every number in the full proposal and budget
- Fits the funder's length limit and uses the funder's terminology
Then run the full proposal review checklist. For how the summary fits with every other section, see the anatomy of a grant proposal.
Common questions
How long should a grant executive summary be?
Follow the funder's limit first. Without one, aim for half a page to one page, roughly 250 to 400 words. Federal project abstracts are usually limited by the notice of funding opportunity or the abstract form itself. Shorter is usually better, as long as you include the need, the project, the expected results, your qualifications, and the dollar amount.
Should I write the executive summary first or last?
Write it last. The summary condenses decisions you make while writing the rest of the proposal: the final participant numbers, objectives, budget total, and timeline. Drafting it first almost always means rewriting it, and summaries written early tend to drift out of sync with the final proposal.
Is an executive summary the same as a project abstract?
They serve the same purpose but differ in tone and use. A foundation executive summary is persuasive and usually written in first person plural. A federal project abstract is more neutral and descriptive. Some agencies publish abstracts of funded projects (NIH, for example, shares the project summary of awarded grants through its RePORTER database), so avoid confidential details and write it so the public can understand it.
Do I need an executive summary if the funder doesn't ask for one?
For a full proposal of several pages, yes, unless the funder's format clearly has no place for it. A short summary at the top helps every reader. For a two-page letter proposal or a portal with fixed questions, the opening paragraph does the same job, so write that paragraph as if it were the summary.
Sources
We check facts against primary sources wherever possible. Rules and programs change, so confirm details with the funder or agency before you apply.
- How to write a grant proposal — Candid
- Applying for an award — health.gov (HHS Office of Disease Prevention and Health Promotion)
- SF-424 Family forms repository — Grants.gov
- Will NIH share my grant application's abstract publicly? — NIAID
- 2 CFR Part 200, Appendix I — Full Text of Notice of Funding Opportunity — eCFR
Spotted something out of date? Send a correction.