Appendix E: Annotated Sample Proposals

Seeing the principles on the page is worth more than any amount of advice about them. This appendix presents annotated excerpts from two proposals that recur throughout the book — a small nonprofit's foundation proposal and a research specific-aims page — with running annotations (marked ▸) that point out what each move does and why, cross-referenced to the chapters.

These are composite, illustrative examples. The organizations, people, and projects are composites created for teaching — Riverside Youth Coding Collective (RYCC) and the diabetes-adherence study among them — not real applicants. The funder facts referenced (NIH mechanisms and review criteria, foundation practices, the structures of each document) are real and verifiable; the applicants are not. Study the moves, not the specifics. Your own content, funder, and project are yours to supply (Appendix A).

E.1 A Foundation Proposal Excerpt (RYCC — annotated)

Context. Riverside Youth Coding Collective (RYCC) is a small nonprofit seeking $50,000 from the (composite) Hartwell Family Foundation to teach coding to 90 students across 3 sites over a 30-week program. A foundation proposal is shorter and more relationship-driven than a federal one (Chapter 18); coherence and a clear, evidenced story matter most (Chapter 5). The excerpt below shows the opening of the narrative.

The problem and the opportunity. In Riverside's east-side neighborhoods, fewer than one in ten high-school students has access to a computer-science course, even as regional demand for technology skills grows. The young people are here, and they are capable; the pathway is missing. Riverside Youth Coding Collective exists to build that pathway.

▸ The opening states a specific, local, evidenced problem (Chapter 8) and immediately reframes it as opportunity — asset-based, not deficit-based (Chapter 25). "The young people are here, and they are capable" names the community's strength before the barrier. Note the concrete framing ("fewer than one in ten") over a vague claim. The last sentence ties the problem directly to the organization's mission — fit, made explicit (Chapter 3).

What we propose. With $50,000 over one year, RYCC will deliver a 30-week coding program to 90 students across three east-side sites — two high schools and one community center — building on the model we piloted last year with 22 students, of whom 19 completed and 14 enrolled in a follow-on course.

▸ The ask, the scope, and the numbers are concrete and specific (Chapters 6, 11) — the reader knows exactly what $50,000 buys. The pilot data is preliminary evidence of feasibility placed exactly where a skeptical reader's doubt arises (Chapter 9): "can they actually do this?" The completion and follow-on numbers answer it before it's asked.

Why RYCC. Our instructors are working software developers from the Riverside tech community who teach because they grew up here. We are small, but we are embedded — we know these students, these schools, and these families, and they know us. Last year's pilot retention rate of 86% reflects that trust.

▸ Capacity framed as fit-for-this-project, not generic credentials (Chapter 13). The competitive advantage of a small, embedded organization is named as a strength rather than apologized for. The retention figure ties the capacity claim to evidence — a claim plus its proof (Chapter 13).

What success looks like. By the program's end, we will have served 90 students; we expect at least 75 to complete (based on our pilot) and at least 45 to pursue further computer-science learning. We will track completion, a pre/post skills assessment, and follow-on enrollment, and we will share results with the Foundation and our school partners.

▸ Outcomes, not just outputs (Chapter 10): "serve 90" is an output; "45 pursue further learning" is an outcome — a change in the world. Targets are specific and justified by the pilot (not pulled from air). The measurement method and the commitment to share results show evaluation thinking and stewardship (Chapters 10, 26). "Share results with the Foundation" signals relationship, which foundations value (Chapter 18).

Sustaining the work. This grant launches a program we intend to sustain: we are pursuing a parallel corporate-sponsorship track with two Riverside employers, and the curriculum and instructor network this grant builds become permanent assets, reusable each year at a fraction of the start-up cost.

▸ Sustainability matched honestly to the project (Chapter 14): not a vague promise of "future funding" but a specific, plausible plan (diversified funding + reusable assets). Foundations fund launches more readily when they can see the work won't collapse when their grant ends.

What makes this excerpt work (summary). It is coherent — problem, proposal, capacity, outcomes, and sustainability all point at the same goal (Chapter 5). It is specific and evidenced — every claim has a number or a proof. It is asset-based and relational — fitting both the community and the foundation. And it is honest — the pilot was small, and the proposal says so, turning modest scale into credible feasibility.

E.2 A Research Specific-Aims Page (NIH R01 — annotated)

Context. This is the opening of a (composite) NIH R01 specific-aims page — the single most important page in an NIH application (Chapters 6, 16). The project: a randomized controlled trial testing whether a text-message intervention improves medication adherence in adults with type 2 diabetes. NIH reviews applications on Significance, Investigator(s), Innovation, Approach, and Environment (verify current criteria); the aims page must make all five visible in one page. Annotations show the standard structure (Chapter 6).

