FastTrack360 Version 12 Online Help
AWR - Clock Reset From Non Submission of Timesheets V12.31
Description
This Stimulsoft report will allow you to monitor when jobs are about to have its clock reset because there has been no submission of timesheets for the time period specified. The report can be distributed to your Front Office teams to check the status of the missing timesheets.
This report will only output those candidates where monitoring is required.
Report Parameters
The report data can be filtered using the following parameters:
Parameter | Description | Rules |
---|---|---|
Brand | To be able to filter for jobs within a particular brand | Can choose all brands or a particular brand. |
Region | To be able to filter for jobs within a particular region. | Can choose all regions or a particular region. |
Office | To be able to filter for jobs within the offices selected. | Can select multiple offices. Leave blank if all offices are required. Data is restricted to the user’s security data profile when running the report. |
Client Name | To be able to filter for jobs that are for a particular client. | Can be left blank to see all client jobs. Can enter a part client name. A wildcard % is not required to search for the part name. |
Job Ends On or After | To be able to filter on jobs where the job end date is on or after the date entered. This is so jobs that have ended prior to the date are not displayed as they are already ended. | This defaults with today’s date but can be changed. |
Job Active for More Than No. of Weeks | The report is only relevant for those jobs that are greater than the parity weeks. If the job is active for less than the number of weeks entered, these will not appear in the report. As this could be different for a Office or Client, this can be changed where required. | This defaults with 12. An entry must be made to return data. If all jobs are required, enter a value of 0. |
No. of Weeks Since a T/S Received. | To filter for those candidates who have not submitted a timesheet for the number of weeks since they last submitted a timesheet. | This defaults to 4 but can be changed. This is set to 4 as the clock will be reset from week 7 and allows you time to check to see where timesheets are missing. |
Report Date | This is the date to determine the number of weeks from which a timesheet has not been received. | This defaults to today’s date but can be changed. |
Include Week of Report Date | To decide if the count should include the timesheet week that contains the report date. This is needed because it depends at what point in the week the report is run as to whether to include the week that contains the report date or not. | This defaults to No. This means that the count will look back from the previous timesheet week. If Yes is selected, it will consider the week that contains the Report Date that has been entered. |
Report Content
The report content will output the following data:
Column | Comments |
---|---|
Office | The data is grouped under the office the job is assigned. |
Client No. | Â |
Client Name | Â |
Candidate Id | Â |
First Name | Â |
Surname | Â |
Job No. | Â |
Client Job Position | Â |
Position | Â |
Job Start Date | Â |
Job End Date | Â |
Clock Count | This is the latest clock count on the job. |
Office Reset Weeks | If there is a different number of weeks reset applied to the office the job belongs to, it will display the office reset weeks, otherwise it will be blank. |
Last Timesheet | This displays the last timesheet end date that was processed for the job. |
No. of Weeks | This displays the number weeks since the last timesheet date to the report date. |
Benefits
Helps manage the AWR process for ensuring timesheets are received before a reset occurs and the payee having their parity rate being reverted back to parity.
Configuration
If you want the report to be distributed to multiple teams, it will be necessary to configure a report schedule.
Related pages
Classification-Public