JOB SUMMARY

The Office of the Vice President for Research at the University of Connecticut is seeking a highly dynamic, creative, and driven professional to assist in the management of an institutional initiative in Stamford, CT focused on data science. The UConn Data Science Initiative revolves around the establishment of a data science tech incubator, the hiring of data science research faculty, and the creation of a year-long entrepreneurial co-op opportunity for undergraduate students.  The Program Coordinator (Education Program Coordinator) will be a self-starting, team player, motivated to contribute novel and fresh ideas to grow each dimension of the initiative in a manner that supports the institution, the region, and the overall economic development of the State.

DUTIES AND RESPONSIBILITIES

• Assisting with various logistical and administrative duties related to the UConn Data Science Initiative (purchasing, hiring, scheduling, travel, etc.).
• Supporting the marketing and communications objectives of the initiative (including the management of the social media campaign, design and copy for various print/digital promotional materials, etc).
• Working with the executive director of the initiative to develop a sustainable budgetary model and plan for growth/expansion of the initiative.
• Assisting with the creation of quarterly written reports delineating progress and milestone achievements of the initiative.
• Maintaining an accurate system for billing tenants of the data science incubator (including keeping track of rates, sending invoices, collecting payment, etc.)
• Supporting the recruitment efforts of the initiative (assisting with the identification of, and communication with, prospective incubator tenants as well as potential data science faculty).
• Providing strategic analytics around data science in the region and working to develop an action plan for establishing new partnerships.
• Working with financial staff to maintain oversight on project budgets and developing budgetary projections.
• Creating a series of technical and social events to build community among the occupants of the data science initiative space.
• Overseeing student employees (including hiring and determining work assignments/schedules).
• Assisting data science faculty in the identification of potential funding opportunities from the public and private sectors.
• Serving as a point of contact for data science initiative inquiries.
• Other related duties as required

MINIMUM QUALIFICATIONS

1. Bachelor’s degree in an appropriate/related subject matter.
2. At least 4 years of related experience, demonstrating considerable knowledge of administrative methods and program support in the area(s) of marketing, industry relations, technology commercialization, startup venture development, or comparable areas.
3. Superior verbal, written and interpersonal communication skills.
4. Superior organizational skills and follow-through.
5. Superior accuracy and attention to formatting and detail.
6. Evidence of creative, out-of-the-box, thinking.
7. Ability to synthesize large amounts of information into concise analytical reports.
8. Experience with event planning and management and/or managing a complex calendar or schedule of activities.
9. Demonstrated experience developing program support materials (both web and print), graphics, and using social media platforms for outreach and communications.
10. Willingness and ability to carry out job responsibilities in Stamford and occasionally at the Storrs and Farmington locations.
11. Proficiency with Microsoft Office suite software, but more importantly, online technology tools aimed at improving productivity and efficiency.
12. Ability to work a flexible schedule to include evenings and weekends, as required by programming.
13. Demonstrated ability to work independently and exercise a high degree of professional discretion and confidentiality in communicating with executives and officials across a variety of industries in the public and/or private sectors.

PREFERRED QUALIFICATIONS

1. Graduate degree in an appropriate discipline.
2. Experience working in data science.
3. Experience working in the fintech and/or digital media industries.
4. Experience developing public/private partnerships.
5. Hands-on experience working with or within universities.
6. Experience implementing design thinking with a general ability to bridge design, communication, and technology.
7. Experience simultaneously managing complex programs and budgets.

APPOINTMENT TERMS

