Employment Hero Award Setup: More Than Activate and Use

All blogs & guides

Checked against Employment Hero’s Help Centre, the Fair Work Ombudsman and current award text on 13/08/2026.

The short version

1. Employment Hero’s pre-built awards provide a strong rules engine, but they cannot decide how a particular business classifies, rosters or pays its people.
2. Work Types, Shift Conditions, Tags, pay categories and rule-set periods must match the business before the first live pay run.
3. Unlocking or overriding award rules creates an ongoing maintenance obligation that needs documented tests at every update.

Full detail below.

Employment Hero award setup starts with the pre-built package

Employment Hero award setup starts with substantial work already completed inside the pre-built packages. Current Help Centre pages use different counts for the supported packages, so the live award list is the source of truth. Installing a supported award can create pay-rate templates, pay categories, Work Types, Shift Conditions, Tags and rule sets that would otherwise need to be built by hand. Payd Co is an Employment Hero Certified Partner that maps those rules to the employer’s classifications, rosters and inputs.

It does not know how the business operates. The award text provides legal conditions; the pre-built package translates many of those conditions into payroll logic; the employer still needs to map its people, rosters and working arrangements into that logic. Employment Hero’s award pages tell users to evaluate each package for accuracy, currency and relevance before relying on it.

Six decisions an award package cannot make for you

1. Which award and classification applies

Employment Hero can list classifications and their current rates. It cannot determine which classification matches an employee’s duties or whether another award has coverage.

Job titles are not enough. Two employees called “team leader” can sit at different levels because their responsibilities, qualifications and supervision differ. Payd Co maps the role evidence to the current award before assigning the payroll template. Where coverage or classification is unclear, the employer obtains workplace-relations advice before configuration continues.

2. Which Work Types people will select

Work Types tell the rules engine what kind of work a timesheet line represents. They can identify annual leave, call-backs, higher duties, travel, overtime by agreement or a specific allowance trigger.

The package can provide the options; the business decides which ones are relevant and how employees will know when to use them. A perfect rule attached to a Work Type nobody selects will never run. We remove unused choices, document the live set and test it with the people who enter or approve time.

3. Which Shift Conditions belong on each shift

Shift Conditions add context where one timesheet entry carries more than one condition. This matters when a condition is attached to the shift instead of the employee: a first-aid duty, a broken-shift exception or work in a particular environment.

Roster and time-capture design decides whether that condition reaches payroll. Payd Co maps the source system’s fields and tests the transfer into Employment Hero so the rule is triggered by real data, not only by a test typed directly into payroll.

4. Which Tags describe an employee’s arrangement

Tags switch award variants on and off for groups or individuals. Employment Hero uses them when one rule set needs to handle different arrangements, such as overtime payment versus time off in lieu.

The SCHADS package is a useful example. Employment Hero’s current help page says the correct service Tag is needed for overtime logic, and a Shiftworker Tag is needed for the additional annual-leave entitlement. The rule exists, but it cannot run for an employee who was never tagged.

We maintain an assignment register showing why each Tag applies and add Tag checks to onboarding, role changes and the annual award review.

5. How pay categories map to the business

Awards can create system categories, but the business may already have accounting mappings, allowances, salary arrangements or external timekeeping codes. Those mappings decide what appears on the payslip, what flows to the ledger and which earnings are included in leave, tax and super.

A rate can be correct while the category behind it is wrong. Payd Co reconciles both the employee’s gross result and the category-level output before the rule set is approved.

6. What period and anchor day the rule set uses

The rule-set period does not always match the pay schedule. Employment Hero’s award setup guide gives the example of overtime measured over a four-week cycle even where employees are paid weekly.

The period length and anchor day determine which hours are grouped together. A wrong Sunday or Monday boundary can move overtime into the next calculation without generating an error. We set the award period from the industrial arrangement and roster cycle, then test shifts on both sides of the boundary.

What “activate and use” misses in HIGA and SCHADS

The Hospitality Industry (General) Award and SCHADS Award show why the business mapping matters.

HIGA examples

The current Hospitality Industry (General) Award includes, among other conditions:

