Key Takeaways — Chapter 7: The Executive Summary
-
The executive summary is the foundation/government gateway. Busy reviewers triage on summaries and read fully only the most promising; a weak summary causes your careful proposal to go unread. It deserves disproportionate effort, like the aims page.
-
If a reviewer reads only the summary, they should understand the project and want to fund it (threshold concept). It is the proposal compressed, not an introduction to it.
-
Structure (five moves): need (specific, data-driven, mission-aligned) → project (what/whom/where/when) → organization (why you, briefly) → outcomes (measurable, with targets) → request (the ask, tied to what it buys). The order mirrors the reviewer's reasoning; never lead with your organization or the ask.
-
The two-page test: a stranger reading only the summary should answer what/why/who/results/ask and want to fund it. It demands completeness and concision — be dense, not thorough-or-brief. Test it on an actual stranger.
-
Tune the register to the reader (the "rooms" from Ch 2). Foundations: warmer, narrative, mission and a human face, outcomes as mission impact. Government: tighter, rubric-keyed, the program's own performance-measure vocabulary. Same structure, different clothes — write two versions for two funder types.
-
Put a number in every paragraph that can carry one (quantified need, targeted outcomes, named ask), and reframe apparent weaknesses (e.g., being small) as fit (rooted, proven).
-
The letter of inquiry is the even-shorter, warmer cousin — first contact in a foundation relationship, closing with a soft request to be invited (Chapter 18). The cover letter frames the submission but does not re-argue the case.
-
Your one-page pitch is your proposal's table of contents. Each later component redeems a promise it made: significance proves the need, the narrative details the project, the evaluation measures the outcomes, the budget funds the ask, capacity establishes you can deliver.
Common Mistakes
- Leading with the organization instead of the need ("about us" summary).
- Omitting the dollar amount or the measurable outcomes.
- One generic summary for every funder regardless of type.
- A cover letter that becomes a second, weaker summary.
Decision Framework — Is your executive summary ready?
(1) Does the need land first, tied to the funder's mission? (2) Is the project concrete? (3) Is the ask named and tied to measurable outcomes? (4) Does it pass the two-page test with a stranger? (5) Is the register right for this funder? Any "no" is your next revision.
Your Project
You should now have a complete executive summary (or refined aims page) that passes the two-page test, with the register tuned to your funder — and, if needed, an LOI version. It is the spine the rest of Part II builds on.