This is a one-year, full-time, grant-funded, annually renewable position. Salary in the high $60’s. The University offers an excellent benefits package including medical and retirement, as well as employee and dependent tuition reimbursement at the University of Connecticut (outlined here:  https://hr.uconn.edu/benefits-beyond-pay/).  Screening of applications will begin immediately and continue until the position is filled, with a target start date of as soon as possible.

TO APPLY

Please apply online at https://hr.uconn.edu/jobs, Staff Positions, Search #494735 to upload a resume, cover letter, and contact information for three (3) professional references.

Employment of the successful candidate is contingent upon the successful completion of a pre-employment criminal background check.

This job posting is currently scheduled to be removed at 11:55 p.m. Eastern time on September 28, 2020.

All employees are subject to adherence to the State Code of Ethics which may be found at http://www.ct.gov/ethics/site/default.asp.

The University of Connecticut is committed to building and supporting a multicultural and diverse community of students, faculty and staff. The diversity of students, faculty and staff continues to increase, as does the number of honors students, valedictorians and salutatorians who consistently make UConn their top choice. More than 100 research centers and institutes serve the University’s teaching, research, diversity, and outreach missions, leading to UConn’s ranking as one of the nation’s top research universities. UConn’s faculty and staff are the critical link to fostering and expanding our vibrant, multicultural and diverse University community. As an Affirmative Action/Equal Employment Opportunity employer, UConn encourages applications from women, veterans, people with disabilities and members of traditionally underrepresented populations.

 

 

The University of Connecticut Institutional Review Board (IRB) recognizes that some research projects involving existing data sets and archives may not meet the definition of “human subjects” research requiring IRB review; some may meet definitions of research that is exempt from the federal regulations at 45 CFR part 46; and some may require IRB review. This document is intended to provide guidance on IRB policies and procedures and to reduce burdens associated with IRB review for investigators whose research involves only the analysis of existing data sets and archives. The IRB acknowledges the guidance document prepared by the University of Chicago Social and Behavioral Sciences IRB as the model for this Guidance.

Although projects that only involve secondary data analysis do not involve interactions or interventions with humans, they may still require IRB review, because the definition of “human subject” at 45 CFR 46.102(f) includes living individuals about whom an investigator obtains identifiable private information for research purposes.

1. When does secondary use of existing data not require IRB review?

In general, the secondary analysis of existing data does not require IRB review when it does not fall within the regulatory definition of research involving human subjects.

A. Public Use Data Sets

Public use data sets are prepared with the intent of making them available for the public. The data available to the public are not individually identifiable and therefore analysis would not involve human subjects. The IRB recognizes that the analysis of de-identified, publicly available data does not constitute human subjects research as defined at 45 CFR 46.102 and that it does not require IRB review. The IRB no longer requires the registration or review of studies involving the analysis of public use data sets unless a project merges multiple data sets and in so doing enables the identification of individuals whose data is analyzed. An IRB review may be required for a research study that relies exclusively on secondary use of anonymous information BUT records data linkage or disseminates results in such a way that it generates identifiable information.

In addition to being identifiable, existing data must include “private information” in order to constitute research involving human subjects. Private information is defined as information which has been provided for specific purposes by an individual and which the individual can reasonably expect will not be made public (e.g., a medical or school record). For example, a study involving only analysis of the published salaries and benefits of university presidents would not need IRB review since this information is not private.

B. De-identified Data

If a dataset has been stripped of all identifying information and there is no way it could be linked back to the subjects from whom it was originally collected (through a key to a coding system or by other means), its subsequent use by the Principal Investigator or by another researcher would not constitute human subjects research, since the data is no longer identifiable. “Identifiable” means the identity of the subject is known or may be readily ascertained by the investigator or associated with the information. In general, information is considered to be identifiable when it can be linked to specific individuals by the researcher either directly or indirectly through coding systems, or when characteristics of the information obtained are such that a reasonably knowledgeable person could ascertain the identities of individuals. Even though a dataset has been stripped of direct identifiers (e.g., names, addresses, student ID numbers, etc.), it may still be possible to identify an individual through a combination of other characteristics (e.g., age, gender, ethnicity, place of employment).

Example: Many student research projects involve secondary analysis of data that belongs to, or was initially collected by, their faculty advisor or another investigator. If the student is provided with a de-identified, non-coded data set, the use of the data does not constitute research with human subjects because there is no interaction with any individual and no identifiable private information will be used.

Coded data: Secondary analysis of coded private information is not considered to be research involving human subjects and would not require IRB review IF the investigator(s) cannot readily ascertain the identity of the individuals to whom the coded private information pertains as a result of one of the following circumstances:

1. The investigators and the holder of the key have entered into an agreement prohibiting the release of the key to the investigators under any circumstances, until the individuals are deceased (HHS regulations for humans subjects research do not require the IRB to review and approve this agreement);
2. There are IRB-approved written policies and operating procedures for a repository or data management center that prohibit the release of the key to the investigator under any circumstances, until the individuals are deceased; or
3. There are other legal requirements prohibiting the release of the key to the investigators, until the individuals are deceased.

For more information on when analysis of coded data is or is not human subjects research, see the HHS Office for Human Research Protections Guidance on Research Involving Coded Private Information or Biological Specimens at http://www.hhs.gov/ohrp/policy/cdebiol.html.

Note: If a student is analyzing coded data from a faculty advisor/sponsor who retains a key, this would be human subjects research, because the faculty advisor is considered an investigator on the student’s protocol, and can readily ascertain the identity of the subjects since he/she holds the key to the coded data. If the student’s work fits within the scope of the initial protocol from which the dataset originates, the faculty advisor (or investigator who holds the dataset) may wish to consider adding the student and his/her work to the original protocol by means of an amendment application rather than having the student submit a new application for review.

Example: Researcher B plans to examine the relationships between attention deficit hyperactivity disorder (ADHD), oppositional defiance disorder, and teen drug abuse using data collected by Agencies I, II, and III that work with “at risk” youth. The data will be coded and the agencies have entered into an agreement prohibiting release of the key to the researcher that could connect the data with identifiers. The use of the data would not constitute research with human subjects.

If the IRB determines that the project does not constitute human subjects research, the IRB will notify the investigator. If the IRB determines that the project does involve human subjects research, the investigator will be asked to submit a protocol for consideration by the IRB.

2. When is the secondary use of existing data exempt?

There are six categories of research activities involving human subjects that may be exempt from the requirements of the federal regulations on human subjects research protections (45 CFR 46.101(2)(b)). However, only one exemption category (Category 4) applies specifically to existing data. If research is found to be exempt, it need not receive full or expedited review. In order to qualify for an exempt determination, an IRB-5 application must be submitted in InfoEd for IRB review.

Research involving collection or study of existing data, documents, and records can be exempted under Category 4 of the federal regulations if: (i) the sources of such data are publicly available; or (ii) the information is recorded by the investigator in such a manner that subjects cannot be identified, directly or through identifiers linked to the subjects.

The latter condition of this category applies in cases where the investigators initially have access to identifiable private information but abstract the data needed for the research in such a way that the information can no longer be connected to the identity of the subjects. This means that the abstracted data set does not include direct identifiers (names, social security numbers, addresses, phone numbers, etc.) or indirect identifiers (codes or pseudonyms that are linked to the subject’s identity). Furthermore, it must not be possible to identify subjects by combining a number of characteristics (e.g., date of birth, gender, position, and place of employment). This is especially relevant in smaller datasets, where the population is confined to a limited subject pool.
The following do not qualify for exemption: Research involving prisoners, and FDA-regulated research.

Example: Student A will be given access to data from her faculty advisor’s health survey research project. The data consists of coded survey responses, and the advisor will retain a key that would link the data to identifiers. The student will extract the information she needs for her project without including any identifying information and without retaining the code. The use of the data does constitute research with human subjects because the initial data set is identifiable (albeit through a coding system); however, it would qualify for exempt status.

3. When does the secondary use of existing data require expedited or full board review?

If secondary analysis of existing data does involve research with human subjects and does not qualify for exempt status as explained above, the project must be reviewed either through expedited procedures or by the full (convened) IRB, and an IRB-1 protocol application must be submitted in InfoEd for IRB review.

Consent: Researchers using data previously collected under another study should consider whether the currently proposed research is a “compatible use” with what subjects agreed to in the original consent form. For non-exempt projects, a consent process description or justification for a waiver must be included in the research protocol.

The IRB may require that informed consent for secondary analysis be obtained from subjects whose data will be accessed.

Alternatively, the IRB can consider a request for a waiver of one or more elements of informed consent under 45 CFR 46.116(d). In order to approve such waiver, the IRB must first be satisfied that the research:

1. presents minimal risk (no risks of harm, considering probability and magnitude, greater than those ordinarily encountered in daily life or during the performance of routine examinations or tests); and
2. the waiver or alteration will not adversely affect the rights and welfare of the subjects; and
3. the research could not practicably be carried out without the waiver or alteration; and
4. whenever appropriate, the subjects will be provided with additional pertinent information after participation.

“Restricted Use Data”: Certain agencies and research organizations release files to researchers with specific restrictions regarding their use and storage. These restrictions are typically described in a data use or restricted use data agreement the organization requires be signed in order to receive the data. The records frequently contain identifiers or extensive variables that combined might enable identification, even though this is not the intent of the researcher. Research using these data sets requires expedited or full board level review. Note that the data use or restricted use data agreement must be reviewed by Sponsored Programs Services (SPS) prior to institutional approval. The IRB will not approve the study until the agreement receives approval by SPS. The protocol may be submitted to the IRB at the same time the agreement is submitted to SPS.

Examples:

1) Student C will be given access to coded mental health assessments from his faculty advisor’s research project. The student plans to analyze the data with a code attached to each record, and the advisor will retain a key to the code that would link the data to identifiers. The use of the data does constitute research with human subjects and does not qualify for exempt status since subjects can be identified. This student project would require an IRB-1 protocol application to be submitted in InfoEd for expedited or full board review by the IRB.

