NATIONAL SCIENCE FOUNDATION PROPOSAL



[pic]

NSF Checklist

The following checklist is designed for most National Science Foundation proposals. The checklist is designed to help Principal Investigators and grant preparers to see at a glance the elements required for the proposal and to help organize and delegate the work involved in such a proposal.

It is important to remember that particular funding opportunity announcements have specific requirements that may not be included in this checklist, or the checklist may have more than is required for your project. With advance notice, the Office of Sponsored Projects can provide assistance in adapting this checklist for any funding agency or mechanism. Please contact your Sponsored Projects Officer for more information.

This document is designed only to serve as a project management tool. It does NOT replace the detailed information available within the relevant funding opportunity announcement, the funding agency’s forms, instructions, and review criteria. For any questions, please refer to the FOA or contact your program officer.

|Principal Investigator: | |

|RFA in response to (RFA/PA): | |

|Due Dates: | |

|Internal Deadline: | |

|Title of Project: | |

|Co-Principal Investigator(s): | |

|Senior Personnel: | |

|Vertebrate Animals (Yes/No): | |

|Human Subjects (Yes/No): | |

|GPG Instructions Link: | |

| | |

|NSF Proposal Preparation Checklist: | |

|Sponsored Projects Officer: | |

|Document Summary Sheet Number: | |

|Components of Proposal |Elements to Complete |Notes |Person responsible |Internal |Final |

