How the Obligations Stack
Australian rostering obligations come in layers, and confusing the layers is where most employers go wrong.
At the base sits the Fair Work Act 2009 and the National Employment Standards, covering maximum weekly hours, leave and the general protections. The NES applies broadly and is the same for everyone in the national system.
On top sit the Modern Awards, around 120 of them, each with industry-specific rostering rules: minimum engagements, penalty rates, breaks, notice of change, allowances.
Above that, where one exists, sits an enterprise agreement, which displaces the award provided it passes the better off overall test.
The practical consequence is that most of the rules people call Fair Work requirements are actually award requirements. The NES does not set a minimum shift length. It does not set penalty rates. It does not specify roster change notice. Those all come from your award, which is why the answer to almost every rostering question is which award covers you, and why generic advice is close to useless.
What the Act itself does impose, universally, is record-keeping. That part is the same for everyone, and it is also the part employers most often treat casually.
The Records You Must Keep
The Fair Work Regulations 2009 set out what has to be kept. Records must be retained for seven years, be legible, be in English, and not be false or misleading. They must be made available to a Fair Work Inspector on request, and to the employee.
| Record type | What it must contain |
|---|---|
| Employee details | Name, employment status, whether full-time, part-time or casual, and commencement date |
| Pay | Rate paid, gross and net amounts, and any deductions |
| Hours | Start and finish times where the employee is paid by reference to time worked |
| Overtime | Overtime hours and the rate at which they were paid |
| Loadings and penalties | The nature and amount of any loading, penalty or allowance applied |
| Leave | Leave taken and leave balances |
| Superannuation | Contributions made, amounts and fund |
The row that causes the most trouble is hours. A published roster is not a record of hours worked. It records what was planned, and plans and days diverge constantly through late starts, early finishes, cancellations and overruns. Paying from the roster is paying from an intention, and treating the roster as your time record leaves you with no evidence of what actually happened.
Section 557C, and Why It Changes the Stakes
This is the provision worth knowing by name.
Section 557C of the Fair Work Act 2009 provides that where an employer has failed to keep or produce records they were required to keep, and has no reasonable excuse, the employer bears the burden of disproving an allegation in proceedings about those matters.
Sit with the consequence for a moment, because it inverts the usual intuition. Normally a person alleging underpayment has to establish it. Without records, you are instead required to establish that you paid correctly, about shifts worked possibly years earlier, using evidence you do not have because not having it is the whole problem.
A record-keeping lapse can therefore become a wages liability without anyone ever proving an underpayment occurred. That is why record-keeping is not the administrative afterthought it is usually treated as, and it is the single strongest argument for capturing actual times electronically rather than reconstructing them. A GPS time clock generates the record at the moment of the event; a timesheet written up on Friday afternoon from memory does not.
What Your Award Adds
Award rostering provisions vary substantially, but they tend to cover the same categories. Work through these for your own award rather than assuming.
Minimum engagement. The shortest period an employee must be paid for when they attend. Differs by award and sometimes by classification or stream within an award, which trips up employers who apply one figure across a mixed workforce. Compared across awards in minimum shift lengths in Australia.
Penalty rates. Loadings for evenings, weekends and public holidays, and how casual loading interacts with them. Under SCHADS, for example, permanent employees receive 150% on Saturday, 200% on Sunday and 250% on public holidays, with the 25% casual loading added on top rather than absorbed into the penalty.
Notice of roster change. Many awards set a notice period for changing a regular roster and some require consultation about significant changes to ordinary hours. Short-notice changes can attract compensation under some awards.
Breaks and rest between shifts. Meal and rest breaks within a shift, and minimum rest between the end of one shift and the start of the next. The rest-between-shifts rule is the one rosters breach accidentally, typically through a close followed by an open.
Maximum consecutive days. Several awards limit how many days can be worked without a break.
Allowances. Broken shifts, sleepovers, travel, on-call. These sit outside the hourly rate and are missed more often than penalties because they are not visible on the roster.
On rates specifically: get current percentages from the Fair Work Ombudsman's Pay and Conditions Tool or the award text, not from a blog. The Fair Work Commission adjusts award wages annually, usually effective from the first full pay period on or after 1 July, and any figure published in vendor material has a shelf life. Our sector guides for hospitality, retail and children's services set out the structure, and you should still confirm the numbers for your classifications.
Building Compliance Into the Roster
Compliance handled as a separate task gets done late or not at all. Handled as a property of the rostering process, it mostly takes care of itself.
Cost the roster before publishing. Seeing award-adjusted cost at build time catches both budget problems and misapplied rates while the roster is still changeable.
Capture actual times, not rostered times. This is the record that matters under section 557C.
Log roster changes and when notice was given. If your award attaches consequences to short notice, you need to know what notice you actually gave rather than what you intended to give.
Re-check configuration every July. Rates set last year are wrong this year and no system will warn you.
Know where your enterprise agreement overrides the award. If you have one, it governs, and configuring software to award defaults will produce consistent errors.
A closing caveat worth stating plainly. Software applies the rules you configure. It does not interpret your award, know about your enterprise agreement, or correct a classification entered wrongly at onboarding. It moves the failure point from arithmetic, which machines do reliably, to configuration and judgement, which they do not. That is a substantial improvement and it is not the same thing as compliance, and any vendor suggesting otherwise, including in earlier versions of this article, is overselling. This article is general information rather than legal advice; for your specific circumstances consult the Fair Work Ombudsman or a workplace relations adviser.
Where Compliant Employers Still Get Caught
The employers who end up in trouble are rarely the ones ignoring their obligations. They are usually the ones who got something structurally wrong once and then applied it consistently.
The wrong award. Everything downstream is wrong if this is wrong, and it is not always obvious. Businesses that have changed what they do, a cafe that added catering, a support provider that took on cleaning contracts, sometimes drift across award boundaries without anyone revisiting the question. Check coverage when the business changes, not only when someone is hired.
The wrong classification. A worker entered at the wrong level at onboarding is paid wrongly with perfect consistency for years. Nobody re-examines it because the number has always been that number. Audit classifications periodically, particularly after promotions and changes in duties, since classification usually follows the work rather than the title.
The agreement nobody read. If an enterprise agreement applies, it governs. Configuring your systems to award defaults produces confident, automated, consistent errors. Someone should be able to say which clauses differ from the award.
The July that got missed. Annual wage review changes take effect from the first full pay period on or after 1 July. Configured rates do not update themselves and no system raises an alarm, so this needs a calendar reminder and an owner.
Allowances that never trigger. Broken shifts, travel, sleepovers, on-call. These are invisible on a published roster, which is exactly why they are missed more reliably than penalty rates. If your process depends on a coordinator remembering, it will fail at some rate, and that rate is not zero.
Every one of these shares a shape: a single error applied repeatedly, quietly, at scale. That is also why self-auditing works better than people expect. Take one past fortnight, pick three employees across different employment types, and reconstruct what they should have been paid from the award text. If it reconciles you have real assurance. If it does not, you have found a systematic problem while it is still small, which is the entire point of looking. Sample a weekend fortnight rather than a quiet weekday one, because that is where penalties, allowances and minimum engagements all appear at once.
Frequently Asked Questions
Build the Records as You Roster
Capture actual start and finish times and export award-categorised hours to payroll. Start free for up to 5 staff; time clock and award costing on paid plans.
Start Free - No Credit Card