Every federal agency and most foundations structure a grant application differently in the details, but the underlying components repeat across almost all of them: a project narrative, a budget and budget justification, biosketches for key personnel, letters of support, and a set of compliance certifications, all routed through an institutional sponsored-programs office before submission. This guide walks through that common structure as a sequential checklist, aimed at a first-time or early-career principal investigator (PI) assembling an application for the first time. It is deliberately agency-agnostic: for the specific form sets and portals used by NIH, NSF, and other funders, see the agency-specific guides linked throughout and in the further-reading section at the end.
Before you start: read the actual funding opportunity announcement (FOA), program solicitation, or request for proposals (RFP) in full, not just the summary. Every checklist item below is subject to whatever that specific announcement requires — page limits, font/margin rules, required forms, and submission deadlines vary by funder and even by competition within the same funder, and an application that otherwise looks complete can still be rejected without review (administratively withdrawn) for failing a formatting or completeness rule stated in the announcement itself.
1. Confirm eligibility and internal deadlines first
Before drafting anything, confirm two things separately: that the PI and institution are eligible under the specific announcement (career stage, citizenship, institutional type, and prior-award restrictions all vary by program), and that the institution’s own internal deadline — typically several business days to a couple of weeks before the funder’s deadline — is on the calendar. The internal deadline exists so the sponsored programs office has time to review the budget, confirm compliance items, and route the application for institutional endorsement before it can be submitted to the funder. Missing the internal deadline is one of the most common reasons a technically-ready application doesn’t go out on time.
2. Register on the relevant submission system
Federal grant applications in the US are submitted through a government-wide or agency-specific electronic portal, and registration on these systems has its own lead time — sometimes weeks, if an institutional registration has lapsed or a new PI needs individual credentials added. Grants.gov registration is the government-wide starting point for most federal agencies; NIH applications specifically route through ASSIST or an institutional system-to-system solution; NSF applications go through Research.gov. Confirm with the sponsored programs office that the PI’s individual account is active well before assembling the rest of the package — this step is easy to overlook because it doesn’t feel like drafting content, but a lapsed registration can block submission even when every document is finished.
3. Draft the project narrative
The project narrative (called different things by different funders — Research Strategy at NIH, Project Description at NSF, Research Plan or Proposal Narrative at many foundations) is the scientific or programmatic core of the application: the problem being addressed, the specific aims or objectives, the approach, and — for most funders — an explicit statement of significance or impact. NSF’s Project Description, for example, is evaluated against two review criteria set out in the NSF Proposal & Award Policies & Procedures Guide (PAPPG): Intellectual Merit (the potential to advance knowledge) and Broader Impacts (the potential to benefit society or contribute to specific societal outcomes) — both criteria must be explicitly addressed in the narrative itself, not left implicit. Whatever the funder, treat the narrative’s own page limit, required subsections, and formatting rules (font, margins, line spacing) as hard constraints stated in the announcement, not general guidance — reviewers and, increasingly, the electronic submission systems themselves will flag or reject a narrative that doesn’t conform.
4. Build the budget and write the budget justification
The budget is a structured, line-itemized cost estimate (personnel, equipment, travel, supplies, indirect/facilities-and-administrative costs, and — if applicable — subawards); the budget justification is the accompanying narrative that explains and defends each significant line. These are two distinct documents, both required, and they need to agree with each other and with the narrative’s described scope of work — reviewers routinely check that the personnel and effort described in the budget justification match the roles described in the project narrative. For the mechanics of each, see the guide’s own worked examples: a full worked budget justification example and what a budget justification narrative needs to include. Some funders use simplified budget formats for smaller awards — NIH’s modular budget applies to applications requesting $250,000 or less in direct costs per year, in $25,000 increments, and still requires a personnel justification even though it doesn’t require a full line-item budget; if you’re preparing an NIH application, confirm which budget format applies before building either document.
5. Prepare biosketches and current-and-pending-support disclosures
A biosketch is a structured, funder-specified CV format for each senior/key person on the project — not a general resume, and not free-form. Format requirements are funder-specific and have changed recently for the two largest US federal funders: NSF and NIH both now require a Biographical Sketch built on the NSPM-33 Common Form structure, prepared through SciENcv, and NIH’s own transition to this Common Form format took effect for applications with due dates on or after January 25, 2026, replacing the narrative Sections A-D format used since 2015. See a worked NIH biosketch example for the current structure. Alongside biosketches, most federal funders also require a current and pending support disclosure (NSF calls its version Current and Pending (Other) Support) listing every other source of research support each senior/key person currently has or has applied for — this is a compliance-sensitive document, since undisclosed foreign or overlapping support is one of the most common triggers for a federal research-integrity inquiry, and it must be kept current through award, not just filed once at submission.
6. Collect letters of support (and know when a letter of collaboration is the correct document instead)
Letters from collaborating institutions, community partners, or named consultants confirm their commitment to the project. These take different forms depending on what they’re attesting to, and funders are specific about which one they want: a letter of support generally confirms institutional or organizational backing and access to resources or populations, while NSF specifically distinguishes a narrower letter of collaboration, which the NSF PAPPG restricts to stating the intent to collaborate — it explicitly should not contain endorsements or evaluation of the proposed project, or commit organizational resources or cost-sharing. Using the wrong type, or including endorsement language in a document a funder restricts to a bare statement of intent, is a compliance issue reviewers and program staff do check for. See what a letter of support should include for the general version; confirm the specific document type your funder requires directly against that funder’s own instructions.
7. Gather compliance certifications and clearances
Depending on the project’s scope, this can include human subjects research review (IRB approval or exemption determination), animal welfare (IACUC) approval, conflict of interest disclosure, biosafety review, export control screening, and — for many funders now — a data management plan describing how research data will be handled, stored, and shared. Some of these (like full IRB approval) don’t need to be finalized before submission — most funders only require a statement of intent or exemption determination at application, with full approval due before funds are released — but confirm exactly what stage is required at submission versus at award for the specific funder and mechanism, since this varies and getting it wrong can delay both review and award setup.
8. Assemble the full package and route for institutional endorsement
A complete federal application is typically built from a common cover form plus the component documents above — for example, most federal agencies still build on some version of the government-wide SF-424 (Application for Federal Assistance) form family, even though the attached component forms vary by agency (see SF-424 (R&R) instructions and, for NIH’s legacy form set specifically, the PHS 398 guide). Before submission, every application also needs institutional sign-off — usually from the sponsored programs office acting as the institution’s Authorized Organizational Representative (AOR) — certifying that the institution stands behind the budget, the compliance representations, and the commitment to administer the award if made. This is the step the internal deadline in item 1 exists to protect: give the office real review time, not just time to click submit.
9. Do a final consistency and completeness pass
Before submission, re-check the whole package against the funder’s own instructions one more time, specifically for internal consistency: do the personnel and effort levels match across the narrative, budget, budget justification, and biosketches? Does every required attachment appear in the format specified (PDF, specific naming convention, page limits)? Are all signatures and institutional certifications in place? Electronic submission systems increasingly run automated completeness checks on upload and will bounce a package back with errors to fix before the funder’s deadline — submit a few days early with buffer to fix a rejected upload, rather than at the literal deadline with no room left to correct an error.
Where to go next
This checklist covers what’s common across most federal and foundation applications. For the specific form sets, portals, and deadlines of a particular funder, use the agency-specific guides: SF-424 (R&R) instructions, the PHS 398 legacy NIH form, and the comparison of NIH biosketch vs. UKRI R4RI narrative CV formats for researchers working across US and UK funders. For the broader pre-award process this checklist sits inside, see the grants management pillar page.
Frequently asked questions
What documents are needed for a grant application?
Most federal and foundation applications need, at minimum: a project narrative describing the work, a budget and budget justification, biosketches for senior/key personnel, a current-and-pending-support (or other-support) disclosure, and — depending on the project — letters of support, compliance certifications (human subjects, animal welfare, conflict of interest), and a data management plan. The exact list and required formats are set by the specific funding opportunity announcement, not by a single universal standard.
How long does it take to prepare a grant application?
This varies enormously by mechanism and institution, but early-career PIs are routinely advised to allow several weeks to a few months for a substantial federal research-project application, and to hit the institution’s own internal deadline (often one to two weeks ahead of the funder’s deadline) rather than the funder’s deadline itself, since the sponsored programs office needs real time to review the budget and route the package for institutional sign-off.
What is the difference between a grant application and a grant proposal?
In practice the terms are often used interchangeably. Where a distinction is drawn, proposal more often refers to the narrative and technical content of what is being proposed and why, while application refers to the complete submitted package, including the proposal narrative plus the administrative forms, budget, and certifications required by the funder.
Do foundation (non-federal) grant applications follow the same structure?
Many of the same components recur — a narrative, a budget, and some form of organizational or personnel credentials — but foundations generally have far less standardized formats than federal agencies, and some use a shorter letter of inquiry stage before inviting a full application. Always follow the specific foundation’s own application instructions rather than assuming a federal-style structure applies.
