On the right hand side of the AWR report is a column titled Week. This shows the current number of qualifying weeks. Clicking on the number opens the AWR Work History page.
Any week were the contractor has worked in a particular role for a particular client is a qualifying week. This includes weeks worked under a different placement reference. Once there are 12 qualifying weeks the contractor becomes subject to the AWR regulations. There can be gaps in the worked weeks but after a gap of 6 consecutive weeks or more the count is reset to 0 and starts again.
Whenever a timesheet is approved in InTime it automatically registers a qualifying week. In some cases you may need to register working weeks that are not accounted for with timesheets in InTime. This could be if you are starting to use InTime for a placement that started some time ago. You can do this via the AWR Work History page.
From this screen you can select and update the worked status of previous weeks. Maternity leave also counts as a qualifying week.
Work History Bulk Upload
There is also a facility to bulk upload work history which is accessed under the Batch - Upload AWR Work History menu. From this screen you can select an upload a CSV file which must contain data in the following format:
Placement ref, Date, Number of weeks, Type (optional)
Example:
place_123, 01/06/2016, 6
place_456, 24/05/2016, 4, NOT WORKED
The placement must already exist. Any existing worked weeks created from timesheets will not be affected but manually entered work history will be overridden.
The Type field is optional, if it is not supplied the week will be set as 'WORKED'. Accepted week Types are:
WORKED
HOLIDAY
SICKNESS
MATERNITY
JURY
STRIKE
SHUTDOWN
NOT_WORKED
By default the system checks the work history for the entire length of the placement and flags it as low risk if a number of weeks are unaccounted for. You can configure the system to ignore the work history prior to a set date in the AWR Configuration screen. This is particularly useful when starting to use InTime so you can configure it to your go-live date.