Written business rules
Each interpretation call, the reasoning behind it, and the clause it rests on. The source of truth that didn't exist before.
Most start with a scoped review — a fixed piece of work with a clear end point. Each phase ends with a deliverable and a decision, so you're never committed past the next agreed piece.
What the system is actually doing, tested against what your agreements and awards require — across every award, agreement and state in scope.
Typical duration: 4–8 weeks. Data quality and the number of legacy systems drive most of the variance.
Entitlements rebuilt across the agreed lookback, against a written business rule signed off before anyone opens a file.
Scoped by: how many employees, how many agreements, and how far back.
Calculating what's owed is one project. Paying it out is another — and it's the one that usually gets underestimated.
Delivered as: a full project plan with comms, escalation paths and a reconciled payment file.
If the configuration that caused it stays as it is, you're back here in three years with a bigger number. This is the part that closes it out.
You keep: the tools, the workings and the methodology. No ongoing licence.
Every engagement leaves the same artefacts. Yours to keep, yours to defend, yours to run without us.
Each interpretation call, the reasoning behind it, and the clause it rests on. The source of truth that didn't exist before.
Every assumption, who approved it and when. The document that answers "why did you do it that way?"
Built in your environment and documented so your team can run, audit and extend it.
Findings by cohort, entitlement and period — with the working shown, not just the totals.
Sequenced rollout across current staff, former staff and estates, with verification and tax treatment.
What people are told, when and by whom — drafted for employees about to receive unexpected money.
It's the right time. A scoped review costs a fraction of a full remediation and often narrows the problem considerably — sometimes it rules things out entirely. Coming to us with a suspicion is far better than coming to us with a regulator's letter.
That's a decision, not a default, and it's made with you and your legal advisers before any calculation runs. Limitation periods, record availability, and whether there's a point where balances can be evidenced as correct all feed into it. Whatever's agreed goes into the methodology paper with the reasoning attached.
The opposite. Your team knows things no external consultant will, so we work alongside them — but we carry the calculation load, the project management and the documentation. The point is that BAU keeps running while the remediation gets done properly.
It stays in your environment. Everything is built and run inside your systems and infrastructure — nothing uploaded to external platforms or processed offshore. You keep the tools, the workings and the documentation when we're finished.
No. We'll agree the right build based on who's actually using it day to day and what your environment supports. Sometimes that's Excel; often it's something better suited to the people running it each fortnight.
It depends on headcount, how many awards and agreements are in play, and how far back we're going. Work is scoped in phases with defined deliverables, so you're never committed beyond the next agreed piece. Ask and you'll get a straight answer rather than a range.
A suspicion, a known gap, or a project already underway and drifting. First conversation, no obligation.