Skip to main content

Customise Roster Validations

Customise how staff can be rostered with roster validations

Updated this week

Ensure you and your managers are rostering compliant shifts based on your business and award requirements with Tanda’s roster validation feature.

Customise the values, and choose to warn managers or block publishing of the shifts when certain validations have been breached.


Validations on the Roster

When roster validations are enabled, they'll appear on a shift with an orange or red icon:

  • Orange is a warning that a validation has been breached, but shifts can still be published

  • Red shows that a shift validation is breached, and cannot be published

Clicking on the icons that appear will show the validation rules the shift has breached, as well as the recommended rostering practices to resolve the errors.

When a shift has breached a custom validation rule set, the relevant set name will be included in the description (in the example above, the Casual validations rule set has been breached).

Block Roster Publishing

Certain validations can be configured to prevent shifts from being published until validation errors have been resolved. This blocking setting applies to all users, irrespective of permission levels.

Should a user attempt to publish a roster breaching the validations, the Publish button will be disabled until the errors are resolved. All other shifts can be published by deselecting the affected Teams or Staff.


Validation Toggles

Ensure the roster validations setting (Settings > All Settings > Roster Validations) has been toggled:

Customise All Staff validations to determine which should warn managers, and which should block roster publishing.

The Blocking toggle cannot be switched on without the Enabled toggle also being on.

These validations, including where the related value is configured in your account, are explained below:

Validation name

Description

Where to configure

Shift Clash

Triggered when two shifts are overlapping

Leave Clash

Triggered when a shift overlaps a pending or approved leave

Unavailability Clash

Triggered when a shift is rostered with overlapping pending or approved leave

RDO Clash

A shift is overlapping with a rostered day off

Preferred Hours Under

Total hours rostered for a week are less than half the total preferred hours by an employee

Preferred weekly hours for rostering field under the Pay Configuration tab in employee profiles

Preferred Hours Over

Total hours rostered for a week exceed the total preferred hours by an employee

Preferred weekly hours for rostering field under the Pay Configuration tab in employee profiles

Qualification Invalid

A qualification is expired, pending approval, not currently effective, or has had maximum hours breached

Qualifications tab in staff profiles

Overtime

The rostered shift will incur an overtime rate or penalty

Applicable award rules and overtime rates for each employee found in 'Award Rules' on staff profiles. Additionally, click See Costs on the rostered shift to see which specific rules are applying

Under Rostered

Total hours rostered do not meet an employee's contracted weekly hours

Based on the value under Employee Profile > Pay Conditions > Edit current pay conditions > Contracted weekly hours:

Missing Regular Hours of Work

Staff that have permanent part-time shift acceptance applying do not have regular hours configured

Add agreed hours of work in the Regular hours of work field of employee profiles

Mismatching Regular Hours of Work

Rostered shifts do not match the regular hours configured on staff profiles

Based on values in the Regular hours of work field of employee profiles

Breaks Don't Match Automatic Break Rules

When automatic break rules have been enabled in your account, any manual breaks that do not match will be flagged

Configure break rules through Settings > All Settings > Shift Breaks

Consecutive Days Off

An employee doesn't have two consecutive days off in a week (or similar)


Additional Validations

On top of the above toggles, roster validations can be based on specific values, and configured to apply to individual staff.

Default Rule Set

A default validation rule set will apply to all staff not covered by a custom rule set.

Here, you can enter values for:

  • Maximum shift lengths (in hours)

  • Minimum shift lengths (in hours)

  • Minimum hours between shifts (in hours)

  • Earliest start time for a shift

  • Latest finish time for a shift

  • Maximum number of shifts per week

  • Maximum number of hours per week

  • Maximum number of shifts per day

  • Maximum span of hours per day (for back-to-back/multiple shifts in one day)

  • Maximum hours in a day

Set these validations to block roster publishing with the toggle underneath.


Custom Rule Sets

You may wish to apply certain validations to only a few staff based on employment type, age, mutual agreements, and other factors.

When creating a new validation rule set, you'll need to enter:

  • Name of the validation

  • Who it applies to

  • When it applies

  • Validations they should receive

  • Any overtime conditions that should be blocking