Note: As previously noted, if the student’s work fits within the scope of the initial protocol from which the dataset originates, the faculty advisor (or investigator who holds the dataset) may wish to consider adding the student and his/her work to the original protocol by means of an amendment application rather than having the student submit a new application for expedited or full board review.

2) Student D is applying to the National Center for Health Statistics for use of data from the National Health and Nutrition Examination Survey that includes geographic identifiers and date of examination. The analysis of this restricted use data would require IRB-1 protocol application to be submitted in InfoEd for expedited or full board review by the IRB.

 

Back to Researcher’s Guide

A completion report is required for all human subject studies. The closure report updates the IRB on the conduct and the outcomes of the study, any new risks, safety issues or problems that may have arisen since the last study renewal, and informs the IRB of the final disposition of research records and data.

Completion reports should be submitted to the IRB within 30 days of study completion by completing the IRB-2 Re-Approval/Completion report application in InfoEd. Note: The PI does not have to wait for the end of the study approval period to submit a completion report.

If any of the following six conditions apply do not file a completion report. Such studies must remain active and continue to receive ongoing IRB review and approval:

1. Enrollment is on-going.
2. Research-related interventions and/or follow-up is ongoing.
3. Participant follow-up is ongoing.
4. Biological specimens containing personally identifiable information are being maintained in a repository that has been approved as part of this study or upon which analysis or research is ongoing. If, however, specimens were transferred to a separate repository that has ongoing IRB approval, the study may be closed.
5. Data analysis or manuscript preparation that involves the use or access to personally identifiable information is ongoing.
6. If there is an external study sponsor and the sponsor has not provided permission to close the study with the IRB.

 

