Chapter III - NSF Proposal Processing and Review
Proposals received by the NSF Proposal Processing Unit are assigned to the appropriate NSF program for acknowledgement and, if they meet NSF requirements, for review. All proposals are carefully reviewed by a scientist, engineer, or educator serving as an NSF Program Officer, and usually by three to ten other persons outside NSF who are experts in the particular fields represented by the proposal. Proposers are invited to suggest names of persons they believe are especially well qualified to review the proposal and/or persons they would prefer not review the proposal. These suggestions may serve as one source in the reviewer selection process at the Program Officer's discretion. Program Officers may obtain comments from assembled review panels or from site visits before recommending final action on proposals. Senior NSF staff further review recommendations for awards. A flowchart that depicts the entire NSF proposal and award process (and associated timeline) is included as GPG Exhibit III-1.
The National Science Foundation strives to conduct a fair, competitive, transparent merit-review process for the selection of projects. All NSF proposals are evaluated through use of two National Science Board approved merit review criteria. In some instances, however, NSF will employ additional criteria as required to highlight the specific objectives of certain programs and activities. For example, proposals for large facility projects also might be subject to special review criteria outlined in the program solicitation.
The two merit review criteria are listed below. The criteria include considerations that help define them. These considerations are suggestions, and not all will apply to any given proposal. While proposers must address both merit review criteria, reviewers will be asked to address only those considerations that are relevant to the proposal being considered and for which the reviewer is qualified to make judgments.
How important is the proposed activity to advancing knowledge and understanding within its own field or across different fields? How well qualified is the proposer (individual or team) to conduct the project? (If appropriate, the reviewer will comment on the quality of prior work.) To what extent does the proposed activity suggest and explore creative, original, or potentially transformative concepts? How well conceived and organized is the proposed activity? Is there sufficient access to resources?
What are the broader impacts of the proposed activity?33
How well does the activity advance discovery and understanding while promoting teaching, training, and learning? How well does the proposed activity broaden the participation of underrepresented groups (e.g., gender, ethnicity, disability, geographic, etc.)? To what extent will it enhance the infrastructure for research and education, such as facilities, instrumentation, networks, and partnerships? Will the results be disseminated broadly to enhance scientific and technological understanding? What may be the benefits of the proposed activity to society?
NSF staff will give careful consideration to the following in making funding decisions:
Integration of Research and Education
One of the principal strategies in support of NSF's goals is to foster integration of research and education through the programs, projects and activities it supports at academic and research institutions. These institutions provide abundant opportunities where individuals may concurrently assume responsibilities as researchers, educators, and students, and where all can engage in joint efforts that infuse education with the excitement of discovery and enrich research through the diversity of learning perspectives.
Integrating Diversity into NSF Programs, Projects, and Activities
Broadening opportunities and enabling the participation of all citizens, women and men, underrepresented minorities, and persons with disabilities, are essential to the health and vitality of science and engineering. NSF is committed to this principle of diversity and deems it central to the programs, projects, and activities it considers and supports.
The NSF guidelines for the selection of reviewers are designed to ensure selection of experts who can give program officers the proper information needed to make a recommendation in accordance with the NSB approved criteria for selection of projects. Optimally, reviewers should have:
- Special knowledge of the science and engineering subfields involved in the proposals to be reviewed to evaluate competence, intellectual merit, and utility of the proposed activity. Within reasonable limits, reviewers’ fields of specialty should be complementary within a reviewer group.
- Broader or more generalized knowledge of the science and engineering subfields involved in the proposals to be reviewed to evaluate the broader impacts of the proposed activity. Reviewers with broad expertise are required for proposals involving substantial size or complexity, broad disciplinary or multidisciplinary content, or significant national or international implications.
- Broad knowledge of the infrastructure of the science and engineering enterprise, and its educational activities, to evaluate contributions to societal goals, scientific and engineering personnel, and distribution of resources to organizations and geographical areas.
- To the extent possible, diverse representation within the review group. The goal is to achieve a balance among various characteristics. Important factors to consider include: type of organization represented, reviewer diversity, age distribution and geographic balance.
It is the responsibility of the proposing organization to thoroughly review each proposal prior to submission. On occasion, however, a problem is identified with a portion of the proposal after the proposal has been submitted electronically to NSF.
The FastLane Proposal File Update Module allows the organization to request the replacement of files or revision of other Proposal Attributes, associated with a previously submitted proposal. A request for a proposal file update must be submitted by an individual who is authorized to submit proposals on behalf of the organization, and electronically signed by the Authorized Organizational Representative (AOR). An update request must contain a justification that addresses:
- why the changes or file replacements are being requested; and
- any differences between the original and proposed replacement files.
A request for a proposal file update automatically will be accepted if submitted prior to:
- the deadline date specified in a program solicitation;
- initiation of external peer review in cases when a target date is utilized;34 and
- initiation of external peer review in the case of an unsolicited proposal.
A request for a proposal file update after the timeframes specified above will require acceptance by the cognizant NSF Program Officer. Such requests may be submitted only to correct a technical problem with the proposal (i.e., formatting or print problems). Changes in the content of the proposal should not be requested after the timeframes specified above. When a request is accepted, the proposed files or revisions to proposal attributes will immediately replace the existing files and become part of the official proposal.
PIs can access the Proposal File Update Module via the "Proposal Functions" section of FastLane. Authorized individuals in the organization’s Sponsored Projects Office (or equivalent) can initiate or review requests for proposal file updates using the "Submit Proposals/Supplements/File Updates/Withdrawals" Module via the FastLane "Research Administration Functions.35
NSF will consider only one request for a proposal file update per proposal at a time. It is anticipated that it will be a rare occurrence for more than one file update request to be submitted for a proposal.
In the event of a significant development (e.g., research findings, changed circumstances, unavailability of PI or other senior personnel, etc.) that might materially affect the outcome of the review of a pending proposal, the proposer must contact the cognizant Program Officer to discuss the issue. Submitting additional information must not be used as a means of circumventing page limitations or stated deadlines.
Before recommending whether or not NSF should support a particular project, the NSF Program Officer may, subject to certain constraints outlined below, engage in discussions with the proposing PIs.
Negotiating budgets generally involves discussing a lower or higher amount of total support for the proposed project. The NSF Program Officer may suggest reducing or eliminating costs for specific budget items that are clearly unnecessary or unreasonable for the activities to be undertaken, especially when the review process supports such changes; however, this would generally not include faculty salaries, salary rates, fringe benefits, or tuition. Note: indirect cost rates are not subject to negotiation. The NSF Program Officer may discuss with PIs the “bottom line” award amount, i.e., the total NSF funding that will be recommended for a project. NSF Program Officers may not renegotiate cost sharing or other organizational commitments.
When such discussions result in a budget reduction of 10% or more from the amount originally proposed, a corresponding reduction should be made in the scope of the project. Proposers must use the FastLane Revised Proposal Budget Module to submit this information. A revised proposal budget also must include a Budget Impact Statement that describes the impact of the budget reduction on the scope of the project.
Revised proposal budgets must be electronically signed by the AOR.
After scientific, technical and programmatic review and consideration of appropriate factors, the NSF Program Officer recommends to the cognizant Division Director whether the proposal should be declined or recommended for award. Normally, final programmatic approval is at the division/office level. Because of the large volume of proposals, this review and consideration process may take up to six months. Large or particularly complex proposals may require additional review and processing time. If the program recommendation is for an award and final division/office or other programmatic approval is obtained, then the recommendation goes to the Division of Grants and Agreements for review of business, financial and policy implications and the processing and issuance of a grant or cooperative agreement. The Division of Grants and Agreements generally makes awards to academic institutions within 30 days after the program division/office makes its recommendation. Grants being made to organizations that have not received an NSF award within the preceding two years, or involving special situations (such as coordination with another Federal agency or a private funding source), cooperative agreements, and other unusual arrangements may require additional review and processing time.
Proposers are cautioned that only an appointed NSF Grants and Agreements Officer may make commitments, obligations or awards on behalf of NSF or authorize the expenditure of funds. No commitment on the part of NSF or the Government should be inferred from technical or budgetary discussions with an NSF Program Officer. A PI or organization that makes financial or personnel commitments in the absence of a grant or cooperative agreement signed by the NSF Grants and Agreements Officer does so at its own risk.
When a decision has been made (whether an award or a declination), the following information is released electronically to the PI through FastLane:
- description of the context in which the proposal was reviewed;
- copies of all reviews used in the decision (with any reviewer-identifying information redacted);
- copy of panel summary, if the proposal was reviewed by a panel at any point in the process;
- site-visit reports, if applicable.
In addition, if not otherwise provided in the panel summary, the PI is provided an explanation (written or telephoned) of the basis for the declination. A PI also may request and obtain any other releasable material in NSF's file on his/her proposal. Everything in the file, except information that identifies either reviewers or other pending or declined proposals is usually releasable to the PI.
A proposal that results in an NSF award will be available to the public on request, except for privileged information or material that is personal, proprietary or otherwise exempt from disclosure under law. Appropriate labeling in the proposal aids identification of what may be specifically exempt. (See GPG Chapter I.D.3) Such information will be withheld from public disclosure to the extent permitted by law, including the Freedom of Information Act. Without assuming any liability for inadvertent disclosure, NSF will seek to limit disclosure of such information to its employees and to outside reviewers when necessary for merit review of the proposal, or as otherwise authorized by law.
Portions of proposals resulting in grants that contain descriptions of inventions in which either the Government or the grantee owns a right, title, or interest (including a non-exclusive license) will not normally be made available to the public until a reasonable time has been allowed for filing patent applications. NSF will notify the grantee of receipt of requests for copies of funded proposals so the grantee may advise NSF of such inventions described, or other confidential, commercial or proprietary information contained in the proposal.
33 Examples illustrating activities likely to demonstrate broader impacts are available electronically on the NSF website at https://www.nsf.gov/pubs/gpg/broaderimpacts.pdf. Back to Text
34 The status of a proposal may be found via the "Proposal Functions" section of FastLane. Back to Text
35 Detailed instructions on submitting proposer-initiated proposal file updates are available on the FastLane website at https://www.fastlane.nsf.gov/documents/pfu/pfu.jsp. Back to Text