Chapter 7: The Executive Summary — Telling Your Story in Two Pages

A foundation program officer sits down with a stack of forty proposals to recommend a handful to the board. She does not read forty proposals cover to cover; no one could. She reads forty executive summaries, and from them she decides which proposals earn a careful, full read and which get a polite decline. For a great many foundation and government applicants, those two pages — the executive summary — are the whole ballgame, exactly as the specific aims page is for the NIH researcher. They are the gateway, and most proposals that fail never make it through.

This chapter teaches you to write that gateway. The executive summary is the foundation and government cousin of the specific aims page you wrote in Chapter 6, and it does the same job in a different dialect: it compresses your entire project into a short, self-contained, persuasive document aimed at a busy, mission-driven reader. We will lay out its structure, build a full annotated example, learn the test that tells you whether it can stand alone, and tailor it to the different readers in the foundation and government worlds. By the end you will draft a complete executive summary for your own project.

If you wrote a specific aims page in Chapter 6 because your funder is the NIH or similar, you may be tempted to skip this chapter. Don't. The two-page compression skill it teaches — and especially the "two-page test" and the tailoring to mission-driven readers — will sharpen any one-page pitch, and most grant writers eventually need both. If your funder wants an executive summary rather than aims, this is your central chapter; read Chapter 6 first anyway, because its discipline underlies everything here.

It is worth naming why the executive summary is, for many readers of this book, even more important than the specific aims page. Far more grant-seekers write for foundations and government programs than for the NIH, and far more dollars flow through proposals that open with an executive summary than through ones that open with specific aims. The nonprofit development director, the program manager, the teacher, the arts administrator, the community organizer — for all of them, the two-page executive summary (or its even-shorter cousin, the letter of inquiry) is the document that determines whether their work gets funded. If you serve any of these worlds, this chapter is not a detour from the "real" aims-page skill; it is the main event. The aims page taught the compression discipline in its most rigorous form; the executive summary applies that discipline to the document you will actually write most often.

7.1 The Executive Summary's Job

🧩 Productive Struggle: Imagine you are a foundation program officer who must cut forty proposals down to eight recommendations, and you have one afternoon. You will not read forty full proposals. What will you read, and what will you need it to tell you to keep a proposal in the running? Write your answer before reading on. Most people arrive at: "I'll read the summaries, and I need each to tell me — fast — what the problem is, what they'll do, whether they can do it, what it'll achieve, and what it costs." That is the executive summary's job, derived from the reader's actual constraint. The structure exists because of that afternoon and that stack.

The executive summary goes by several names — executive summary, project summary, abstract, proposal summary — and appears at the front of a proposal, but do not let "summary" mislead you. It is not a dry précis written last and ignored. It is the single most-read and most-decisive part of a foundation or government proposal, and like the aims page it deserves disproportionate effort and relentless revision.

🚪 Threshold Concept: If a reviewer reads only your executive summary, they should understand the entire project and want to fund it. The summary is not an introduction to the proposal; in the reviewer's experience it often is the proposal — the part they read carefully, decide on, and (if they advance you) summarize to others. Write it so that a busy reader who never turns past page two comes away knowing what you'll do, for whom, why it matters, what it will achieve, and what it costs — and wanting to say yes. Everything else in the proposal exists to support and substantiate the case the summary makes; if the summary doesn't make the case, the support is never read.

This mirrors the aims-page logic from Chapter 6 almost exactly. The reviewer is tired and overloaded (Chapter 2); they form an early impression from the summary and let it frame everything after; most proposals are lost at this gate. The difference is the reader and the register. Where the aims page addresses a peer scientist evaluating rigor and significance, the executive summary often addresses a mission-driven program officer evaluating fit, need, and impact — and it tells more of a story and less of a hypothesis. But the underlying demand is identical: compress the whole project into a short, self-sufficient, persuasive page or two.