| | | | |Deadline |( |

|Cover Sheet |Fillable form |If Human Subjects involved: | | | |

| | |Include affirmation that IRB has declared the research exempt and provide exemption number(s) OR | | | |

| | |Provide IRB approval date OR | | | |

| | |Indicate if approval is pending (pending means that you have submitted a request for approval or are | | | |

| | |planning to submit prior to grant award) | | | |

| | |Include UofU’s Federal Wide Assurance (FWA) number () | | | |

| | | | | | |

| | |If Vertebrae Animals involved: | | | |

| | |Include approval date from Institutional Animal Care and Use Committee | | | |

| | |() OR | | | |

| | |Indicate if approval is pending | | | |

| | |Include Utah’s Animal Welfare Assurance Number () | | | |

|Project Summary | |Generally limited to 1 page. Must be suitable for publication and entered as text in three discrete | | | |

| | |boxes in FastLane: | | | |

| | |Overview (a self-contained description of the proposed work, including a statement of objectives and | | | |

| | |methods to be employed) | | | |

| | |Intellectual Merit | | | |

| | |Broader Impacts | | | |

| | |NSF has provided resources describing some of the more common broader impacts: | | | |

| | | | | | |

| | |Make sure to address these points in your project description as well. | | | |

| | | | | | |

| | |If your project summary contains special characters that cannot be entered into the FastLane text boxes,| | | |

| | |you must check the applicable box (located just above the Overview text box) indicating that you’re | | | |

| | |uploading a pdf document. The summary must still include the same information, including distinct | | | |

| | |headings for each of the three sections. Upload the summary as a supplementary document after checking | | | |

| | |the appropriate box on the FastLane proposal module. | | | |

| | | | | | |

| | | | | | |

| | | | | | |

|Project Description |See outline below |Generally limited to 15 pages and not include URL’s. Ensure merit review criteria (intellectual merit | | | |

| | |and broader impacts) are well described and integrated throughout. | | | |

| | | | | | |

|Bibliography/References Cited | |Provide a bibliography of all works cited in the project description. Each reference must include the | | | |

| | |names of all authors (in the same order in which they appear on the publication), either the article and| | | |

| | |journal title or the book and chapter title, volume number, page numbers (both starting and ending), and| | | |

| | |year of publication. Do not use “et al.” in references unless the publication has an extremely large | | | |

| | |number of authors (10 or more), even if the reference style you’re using would normally call for it. NSF| | | |

| | |does check the references, and will return proposals without review if they are not formatted correctly.| | | |

| | |If the document cited is available electronically, NSF encourages researchers to include the URL, but | | | |

| | |this is not required. | | | |

| | | | | | |

|Biographical Sketches |Template available |A separate bio sketch (limited to 2 pages) must be provided through use of the NSF-approved format, for | | | |

| | |each individual designated at senior personnel. | | | |

| | | | | | |

| | | | | | |

| | |See and look under NSF Resources for NSF | | | |

| | |Biosketch | | | |

|Budget |$ / Years | | | | |

|Budget Justification |Template available |Generally limited to 3 pages | | | |

| | |See and look under NSF Resources for NSF Budget | | | |

| | |Justification (doc) | | | |

|Facilities |Laboratory |Template available. See and look under NSF | | | |

| | |Resources for NSF Facilities, Equipment, and Other Resources. | | | |

| | | | | | |

| | |Include narrative aggregated description of internal and external resources (physical and personnel) | | | |

| | |directly applicable to project (do not include any quantifiable financial information). | | | |

| | | | | | |

| | |If there are no Facilities, Equipment, etc. to describe, a statement to that effect must be included. | | | |

| |Clinical | | | | |

| |Animal | | | | |

| |Computer | | | | |

| |Office | | | | |

| |Other |e.g., Libraries | | | |

| |Major Equipment | | | | |

| |Other Resources | | | | |

|Current & Pending Support |Template available | | | | |

| | |Current and pending support information must be separately provided through use of an NSF-approved | | | |

| | |format, for each individual designated as senior personnel on the proposal. | | | |

| | | | | | |

| | |See and look under NSF Resources for NSF | | | |

| | |Current and Pending Support | | | |

| | | | | | |

| | |Current and pending support for ongoing projects (including this proposal) requiring time from PI and | | | |

| | |senior personnel: include total award amount and number of person months devoted to the project. | | | |

|Postdoctoral Researcher Mentoring |Required for proposals |See | | | |

|Plan |requesting funding for | | | | |

| |Postdocs. | | | | |

|Data Management Plan |Required for all | | | | |

| |proposals. | | | | |

|Supplementary Documents |Data Management Plan |See for assistance. | | | |

| | |Check the guidelines for the directorate you are applying to for additional instructions | | | |

| | |Data to be produced? | | | |

| | |Standards to be used for data/metadata format and content? | | | |

| | |Policies for access and sharing? For re-use, re-distribution and production of derivatives? | | | |

| | |Plans for archiving and preservation of access? | | | |

| |Letters of Collaboration|Such letters should be limited to stating the intent to collaborate and should not contain endorsements | | | |

| | |or evaluation of the proposed project. Proposals that are not consistent with the instructions in this | | | |

| | |section will be returned without review. | | | |

| | | | | | |

| |Postdoctoral Mentoring |If funding requested to support postdoctoral researchers (1 page) | | | |

| |Plan | | | | |

| |Outside Partners/ | | | | |

| |Subcontracts | | | | |

| |Optional |List of suggested reviewers/reviewers not to include (highly recommended) | | | |

|Suggested Reviewers | | | | | |

|Collaborators & Other Affiliations | | | | | |

|Information | |Collaborators and Other Affiliations information must be separately provided for each individual | | | |

| | |identified as senior project personnel. (See NSF PAPPG, Chapter II.C.1.e.) | | | |

| | |Collaborators and co-Editors. A list of all persons in alphabetical order (including their current | | | |

| | |organizational affiliations) who are currently, or who have been collaborators or co-authors with the | | | |

| | |individual on a project, book, article, report, abstract or paper during the 48 months preceding the | | | |

| | |submission of the proposal. Also include those individuals who are currently or have been co-editors of | | | |

| | |a journal, compendium, or conference proceedings during the 24 months preceding the submission of the | | | |

| | |proposal. If there are no collaborators or co-editors to report, this should be indicated. | | | |

| | |Graduate Advisors and Postdoctoral Sponsors. A list of names of the individuals’s own graduate | | | |

| | |advisors(s) and principal postdoctoral sponsor(s), and their current organizational affiliations, if | | | |

| | |known. | | | |

| | |Thesis Advisor and Postgraduate-Scholar Sponsor. A list of all persons (including their organizational | | | |

| | |affiliations, if known), with whom the individual has had an association as thesis advisor. In addition,| | | |

| | |a list of all persons with whom the individual has had an association within the last five years as a | | | |

| | |postgraduate-scholar sponsor. | | | |

| | |The COA information must be provided through use of the COA template. The template has been developed to| | | |

| | |be fillable, however, the content and format requirements must not be altered by the user. This template| | | |

| | |must be saved in .xlsx format and directly uploaded into FastLane as a Collaborators and Other | | | |

| | |Affiliations Single Copy Document. | | | |

|Special Considerations |Any additional materials| | | | |

| |requested by funding | | | | |

| |agency | | | | |

Project Description Outline

This outline should be customized for individual RFAs and expanded based on initial discussions of the project.

Ensure merit review criteria (intellectual merit and broader impacts) are well described and integrated throughout Project Description.

I. Objectives and expected significance

II. General plan of work undertaken/Methodology

III. Relation to longer term goals of project

IV. Relation to present state of knowledge in field, to work in progress by PI and to work in progress elsewhere

V. What benefits could result if project is successful?

VI. The project description must now contain, as a separate section within the narrative, a section labeled ‘Broader Impacts of the Proposed Work’.

VII. Results from prior NSF support (5-page limit; included within 15 pages). If any PI or co-PI identified on the proposal has received NSF funding with a start date in the past 5 years (including any current funding and no-cost extensions), information on the award is required for each PI and co-PI, regardless of whether the support was directly related to the proposal or not. In cases where the PI or co-PI has received more than one award (excluding amendments to existing awards), they need only report on the one award most closely related to the proposal.

The following information must be provided: 

a) The NSF award number, amount and period of support ;