Report Study Completion Procedures

Complete the IRB-2 Re-Approval/Completion Form in InfoEd.

• Provide the date the study was completed in the Status of Study section.
• Provide a copy of the final DSMB report if applicable.
• Provide a summary of the findings and provide copies of any publications or manuscripts resulting from the study.
• Complete sections VI, VII, VII and IX, if applicable.

Record Retention

The IRB would like to remind investigators that data from the completed study should be stored and protected in the manner approved by the IRB and consented to by the research participant so as to maintain the privacy and confidentiality of the participants. Whenever possible, the data should be permanently de-identified. Also, at a minimum, per federal regulations (45 CFR 46.115(b) and 21 CFR 56.115(b)), investigators must maintain research records for three years beyond the completion/termination of the study. Investigators should be aware that other laws and requirements (e.g., funding agency) may require a longer record retention period.

Refer to the IRB’s record retention policy for additional guidance – https://ovpr.uconn.edu/irb/irb-policies-and-procedures-intro/record-retention/.

 

Serious Adverse Events or Unanticipated Problems Learned After Study Closure

The PI must report to the IRB any information learned after study closure that could affect participant safety or care, including but not limited to serious adverse events or unanticipated problems report by the Sponsor or other responsible for study monitoring.

 

Back to Researcher’s Guide

Listed below are various self-service handouts and instructional sheets with step-by-step instructions on how to perform various functions within the UConn (Storrs/Regional Campus) InfoEd External Interests / FCOI & FCO system.

These materials are specific to UConn (Storrs and Regional Campuses) and should not be used by persons from UConn Health unless specifically instructed to do so by the FCOI staff.

• Quick Reference Guide New – for UConn Storrs and Regional Campuses only
• Create an Initial Financial Interest Disclosure New – for UConn Storrs and Regional Campuses only
• Edit or Resubmit a Financial Interest Disclosure New – for UConn Storrs and Regional Campuses only
• View, Print, Download or Save a Financial Interest Disclosure  New – for UConn Storrs and Regional Campuses only
• Turning Off Pop-up Blocking on Various Web Browsers Updated

MAC USERS:  Safari blocks popups by default. To have a better experience with the FCOI eform, please follow these steps to allow popups on your machine: https://content.research.uconn.edu/pdf/storrs/rits/infoed/PopupBlocker.pdf  Or, use something other than Safari for completion of the FCOI eform.

NEW: On March 1, 2024, the Office of the Vice President for Research launched a revised FCOI disclosure e-form (see: announcement shared with the UConn research community).

If you have questions about the requirements to submit an annual financial disclosure, please contact Ms. Kristen Tremblay (kristen.tremblay@uconn.edu or 860.679.3276) or fcoi@uconn.edu.

For technical issues with InfoEd, please email era-support@UConn.edu or call 860.486.7944.

Please choose your system role to view tailored assistance:

• • • Faculty/PI
    • Departmental Staff
    • Department Head

 

Faculty Member/Principal Investigators ERC Help

Quick Guides:

