Timesheet Period Generation

Timesheet periods must be defined before Team Members will be able to submit a timesheet.  Therefore, we recommend generating timesheet periods well into the future, typically a year at a time, to ensure that there are no interruptions to the timesheet process in your organization. 

Each timesheet period should be clearly identified with a meaningful label to make it easy for both Team Members and Timesheet Managers to ensure they are working with the appropriate timesheet.  While each organization will have its own naming standards, we recommend something like YYYY – Timesheet Period 99 or Timesheet Period Start Date – Finish Date.

While bulk generation of timesheet periods is the typical process, you can create individual timesheet periods as needed.

And finally, you will most likely want to close old timesheet periods to ensure that historical timesheets are not accidentally changed.  Timesheet periods should be closed based on organizational timesheet policies and procedures, but we find this is typically done quarterly, though some organizations lock timesheet periods monthly before critical organizational reports are produced.

_{Disclaimer: Some images in the instructional video and text instructions contained herein may appear different from (or not available) in your organization’s Sensei IQ instance due to specific custom configurations and/or continuous solution updates. Ensure that you are already an enabled user in the Sensei.IQ for Project application and check out the What’s New page. Contact your system administrator for any assistance.}