In this article, I will show you how to create a Working Pattern so that you can support full-time, part-time and condensed-hour employees. A Working Pattern allows you to capture an employee's expected working days and the number of hours they work each morning and/or afternoon.
The name of every working pattern must be unique along with the Working Pattern itself.
If you attempt to create a Working Pattern with a name that already exists, you will receive an alert “The following fields need your attention: Pattern name.”
If you attempt to create a Working Pattern that already exists, you will receive an alert “A working pattern with these details already exists.”
Steps to Create a Working Pattern:
- Go to the Administration Tools menu
- Select Working Patterns from the Administration Tools menu
- Select ‘Add new pattern’ (on this page is a list of any existing working patterns you have set up
- On this page, name the working pattern (this name needs to be unique) and confirm if holidays are classed as working days. Next, select which days an employee works and the hours worked in the AM and/or PM. Once added, it will show the total hours worked for that day in the right-hand column. Continue selecting the days and inputting the hours until the working pattern is completed. You can add additional weeks if you need them. On saving the working pattern, this will automatically default to being on and be listed on the Working Patterns page.
Before setting a Working Pattern, please ensure you have set the Full-time equivalent hours - Sapling - Setting the Full-time equivalent
Turning off a Working Pattern
If you do not want the working pattern to be available to assign to employees, you can toggle the working pattern status to off. If a Working pattern has been toggled off and already assigned to an employee, the working pattern will still be assigned, and all time-off calculations will be based on the assigned working pattern.
To edit an existing working pattern and learn about the impact - Editing a Working Pattern
Comments
0 comments
Article is closed for comments.