• • • Certifying an Effort Report (pdf)
    • Certifying an Effort Report with Multiple PIs (pdf)
    • Understanding My Reports (pdf)
    • Submitting a Commitment Change (pdf)
    • Commitment Comparison Quick Guide
    • Commitment by Project-Person Screens Quick Guide

 

Frequently Asked Questions:

• • • What is effort reporting?
    • Who can certify an effort report?
    • How do I certify an effort report?
    • Who needs to have their effort certified?
    • What is included in the effort reports?
    • What do the percentages on the effort report mean?
    • How do I add a project to an effort report?
    • What should I review prior to certification?
    • How does the effort report routing work?
    • How does routing/certification work when someone works for multiple PIs?

 

What is effort reporting?

Effort reporting (or effort certification) is UConn’s means of assuring sponsors that:

• • • The commitment of effort (proposed or otherwise obligated) to the project was met
    • The effort expended on the project was at least commensurate with the salary charged
    • Effort devoted to research and other sponsored projects was properly accounted for

This is not “timekeeping” or “activity tracking”. Actual effort should be reported in whole percentages. Voluntary uncommitted effort (effort on a project that was not charged to a sponsored program and was not committed to the sponsor) should not be included on the effort report.
_{Return to Frequently Asked Questions}

 

Who can certify an effort report?

Faculty are expected to certify their own reports. Graduate and undergraduate students’ reports are certified by the PI of each project listed. Staff reports can be certified by the individual or the PI of each project; however, most schools prefer that the PI certifies these reports as well. Department Heads may certify for the PI or individual if they have left the university or are unavailable to certify.
_{Return to Frequently Asked Questions}

 

How do I certify an effort report?

When an effort report is routed to you, you will receive an email notification. Click on the link provided in the email or click here to log into the ERC system. You can access the effort report directly from the email or via your worklist (the default application page). Double-click on the report line to access the report. Once in the report, you will need to enter the Actual Effort worked for each project for the reporting period. If the calculated amounts are correct, you may simply auto-populate those amounts by clicking on the “Default to Calculated Amounts” link above the Actual Effort column. Click on Submit to approve/certify the report (or to return the report to your department administrator or to SPS, if needed). Please see our Quick Guide for Certifying an Effort Report for a detailed guide with screenshots.
_{Return to Frequently Asked Questions}

 

Who needs to have their effort certified?

For each effort reporting period, effort reports are generated for each employee whose salary is charged to a sponsored award and for each employee with an effort commitment on a sponsored award. This includes faculty, staff, post docs, graduate students and undergraduate students. Only non-students are able to certify their own reports.
_{Return to Frequently Asked Questions}

 

What is included in the effort reports?

An individual’s report will reflect all of their University activities – totaling 100% regardless of the actual hours worked. All non-sponsored activities are reflected in the “All other sources associated with your appointment” line. Effort reports are generated three times a year (Fall, Spring and Summer – see SPS Academic Calendar for dates) for all individuals who were paid from or had effort commitments on sponsored awards.
_{Return to Frequently Asked Questions}

 

What do the percentages on the effort report mean?

The Calculated Effort column includes the percentage of salary paid on the project plus any cost shared commitment made to the project which was entered in the ERC application. The percentage is calculated when the effort report is generated. Commitments recorded in the ERC system may be viewed through the Commitment Comparison screen (see Commitment Comparison Quick Guide).

The Actual Effort column is entered by the certifier at a project level. This amount should reflect a reasonable approximation of the effort devoted to the project during the reporting period.
_{Return to Frequently Asked Questions}

 

How do I add a project to an effort report?

While in the effort report, click on the Add Another Project link and then search for an award (by PI Name, KFS Account Number, InfoEd Proposal Number or Sponsor Award Number) to add a project. This functionality is only available when the report is currently routed to you for certification.

It is highly recommended that a report be returned to your department or SPS (see Quick Guide for Certifying an Effort Report) if there should have been pay on the missing project or if there should have been a cost share commitment recorded in our system.
_{Return to Frequently Asked Questions}

 

What should I review prior to certification?

Review the effort report to ensure that all projects with paid or committed effort have been reflected on the report. You may also review the Effort Report Details to review the current commitments in the system.
_{Return to Frequently Asked Questions}

 

How does the effort report routing work?

Changes are allowed ONLY when the report is currently routed to you. Only the PIs or the individual listed on a report can enter the Actual Effort. You can view any report involving your awards at any time in the route.
_{Return to Frequently Asked Questions}

 

How does routing/certification work when someone works for multiple PIs?

