NSF continues to focus on the automated compliance checks of proposals in order to decrease the burden on both the research community and NSF staff. Effective July 25, 2016, all proposals will be subject to a new series of automated compliance validation checks to ensure proposals comply with requirements outlined in Chapter II.C.2. of the Proposal and Award Policies and Procedures Guide (PAPPG).
The new set of automated compliance checks will trigger error messages for each of the following rules:
oBiographical Sketch(es) and Current and Pending Support files are required for each Senior Personnel associated with a proposal; and
oBiographical Sketch(es) can only be uploaded as a file, must not exceed two pages and can no longer be entered as text.
Note About Proposal File Update (PFU):
Proposers should be aware should that if a proposal was received prior to July 25 and contained only one Biographical Sketch and/or Current & Pending Support file (rather than individual files for each senior personnel), a PFU addressing any section of the proposal will result in the proposal not being accepted if it does not comply with these new compliance checks. The checks will be run on all sections of the proposal regardless of which section was updated during the PFU.
Note About Grants.gov:
Proposers should also be aware that Grants.gov will allow a proposal to be submitted, even if it does not comply with these proposal preparation requirements. Should NSF receive a proposal from Grants.gov that is not compliant, it will be returned without review.
Please note that the new set of compliance checks are in addition to the compliance checks that currently exist in FastLane. You can view a complete list of FastLane auto-compliance checks, including these checks, by clicking here . The list specifies which checks are run depending on funding opportunity type (GPG, Program Description, Program Announcement, or Program Solicitation) and type of proposal (Research, RAPID, EAGER, Ideas Lab, Conference, Equipment, International Travel, Facility/Center, or Fellowship). It also specifies whether the check triggers a “warning” or “error” message for non-compliant proposals.