Answers to Selected Exercises

Model answers and solution guidance for selected exercises across the book. These are the recall and applied-reasoning items whose answers are definite enough to check yourself against, plus guidance on the project-creation items (Part C) — which can't have a single answer, because they're about your proposal, so for those this appendix gives the standard a strong answer should meet.

How to use this. Try the exercise first, then check here. For recall items (Part A), compare your answer to the model for completeness, not word-for-word match. For applied items (Part B), the reasoning matters more than the exact conclusion. For creation items (Part C), evaluate your work against the criteria given and the self-review worksheet (Appendix A.12). Not every exercise is answered here — the selection is representative, and the chapters themselves contain the full reasoning.

Chapter 1 — What Is a Grant?

1.1. A grant is an award of financial support to carry out a defined project or purpose, not repaid, given in exchange for delivering on stated goals and reporting back. The two parties are the grantor (funder) and the grantee (recipient).

1.2. (a) A loan must be repaid; a grant need not. (b) A contract buys specific deliverables the buyer defines and owns; a grant supports the grantee's project toward the funder's mission, with more latitude. (c) A gift carries no defined obligations or reporting; a grant comes with stated goals and accountability.

1.4. Restricted funding may be used only for a specified project; unrestricted (general operating) funding may be used flexibly — salaries, rent, infrastructure. Unrestricted is more prized because it funds the things that keep an organization alive and adaptable, which most project grants won't cover.

1.5. Direct costs are attributable to the specific project (e.g., a project coordinator's salary, project supplies); indirect (F&A) costs are real but diffuse overhead (e.g., the finance office, the building's utilities). Examples will vary; the test is whether the cost is traceable to the one project or shared across many.

1.6. Triage is the NIH practice of scoring but not discussing the lower-ranked portion of applications, to focus the panel's limited time on those most likely to be funded. It is not a judgment that the science is bad — a triaged application still gets written critiques, and many are strengthened and funded on resubmission.

1.8. The mission transaction is the reframe that a funder isn't giving money away — it's buying progress toward its own mission, and your proposal is the offer. It matters because it shifts your writing from "what I need" to "what the funder accomplishes by funding me" — the orientation behind every chapter that follows.

1.9 (Part B). (a) research; (b) operating; (c) fellowship; (d) capital; (e) seed/pilot; (f) capacity. The point: naming the type tells you what the reviewer will weigh most.

1.11 (Part B). Each rewrite should move from the applicant's need to the funder's mission. For example, (a) "We need money to run our tutoring program" → "Your foundation's goal of closing the local reading gap can be advanced by [specific outcome] for [number] students through our tutoring program." The pattern: funder's goal → your project as the means → concrete outcome.

1.12 (Part B). "12% chance" is misleading because funding isn't a lottery — your odds depend on fit, quality, and execution, not the base rate. A well-fitted, well-written proposal beats the average; a poorly fitted one trails it. The base rate describes the pool, not your specific, controllable position in it.

1.13–1.17 (Part C). These build your "My Proposal" starter and have no single answer. A strong response: states what you'll do, why it matters, and who you are concretely (not vaguely); names a plausible grant type and river with a reason; and frames the work as a funder's mission transaction. Check your pre-mortem (1.16) against the six failure patterns — the most common is poor funder fit, so make sure one of your two risks engages fit.

Chapter 2 — Thinking Like a Funder

2.1. A funder with "spare cash" would fund anything worthy; a funder with "a mission to advance" funds only what serves its goals. The distinction matters because it means your job is not to prove your project is good in the abstract, but to prove it advances their specific mission — fit, not merit alone.

2.2. The three "rooms": the program officer's office (write to a person who can advise and advocate — talk to them early); the review panel (write for busy expert peers scoring against criteria — be clear, structured, and easy to score); the funder's board/decision room (write so your champion can sell your project to people who never read it — give them a crisp, repeatable case).

2.3. Reviewer fatigue is the tired-reviewer psychology of someone reading many proposals: attention and patience are scarce. Implications: front-load your most important points; make structure visible (headings, topic sentences); never make the reviewer hunt for the answer to a scored criterion.