Following the initial department administrator review, the effort report will route to all PIs listed on the report as well as the individual themselves, for non-students. For example, the report for a graduate student working on two different PIs’ awards will route to both PIs at the same time. The first PI who logs into the report will see all Actual Effort fields “unlocked”. After the first PI certifies, when the second PI certifies the report, the Actual Effort for the first PI’s award will be locked. The “All other sources associated with your appointment” line will remain unlocked.
_{Return to Frequently Asked Questions}

 

 

Departmental Staff ERC Help

We are in the process of developing additional guidance for Department Administrators.  In the interim, please review the training slides below.  Contact Jen Lamontagne (jennifer.lamontagne@uconn.edu) or Kristin Winot (kristin.winot@uconn.edu) for additional assistance.

• • • ERC Department Admin Training (pdf)

 

 

Department Head ERC Help

We are in the process of developing a guide for Department Heads to claim and certify an effort report when the PI is otherwise unavailable.  In the interim, please contact Jen Lamontagne (jennifer.lamontagne@uconn.edu) or Kristin Winot (kristin.winot@uconn.edu) for assistance with this functionality.

Please view the Faculty Help Section for additional information.

ERC is an enterprise-level, web-based application designed to manage sponsored program effort. The system consists of two major aspects – commitments and effort reporting. The commitments section is used to track details for all effort commitments made to the sponsor by individual and by project. The effort reporting section is used to generate, review and certify effort reports. By using this system, University faculty and staff are able to electronically certify their reports.

Link to ERC: https://erc.research.uconn.edu

Request ERC Access

The Effort Reporting & Commitments (ERC) application is secured with the UConn NetID single sign-on. All users are required to have a valid UConn NetID. UConn faculty and staff are automatically set up with an account.  Department Heads are also automatically assigned and managed in the system.

1. If you have an UConn NetID, first try to see if you can login to the ERC system at https://erc.research.uconn.edu.
2. If you cannot login, make sure you are using your correct NetID and password combination or your correct username and password. Consult the https://netid.uconn.edu website tools to verify your NetID and password credentials or contact the eRA Help Desk at era-support@uconn.edu or 860-486-7944.

If you still cannot access the ERC application after verifying your correct credentials and attempting to login, contact the eRA Help Desk at 860-486-7944 to verify that you have an account on the particular system. If you do not have an account or you need additional permissions, you can request access by completing the ERC Access Request Form.

This form is primarily used to request additional security permissions (e.g. a Departmental Administrator requesting access to review and route effort reports for their department/school). You may type directly on the form and print it. The form must be signed by the applicant and the applicant’s supervisor.

• ERC Account Request Form – A fillable PDF file

Effort Reporting & Commitments (ERC) Application Training

ERC is an enterprise-level, web-based application designed to manage sponsored program effort. The system consists of two major aspects – commitments and effort reporting. The commitments section is used to track details for all effort commitments made to the sponsor by individual and by project. The effort reporting section is used to generate, review and certify effort reports. By using this system, University faculty and staff are able to electronically certify their reports.

Link to ERC: https://erc.research.uconn.edu/erc/

Name	Training Area	Phone	Email
Jennifer Lamontagne	Manager, Effort & Data Reporting Services	860.486.4858	jennifer.lamontagne@uconn.edu
Kristin Winot	Effort Reporting Specialist	860.486.5067	kristin.winot@uconn.edu

 

For 9 and 10 Month Faculty

Training sessions were offered in July 2016 with instructions for charging salaries to sponsored program accounts specifically related to 9 and 10 month faculty whose salary will be automatically accrued beginning in Academic Year 2016-17 (effective 8/23/2016).  Please contact Jen Lamontagne with questions.

• UConn Salary Calculator (available here)
• Presentation Slides

 

For salary expenses in Academic Year 2014-15 and Academic Year 2015-16, the following instructions apply.

Training sessions were offered throughout February 2015 with instructions for charging salaries to sponsored program accounts specifically related to 9 and 10 month faculty who are direct charged to a grant, contract or designated match account during the academic year.  Training materials from those sessions are provided below.

• Salary Calculator and Payroll Authorization Examples (available upon request)
• Additional Guidance: Flowchart 9 & 10 Month Employees Under 75% Grant Funded
• Additional Guidance: Example for 9 & 10 Month Employees Under 75% Grant Funded (available upon request)
• OVPR SPS Salary Calculator for payroll BEFORE 8/22/2016 (available upon request)

 Fall Semester

Activity	Timeframe
Report Generation	January/February
Department Admin Initial Review	March/April
PI Certification/Final Dept Admin Review	April/May
Grace Period for cost transfers and commitment changes	May/June

 

Spring Semester

