Quiz — Chapter 34: Capstone — Your Complete Proposal
Answer from memory, then check. These test assembling the package, the reviewer's-eye self-review, peer and mock-panel review, the three-pass revision, and submission readiness.
1. Which best captures the capstone's threshold concept? a) A complete draft is ready to submit. b) Reviewing your own proposal as a reviewer is the last and best revision. c) Only the real reviewers can find a proposal's weaknesses. d) Polish matters more than substance.
Answer
(b). Stop being the author and become the critical reviewer — read your proposal against the funder's criteria, as the real reviewer will, and find the weaknesses before they do, while you can still fix them.
2. Why is a proposal with strong individual components not yet fundable?
Answer
Because a fundable proposal also requires coherence (components forming one argument bound to the aims, Ch 5), compliance (meeting every requirement, Ch 15), and the reviewer's-eye scrutiny that catches the gaps the author can't see. The capstone supplies all three — strong components are necessary but not sufficient.
3. Why is the author the worst judge of their own proposal?
Answer
The author knows what they meant (so they read intentions into gaps the reviewer sees), loves their work (so they're blind to weaknesses), and is immersed in the project (so they can't tell where it's unclear to an outsider). The reviewer has none of these handicaps — they read only what's on the page, critically, against the criteria.
4. How do you conduct the reviewer's-eye self-review?
Answer
Set the proposal aside a day (break the author's immersion), then return as the reviewer: open the funder's actual review criteria and read your proposal against them, scoring yourself critically as the reviewer would, asking "would I fund this, and if not, why?" The weaknesses you find as the reviewer are the revisions you make as the author.
5. What is a mock review panel, and what makes one effective?
Answer
A simulation of the real review — several people review your proposal as a panel would, against the criteria, discussing and scoring. Effective ones: assign the real criteria, recruit genuinely critical reviewers (not friendly ones), simulate the process (independent scoring then discussion), capture specific feedback, and the applicant receives it without defending.
6. What are the three revision passes, in order?
Answer
(1) Substantive revision (address what the reviews found — the deepest layer), (2) compliance pass (the binary gates that determine whether it's read at all), (3) polish pass (the surface — one voice, unmistakable significance/approach). In that order, because each depends on the one before.
7. Why must the substantive revision come before the polish pass?
Answer
Because no amount of polish saves a weak argument, and polishing before the substantive revision wastes effort on text you'll change. Fix what the reviews found wrong with the substance first, then make the now-strong proposal read compellingly. Order: substance → compliance → polish.
8. Why does assembly require integration, not just stacking components?
Answer
Because a proposal is one argument (Ch 5), so the components must cohere — every part binding to the aims, the budget matching the narrative, the evaluation measuring the promised outcomes, one voice. Assembly surfaces the cross-component incoherences (a budget line with no narrative, an aim with no measure) that disconnected drafting leaves and that a reviewer would notice.
9. What does submission readiness mean (and not mean)?
Answer
Not perfection (no proposal is perfect, and most are funded on resubmission anyway), but genuine readiness: complete, coherent, compliant, critically reviewed, revised in response, and polished — your best fundable work, ready to submit with confidence. Recognize it and submit, rather than chasing unreachable perfection past the deadline.
10. Why does the reviewer's-eye skill make you a permanently better grant writer?
Answer
Because it's a transferable, permanent skill: once you can read your own work critically against the criteria as a reviewer will, you apply it to every future proposal — writing knowing how a reviewer will read, self-reviewing each draft, and finding weaknesses before submission. The capstone finishes one proposal and leaves you with the reviewer's eye that improves all future ones.
11. Why receive critical feedback (peer/mock) without defending it?
Answer
Because every weakness the reviewers find is one you can fix before the real review (the resubmission lesson, Ch 22, applied pre-emptively). Defending the work protects your ego but forfeits the improvement; the point of critical review is to surface weaknesses, so listening and revising — not defending — is what makes the review valuable.
12. (Synthesis) An applicant submits a complete proposal without any reviewer's-eye review. Why is this a serious mistake?
Answer
Because a complete draft isn't a fundable proposal, and the author is the worst judge of its weaknesses — so the applicant submits a proposal tested only by its own creator's biased, intention-filled reading, leaving gaps, unclear passages, unconvincing claims, and unmet criteria that the real reviewer will find and score down, when the applicant could have found and fixed them first. The reviewer's-eye review (self, peer, mock) is the last and best revision; skipping it forfeits the single most valuable improvement a complete draft can get.