2.4. Order: fit → significance → approach → capacity → budget. "Fit," answered no, ends the review immediately — a misfit proposal isn't read charitably no matter how strong.

2.6. The "two fears": fear of funding a failure (the project won't deliver) and fear of missing a success (passing on something important). A strong proposal soothes both — it shows enough rigor and feasibility to make failure unlikely, and enough significance to make not funding it feel costly.

Chapter 3 — Finding the Right Funder

3.1. A list of fifty "possible" funders is a trap because it invites scattershot applying — effort spread thin across weak fits, each a low-probability, high-cost gamble. Research's value is in disqualifying, not accumulating.

3.2. The three outputs, in order of value: (1) a short list of strong fits to pursue; (2) a list of funders to reject (a fit you can rule out is time saved); (3) funders to cultivate first before applying. Two are forms of not applying because not applying where you'll lose is the highest-return decision in prospecting.

3.4. The two readings: a compliance reading (eligibility, deadlines, format, required components) and a subtext reading (what the funder weights, prioritizes, and really wants — the one thing the proposal must prove). The first keeps you eligible; the second makes you competitive.

3.5. Scorecard dimensions: mission fit, program fit, eligibility, geography, size, stage, history. Eligibility is the gate (fail it and nothing else matters). Mission/program fit should weigh most — it predicts funding more than any other factor.

3.6. The 80/20 rule: concentrate ~80% of your effort on the ~20% of funders who fit best. It guards against two temptations — spreading effort thinly across many weak fits, and over-investing in one funder to the exclusion of a healthy pipeline.

Chapter 6 — The Specific Aims Page

6.1. Threshold concept: the specific aims page is the proposal in miniature, and it carries disproportionate weight because it's the page every reviewer reads and the frame through which the rest is judged. If it doesn't land, the rest may not be read closely.

6.2. The six moves: hook (an important problem — why care?), gap (what's missing — what don't we know/have?), goal & objectives (what you'll do about it), hypothesis/premise (your testable claim and why it's credible), the aims (how, in 2–4 independent parts), payoff (what changes if you succeed).

6.4. Three properties of a strong aim: it is specific, feasible, and independent of the other aims. The dependency trap is writing aims where a later one collapses if an earlier one fails — making the whole project an all-or-nothing bet a cautious reviewer won't take.

6.5. Five aims-page killers (any five): no clear gap; aims that depend on each other; a goal with no testable premise; vagueness (no specifics); burying significance/no payoff; overpacking (too many aims); jargon a non-specialist reviewer can't follow.

Chapter 8 — Needs Assessment / Significance

8.1. Threshold concept: significance isn't a pile of statistics — it's an argument that a specific, important problem demands action now. More data is often weaker than less because undigested numbers bury the argument; a few well-chosen, well-framed facts in a clear chain persuade.

8.2. The so-what chain: problem → magnitude → consequence/cost → insufficiency (the gap) → necessity. The two most often skipped are consequence/cost (skipping it invites "so what if this problem exists?") and necessity (skipping it invites "why this, why now, why you?").

8.4. A gap analysis credits existing efforts and then names the specific gap they leave. Crediting existing efforts strengthens it because it shows you know the field, you're not duplicating, and the gap is real and unaddressed — not ignorance of work already done.

8.6. Fabrication invents data; cherry-picking reports only the data that helps and hides the rest; false precision implies more certainty than the evidence supports. Each destroys trust because a reviewer who catches one dishonest number disbelieves all your numbers — and your credibility is the proposal's foundation.

Chapter 10 — The Evaluation Plan

10.2. The logic-model chain: inputs (resources) → activities (what you do) → outputs (what those produce, counted) → outcomes (what changes) → impact (the long-term difference). The distinction beginners blur is outputs vs. outcomes — "trained 100 people" (output) is not "100 people changed their practice" (outcome). Funders buy outcomes.

10.4. SMART = Specific, Measurable, Achievable, Relevant, Time-bound. Beyond the objective itself, each needs an indicator (the observable measure), a target (the justified success level), a data source, and a method of collection.

10.6. A power analysis determines the sample size needed to detect a real effect of a given size. An underpowered study is a fatal flaw because it may fail to detect a true effect — wasting the funder's money on a study that couldn't have answered its own question regardless of the truth.

Chapter 11 — The Budget

11.2. Salary is the annual pay for a role; effort is the fraction of time devoted to the project; fringe is benefits as a percentage of salary. One person's personnel cost = salary × effort + (salary × effort × fringe rate), i.e., (salary × effort) × (1 + fringe rate).

11.3. Direct costs are attributable to the project; indirect (F&A) costs are diffuse overhead recovered at a rate times a base. Indirect costs are contentious because they're real but invisible — funders and the public sometimes misread them as waste, fueling the "overhead myth," when they actually fund the infrastructure the work depends on.

11.5. Escalation is the annual increase (commonly 2–4%) applied to multi-year costs for raises and inflation. A multi-year budget isn't year one repeated because salaries rise, costs inflate, and activity levels often change across years — a flat repeat understates real costs.

Chapter 16 — NIH Grants (selected ★)

A1. ★ The CSR makes two assignments: to an Institute or Center (which holds the money and makes funding decisions) and to a study section (which reviews and scores). The separation is fundamental because it splits judgment of scientific merit (decentralized review) from funding priority (institute discretion) — and it means you can, and should, think about both targets.

A4. ★ The five criteria: Significance, Investigator(s), Innovation, Approach, Environment. Approach is often weighted most heavily in practice; it stress-tests whether you can actually do the work — the methods, the rigor, the feasibility, the handling of pitfalls. (Verify current criteria, as NIH periodically reorganizes the framework.)

B1. ★ (a) F31 — predoctoral fellowship: a student with a strong mentor and focused project, judged on candidate and training plan, not preliminary data. (b) R01 — pilot data plus a developed clinical-trial design fit the workhorse research grant. (c) R21 — exploratory/high-risk with no preliminary data, to generate data for a future larger grant. (d) K award — a mid-career scientist needing protected time and mentored training to change fields. The rule: match the mechanism to your stage and evidence, not your ambition.

B3. ★ Two concrete moves: write a cover letter requesting a specific Institute and study section (with a brief justification), and choose your title, abstract, and specific aims language to signal the fit you want (the words route the application). Getting the assignment right can matter as much as the writing because the right expert reviewers in the right study section will understand and value your work — the wrong ones may not.

C1–C2 (Part C). No single answer — evaluated against the chapter. A strong C1 lists every NIH-specific component your project triggers (human subjects, animals, clinical trial, data-management-and-sharing) and honestly flags the two you understand least. A strong C2 runs the threshold-concept test explicitly and, if your ambition outruns your evidence, names the lower-stage mechanism or the preliminary-data step to pursue first.

Chapter 17 — NSF Grants (selected ★)

A1. ★ The two merit-review criteria: Intellectual Merit (the potential to advance knowledge) and Broader Impacts (the potential to benefit society). Applicants most often under-invest in Broader Impacts, treating it as a checkbox — a mistake because it is co-equal, explicitly scored, and a genuine, specific plan is often what separates two scientifically excellent proposals.

A4. ★ NSF rates proposals on a descriptive scale (Excellent–Very Good–Good–Fair–Poor), not NIH's 1–9. The program officer (often a rotating working scientist) makes the funding recommendation, weighing not only the reviews but also portfolio balance — there's no fixed payline. NIH, by contrast, leans on percentile and payline with institute discretion.

Chapter 19 — Government Grants (selected ★)

A1. ★ Threshold concept: you win a government grant by writing to the scoring rubric, and you only get the chance by clearing the binary gates first. The two things: win on the rubric (the points) and clear the binary gates (eligibility, registration, format, deadline).

A4. ★ A NOFO (Notice of Funding Opportunity) is the binding announcement governing the competition — its "law." The two sections that dominate everything: the eligibility/requirements (the binary gates) and the review criteria/scoring rubric (where the points are). They dominate because failing the first disqualifies you and missing the second loses the competition even when you're eligible.

Chapter 22 — The Resubmission (selected ★)

A1. ★ Threshold concept: most funded competitive proposals were rejected first, and the resubmission is where they were won. Rejection is "the middle, not the end" because for most strong applications, the decline plus its critique is a stage in the process — the feedback that, addressed well, produces the funded version.

A4. ★ The introduction-to-resubmission is the document (e.g., NIH's one-page intro to an A1) that demonstrates how you've responded to the prior critique. Under each concern, you should: name the concern fairly, answer it (what you changed, clarified, or — rarely — respectfully retained), and point to where in the revised application the change appears. Specific, evidence-pointing, gracious — a demonstration of responsiveness, not a debate to win.

Chapter 24 — Grant Writing with AI (selected ★)

A1. ★ Threshold concept: AI can sharpen your argument but cannot own it — accountability stays with you. AI can help brainstorm, outline, edit your prose, and summarize material you provide; it can never supply verified truth, the relationships and judgment, the strategy, or the accountability — those remain yours.

A4. ★ Four dangerous uses (any four): trusting AI for citations, statistics/facts, budgets/numbers, or funder-specific nuance — and never put confidential or unpublished material into a public tool. The shared property that makes them risky: they require truth and judgment the model can't provide, and it will produce confident, plausible, wrong output (hallucination) that you alone are accountable for.

Chapter 28 — Nonprofits (selected ★)

A1. ★ Threshold concept: grants are one leg of a diversified funding stool, not the whole stool. Grant dependence is fragility because grants are restricted, time-limited, and competitive — an organization relying on them alone is one declined renewal from crisis, and loses the flexibility that mission health requires.

A4. ★ General operating support is flexible, unrestricted funding (the rarest and most valuable); program support is restricted to a specific program (most grants). The overhead-myth / starvation cycle: funders underfund indirect/administrative costs → nonprofits underinvest in their own infrastructure → they stay weak and under-capacity → which seems to justify underfunding them. Serious funders now repudiate this cycle.

Chapter 33 — Sustainable Funding Strategy (selected ★)

A1. ★ Threshold concept: a pipeline, not a proposal, produces reliable funding. Because any single proposal is likely to be declined (win rates are often roughly one in five), reliability comes from a continuous flow of many proposals at every stage — so that wins arrive steadily and no single decision is decisive.

A4. ★ A pipeline must be continuous (proposals at every stage, always — so funding doesn't arrive in feast-or-famine pulses) and diversified (multiple funders and types — so no single loss is catastrophic). A full pipeline to one funder is fragile: it's a single point of failure, and one change in that funder's priorities can empty it entirely.

Chapter 34 — Capstone (selected ★)

A1. ★ Threshold concept: reviewing your own proposal as a reviewer is the last and best revision. It's the most powerful revision because it replaces the author's hopeful reading with the reviewer's skeptical one — surfacing the weaknesses that will actually cost you points while you can still fix them.

A4. ★ A mock review panel is a simulated review: critical readers score your proposal against the funder's actual criteria, independently, then discuss — as a real panel would. What makes one effective: real criteria, genuinely critical (not friendly) reviewers, independent scoring before discussion, and feedback you treat as a gift to act on rather than a verdict to argue with.

A6. The three revision passes, in order: substance (act on the reviews — the argument, the gaps), then compliance (the binary gates — format, components, limits), then polish (the surface — one voice, clarity). That order because polishing prose you may cut wastes effort, and a beautifully written non-compliant proposal still gets rejected — fix what matters most, and what's disqualifying, before the surface.

On the Part C / project exercises throughout. The creation exercises — building your aims page, your budget, your evaluation plan, your complete proposal — have no answer key because the answer is your funded proposal. Evaluate them against three things: the chapter's framework (does your work do what the chapter teaches?), the self-review worksheet (Appendix A.12: would a critical reviewer fund it?), and, best of all, a real critical reader or mock panel (Chapter 34). The exercises you can't check against this appendix are the ones that matter most — they're the book's true final exam, and you pass it by getting funded.