Enterprise agreements · For consultants

The BOOT Doesn't Stop at Approval

For consultants advising on enterprise agreements: whether the Better Off Overall Test can be proven — for every employee, across the patterns of work that actually eventuate, for the life of the agreement — is largely decided by the client's software, long before it is decided by the Commission.

7 min read

Who this is for. When you help a client negotiate and lodge an enterprise agreement, the Better Off Overall Test is the gate. But passing it once, on a model roster, is not the same as being able to prove it holds — for every employee, across the rosters that actually eventuate, for the term of the agreement. That capability is set, in large part, by the software the client runs. This note is for consultants weighing how a client's system choice supports — or quietly undermines — the advice they give.


What the BOOT actually tests

Under section 193 of the Fair Work Act 2009, the Fair Work Commission must be satisfied that each award-covered employee — and each reasonably foreseeable employee — would be better off overall under the agreement than under the relevant modern award. It is a global assessment: more-beneficial terms are weighed against less-beneficial ones, not compared line by line.

Amendments in force since 2023 sharpened the emphasis. The Commission is directed to consider the views of the parties, and — critically — to assess the agreement against the reasonably foreseeable patterns and kinds of work. The agreement can be amended to resolve concerns, and the BOOT can be reconsidered on application during the term where patterns of work were not reasonably foreseeable when it was approved.

"Reasonably foreseeable patterns of work" is the phrase that turns the BOOT from a one-off arithmetic exercise at lodgement into an ongoing evidentiary one across the life of the agreement.


The BOOT is a moving line, not a lodgement hurdle

The margin by which an agreement beats the award is not fixed at approval. Three forces erode it afterwards:

  • The award moves. The modern award is a moving benchmark — annual wage review increases, penalty and allowance changes, classification updates. Each can narrow or close the gap the agreement relied on.
  • Patterns of work drift. The test is applied to the patterns foreseeable at the time. If actual rostering shifts — more weekend or night work, more overtime, different shift lengths — individual employees can fall below the award-equivalent even though the agreement was properly approved.
  • New roles appear. Employees engaged in arrangements not contemplated at approval may sit outside the original assessment entirely.

An agreement that passed comfortably in year one can be underwater for a cohort of employees by year three — and nothing in a standard payroll run will say so.

BOOT margin at approval Agreement pay Modern award — the benchmark, moves up each year ↑ underwater for a cohort Approval Year 1 Year 2 Year 3 PAY PER PERIOD ↑
The margin at approval is not fixed: as the award benchmark rises, it narrows — and can cross into underwater over the agreement's life.

Why this is a software decision, not only a legal one

A consultant can model the BOOT well in a spreadsheet at lodgement. What no spreadsheet can do is prove it held every fortnight for three years across the rosters actually worked. That is a systems question, and the answer is usually already decided by the client's stack:

  • Payroll configured only to the agreement computes agreement pay — and nothing else. It has no representation of what the modern award would have paid the same person for the same hours. There is nothing to compare against, so there is no BOOT signal at all.
  • When rostering, time capture and payroll sit in separate systems, the actual patterns of work — the very thing the test now turns on — are never assembled in one place to be assessed.
  • When award and agreement rules are not versioned, a change to either cannot be re-tested against history to see who moved below the line.

Your advice is only as durable as the client's ability to keep testing it. The software choice sets that ceiling — often before you are engaged.


What to look for in a client's stack

When advising on, or being asked to bless, a client's system, these are the BOOT-relevant questions:

  1. Dual model. Does it hold both the modern award and the enterprise agreement, and compute pay under each for the same hours?
  2. Comparison on actual work. Can it compare agreement pay to award-equivalent, per employee and per pay period, on the rosters actually worked — not a sample?
  3. Foreseeable-patterns modelling. Can it run that comparison across the range of rosters reasonably foreseeable, to support the assessment at lodgement?
  4. Versioned rules. Are the award and agreement encoded as versioned rule sets, so a variation to either can be re-tested against prior periods?
  5. Independence from payroll. Is the comparison computed independently of the payroll engine? A check that inherits payroll's configuration inherits its assumptions and cannot contradict it.
  6. Per-employee evidence. Can it produce, for any employee and period, the two figures, the clauses behind them, and the margin — without reconstruction?

How a consultant puts this to work

WhenWhat the software makes possible
At lodgementModel the agreement against the award across the reasonably foreseeable patterns of work, and put the comparison — not merely an assertion — in front of the Commission.
Across the termMonitor the BOOT margin each cycle as rosters and awards move; flag cohorts drifting toward the line before an employee or the regulator does.
On variationWhen the award is varied or the agreement changed, re-test against history to quantify who is affected and by how much.
As a serviceThe same capability turns a one-off lodgement into a standing BOOT-assurance relationship — your interpretations, maintained and evidenced, on the client's system.

What to require of any solution

Whatever system a client runs, we suggest these be treated as non-negotiable for BOOT durability:

  1. Both benchmarks, side by side. The system computes award-equivalent pay and agreement pay for the same hours.
  2. Coverage is complete, not sampled. Every award-covered employee, every cycle.
  3. Rules are versioned and citable. Every comparison states the award and agreement clause and rule version behind each figure.
  4. Validation is independent of payroll. A comparison that shares payroll's configuration reproduces payroll's assumptions.
  5. Evidence is retained automatically. The two figures, the margin, the clauses — per employee, per period, retrievable without reconstruction.
  6. Interpretations stay portable. Where you encode a client's interpretation, ownership and portability should be explicit.

Prepared for consultants advising on enterprise agreements. General information only and not legal advice; the application of the Better Off Overall Test depends on the specific award, agreement and circumstances.

See the two figures, side by side

Smartta computes award-equivalent pay alongside agreement pay for the same hours — per worker, per cycle, with the clause and the margin attached. See the comparison, or explore how the award engine works.