Key Takeaways — Chapter 15: Assembling and Submitting
-
A noncompliant proposal is never read (threshold concept). Formatting violations, missing components, lapsed registrations, and late submission cause desk rejection regardless of quality. Treat compliance as seriously as content — a perfect proposal that breaks a rule scores zero, like a blank page.
-
Follow formatting rules exactly: page limits (often per-section), margins, fonts, font sizes, required sections and order, file formats, and attachments. Never shrink margins/fonts to cheat a limit — cut instead.
-
Attachments are the most-missed compliance items (they live outside the main document and often come from others). Inventory and track every required attachment early; obtain the slow ones (letters, audited financials) in time.
-
Submission systems have their own requirements. Federal: Grants.gov/Workspace, eRA Commons, Research.gov, with automated checks (errors must be fixed before the deadline; warnings reviewed). Registrations (SAM.gov, eRA Commons) take weeks to establish/renew — the multi-week trap; verify them the day you decide to apply. Foundation portals vary wildly (character limits, in-form questions) — open them early and draft to their actual constraints.
-
Institutional routing: the AOR submits, by an internal deadline before the funder's. Confirm it, deliver ahead of it, treat it as your real deadline. The grants office is your ally — give them time.
-
Build the pre-submission checklist early (while reading the announcement) and run it before submitting — it externalizes requirements so they don't depend on memory under stress, the way surgical/aviation checklists do.
-
Run a calm final 48 hours (nothing substantive left to do) and submit early — never 5:00:01. The quality of the final 48 hours is set weeks earlier by an early start; "boring" is the goal. After submitting, verify it went through, resolve any errors before the deadline, and keep the exact submitted package.
Common Mistakes
- Cheating formatting to fit a page limit; missing a required attachment.
- A lapsed/missing registration or an unopened foundation portal discovered at the deadline.
- Leaving substantive work or submission to the final hours; the 5:00:01 submission.
- Assuming a submission went through without verifying; composing in a web form that times out.
Decision Framework — Are you ready to submit?
(1) Does the package pass the full compliance checklist (components, formatting, attachments)? (2) Is the budget coherent and within caps? (3) Are registrations current and the internal deadline met? (4) Will you submit early, with buffer, and verify it went through (resolving any errors before the deadline)? Any "no" is your next action — with time to spare.
Your Project — and Part II
You should now have a complete, compliant, submission-ready package, a pre-submission checklist, confirmed registrations/routing, and a final-48-hours plan. Part II is complete: you can build a full grant proposal. If you've followed the project checkpoints, you hold a real, submittable proposal — the goal of the whole progressive project. Part III adapts this craft to specific funders, beginning with NIH.