Who it Applies To

For custom validation rule sets, you can restrict who it applies to based on:

  • Minimum and maximum ages

  • Classification tags

  • Locations they work at

Hover over the x employees match these filters box to see which staff will have these rules applied.

When it Applies

Applicable days or periods that the rules should apply can be based on:

  • Date ranges (Note: date ranges must apply to the full week selected)

  • Days of the week

Leaving this section empty will have the validation rules apply to the relevant staff at all times.

Validations They Should Receive

Value-based validations are split into two sections - shift validations that look at the individual shifts, and roster validations that look at an entire roster week. Values can be entered for:

  • Maximum shift lengths (in hours)

  • Minimum shift lengths (in hours)

  • Minimum hours between shifts (in hours)

  • Earliest start time for a shift

  • Latest finish time for a shift

  • Maximum number of shifts per week

  • Maximum number of hours per week

  • Maximum number of shifts per day

  • Maximum span of hours per day (for back-to-back/multiple shifts in one day)

  • Maximum hours in a day

Breaches to these conditions can be set to block publishing with the toggle below.

Blocking Overtime Conditions

Customise which overtime conditions or penalty rates, based on your managed award template, should block roster publishing.

Blocking can be set for the following overtime conditions:

  • After certain hours per day worked

  • After a certain span of hours per day

  • After certain hours worked in a period

  • Beyond set fixed hours for part-time staff

  • Minimum rostered work hours per day

  • Minimum rostered work hours per week

  • After certain days worked in a week

  • After certain days worked in the second week

  • After certain days worked in a period

  • After consecutive days worked (in an overtime period)

  • Rest between shifts

  • Minimum break during shifts

These conditions are based on the values against each managed award template that the applicable staff for the rule set are under. View the values of specific award templates through Compliance > Manage next to the template > Edit in the Ordinary Business Hours or Maximum Shift Length boxes.


Creating Custom Roster Validation Rules

Natural Language Roster Validations let you write roster rules in plain English. The system uses AI to interpret and convert your rules into standardised validations, which are automatically checked whenever a roster is built, flagging violations before publishing.

To create custom Roster Validation Rules, navigate to Settings > All Settings > Rosters > Natural Language Validation Rules.

You can create roster rules that will apply organisation-wide or just for specific locations.

When creating rules, be as specific as possible, since the AI does best with measurable constraints (e.g., instead of "roster enough staff during lunch rush on Saturdays", a better written rule would be "roster at least 4 FOH staff during 11:30am-1:30pm on Saturdays"). Open the Example Rules dropdown to see different types of validations that can be configured.

Write roster validations in natural, plain English, with each rule on a new line.

Rules that have successfully been interpreted will be listed under Active Rules:


Common Use Cases (Roster Validations)

Wage Comparison and Outer Limits Validations

For organisations using Wage Comparison, additional rule types are available that link roster validation directly to Wage Compare costing.

Wage Compare Top-Up Warnings flag employees whose rostered shifts (when costed against your wage comparison scenario) would result in a top-up payment, where the comparison cost exceeds the standard award cost.

For example:

"When rostered schedules would trigger a wage compare top-up".

When triggered, the projected top-up amount is shown against the relevant shifts for that employee.

Outer Limits Breach warnings alert you when an employee’s penalty or overtime hours exceed the outer limits thresholds set in their wage comparison settings.

For example:

"When penalty hours exceed outer limits thresholds" or "When overtime hours exceed outer limits thresholds".

If a threshold is exceeded, the rule will show how much it has been exceeded by, in both hours and dollar value.

Exceeding Budgets

When Budgets have been configured, you can use custom roster validations to flag when days exceed their budgeted hours. This also allows you to prevent roster publishing if a budget has been exceeded.

You can use rules such as: "Budgeted Hours cannot be exceeded each day" or "Budgeted Hours cannot be exceeded each week" to do so.

The validation will flag at the top of the roster for each day that exceeds the budget:

A warning will also be displayed when attempting to publish the roster:

Did this answer your question?