skills/venue-templates/references/grants_requirements.md
Funding requirements are controlled by the current solicitation or notice of funding opportunity (NOFO), the effective agency guide, and the submission portal. A general agency summary never overrides the call.
Reviewed: 2026-07-20
Use sources in this order:
Record the source URLs, versions, and date checked in the proposal workspace.
As reviewed on 2026-07-20, NSF 24-1 remains the current PAPPG for proposals submitted or due on or after 2024-05-20, with later supplemental policy notices listed on the PAPPG landing page. Recheck this status for every deadline.
Unless the solicitation modifies them:
| Component | Current general rule |
|---|---|
| Project Summary | No more than 1 page; include Overview, Intellectual Merit, and Broader Impacts |
| Project Description | Up to 15 pages for a standard research proposal |
| References Cited | Separate section; follow PAPPG content rules |
| Data Management and Sharing Plan | No more than 2 pages |
| Biographical Sketch | Generated in SciENcv for each senior/key person; no old three-page cap |
| Current and Pending (Other) Support | Generated and certified in SciENcv |
| Synergistic Activities | Separate document, up to 1 page and up to 5 examples per senior/key person |
General formatting
Do not use the obsolete “three-page NSF biosketch with Synergistic Activities inside it” pattern.
Current workflow:
Clearly label:
The summary should be understandable to a broad scientific audience and is not merely the proposal abstract.
A practical drafting structure is:
This is writing guidance, not a required section order. Follow the solicitation.
Address applicable plans for:
Directorate, office, division, or program guidance may add requirements.
assets/grants/nsf_proposal_template.tex is a planning scaffold for common narrative components. It is not an NSF-issued upload package. Split content into the appropriate Research.gov or Grants.gov fields and use SciENcv/common forms where required.
Use the form set and instructions applicable to the due date. The NOFO always takes precedence over general page-limit tables.
As reviewed on 2026-07-20:
| Attachment | General limit unless the NOFO says otherwise |
|---|---|
| Specific Aims | 1 page |
| R01 Research Strategy | 12 pages |
| R21 Research Strategy | 6 pages; combined mechanisms can differ |
| Introduction to resubmission/revision | 1 page |
| Project Summary/Abstract | 30 lines |
| Project Narrative | 3 sentences for most activity codes |
| Legacy Biographical Sketch | 5 pages |
| Biographical Sketch Common Form and Supplement | No hard page limit; length is controlled through SciENcv data entry |
Not every activity code uses every attachment. Check the NOFO and activity-code instructions.
Verify the current guide for:
Do not compress text or figures to evade a page limit.
A useful writing pattern is:
The pattern is not an NIH-mandated outline. Adapt it to the mechanism and science.
assets/grants/nih_specific_aims.tex is a writing scaffold for the one-page attachment. Confirm the current font, margin, and PDF rules before use.
For R01-style research applications, organize around:
Address rigor, feasibility, analysis, expected outcomes, potential problems, alternatives, milestones, and relevant biological variables where applicable. Mechanism- and NOFO-specific instructions can add or replace requirements.
Do not rely on the old assumption that every NIH biosketch is a manually edited five-page PDF. Determine whether the application uses:
Use the current forms directory and due-date-specific instructions.
DOE requirements vary substantially by Funding Opportunity Announcement. Extract exact rules for:
No DOE template is bundled in this skill.
Every BAA defines its own volumes, page limits, abstract/full-proposal stages, security markings, cost package, and submission channel. Do not apply a generic “20–25 page DARPA proposal” limit.
Use the Heilmeier questions as a thinking aid when relevant:
The BAA controls the actual proposal structure. No DARPA template is bundled.
Foundation programs change frequently. Start from the exact open call and capture:
Do not use remembered award sizes or historical success rates as current facts.
Create a matrix before drafting:
| Requirement | Source and section | Limit/format | Owner | Status |
|---|---|---|---|---|
| Project narrative | NOFO §IV | Example: 12 pages | PI | Drafting |
| Biosketch | Agency guide | SciENcv common form | Each senior/key person | Pending |
| Budget justification | NOFO §IV | Portal PDF | Administrator | Pending |
| Data plan | Policy + NOFO | Example: 2 pages | Data lead | Drafting |
Use the exact source language rather than paraphrasing ambiguous limits.
Begin compliance mapping before writing. Build in time for:
Never use a generic template as evidence that the final package is compliant.