Activity	Timeframe
Report Generation	July/August
Department Admin Initial Review	August/September
PI Certification/Final Dept Admin Review	September/October
Grace Period for cost transfers and commitment changes	October/November

 

Summer Semester

Activity	Timeframe
Report Generation	September/October
Department Admin Initial Review	October/November
PI Certification/Final Dept Admin Review	November/December
Grace Period for cost transfers and commitment changes	December/January

 

Commitments of effort that are promised to a sponsor (as part of the proposal) for principal investigators, co-principal investigators and key personnel are entered, tracked and available for review by faculty and departmental staff via the Effort Reporting & Commitments (ERC) application.

This application allows for:

• Changes to commitments to be submitted within the ERC application by using the Commitment Change Form.
• Commitments entered for cost share to be included as part of the calculated effort amount in the new system generated effort reports.
• Effort commitments that were originally proposed as being paid by a sponsored award, but was not, to continue to be listed on the effort report with a calculated effort of zero (0) as reminder of the commitment to the project.
• All paid and cost shared commitments to be used for post-certification validation of individual effort reports.

Academic Year 2025-2026

	Fall Report	Spring Report	Summer Report
All employees except those with 10 month appointments
Period	Late August – Early January	Early January – Mid May	Mid May – Late August
Pay Periods	9.8	9.7	6.5
Dates	8/23/2025 – 1/7/2026	1/8/2026 – 5/22/2026	5/23/2026 – 8/22/2026
Employees with 10 month appointments
Period	Late August – Early January	Early January – Late June	Late June – Late August
Pay Periods	9.8	11.8	4.4
Dates	8/23/2025 – 1/7/2026	1/8/2026 – 6/22/2026	6/23/2026 – 8/22/2026

Academic Year 2024-2025

	Fall Report	Spring Report	Summer Report
All employees except those with 10 month appointments
Period	Late August – Early January	Early January – Mid May	Mid May – Late August
Pay Periods	9.8	9.8	6.6
Dates	8/23/2024 – 1/6/2025	1/7/2025 – 5/22/2025	5/23/2025 – 8/22/2025
Employees with 10 month appointments
Period	Late August – Early January	Early January – Late June	Late June – Late August
Pay Periods	9.8	12.0	4.4
Dates	8/23/2024 – 1/6/2025	1/7/2025 – 6/22/2025	6/23/2025 – 8/22/2025

Click on the academic year to show the calendar

Academic Year 2023-2024

	Fall Report	Spring Report	Summer Report
All employees except those with 10 month appointments
Period	Late August – Early January	Early January – Mid May	Mid May – Late August
Pay Periods	9.8	9.8	6.6
Dates	8/23/2023 – 1/6/2024	1/7/2024 – 5/22/2024	5/23/2024 – 8/22/2024
Employees with 10 month appointments
Period	Late August – Early January	Early January – Late June	Late June – Late August
Pay Periods	9.8	12.0	4.4
Dates	8/23/2023 – 1/6/2024	1/7/2024 – 6/22/2024	6/23/2024 – 8/22/2024

Academic Year 2022-2023

	Fall Report	Spring Report	Summer Report
All employees except those with 10 month appointments
Period	Late August – Early January	Early January – Mid May	Mid May – Late August
Pay Periods	9.8	9.7	6.6
Dates	8/23/2022 – 1/5/2023	1/6/2023 – 5/22/2023	5/23/2023 – 8/22/2023
Employees with 10 month appointments
Period	Late August – Early January	Early January – Late June	Late June – Late August
Pay Periods	9.8	12.0	4.3
Dates	8/23/2022 – 1/5/2023	1/6/2023 – 6/22/2023	6/23/2023 – 8/22/2023

Academic Year 2021-2022

	Fall Report	Spring Report	Summer Report
All employees except those with 10 month appointments
Period	Late August – Early January	Early January – Mid May	Mid May – Late August
Pay Periods	9.8	9.7	6.6
Dates	8/23/2021 – 1/5/2022	1/6/2022 – 5/22/2022	5/23/2022 – 8/22/2022
Employees with 10 month appointments
Period	Late August – Early January	Early January – Late June	Late June – Late August
Pay Periods	9.8	12.0	4.3
Dates	8/23/2021 – 1/5/2022	1/6/2022 – 6/22/2022	6/23/2022 – 8/22/2022

Academic Year 2020-2021

	Fall Report	Spring Report	Summer Report
