How to Write an NSF Project Summary

The NSF Project Summary is a required, standalone, one-page document in every NSF proposal — separate from the longer Project Description — and it is the one part of the application every reviewer, panelist, and program officer reads before anything else. NSF’s Proposal & Award Policies & Procedures Guide (PAPPG) requires it to contain three explicitly labeled sections, each starting on its own line: an Overview, a statement on Intellectual Merit, and a statement on Broader Impacts. Get the structure wrong — miss a section, blur the labels together, or run past one page — and NSF’s own guidance states the proposal will not be accepted or will be returned without review. This guide covers what belongs in each of the three sections, how the Project Summary differs from the Project Description, and the formatting and submission mechanics that trip up first-time NSF applicants.

What Is the NSF Project Summary?

The Project Summary is a one-page document required in every NSF proposal, submitted as its own separate upload in Research.gov rather than as part of the Project Description. Per the current PAPPG (NSF 24-1, Chapter II, Proposal Preparation Instructions), it must contain three sections — Overview, Intellectual Merit, and Broader Impacts — each beginning on its own line with only the section heading on that line, no other text. All three sections together must fit on the single page; there is no separate page allowance per section.

The Project Summary does more work than its length suggests. Program officers use it to gauge fit with a program’s scope before a proposal is even assigned reviewers, and it is often the only part of the proposal a full panel reads closely before the review meeting — individual assigned reviewers work through the full Project Description, but panelists reviewing dozens of proposals frequently rely on the Project Summary to orient themselves before diving into (or triaging) the rest. A vague, jargon-heavy, or poorly labeled summary can undermine a strong proposal before a reviewer reaches the substantive narrative.

Project Summary vs. Project Description: Not the Same Document

These are two separate required documents, uploaded separately, serving different purposes:

Project Summary — one page, third person, three mandatory labeled sections (Overview, Intellectual Merit, Broader Impacts), written for a reader who may never read further.
Project Description — up to 15 pages (the exact limit depends on the program solicitation), the actual substantive narrative: background, research plan, methods, timeline, prior results, and the detailed case for both merit review criteria that the Project Summary can only state, not fully argue.

A common mistake is treating the Project Summary as a compressed version of the Project Description’s introduction. It isn’t — it’s a distinct genre with its own mandatory structure, closer to a structured abstract than to an executive summary. For the broader question of how a proposal abstract differs from a manuscript abstract and how to approach the writing task generally, see CASRAI’s guide to writing an abstract for a research proposal.

The Three Required Sections

1. Overview

The Overview describes the proposed activity: what will be done, the objectives, and the methods to be used. It should stand on its own as a clear, non-technical description of the project — written so that a program officer or a panelist outside the immediate sub-field can understand what is being proposed without reading the Project Description first.

Common mistakes in the Overview:

Restating the proposal title in slightly different words instead of actually describing the work.
Writing at the same technical density as the Project Description, using jargon or acronyms that assume a specialist reader.
Omitting a clear statement of objectives or methods, leaving reviewers to infer what will actually be done.

2. Intellectual Merit Statement

This section must state the project’s potential to advance knowledge — NSF’s first merit review criterion. It should be explicit and self-contained: what gap, question, or capability does the work address, and why does it matter to the field. Reviewers use this statement, together with the Project Description, to assess the “Intellectual Merit” review criterion directly, so vague or implicit framing (“this research is important”) costs a proposal more here than almost anywhere else in the document.

Common mistakes: folding Intellectual Merit language into the Overview instead of giving it its own clearly labeled statement; asserting significance without saying what specifically would be newly known or possible; and using boilerplate language interchangeable with almost any other proposal in the field.

3. Broader Impacts Statement

This section must state the project’s potential to benefit society and contribute to specific, desired societal outcomes — NSF’s second merit review criterion, applied alongside Intellectual Merit since 1997. NSF’s guidance lists broad, non-exhaustive example categories (STEM education and educator development, public engagement and scientific literacy, societal well-being, a diverse and globally competitive STEM workforce, and others) and recognizes three legitimate pathways for achieving broader impacts: through the research activity itself, through activities directly related to the research, or through complementary activities the research supports.

Getting this section right — and knowing what panels actually weight highly versus what reads as a bolted-on afterthought — is enough of a distinct skill that it deserves its own treatment: see CASRAI’s guide to what review panels actually score highly in Broader Impacts statements for the deep dive on this section specifically, including how NSF’s more recent priorities guidance has reshaped what counts as an acceptable broadening-participation activity.

Formatting and Submission Mechanics

One page, total. All three sections together must fit on a single page — there is no per-section page allowance.
Each section heading on its own line. “Overview,” “Intellectual Merit,” and “Broader Impacts” must each appear alone on their own line, with no other text sharing that line.
Written in the third person. NSF’s convention departs from first-person narrative style used elsewhere in some proposals; the Project Summary is written about the project (“This project will…”) rather than about the applicant (“I will…”).
Uploaded as a separate document. The Project Summary is its own distinct upload in Research.gov, NSF’s proposal preparation and submission system (FastLane was retired as an NSF proposal-submission option effective January 30, 2023) — it is not a section within the Project Description file.
Missing a section is not a minor formatting issue. Per NSF’s own guidance, a Project Summary that omits the overview or either of the two required statements will not be accepted, or will be returned without review — this is a compliance check performed before a proposal is ever routed to reviewers, not a scoring criterion reviewers weigh subjectively.

A Practical Checklist Before Submission

Does the document fit on exactly one page, with all three sections included?
Does each of the three section headings appear alone on its own line, spelled and labeled as NSF expects (Overview / Intellectual Merit / Broader Impacts)?
Is the entire document written in the third person?
Could a program officer outside your immediate sub-field understand the Overview without reading the Project Description?
Does the Intellectual Merit statement explicitly name what new knowledge or capability the work would produce — not just assert that the work is significant?
Does the Broader Impacts statement name a specific, plausible societal outcome and pathway, rather than a generic outreach placeholder?
Is it uploaded as its own separate document in Research.gov, distinct from the Project Description file?

Frequently Asked Questions

Is the NSF Project Summary the same thing as an abstract?

Not exactly. It functions like a structured abstract in that it is short and meant to stand alone, but NSF imposes a specific, mandatory three-section structure (Overview, Intellectual Merit, Broader Impacts) that a general research abstract does not have. See CASRAI’s broader guide to writing a research-proposal abstract for how proposal abstracts differ from manuscript abstracts generally.

Can I write the Project Summary in first person?

No. NSF’s guidance calls for the Project Summary to be written in the third person, unlike some narrative sections elsewhere in a proposal.

What happens if I forget to label one of the three sections?

NSF’s own guidance states that a Project Summary missing the overview or either required statement will not be accepted or will be returned without review — this is checked before a proposal reaches reviewers, so it is a compliance failure, not a scoring deduction.

Does the Broader Impacts statement need to repeat everything in the Project Description’s broader impacts discussion?

No — the Project Summary’s Broader Impacts statement should be a concise, self-contained claim about the project’s societal benefit; the fuller argument, evidence, and plan belong in the Project Description. See CASRAI’s dedicated guide on what review panels actually score in Broader Impacts statements for how to develop that fuller case.

Where do I submit the Project Summary?

As its own separate document upload within Research.gov, NSF’s proposal preparation and submission system. It is not merged into or appended to the Project Description file. For the full proposal-preparation and submission sequence, see CASRAI’s step-by-step guide to applying for an NSF grant.