Quiz — Chapter 5: The Anatomy of a Proposal


Question 1. Why does the chapter insist a proposal is "one argument, not a stack of sections"?

Answer Because the components must agree with and reinforce one another; written as separate tasks, they contradict (the budget funds activities the approach never mentions, the evaluation measures outcomes the aims never promised), and a reviewer feels an unease that reads as muddled thinking and costs the score.

Question 2. State the threshold concept and the "so what?" test.

Answer Threshold: every paragraph must earn its place by answering a specific reviewer question — sections are answers, not containers. The "so what?" test: for any passage, ask which reviewer question it helps answer and whether a tired reviewer sees the answer; if it answers none, cut or rewrite it.

Question 3. Match the component to its reviewer question: significance, approach, budget justification, evaluation plan, biosketches.

Answer Significance → "Does it matter?" Approach → "Can you do it / is the plan sound?" Budget justification → "Why is each dollar necessary?" Evaluation plan → "How will we know if it worked?" Biosketches → "Are these the right people?"

Question 4. Explain "the aims drive everything" with one concrete consequence.

Answer Whatever the aims promise constrains every later component: if the aims promise three outcomes, the evaluation must measure those three, the approach must include activities that produce them, and the budget must fund those activities. The aims are the spine; every component is a rib attached to it.

Question 5. Write the logic-model chain and map each link to a proposal component.

Answer Inputs (budget/capacity) → Activities (approach) → Outputs (near-term evaluation targets) → Outcomes (what the aims promised; evaluation) → Impact (significance). The chain connects budget, approach, evaluation, and significance into one line.

Question 6. What is the most-watched coherence signal, and why is one contradiction so costly?

Answer The budget–narrative match. One visible contradiction (a mismatched total, an unfunded activity, an unexplained line) is costly because a reviewer who catches one inconsistency starts hunting for others and reads the whole proposal with suspicion — coherence is a credibility signal.

Question 7. Distinguish a logic model from a theory of change.

Answer A logic model is the linear inputs-to-impact chain (what connects to what). A theory of change is the richer account of *why* the activities should produce the outcomes — the assumptions and causal logic under the arrows. Many program funders want both; when a funder asks for a theory of change, defend the arrows, don't just draw them.

Question 8. Why follow the funder's component order and labels exactly?

Answer Because reviewers look for each required piece where the instructions said it would be; reorganizing makes them hunt, which breeds irritation and costs points (and can be a compliance failure). Know the universal skeleton for your own coherence, but present it in the funder's exact template.

Question 9. Give two components applicants underinvest in but reviewers weight heavily.

Answer Any two of: the abstract (often the most-read part, sometimes the only part some panelists read); the evaluation plan (increasingly central — funders want evidence of impact, not just activity); the budget (a story in numbers that must match the narrative). Beginners treat these as throwaways; reviewers do not.

Question 10. Why does the chapter say revision is mostly subtraction?

Answer Because cutting what doesn't earn its place strengthens what remains by improving signal-to-noise: when every paragraph is load-bearing, each stands out and the argument feels dense and confident; filler dilutes even strong content. The same evidence in half the words hits harder.

Question 11. Name three funder-specific components or attachments that, if missing, can cause rejection despite a strong proposal.

Answer Any three of: data-management/sharing plan; human-subjects/animal/biosafety sections; mentoring/training plan (fellowships); cover letter (where expected); indirect-cost rate agreement, IRS determination letter, audited financials, or board list (attachments). Missing a required component is a compliance failure regardless of the rest.

Question 12. A reviewer says a proposal "just didn't hang together," though no single section was weak. Diagnose using this chapter.

Answer A coherence failure: the components did not interlock — perhaps the budget didn't match the narrative, the evaluation didn't measure what the aims promised, or the team didn't match the task. Even with strong individual sections, the lack of a single connected argument produces the felt "doesn't hang together" that lowers scores. The fix is to bind every component to the aims and check the logic-model chain.