Date

The date that a Requirement starts.
Leave this field blank and the Requirement Tour will manage the date.

If you want to add a new Requirement that starts from a date that is different to the Requirement Tour date, specify a date here.

Shift

The Shift that the Requirement record will use. For example, day shift may require ten staff, whereas night shift may only require three staff.

Reason

Use this field to associate a Reason with a Requirement. For example, Public Holiday.

Position

You can select a Position for the Requirement.

Placement Criteria

The Placement Criteria filters the employees who are suitable for the Allocation. Select an employee query that includes only the employees you want to include in the search.

Placements required

The number of employees needed to fill the Requirement.

Break

The standard unpaid break that employees are entitled to. For example, Lunch.

Frequency

The number of days before a cycle repeats itself. A frequency of '1' repeats daily, while a frequency of '21' is repeated every 21 days.

You do not need to specify the frequency here as this is managed by the Requirement Tour.

Effective end date

The last date before a Requirement becomes redundant.

Rank

This field allows you to set a rank for multiple Allocations generated for a Requirement on the same day.

The Rank controls which shifts on a particular day take priority. For example, when you rank one shift higher than another, PayGlobal will attempt to roster employees for the day to the higher priority shift first.

When you use auto-placement, Allocations for the same day are filled in ascending order of rank. Rank is only used to differentiate between Allocations for the same day.

Note: If you regenerate Allocations using Maintain Allocations, the rank of the previous instance of the Allocation is retained — even if it was reset.