[Opening — the problem and its importance.] More than one in three adults with type 2 diabetes does not take medication as prescribed, a primary driver of avoidable complications, hospitalizations, and cost. Despite decades of adherence research, scalable, low-cost interventions that work in real-world primary care remain scarce.

▸ The hook establishes an important problem with magnitude and consequence (Chapter 8) in two sentences, then names the gap: not "we don't know about adherence," but specifically "scalable, low-cost, real-world interventions are scarce." A precise gap is more fundable than a vague one (Chapter 6).

[The gap and the opportunity.] Text-message interventions are inexpensive and scalable, and pilot studies suggest they can improve adherence — but prior trials have been small, short, and rarely tested against the practical realities of primary-care delivery. A rigorous, adequately powered trial in a real-world setting is needed to establish whether this approach works at scale.

▸ The gap is sharpened into the specific opportunity this project seizes. Note the honest crediting of prior work ("pilot studies suggest") before naming its limits ("small, short") — respectful and credible (Chapters 8, 9). This sets up why this project, now.

[Central hypothesis and approach.] Our central hypothesis is that a tailored, two-way text-message intervention will improve medication adherence relative to usual care. We will test this in a randomized controlled trial of 400 adults with type 2 diabetes across four primary-care clinics, building on our team's pilot (n=48) showing a 14-percentage-point adherence improvement and strong patient engagement.

▸ A clear, testable hypothesis (Chapter 6) followed immediately by the design and the preliminary data that make it credible (Chapter 9). The pilot — sample size and a concrete effect — pre-empts the reviewer's feasibility doubt and speaks to Investigator and Approach at once. The trial's scale (400, four clinics) signals rigor and adequate power (Chapter 16).

Aim 1. Test the effect of the intervention on medication adherence. In a two-arm RCT (n=400), we will compare the text-message intervention to usual care, with adherence measured at 6 and 12 months. Hypothesis: the intervention arm will show significantly higher adherence.

Aim 2. Test the effect on clinical outcomes. We will compare HbA1c and other clinical indicators between arms. Hypothesis: improved adherence will translate into improved glycemic control.

Aim 3. Identify mechanisms and moderators. We will examine for whom and through what pathways the intervention works, to inform scale-up and tailoring.

▸ Three aims, each independent and each delivering part of the goal (Chapter 6) — a reviewer who doubts Aim 2 can still value Aims 1 and 3. The aims escalate in ambition (does it work → does it matter clinically → why and for whom), which is a strong structure. Each carries its own hypothesis. Crucially, the aims are not sequentially dependent in a way that makes the whole project collapse if one fails — a common reviewer concern (Chapter 9).

[Payoff.] This project will establish whether a low-cost, scalable text-message intervention improves adherence and outcomes in real-world primary care — and if so, provide the evidence base and the implementation knowledge to deploy it widely. The expected impact is a practical tool to address one of the most costly and persistent problems in chronic-disease care.

▸ The close returns to significance and makes the reviewer feel the payoff (Chapter 6): not just "we'll learn something" but "a practical tool for a costly, persistent problem." It connects back to the opening hook — the page is a closed loop, problem to payoff (Chapter 7).

What makes this page work (summary). In one page it makes all five review criteria visible: Significance (the costly, persistent problem), Investigators (the pilot and team capacity), Innovation (scalable, real-world text intervention), Approach (a rigorous, powered RCT with independent aims), and Environment (four primary-care clinics). It moves cleanly from hook → gap → hypothesis → aims → payoff (Chapter 6), credits prior work honestly, and grounds every claim in preliminary evidence. It is the proposal in miniature — and the rest of the application delivers on exactly what it promises (Chapter 5).

E.3 Reading These Samples for Your Own Work

Don't copy these — study the moves, then make them yours:

1. Find the structure. Both excerpts follow a clear arc (Chapters 6, 8–9). Outline yours the same way before you draft.
2. Mark every claim's evidence. In both samples, nearly every assertion is followed by a number, a pilot result, or a citation. Read your own draft and flag every claim that lacks proof — then supply it (Chapters 8, 9, 13).
3. Test for coherence. Both samples point every part at one goal (Chapter 5). Read yours and ask whether a reader could state your single argument after one pass (Card 6).
4. Check the framing. Both are honest and (for RYCC) asset-based (Chapters 22, 25). Find any place you've hidden a weakness or reduced people to a deficit, and fix it.
5. Match it to your funder. The foundation excerpt is relational and concise; the R01 page is rigorous and criteria-driven (Part III). Write to your funder's expectations, not a generic template.

The deeper lesson. Good proposals don't sound impressive — they are clear, specific, evidenced, coherent, and honest. Every annotation in this appendix points back to one of those five qualities. When your own draft has all five, on every page, you've written a proposal worth funding. Use Appendix A's templates to structure it, these samples to calibrate it, and the chapters to deepen it.