b) The title of the project ;

c) A summary of the results of the completed work, including accomplishments, supported by the award. The results must be separately described under two distinct headings, Intellectual Merit and Broader Impacts ;

d) A listing of the publications resulting from the NSF award (a complete bibliographic citation for each publication must be provided either in this section or in the References Cited section of the proposal) ; if none, state ‘No publications were produced under this award.’

e) Evidence of research products and their availability, including, but not limited to : data, publications, samples, physical collections, software, and models, as described in any Data Management Plan ; and

f) If the proposal is for renewed support, a description of the relation of th ecompleted work to the proposed work.

VIII. Responsible Conduct of Research (RCR) Statement. If undergraduate/graduate students/postdoctoral researchers involved with project (for a standard NSF RCR statement, see ) .

IX. Vertebrate animals section – Sufficient information must be provided within the 15-page Project Description to enable reviewers to evaluate the:

▪ Rationale for involving animals;

▪ Choice of species and number of animals to be used;

▪ Description of the proposed use of the animals;

▪ Exposure of animals to discomfort, pain, or injury; and

▪ Description of any euthanasia methods to be used.

X. If human subjects are involved, NSF does not prescribe information to be included, but OSP recommends describing the number and demographics of people involved and research safeguards.

Final Word on Status of Proposal:

|Section |Primary Writer/ |Internal Deadlines |

| |Secondary Writers/Editors | |

| | |First Draft |Revisions |Final Copyedit |

|Introduction and Goals | | | | |

|Background | | | | |

|Methods/Project Plan | | | | |

|Timeline | | | | |

|Dissemination Plan | | | | |

|Management Plan | | | | |

|Institutional Environment | | | | |

|Evaluation Plan | | | | |

|Previous NSF-Funded Research | | | | |

Application Process

▪ Proposals to NSF are submitted electronically via the NSF Fastlane System or (for collaborative proposals where the lead has chosen to submit via )

▪ The PI must login to start the application

▪ The PI should make sure his/her profile is up-to-date

▪ If you are new to Fastlane and need an account established, please read the procedure on how to obtain an account ()

▪ Click on “Proposal Functions” and then click on “Proposal Preparation”

▪ Under “Create New Proposal”, click on “Create Blank Proposal”

▪ Go to the Cover Sheet and select the appropriate and select the appropriate Program Announcement/Solicitation and also the appropriate NSF Unit (Directorate). Use the “Go Back” button at bottom of the page to navigate through the system and not the “Back” arrow in the top left corner.

▪ Your actions are automatically saved when you close out the application.

▪ Once the application is started, the PI must then give OSP access to the application. On Proposal Actions screen, highlight the appropriate application from the Temporary Proposals in Progress list and then click on “Allow SRO Access.” A Proposal Errors/Warning Screen will appear; click on “Proceed” and then select “Allow SRO to view and edit”. This will allow OSP to work on the application.

▪ Once the proposal is ready for final review and submission by OSP, Allow SRO submit access.

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download