Quiz — Chapter 4: The Proposal Development Process


Question 1. Why does the chapter call starting late "the most preventable failure" in grant writing?

Answer Because time is the resource that makes every other quality possible (alignment, feedback, a careful budget, a clean submission), and unlike talent or eloquence, an early start is fully within your control and costs only foresight. Late starters forfeit every advantage at once — not for lack of skill, but for lack of time.

Question 2. How early do professionals typically begin a major federal proposal, and why so early?

Answer Six to twelve months out, because eight stages must happen — funder research, program-officer contact, team and letters, preliminary data, drafting and revision, budget, and institutional routing — each with irreducible lead time, before a hard, to-the-second deadline.

Question 3. Put these in order: submission, concept, full proposal development, funder alignment, internal routing.

Answer Concept → funder alignment → full proposal development → internal routing → submission. (Between alignment and full development sit go/no-go, team assembly, and any required LOI.)

Question 4. What is an internal deadline and why must you treat it, not the funder's deadline, as your real deadline?

Answer It is the date by which your complete proposal must reach your grants office so they can review compliance, check the budget, get signatures, and submit on your behalf — typically a week or two before the funder's deadline. Miss it and the office may not submit, so you can miss the funder's deadline by being late to your own institution.

Question 5. What is the value of a one-page concept paper, and name two uses for it.

Answer It clarifies your thinking cheaply (an hour) before you sink time into prose. Uses (any two): email it to a program officer to test fit; hand it to a potential collaborator; show it to a skeptical colleague for early critique; use it as the skeleton for your aims/executive summary.

Question 6. Why should you engage your budget/grants office early rather than handing them a finished proposal to submit?

Answer Because their value is mostly preventive, and prevention must happen before the mistake. Early, they can fix an indirect-cost error, flag an unallowable expense, and confirm registrations — all fixable with time. At the last minute they can only watch it go in flawed or decline to submit.

Question 7. What is a limited-submission program, and what should you do the moment you spot one?

Answer A program that caps how many applications one institution may submit, sometimes to one — requiring an internal competition with its own much earlier deadline. The moment you spot one, contact your grants office to learn whether a limited-submission process applies and its internal deadline, so you can enter it rather than be shut out.

Question 8. Give two reasons collaborators make a proposal both stronger and harder to schedule.

Answer Stronger: they add expertise and credibility, and reviewers can tell a real, committed team from borrowed names. Harder: they have their own jobs and deadlines, and a partner institution may require *its* grants office to sign off on *its* internal deadline — so more institutions means an earlier start.

Question 9. A solo applicant has no grants office or collaborators. Which roles must they still cover, and which two should they recruit?

Answer They must still cover all functions — checking rules, building the budget, confirming registrations/approvals, and critically reviewing the draft. They should recruit at least a critical reader (catches flaws they can't see) and an accountability partner (holds them to timeline milestones).

Question 10. Why is keeping a single canonical, dated master file (and one budget source of truth) important?

Answer Because proposals accrete edits from multiple people under time pressure, and the failure mode is several versions in circulation, someone editing the wrong one, and the document's budget drifting from the spreadsheet — producing the inconsistencies (e.g., mismatched budget totals) that reviewers notice and that cause errors at submission.

Question 11. Explain why a federal submission system enforcing a deadline "to the second" is fair rather than harsh.

Answer With tens of thousands of applicants competing for the same dollars, the funder needs a bright line that treats everyone identically and cannot be gamed by special pleading. A hard, uniform cutoff is the fair way to do that — which is precisely why you must respect it and never rely on flexibility you haven't been promised.

Question 12. When a three-week deadline is unavoidable, what is the chapter's honest advice?

Answer Triage: confirm the non-negotiables (registrations, routing) are even possible; if so, concentrate effort on the fit-and-significance opening and a clean, compliant submission, and recognize that a rushed proposal is usually a *practice* submission whose main payoff is feedback for a properly-timed next attempt. Choose this with open eyes; don't pretend heroic effort replaces stages that can't be compressed.