All employees except those with 10 month appointments
Period	Late August – Early January	Early January – Mid May	Mid May – Late August
Pay Periods	9.8	9.7	6.5
Dates	8/23/2020 – 1/6/2021	1/7/2021 – 5/22/2021	5/23/2021 – 8/22/2021
Employees with 10 month appointments
Period	Late August – Early January	Early January – Late June	Late June – Late August
Pay Periods	9.8	11.9	4.3
Dates	8/23/2020 – 1/6/2021	1/7/2021 – 6/22/2021	6/23/2021 – 8/22/2021

Academic Year 2019-2020

	Fall Report	Spring Report	Summer Report
All employees except those with 10 month appointments
Period	Late August – Early January	Early January – Mid May	Mid May – Late August
Pay Periods	9.8	9.7	6.6
Dates	8/23/2019 – 1/7/2020	1/8/2020 – 5/22/2020	5/23/2020 – 8/22/2020
Employees with 10 month appointments
Period	Late August – Early January	Early January – Late June	Late June – Late August
Pay Periods	9.8	12.0	4.3
Dates	8/23/2019 – 1/7/2020	1/8/2020 – 6/22/2020	6/23/2020 – 8/22/2020

Academic Year 2018-2019

	Fall Report	Spring Report	Summer Report
All employees except those with 10 month appointments
Period	Late August – Early January	Early January – Mid May	Mid May – Late August
Pay Periods	9.8	9.7	6.6
Dates	8/23/2018 – 1/7/2019	1/8/2019 – 5/22/2019	5/23/2019 – 8/22/2019
Employees with 10 month appointments
Period	Late August – Early January	Early January – Late June	Late June – Late August
Pay Periods	9.8	12.0	4.3
Dates	8/23/2018 – 1/7/2019	1/8/2019 – 6/22/2019	6/23/2019 – 8/22/2019

Academic Year 2017-2018

	Fall Report	Spring Report	Summer Report
All employees except those with 10 month appointments
Period	Late August – Early January	Early January – Mid May	Mid May – Late August
Pay Periods	9.8	9.7	6.6
Dates	8/23/2017 – 1/5/2018	1/6/2018 – 5/22/2018	5/23/2018 – 8/22/2018
Employees with 10 month appointments
Period	Late August – Early January	Early January – Late June	Late June – Late August
Pay Periods	9.8	12.0	4.3
Dates	8/23/2017 – 1/5/2018	1/6/2018 – 6/22/2018	6/23/2018 – 8/22/2018

Academic Year 2016-2017

	Fall Report	Spring Report	Summer Report
All employees except those with 10 month appointments
Period	Late August – Early January	Early January – Mid May	Mid May – Late August
Pay Periods	9.8	9.7	6.6
Dates	8/23/2016 – 1/5/2017	1/6/2017 – 5/22/2017	5/23/2017 – 8/22/2017
Employees with 10 month appointments
Period	Late August – Early January	Early January – Late June	Late June – Late August
Pay Periods	9.8	12.0	4.3
Dates	8/23/2016 – 1/5/2017	1/6/2017 – 6/22/2017	6/23/2017 – 8/22/2017

Academic Year 2015-2016

	Fall Report	Spring Report	Summer Report
All employees except those with 10 month appointments
Period	Late August – Early January	Early January – Mid May	Mid May – Late August
Pay Periods	10	9.5	6.7
Dates	8/21/2015 – 1/7/2016	1/8/2016 – 5/19/2016	5/20/2016 – 8/22/2016
Employees with 10 month appointments
Period	Late August – Early January	Early January – Late June	Late June – Late August
Pay Periods	10	12	4.2
Dates	8/21/2015 – 1/7/2016	1/8/2016 – 6/23/2016	6/24/2016 – 8/22/2016

What is Effort Reporting?

Effort reporting is the University’s method of verifying that the salaries (and corresponding fringe benefits) charged to, or cost shared for, a sponsored award reasonably reflects the activity for which the employee is compensated. It also serves as a method to certify that the level of effort promised, or committed, to the sponsor was met.

Effort is defined as the portion of time spent on a particular activity, expressed as a percentage of the individual’s total activity for the university. University effort includes all activities for which an employee is compensated and includes research, instruction, other sponsored activities, administration, non-sponsored/departmental research, university service, proposal preparation and clinical activities. For the purpose of effort reporting and certification, ‘university effort’ totals 100%, regardless of the number of hours worked or the individual’s appointment percentage.

The University’s Effort reporting process satisfies the federal government’s requirement under 2 CFR Part 200 (Uniform Administrative Requirements, Cost Principles and Audit Requirements for Federal Awards) section 430 – Standards for Documentation of Personal expenses that charges to Federal awards for salaries and wages must be based on records that accurately reflect the work performed.

 

Quick link to: Effort Reporting & Commitments (ERC) System