Work through your team's pay review over several sittings. It shows the guideline, tracks your budget, flags what needs a reason, and checks for a skew between women and men before you submit.
A pay review is rarely done in one sitting. You start, get pulled away, and come back days later. A spreadsheet does not help much. The guideline sits on another tab, the running budget is a formula you have to trust, and a pattern across the team is easy to miss.
This tool keeps your place. It shows the rule beside each decision, adds up the spend as you go, and never makes the decision for you. You enter every number.
It is "stateful", which means it keeps your work between sittings, so it needs somewhere to keep it. This is the first tool on this site that keeps data, which is why the data check below matters more here than on any other page.
It pairs with use case 08, where the reward team loads what managers submit, and with use case 04, which helps you explain the outcomes afterwards.
This is the real tool, running in your browser on an invented team. Enter some proposals, save your work to a file, and open it again.
Your file is read by your own browser. Nothing is uploaded. Your work is kept only in the file you choose to save.
Five steps from opening your team to submitting it. Press Play, or step through at your own pace.
Each bar shows pay against the reference point. The dark line is 100%.
Open your team. Your reward team gives you a file. It lists each person by ID, with their pay, reference point and rating. No names needed.
The guideline beside each decision. The tool shows the rating, where the pay sits and the range that applies. The box stays empty. You decide the number.
Remaining: $12,098
Budget and flags as you go. The spend adds up as you type. A proposal outside the guideline is flagged, and that person is not done until you write a reason.
Save, and come back. Press Save and the file lands on your computer. Next sitting, open it and carry on from the same place.
All 9 people are done. Review the summary, then submit.
Download submission fileCheck for a skew, then submit. Compare the two averages. A difference is a prompt to look again, not proof of a problem. When everyone is done, download your submission.
All figures in this walkthrough are invented, for illustration only.
You can build your own version with any capable AI assistant your employer allows, for example Microsoft Copilot, Claude or ChatGPT. You describe what you want, it writes the code, and you check the answers.
Build it with invented data, never your real team. Expect a few rounds of "that's not quite right, change X". This one has more rules than most, so spell them out.
Say who will use it, what goes in, and what the manager types. Ask the AI to plan before it builds.
Do not let the AI guess how a pay guideline works. Tell it exactly: how position in range is worked out, where the zones start and stop, what the guideline allows, and what counts as outside it, done and over budget. The table below is invented. Replace it with your own.
A tool that remembers has to keep your work somewhere. There are two common choices. The first is in the browser, on one computer. That is quick to build, but the data sits in the browser where you cannot see it, it does not move to another computer, and on a shared computer it can be left behind for the next person. The second is a file you save and open. You can see it, move it, lock it down and delete it, and nothing is left behind in the browser. This site chose the file. It asks a little more of the manager, and gives the organisation a lot more control.
The fairness check compares the average proposed increase for women and men, with a minimum group size so a small group cannot point to one person. The submission only switches on when everyone is done.
A tool that keeps people's pay needs more testing than most. Ask the AI to help, then check the answers by hand.
A checklist to run yourself:
This page gets more room for the data check than the others. It is the first tool here that keeps data, and the data is each person's pay, rating and the reasons you write about them.
Each team member's pay, rating and the reasons you write. This is the most sensitive data on this site, and it is the first tool here that keeps it.
The tool itself stores nothing and sends nothing. The risk is the file it makes: where you save it, who can open that folder, whether it gets emailed, and whether old copies linger.
Use IDs rather than names. Keep reasons about the role and the work, not health or personal circumstances. When you build your own, give the AI assistant invented data only.
Privacy rules for employee records differ between private employers and government agencies, so check with your privacy officer. Start with the OAIC's guidance on the Australian Privacy Principles and on employment and privacy. General information, not legal advice.
The tool is a single file. Save it anywhere and double-click to open it. Use the sample team file to practise opening a file.
What next: Use case 08: the reward team's review tracker · Back to all use cases