There's no capacity
BAU doesn't pause for six months. Something urgent always lands first, and the project keeps getting pushed.
Reviews, historical calculations, back-payments and the documentation behind them — handled end to end, so the project keeps moving without your people being pulled off everything else.
Multiple awards. Multiple agreements. Multiple states. That's the work.
We work with complex, multi-agreement workforces:
Exposure keeps accruing while the project is being scoped. Records get harder to reach. People leave. The three things below are what turn a six-month job into a two-year one.
BAU doesn't pause for six months. Something urgent always lands first, and the project keeps getting pushed.
Someone made a call during an implementation or an EA rollover. It's run quietly ever since, slightly out of step with what the agreement actually says.
Without a written business rule, every calculation is an argument waiting to happen — usually eighteen months after the fact.
Take them in order, or pick up wherever you're already stuck.
What your payroll actually does, checked against what your agreements and awards require — including the parts that turn out to be fine.
Entitlements rebuilt across the agreed lookback, to a methodology signed off before anyone opens a file.
Getting money to a casual who left in 2019 is a harder project than working out what they're owed.
Calculators your team runs each fortnight, plus the config fixes that close the original fault.
Not because the big firms can't do it. Because of what it costs, how long it takes, and who ends up on the engagement.
| Big 4 firm | Sunday Advisory | |
|---|---|---|
| Cost | Partner rates plus the overhead behind them. Scope tends to expand. | Fixed by phase. You're never committed past the next agreed piece. |
| Timeline | Mobilisation, onboarding, internal review gates. Months before real work starts. | Scoped in weeks. The people scoping it are the people doing it. |
| Who's on it | You meet the partner. You get the grad. | The person who scopes it presents the final numbers. |
| The build | A methodology lifted from a firm framework. | Built around your agreements, in your systems. |
| Your data | Frequently extracted to firm environments or offshore delivery centres. | Never leaves your environment. |
| Afterwards | A report, and the knowledge walks out the door. | Calculators, workings and documentation your team keeps running. |
Same sequence every time, whatever the entitlement and whatever the system.
Your agreements, systems and data quality — and an honest read on where the exposure sits. Before any fee proposal.
Lookback, interpretation calls and assumptions, documented and signed off with you and your advisers.
Built to that spec inside your environment, then tested with your team against cases they already know the answer to.
Results presented, payments run, tools and documentation handed across for your team to own.
Write it as though the Ombudsman will read it — because on some engagement, some day, they will.
The house rule
Tell us what you're seeing — a suspicion, a known gap, or a project already underway that's drifting. We'll be honest about whether it warrants an engagement.