All Collections
Adapt Training Articles
Temp Shift
Example of creating a Temp Shift Job, with various Shifts and Rates using a Weekly Rate Time Definition.
Example of creating a Temp Shift Job, with various Shifts and Rates using a Weekly Rate Time Definition.

An example of a Client scenario for setting up a temp shift role, shifts and rates using a Weekly RTD in Adapt.

Written by Jackie Read
Updated over a week ago

Example 1 -  A Client has a Web Developer role with the following shifts and rates of pay:

  • Monday to Friday up to 39 hours (£8.50 per hour Basic, charge rate £12)

  • Overtime Monday to Friday > 39 hours = time and a half (£8.50 x 1.5 per hour, charge rate £20) 

In this example, as workers are paid overtime rates after a certain number of hours are worked in a week, we will use a Weekly RTD.

To create the role and its shifts and rates of pay, users should take the following steps:

Step 1. Create a Client framework 

We need to set up a Client Framework to hold our rates for the Web Developer role, and any other related roles. We will call it ‘Web Developers’:

Step 2. Create a Rate Matrix

From the Rates page of the Framework record, use the Add/Update Rates button and select the Job Category of ‘Web Developer’ to name the matrix.

Create the 2 different rates of pay/charge using different Rate Types. Here we have used Basic, and O/T 1 but additional Rate Types can be set up and called whatever a Client wants (this is done by the system administrator):

Step 3. Create the RTD at Framework level. 

As these rates apply after a certain number of hours are worked in a week, we need to use a Weekly Hours Rate Time Definition. 

As it is a Client framework we can set the RTD on the framework record, thereby enabling the rates to be used by multiple Clients and the RTD to be copied to multiple Clients. From the Framework record for ‘Web Developers’, navigate to the Rate Time Definition page.

We need to define the range of total weekly hours that apply to each Rate Type we have set up. Navigate to the Weekly Hours Rate Time Definitions section and use Add/Update Weekly Rate Time to create. Here we have set up the 2 Rate Types already defined – Basic and O/T1:

What we are saying here is that the ‘Basic’ rate will apply to the Web Developer Job when a Candidate works 39 hours or less a week and the O/T 1 rate will apply to any hours over 39.

Step 4. Link the Client to the Framework.

From the Framework Summary page, any Clients using this Framework can be linked. Use the Link Client button, and search and select the Client in the Client field:

Ensure the ‘Apply Rate Time Definition’ box is ticked, to ensure the RTD is copied to the Client record, then confirm:

This now means the Client ‘Gordon Edwards’ can access the rates called ‘Web Developer’ that we have set up in the Framework called ‘Web Developers’.

Step 5. Create Temp Shift job

We are now ready to create the Job using all the information we have set up. Navigate to the Contact record on the Client ‘Gordon Edwards’ to create the Job:

Choose Temp Shift Job and complete the details:

  1. Use the same Job Category of ‘Web Developer’ to be able to pull in the rates. 

  2. Ensure the Rate Time Definition Type is set to ‘Weekly Hours’ (as this is what we set up), 

  3. Select ‘Client Specific rates’ (as we have set up a Client Framework). 

  4. Finally select the Framework ‘Web Developers’:

Input the Primary Job Category and any other information required, before clicking Next. The rates from your Web Developer Rate Matrix will now be presented for adjustment or confirmation:

Click Confirm to create the Job.

Step 6. Create Shifts

From the Job record, Shift Info page, use ‘Add Shift Range’ to set up the shifts. In this example I am setting up 3 days of Shifts from 9-5pm:

Click confirm and the shifts will be created, showing they are using the Rate Matrix of ‘Web Developer’:

If you click into one of the shifts, you can see the ‘Basic’ rate is being used as the total shifts for that week are less than 39 hours:

Step 7. Shifts can now be filled in the usual way.

Did this answer your question?