Notify the PM with a list of tasks for their project as soon as the Timesheet is submitted.  This is a good substitute for PM approval. When a timesheet is submitted, then the PM knows the time entered by person. This is an Auto-start process in Clarity named PM Time Notification - On Timesheet Submission and will be automatically spawned when a Timesheet is submitted. When the process is started it will be seen in the Initiated on the Processes tab. The process status can be monitored from Running to the Completed stage. The Progress when 100% and the Status is Completed, an email would have arrived to the Project Manager with subject: “Resource <Name> has entered the following time on your Investment(s) for the week starting <Timesheet Start Date> ”. This email will list the Investments managed by the PM where task was entered by the Resource submitting the timesheet.  Each PM would get a separate notification. PM for project X notified, and PM for project Y gets notified in another email. Therefore, one timesheet may spawn out multiple emails. But, if both the Projects have the Same PM, then only a single email gets sent out. “Opt-out Timesheet Notifications" checkbox is provided on the Project for PM’s who do not want to get notified on those projects.

This Process sends an email to every Action Item Assignee where the Due Date/Time has passed and the Status is either Open, or In Progress.  Users may want to modify this stalker to include Status = Deferred.  In addition, the Resource Manager for the Assignee receives a copy of the email. In order to generate emails, the SMTP gateway must be up and running and Resources must have a valid email address.

The Timesheet Smoothing Process Workflow kicks-off when an individual timesheet is Submitted.  It splits each transaction on the timesheet when total timesheet actuals exceed total weekly availability for the resource.  Total weekly availability is determined by multiplying resource availability rate by the number of workdays in the week.  Non-workdays include weekends, holidays, PTO, and other scheduled days off, as set on the resource calendar.  If timesheet actuals <= total weekly availability, then the timesheet remains unchanged.  But if timesheet actuals > total weekly availability, then the following occurs. Each timesheet transaction is reduced by a calculated percentage that will reduce the total regular hours to equal the total weekly availability.  Then the remaining transaction hours are placed in a “Split” row for that task on that day, with an Input Type Code set based on a process parameter (which parameter can be set within the script action on the process). Note:  If a single day has overtime hours, but the total timesheet actuals <= total weekly availability, no splitting occurs.