Quiz — Chapter 15: Assembling and Submitting
Question 1. State the threshold concept and its consequence.
Answer
A noncompliant proposal is never read, no matter how good. Formatting violations, missing components, lapsed registrations, and late submission cause desk rejection before any reviewer evaluates the merits. So compliance deserves the same seriousness as content — a perfect proposal that breaks a rule scores zero, like a blank page.Question 2. Why is shrinking margins or fonts to fit a page limit doubly self-defeating?
Answer
It breaks the formatting rules (risking automated desk rejection) AND signals to any reviewer who notices that you couldn't bear to cut (a failure of the "earn its place" discipline). The correct response to "it won't fit" is always to cut until it fits, never to cheat the formatting.Question 3. What is the "multi-week trap," and how do you avoid it?
Answer
Required registrations (SAM.gov with a Unique Entity ID, eRA Commons) must be established or annually renewed, and the process takes days to weeks. A lapsed/missing registration discovered at the deadline is fatal with no time to fix. Avoid it by verifying every required registration the moment you decide to apply — the cheapest insurance in grant writing.Question 4. Why can't most institutional applicants submit their own federal proposals, and what deadline does that create?
Answer
Because the AOR (authorized organizational representative) in the grants office is the only one who can legally commit the institution; they submit. This creates the internal deadline — typically days before the funder's — by which your complete package must reach the grants office for review and submission. 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. When should you build the pre-submission checklist, and why then?
Answer
When you first read the announcement (Ch 3). Building it incrementally means each requirement becomes a checklist item at no extra effort, you have a complete funder-specific checklist by submission, and it shapes the work along the way (requesting letters and gathering documents in time). It's a planning document, not just final verification.Question 6. Distinguish errors from warnings, and why submit early relative to them?
Answer
An error is a hard stop that prevents/invalidates submission and must be fixed; a warning is a flag to review that won't block submission. Errors must be resolved *before the deadline* — and a post-submission error must be fixed and resubmitted before the deadline closes. Submitting early gives you time to resolve errors while the window is open; submitting at 4:59 leaves no time.Question 7. Why does the chapter compare a pre-submission checklist to those used by surgeons and pilots?
Answer
Because the failure at submission isn't incompetence but limited working memory under stress — no one can hold thirty requirements in their head while exhausted and racing a deadline. A checklist externalizes the requirements and forces item-by-item verification, catching what a holistic glance misses. Like surgical/aviation checklists, it compensates for the universal human tendency to miss items under load.Question 8. Why are attachments especially error-prone, and how do you defend against missing one?
Answer
They live outside the main document, often come from other people, and are easy to forget amid the narrative focus — yet a missing required attachment makes the application incomplete. Defend by inventorying every required attachment early, tracking each to completion (who provides it, received, formatted), and obtaining the slow ones (letters, audited financials) in time.Question 9. What is the special hazard of foundation portals?
Answer
Their variety: each is different, with character-limited fields that silently truncate, required questions in forms (not uploads), and quirks not in the published guidelines. Defense: get into the portal early to see what it actually asks, draft to its real constraints, and never compose directly in a web form that might time out — write in your own document and paste in.Question 10. Why is a "boring" final 48 hours the goal, not a disappointment?
Answer
Because drama at the deadline is the symptom of a process that failed; calm is the mark of one that worked. The heroic all-nighter signals the timeline broke down. The experienced applicant aims for the anticlimactic submission — sent a day early, confirmed, deadline passing unremarked — because that calm means every risk was managed in advance. The quality of the final 48 hours is set weeks earlier by an early start.Question 11. What should you do immediately after submitting?
Answer
Verify it went through (get the confirmation/tracking number); check for errors and warnings and resolve any errors before the deadline; confirm with the grants office that the AOR submitted; and keep the exact submitted package (final PDFs, confirmation) unaltered for your records, just-in-time requests, and any resubmission.Question 12. Why does the chapter say "the final mile is won or lost in the first mile"?