💡 Key Insight: The executive summary is frequently the only part of your proposal that some decision-makers read. A foundation program officer may read your full proposal, but the board members who vote on her recommendation may see only the summary (or her summary of it). A government reviewer scoring against a rubric may read everything, but they form their impression from the summary first. In both cases, the summary is doing the same double duty as the aims page: fully persuading those who read nothing else, and framing the read for those who read everything.

There is a brutal arithmetic behind the gateway. A program officer with forty proposals and limited hours cannot give each a full read; the rational move is to triage on the summaries and read fully only the most promising. This means your summary is competing not for funding directly but for attention — for the privilege of having the rest of your careful work actually read. A weak summary does not merely lose points; it causes the thirty-eight excellent pages behind it to go unread entirely. That is why the summary, like the aims page, is the highest-leverage writing in the proposal: it is the bottleneck through which everything else must pass. Pour your best effort here, because here is where most proposals quietly die — not rejected on the merits, but never read closely enough for the merits to matter.

📜 How We Got Here: The executive summary migrated into grant writing from the business world, where busy executives needed the gist of long reports without reading them. The logic is identical: a decision-maker with more to read than time adopts a convention where the opening page or two must stand on its own and carry the decision. As foundations professionalized and application volumes grew through the late twentieth century, the executive summary became the standard front matter precisely because it let overloaded program staff and volunteer boards make decisions efficiently. Understanding this origin explains the threshold concept: the summary exists because the reader may not read further, so it must be written to win on its own.

7.2 The Structure: Need, Project, Organization, Outcomes, Request

A strong executive summary, like a strong aims page, has a structure that answers the reviewer's questions in order (Chapter 2). The classic five moves, flowing as a few tight paragraphs across one to two pages:

1. The need (the hook). Open with the problem — specific, data-driven, urgent, and aligned with the funder's mission. This is the executive summary's version of the aims-page hook, and it has the same job: make a busy reader care, immediately, about a problem that is the funder's business. Lead with a concrete, often quantified statement of need, not generic background. (We develop the full needs argument in Chapter 8; here you state its essence.)

2. The project (the solution). State what you will do about the problem: what the project is, who it serves, where, and over what period. This is the "here is our answer" move. Be concrete — a reader should be able to picture the program or activities — but stay at summary altitude; the details come later in the narrative.

3. The organization (why you). Establish briefly why your organization is the right one to do this — your track record, relevant experience, community relationships, and capacity. This answers the reviewer's "can they pull it off?" The full capacity case comes in Chapter 13; here you plant the credibility in a sentence or two.

4. The outcomes (the payoff). State what the project will achieve, in measurable terms. Not "we will help youth" but "120 middle-schoolers will gain coding skills, and at least 60% will enter high-school tech tracks." Measurable outcomes are increasingly decisive (Chapter 10), and naming them in the summary signals seriousness about results.

5. The request (the ask). State plainly what you are asking for — the amount, and what it will accomplish. Many summaries bury or omit the actual ask, leaving the reader unsure what is even being requested. Name it clearly, and connect it to the outcomes: this amount buys these results.

