Fields

Date:

The date that a requirement starts.

Normally you would leave this field blank and the Requirement Tour will manage the date.

If you want to add a new requirement that starts from a certain date that is different to the requirement tour date, specify it 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:

To associate a reason code to a requirement, if required. 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 that 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, then the rank of the previous instance of the allocation is retained - even if it was reset.