NSF S-STEM Projects Meeting

Strengths, Challenges, Insights & Areas for Improvement

Session Title: NSF Annual and Final Reports

Room: Salon B

Scribe’s Name: Guillermo Francia, III

Lead’s Name: Christopher F. Sacchi

Please use this template to capture the main points from the discussion in your session. Add additional rows as needed. You should not attempt to transcribe the meeting, but note the main discussion points as they fall within the SCII framework. Scribes should be sure to note any points of consensus and capture any strongly held monitory views within your group.

Scribes must use their own computer to take notes. A computer will not be provided to you. Please bring your own computer to your assigned session for note taking. Please make sure you have this template saved on your computer prior to the meeting.

I. Strengths Envisioned

1. STEM Demographics report is a nice tool for keeping track of student records and activities
2. Facility for a narrative type report where additional information can be included.
3. Feedbacks from program officer are very informative and encouraging.
4.
5.

Additional Notes:

  1. Challenges Encountered

  1. Bibliography section is confusing

  1. Concerns whether to include all personnel in the report regardless of whether they are remunerated

  1. There are concerns about what gets into the Public Obligation Report (POR).

5.

Additional Notes:

III. Insights Obtained

  1. Although there is a 90-day reporting period, you need to file your report as soon as possible. The Program Officer has many reports to review.

  1. Annual report is a formative report. Final report is a summative report.

  1. The form is identical for final report and annual report. May need to restructure these.

  1. Student names should never be revealed due to confidentiality agreement. You may include their names in publications if the student is a co-author.

  1. Evaluator does not need to be an external person but someone who is independent from the project.

  1. Once a final report is submitted, the project is closed and no expenses are allowed.

  1. The reporting system is going to move to Research.gov.

  1. Some interesting stuff that NSF wants to read in reports are: formation of learning communities, adjustments on activities to improve on what is not working, and challenges encountered on the original intent.

  1. Research publications with students can be included in the report.Make sure that the award information and disclaimer are included in the Acknowledgement section.

  1. Keep track of students by preparing an electronic journal that they can fill up every two weeks. This will provide most of the data needed for reporting purposes.

  1. Keep your records in case you get audited by the State or Federal government.

  1. Your own STEM demographic data can be downloaded in Excel format

  1. Generally, do not send raw data. Provide a summary of how project activities are going both qualitatively and quantitatively.

Additional Notes:

  1. Areas for Improvement

  1. Need to figure out the difference between annual report and final report.

  1. There is a need to make sure Fastlane is flexible for requiring annual reports on certain projects that have extenuating circumstances.

  1. There is a need to be able to view the report while being written.

4.
5.

Additional notes:

Before the end of the session, please take some time to clean up your notes, and email them to Tengiz Sydykov - . Please coordinate with your Session Chair to make sure you have sufficient time to clean up your notes prior to the end of the session. Tengiz will pull together the notes from all of the breakout sessions and will post the notes on-line prior to the next breakout session.