📋 Template — The executive summary skeleton (1–2 pages): - ¶1 (Need): [Specific, data-driven problem, aligned to the funder's mission, affecting a defined population.] - ¶2 (Project): [What you will do, for whom, where, when — the solution at summary altitude.] - ¶3 (Organization): [Why you are the right entity — track record, capacity, relationships — in brief.] - ¶4 (Outcomes): [Measurable results the project will achieve, with targets.] - ¶5 (Request): [The amount requested and what it will accomplish; a clear close.]

🔍 Why Does This Work?: Why this order — need before project, project before organization, outcomes before the ask? Because it mirrors the reviewer's natural reasoning and the mission-transaction logic from Chapter 1. The reader must care about the problem (their mission) before they can care about your solution; they must believe the solution is sound before they care who delivers it; and they must see the outcomes before the ask makes sense, because the ask is only justified by what it buys. Lead with the organization or the ask, as anxious applicants often do ("We are writing to request \$50,000 for our wonderful organization..."), and you have asked the reader to care about you before you have made them care about the problem — which they will not.

Two of the five moves deserve a second look because they are where summaries most often go soft. The need must do in the summary what the hook does on the aims page: it must be specific and quantified, not a sympathetic generality. "Many local youth lack opportunity" is a sentiment; "fewer than one in ten middle-schoolers in this neighborhood has access to computer-science education" is a fact a reader can act on. The need is also where alignment lives — state the problem in terms the funder's mission already cares about, so the reader's first reaction is "yes, that is our concern." The request, at the other end, must be named and connected: not a vague hope for support but a specific amount tied to specific results ("\$50,000 to reach 90 students across three sites"). A startling number of summaries never actually state the dollar figure, leaving the reader to hunt for it in the budget — a small but real friction that signals carelessness. Name the need with a number, and name the ask with a number tied to outcomes; those two numbers anchor the whole summary.

🔄 Check Your Understanding: An applicant's executive summary opens: "For over twenty years, our award-winning organization has been a trusted leader in youth services, and we are excited to share an opportunity to partner with your foundation." Diagnose the opening and rewrite its first sentence.

Answer

It opens with the organization and self-praise ("award-winning," "trusted leader") rather than the need, asking the reader to admire the applicant before giving them any reason to care about the problem — the "about us" inversion. Rewrite to lead with a specific, mission-relevant need: e.g., "One in three teenagers in [area] reports a mental-health need that goes unmet for lack of accessible services — the gap this project closes." The organization's credibility comes later (move 3), briefly.

7.3 A Worked Example: RYCC's Executive Summary

Here is an executive summary for the Riverside Youth Coding Collective's expansion (composite; figures illustrative), annotated move by move. Read it imagining you are the Hartwell Family Foundation's program officer with thirty-nine other summaries to get through.

¶1 — Need. "In the [neighborhood] community, fewer than one in ten middle-schoolers has access to computer-science education, even as the regional economy adds technology jobs faster than it can fill them. The result is a widening digital-skills gap that forecloses opportunity for exactly the young people the Hartwell Foundation exists to serve." — Annotation: specific, quantified, local, and explicitly tied to the funder's mission in the second sentence. A busy reader knows in two sentences that this matters and that it is their kind of problem.

¶2 — Project. "The Riverside Youth Coding Collective proposes to expand its proven, free, after-school coding program from one school to three, reaching 90 additional middle-schoolers over the next year through twice-weekly classes taught by experienced instructors in partnership with local schools." — Annotation: concrete — what, for whom, where, how much, how long — at summary altitude. The reader can picture it. "Proven" plants the credibility that paragraph 3 will support.

¶3 — Organization. "RYCC has run this program successfully at [school] for four years, with strong attendance, engaged families, and graduates now entering high-school technology tracks. We bring established school partnerships, a tested curriculum, and the staff and systems to manage growth responsibly." — Annotation: answers "can they do it?" with track record and specific evidence of capacity, briefly. Note the smallness is framed as rootedness, not weakness (recall Chapter 2's RYCC framing).

¶4 — Outcomes. "Within the grant year, we expect 90 students to gain demonstrable coding skills (measured by pre/post assessment), 80% to complete the program, and at least half to express intent to pursue further technology coursework — extending a track record that has already moved neighborhood youth onto tech pathways." — Annotation: measurable, with targets and a measurement method — signaling seriousness about results, which foundations increasingly demand. The outcomes connect directly to the need (the digital-skills gap) and the mission (youth opportunity).

¶5 — Request. "We request \$50,000 to fund this expansion — instructors, materials, and coordination across three sites. This investment will turn the Foundation's support directly into measurable opportunity for 90 local young people, and into a model RYCC can sustain and grow." — Annotation: the ask is named plainly, tied to what it buys, and framed as the mission transaction — the Foundation's dollars become youth opportunity. The close looks forward (sustainability), which foundations like.

Read as a whole, the five paragraphs form a complete, self-contained case: a program officer who read only this would understand the project, believe it matters, see that RYCC can do it, know the measurable outcomes, and know exactly what is being asked and what it buys. That self-sufficiency is the test of a strong executive summary — and it is the same test we applied to the aims page in Chapter 6.

Notice a few craft choices in the RYCC example worth stealing. Every paragraph is short — a busy reader can take each in at a glance, and the white space keeps the page from reading as a wall (the same visual discipline as the aims page). Every move ties back to the funder's mission: the need names "exactly the young people the Hartwell Foundation exists to serve," and the request frames the money as "the Foundation's support" becoming "measurable opportunity." Numbers appear in every paragraph that can carry them — fewer than one in ten, 90 students, three sites, 80% completion, \$50,000 — grounding the story in specifics a reader can trust and a board can repeat. And the organization paragraph turns a potential weakness (RYCC is small) into a strength (rooted, proven, ready to grow responsibly). None of these is an accident; each is a deliberate choice to serve the reader. When you draft your own summary, reverse-engineer these moves: short paragraphs, mission ties throughout, a number in every paragraph that can bear one, and your apparent weaknesses reframed as fit.

🗣️ From the Review Panel: When I take a recommendation to my foundation's board, I am working from the executive summary — often I am reading them the executive summary, or my condensed version of it. If the summary gave me a clean arc — here's the need, here's what they'll do, here's why them, here's what it achieves, here's the ask — my recommendation is crisp and the board says yes. If the summary made me assemble the story myself from a muddle, my recommendation is hesitant, and a hesitant recommendation rarely wins a grant. Like the aims page, your executive summary is the script your advocate performs. Hand them a script that makes the project sound inevitable.

The Same Summary, Done Weakly

For contrast, here is the weak version of RYCC's summary — the kind that earns a polite decline. "The Riverside Youth Coding Collective is a nonprofit organization founded in 2022 with a mission to empower youth through technology. We are passionate about coding education and have worked hard to serve our community. We are writing to request funding from the Hartwell Family Foundation to support our important work. Our program teaches kids to code, and we believe it makes a real difference. We would be grateful for your generous support of \$50,000 so we can continue and grow our efforts to help young people."

Diagnose it against the structure. It opens with the organization ("founded in 2022... our mission"), not the need — the reader is asked to care about RYCC before being given any reason to care about the problem. There is no specific, data-driven need at all; the digital-skills gap is never named. The project is vague ("teaches kids to code") with no scope, population, or scale. There are no measurable outcomes — only "makes a real difference" and "help young people." The ask is present but disconnected from any results ("so we can continue and grow our efforts"). And the whole thing leans on emotion ("passionate," "important," "grateful") in place of evidence and specificity. A program officer finishes it knowing RYCC wants \$50,000 for coding and feeling nothing actionable — no urgency, no measurable promise, no clear fit. It is not offensive; it is forgettable, and forgettable loses against thirty-nine other summaries. The strong version in this section contains the same organization and the same request. The difference is structure, specificity, and the discipline of leading with the funder's problem rather than your own worthiness.

7.4 The Two-Page Test

The single most useful check for an executive summary is the two-page test: if the reviewer read only your executive summary and nothing else, would they understand the entire project and want to fund it? If yes, your summary is doing its job. If no — if it raises questions it does not answer, omits the outcomes or the ask, or fails to make the reader care — it is not yet a summary but a teaser, and a teaser that depends on the reader turning the page is a gamble on attention you may not get.

Applying the test means reading your summary as a stranger would. Does the need land in the first sentence, or is it buried under background? Can you state, from the summary alone, what the project will do and for whom? Are the outcomes measurable and present? Is the ask named? Could a board member who reads nothing else vote yes with confidence? Each "no" is a place to revise.

📋 Template — The two-page test checklist: A summary passes when a first-time reader, from the summary alone, can answer all of these: - What is the problem, and why does it matter to this funder? (need + alignment) - What exactly will be done, for whom, where, and when? (project) - Why is this organization able to do it? (capacity) - What measurable results will it achieve? (outcomes) - How much is requested, and what does it buy? (the ask) - Did I come away wanting to fund it? (the persuasion check) If a reader cannot answer any one of these from the summary, that is your next revision.

The two-page test is more demanding than it sounds, because passing it requires completeness and concision at the same time — the summary must contain every essential element yet stay within a page or two. This is exactly the tension that makes the summary hard and valuable: you cannot pass by being thorough (that produces a four-page "summary" that is really a second narrative) or by being brief (that produces a teaser that fails the completeness check). You pass by being dense — every sentence carrying an essential element, nothing padded, nothing missing. When a summary fails the test, the fix is usually not "add more" or "cut more" but "replace filler with substance": find the sentences doing no work (the throat-clearing, the self-praise, the generic background) and replace them with the missing essentials (the quantified need, the measurable outcome, the named ask). The two-page test, in other words, is the "so what?" test from Chapter 5 applied to the highest-stakes two pages in the proposal.

🪞 Learning Check-In: The hardest part of the two-page test is reading your own summary as a stranger, because you know everything that is not on the page and unconsciously fill the gaps. The fix is the same as for the aims page (Chapter 6): give it to an actual stranger — someone outside your organization and your field — and have them answer the checklist questions back to you. Where they cannot, your summary has a gap that you, the insider, literally cannot see. This test is humbling and indispensable.

7.5 Tailoring to Foundation vs. Government Readers

The structure is universal, but the register shifts with the reader. The two great audiences for executive summaries — foundation program officers and government reviewers — want subtly different things, and a summary tuned to one can fall flat with the other (recall the "rooms" from Chapter 2).

Foundation readers are mission-driven and relationship-oriented. They respond to a compelling, human story backed by evidence; to clear alignment with their stated priorities; and to a sense that funding you advances their philanthropic vision. A foundation summary can be a little warmer and more narrative — the need stated with a human face as well as a number, the outcomes tied to the funder's mission language, the close looking toward partnership and sustainability. Foundations also often read the summary as part of an ongoing relationship (Chapter 18), so it should feel like the next step in a conversation, not a cold transaction.

Government reviewers are typically scoring against a published rubric and operating in a compliance-heavy culture (Chapter 2, Chapter 19). They respond to a summary that visibly addresses the program's stated criteria and priorities, uses the program's language, and signals rigor and accountability. A government summary should be tighter, more explicitly tied to the funding announcement's required elements and outcome measures, and scrupulously aligned to the rubric. Warmth matters less; coverage and compliance matter more — the reviewer should be able to check off each required element and see your stated outcome measures, often the program's own performance metrics.

📊 From the Field: The same project, summarized for these two readers, shifts in emphasis. For a family foundation: "In our neighborhood, kids like [composite name] are shut out of the tech economy before they reach high school — a gap the Foundation's youth-opportunity mission exists to close." For a government STEM-education program: "This project addresses [Program]'s priority of expanding computer-science access in underserved schools, serving 90 students across three Title I sites, with outcomes aligned to the program's required performance measures of enrollment, completion, and progression." Same program, same outcomes — but one leads with mission and a human face, the other with rubric alignment and required measures. Reading the funder (Chapters 2–3) tells you which register to write in.

⚠️ Common Pitfall: Writing one generic executive summary and sending it to every funder regardless of type. A warm, narrative foundation summary submitted to a government rubric reviewer reads as vague and non-compliant (where are the required measures?); a tight, rubric-keyed government summary submitted to a family foundation reads as cold and bureaucratic (where is the mission, the story?). The structure stays; the register must be tuned to the reader. This is the executive-summary version of "wearing the funder's clothes" from Chapter 5.

There is a deeper point here about what "outcomes" means to each reader. A foundation often cares about outcomes as evidence the mission is being advanced — did young people gain opportunity? — and will accept a mix of numbers and human story to show it. A government program frequently cares about outcomes as the specific performance measures the program is accountable for reporting to Congress — enrollment, completion, progression — and wants to see your project's outcomes mapped to those measures explicitly. So "name measurable outcomes" means something slightly different in each room: for the foundation, measurable results tied to mission impact; for the government program, your outcomes expressed in the program's own metric framework. Reading the announcement (Chapter 3) tells you which outcome language to speak, and using the funder's own metric vocabulary signals that you understand what they will be held accountable for.

🔄 Check Your Understanding: You have one project and two target funders — a community foundation and a federal education program. Should you write one executive summary or two, and what specifically changes between them?

Answer

Two — same project, two summaries. What changes: the register (the foundation version warmer and more narrative, leading with mission and a human face; the government version tighter and rubric-keyed) and the outcome language (foundation: measurable results tied to mission impact; government: outcomes mapped explicitly to the program's required performance measures, using its vocabulary). The five-part structure stays the same; the clothes change to fit the room.

For government summaries especially, there is a concrete technique that pays off: write the summary against the rubric. If the funding announcement lists scored criteria (need, project design, capacity, evaluation, budget) with weights, ensure your summary touches each criterion in roughly its order and proportion, using the announcement's own terms. A reviewer who will later score the full proposal against that rubric is primed by a summary that previews every criterion — they enter the full read already able to locate each scored element, and they form an early impression that your proposal is complete and compliant. This is the executive-summary application of the "write to the rubric" lesson from Chapter 3: the rubric is the answer key, and a summary that mirrors it tells the reviewer, in the first two pages, that you have answered every question they are required to ask.

7.6 The Letter of Inquiry: The Even-Shorter Cousin

Many foundations do not accept full proposals unsolicited. Instead they require a letter of inquiry (LOI) — a one-to-two-page letter that is, in effect, an executive summary in letter form, whose job is to earn an invitation to submit a full proposal. The LOI is a gate before the gate: most applicants are screened out here, and only the invited write a full proposal.

The good news is that you already know how to write one, because the LOI follows the executive-summary structure — need, project, organization, outcomes, request — compressed into a letter and usually opened with a brief framing of who you are and why you are writing to this funder (ideally referencing a prior conversation or clear alignment with their priorities). We treat the LOI fully in Chapter 18, alongside foundation strategy, because the LOI is where the foundation relationship begins. For now, recognize it as the executive summary's shorter cousin: if you can write a strong two-page summary, you can write a strong two-page LOI, with a warmer, more relational opening and a clear, low-pressure request to be invited to apply.

🔗 Connection: The LOI, the executive summary, and the specific aims page are three sizes of the same skill — compressing a whole project into a short, self-sufficient, persuasive document for a busy reader. Master the compression and you can produce any of them. The differences are register (scientific vs. mission-driven) and length (one page, two pages, a letter), not architecture. Chapter 18 develops the LOI; Chapter 6 the aims page; this chapter the executive summary.

One feature distinguishes the LOI from a pure executive summary, and it points toward the relationship-driven world of Chapter 18: the LOI is often the first contact in a funder relationship, so its tone matters more than its mere content. A strong LOI opens by establishing a connection — a prior conversation, a shared priority, a reason you are writing to this funder specifically — before moving into the need-project-outcomes-ask structure. And it closes not with a hard ask for money but with a soft ask to be invited: "We would welcome the opportunity to submit a full proposal." The LOI's job is not to win the grant; it is to open the door and begin the relationship. That subtle shift in purpose — from closing a sale to starting a conversation — is why the LOI rewards warmth in a way a government executive summary does not, and why we develop it alongside foundation cultivation strategy rather than here.

7.7 The Cover Letter

Distinct from the executive summary is the cover letter — a brief letter that accompanies a proposal. Where the executive summary is part of the proposal and summarizes the project, the cover letter sits outside it and frames the submission: who you are, what you are submitting and to which program, and any administrative notes. For foundations, a warm cover letter from a known contact (or referencing a prior conversation) can prime a friendly read. For NIH, the cover letter serves specific administrative functions (such as requesting an institute assignment or noting a relevant study section — Chapter 16). For many government submissions, a cover letter is optional or unneeded.

Keep cover letters short and purposeful. A good one does three things: identifies the submission clearly, makes a brief, specific connection (to the funder's priorities or a prior conversation), and stays out of the way of the proposal. A cover letter is not a place to re-argue your case — that is the executive summary's job — but it is a low-cost opportunity to frame the read warmly when the funder permits it.

✅ Best Practice: When a funder permits a cover letter and you have any relationship or specific point of alignment, use it — briefly. "Following our conversation at [event], I'm pleased to submit [project] to [program], which aligns with your priority of [X]" does real, cheap work: it signals warmth (Chapter 3), reminds the reader of an existing relationship, and frames the proposal as the next step in a conversation rather than a cold arrival. When you have no relationship and the funder does not invite a cover letter, skip it rather than padding the submission.

One caution on cover letters: never let the cover letter become a second, weaker executive summary. The temptation, especially when you are proud of the project, is to use the cover letter to re-tell the whole story — and the result is redundancy that wastes the reader's time and dilutes the summary's impact. The division of labor is clean: the cover letter frames the submission (who, what, to which program, and any administrative note or relationship reference); the executive summary makes the case. If you find your cover letter restating the need, the outcomes, and the ask, you have duplicated the summary's job — cut the cover letter back to its framing function and let the summary carry the argument. A three-sentence cover letter that does its one job well beats a one-page cover letter that competes with your summary.

7.8 Common Mistakes

Executive summaries fail in recognizable ways, most of them mirrors of the aims-page mistakes from Chapter 6.

• Burying the need. Opening with the organization ("Founded in 1998, we are a leading...") or with generic background instead of a specific, mission-relevant problem. Lead with the need, every time.
• Omitting the ask. Astonishingly common: a summary that never states clearly how much money is requested or what it will accomplish. Name the ask.
• No measurable outcomes. Vague aspirations ("we will improve lives") instead of targets. State what success looks like in numbers.
• Too long, or not self-contained. A summary that runs to four pages, or one that depends on the reader turning to the narrative to make sense — failing the two-page test.
• Wrong register for the reader. A narrative foundation summary sent to a rubric reviewer, or vice versa (Section 7.5).
• All organization, no mission. A summary that is mostly about how wonderful the applicant is rather than how the project advances the funder's mission. (The mission-transaction failure from Chapter 1, in miniature.)

⚠️ Common Pitfall: The "about us" summary. Anxious applicants, wanting to establish credibility, open and dwell on their organization — its history, its awards, its mission statement — before ever naming the problem the funder cares about. This inverts the order that persuades. The reader does not yet care about your organization; they care about their mission and the problem. Earn the right to talk about yourself by first making the reader care about the need your project addresses. Organization comes third, briefly, not first, at length.

Notice, as with the aims page, that the failures share a root: each is a place where the summary serves the applicant's instincts rather than the reader's needs. Leading with the organization serves the applicant's pride; omitting the ask avoids the applicant's discomfort with asking; vague outcomes spare the applicant the risk of committing to a number; emotional language substitutes the applicant's passion for the reader's evidence. The discipline of a strong summary is, over and over, to subordinate what feels natural to write to what the reader actually needs to decide. Write the summary the busy, mission-driven reader needs — specific need first, concrete project, brief credibility, measurable outcomes, clear ask — and you will write against your own anxious instincts, which is precisely why it is hard and precisely why most summaries are weak.

📐 Project Checkpoint — Draft your executive summary: For your project and chosen funder, draft a complete executive summary (one to two pages) using the Section 7.2 skeleton: need (specific, data-driven, mission-aligned), project (what/whom/where/when), organization (why you, briefly), outcomes (measurable, with targets), and request (the amount and what it buys). Then: (1) run the two-page test using the checklist — can a stranger answer all six questions from the summary alone? (2) Tune the register to your funder type (foundation = warmer, mission/story; government = tighter, rubric-keyed). (3) If your funder requires a letter of inquiry instead, adapt this into LOI form (you'll refine it in Chapter 18). Save it in your "My Proposal" document. If you wrote a specific aims page in Chapter 6 instead, you can skip drafting a separate summary — but run your aims page against the two-page test's persuasion check anyway.

Spaced Review

Retrieve these from earlier chapters without looking back.

1. (From Chapter 6) How does the executive summary's structure translate the specific aims page's moves? Map at least three.
2. (From Chapter 2) Why does tailoring the summary's register to a foundation vs. government reader matter, and which "room" concept does this draw on?
3. (From Chapter 5) The executive summary is the load-bearing component from Chapter 5. What must every other component do with respect to it?

Answers

1. Aims-page hook → executive-summary need; central hypothesis → the project/approach; specific aims → key objectives/outcomes; payoff → outcomes + community benefit; (and the alignment in the hook → the mission-aligned need). Same architecture, mission-driven register. 2. Because foundation and government reviewers are in different "rooms" (Chapter 2) wanting different things — mission/story vs. rubric/compliance — so a summary tuned to one can fall flat with the other. 3. The summary makes the promises the rest of the proposal must honor: the need it states, the significance section justifies; the project, the narrative details; the outcomes, the evaluation measures; the request, the budget funds. It is the spine (Chapter 5's "aims drive everything").

Chapter Summary

Key Takeaways

• The executive summary is the foundation/government gateway: the most-read, most-decisive part, and often the only part some decision-makers read. 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: need (specific, data-driven, mission-aligned) → project (what/whom/where/when) → organization (why you, briefly) → outcomes (measurable) → request (the ask, tied to what it buys). The order mirrors the reviewer's reasoning.
• The two-page test: a stranger reading only the summary should be able to answer what/why/who/results/ask — and want to fund it. Test it on an actual stranger.
• Tailor the register: foundations want warmth, story, and mission alignment; government reviewers want tightness, rubric coverage, and required outcome measures. Same structure, different clothes.
• The letter of inquiry is the even-shorter cousin (Chapter 18); the cover letter frames the submission warmly but does not re-argue the case.
• Common failures mirror the aims page: burying the need, omitting the ask, no measurable outcomes, the wrong register, and the "about us" summary.

Action Items

• Draft your executive summary (Project Checkpoint).
• Run the two-page test on a stranger.
• Tune the register to your funder type; draft an LOI version if required.

Common Mistakes to Avoid

• Leading with your organization instead of the need.
• Omitting the ask or the measurable outcomes.
• One generic summary for every funder regardless of type.

Decision Framework: Is your executive summary ready?

Ask: (1) Does the need land in the first sentence, tied to the funder's mission? (2) Is the project concrete (what/whom/where/when)? (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.

Looking Ahead

Your one-page pitch — aims page or executive summary — states a need; the next chapter proves it. Chapter 8: The Needs Assessment / Significance Section teaches you to build the evidence-based argument that the problem is real, urgent, and important: the "so what?" chain from problem to consequence to cost to insufficiency of current approaches, the data sources that make a need credible, the gap analysis, and the honest use of statistics. The need you asserted in two sentences here becomes, in Chapter 8, a rigorous case a skeptical reviewer will believe.

This is the pattern for the rest of Part II: each component chapter takes one of the promises your one-page pitch made and builds it into a full, evidence-backed section. The summary said the problem matters — Chapter 8 proves it. The summary said you have a sound plan — Chapter 9 details it. The summary named measurable outcomes — Chapter 10 designs the evaluation that delivers them. The summary implied a cost — Chapters 11 and 12 build and justify the budget. The summary claimed you can do it — Chapter 13 establishes the capacity. Your aims page or executive summary is the table of contents for your own proposal, and the promises it makes are the work the rest of the proposal must do. Keep it in front of you as you write each component; every section should be redeemable to a promise on that first page.

Continue to the Exercises, the Quiz, and the two Case Studies (1, 2). The Key Takeaways card is your quick-review anchor.

Next: Chapter 8 — The Needs Assessment / Significance Section: Proving the Problem Is Real and Urgent.