• a maximum 12-hour spread for a full-time or part-time employee working split shifts
• split-shift allowances that change with the length of the break
• minimum-break, part-time engagement and annualised-wage controls

The award does not say which employee has a split arrangement, whether a particular gap is a meal break, or whether a salary arrangement and its records meet the clause. Those are business facts that need Work Types, rosters, Tags and written records.

SCHADS examples

SCHADS includes broken shifts, sleepovers, 24-hour care and on-call arrangements. From the first full pay period starting on or after 1 June 2026, sleepover rules changed.

An employer and employee can agree to extend ordinary work around a sleepover to 12 hours for the shift, with no more than eight ordinary hours on either side. Extra work over the applicable ordinary-hours limit is overtime. Work before and after the sleepover is treated as part of the same shift for ordinary-hours and rest-break purposes, while shift allowances are considered separately for each work period.

Employment Hero added Work Types and Shift Conditions for the 12-hour agreement. The rule still needs the agreement, correct service and shiftworker Tags, accurate before-and-after times and a tested roster feed. Payd Co configures those inputs together and keeps the agreement with the payroll evidence.

Unlocking a rule set changes who maintains it

Installed award rules are locked by default. Unlocking exposes the rules for editing and allows a business to disable or customise them. That can be the right answer where the award package does not match a lawful arrangement.

It is also a control change. Employment Hero’s award-management guide warns that:

• locking a customised rule set again reverts it to the default and removes the customisation
• an award update can reset a changed rule-set period
• custom rule sets and disabled rules must be preserved explicitly during an update
• overridden employee rates are not changed by the award-rate update

From those documented behaviours, the practical conclusion is that a customised build needs its own maintenance owner. The vendor can continue to publish the base package, but it cannot know whether a future change should replace, merge with or sit beside the custom logic.

Payd Co records the reason for every custom rule, the award clause it implements and the test cases that prove it. At update time we review the release, preserve the right components and run the tests before activating the new version.

Use Test Rules before a change reaches a pay run

Employment Hero provides Test Rules from the rule-set screen. Use it as a simulator, not as the whole sign-off.

A useful test pack covers normal cases and boundaries, including:

• ordinary weekday hours
• Saturday, Sunday and public-holiday work
• daily and weekly overtime thresholds
• a shift crossing midnight
• a shift crossing the rule-set anchor day
• broken or split shifts and minimum breaks
• each active allowance, Work Type, Shift Condition and Tag
• an annualised salary reconciliation case where relevant

Compare each result with the current award and the business arrangement. Then run a parallel pay cycle using real roster data, because the simulator cannot reveal a missing field in an external time-and-attendance feed.

Award updates need a managed release, not an install click

Employment Hero posts award-package updates and provides dashboard prompts to apply them. The 1 July 2026 changes included updated wage rates and, for some awards, expense-related allowances and rule changes.

The controlled sequence is:

1. finish the last pay run governed by the old rates
2. read both the Fair Work change and Employment Hero’s package notes
3. export or record current customisations, periods, overrides and disabled rules
4. apply the update with the right preservation choices
5. re-check classifications, Tags, templates and employee overrides
6. run Test Rules and a parallel comparison
7. approve the version and retain the evidence

This is the ongoing management case for a Certified Partner. Employment Hero supplies a capable award engine and update stream. Payd Co supplies the business interpretation, controlled configuration and evidence that the changed rule works for the people and rosters it will pay.

Plan labels in Employment Hero’s Help Centre are not fully consistent. Confirm award and feature access against the live account and contract before planning the build.

Does installing an Employment Hero award make payroll compliant?

No. It installs a substantial rules package, but the employer still needs correct coverage, classifications, employee Tags, Work Types, roster inputs, pay-category mappings and tested update controls.

What happens when an Employment Hero award rule set is unlocked?

The rules can be viewed and customised. The business must then preserve and test those customisations during updates; locking the set again can remove the changes and restore the default rules.

Should the award rule-set period match the pay schedule?

Not always. The award or arrangement may measure overtime over a different cycle. Set the period and anchor day to the rule being calculated, then test shifts across that boundary.